From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Emanuel Berg Newsgroups: gmane.emacs.help Subject: Re: Gnus + emacs.stackexchange Date: Fri, 08 May 2015 01:58:23 +0200 Organization: Aioe.org NNTP Server Message-ID: <87vbg4hrds.fsf@debian.uxu> References: <87fv7hoxnd.fsf@debian.uxu> <87mw1luz3o.fsf_-_@debian.uxu> <87a8xjpxdh.fsf@gmail.com> <87ioc61r9c.fsf@debian.uxu> <87twvq82ou.fsf@lifelogs.com> <87pp6d7bb4.fsf@debian.uxu> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1431042919 27363 80.91.229.3 (7 May 2015 23:55:19 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 7 May 2015 23:55:19 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri May 08 01:55:19 2015 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1YqVdN-0006VN-QT for geh-help-gnu-emacs@m.gmane.org; Fri, 08 May 2015 01:55:18 +0200 Original-Received: from localhost ([::1]:53138 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YqVdM-0003yh-Pw for geh-help-gnu-emacs@m.gmane.org; Thu, 07 May 2015 19:55:16 -0400 Original-Path: usenet.stanford.edu!goblin2!goblin.stu.neva.ru!aioe.org!.POSTED!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 72 Original-NNTP-Posting-Host: feB02bRejf23rfBm51Mt7Q.user.speranza.aioe.org Original-X-Complaints-To: abuse@aioe.org User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) X-Notice: Filtered by postfilter v. 0.8.2 Cancel-Lock: sha1:8Z19BsMDYkBoq8qQc7VlCYTEvDw= Mail-Copies-To: never Original-Xref: usenet.stanford.edu gnu.emacs.help:212001 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:104285 Archived-At: Artur Malabarba writes: >> Indeed, the participation would be needed. So start >> with the Emacs SX! But the sx.el people already did >> it (tho I didn't got it to work myself). >> But because they already did it (not NNTP perhaps >> but something to the extent of what we discuss) > > It's the Stackexchange API. Well, yeah :) A solution with Gnus would be a gateway from/to the NNTP protocol and the SX interface (or API). Actually Gnus can do and does other things than that (NNTP) but I don't see why anyone would choose the small shop when there is a big. Anyway if there already is considerable work on sx.el as it seems it might not be a real need to have it in Gnus as well. It would be nice tho, and it would make sense in terms of technology. >> I'd say the "all-in", nested thread post/comments >> blog idea is more interesting and beneficial to the >> Gnusers around the world... > > I've toyed with the idea of combining sx.el with > some sort of mailbot, so that each question on > Emacs.stackexchange gets sent to some list, and if > people reply to that list the bot would post the > reply to the site (using sx.el). > > Issues with this are: 1) I've no idea how (and no > time) to write a mailbot. 2) It would have to be > VERY smart about which replies it posts and be > moderated. The SX API has a very incisive “Quality > of Content” clause, which indicates the bot might > get banned quickly if it's just posting random > comments everywhere. 3) On SX, it's possible to > call's someones attention by directly @naming them. > I'm not sure how the bot would handle these > notifications. I think the only answer would be > someone with a lot of common sense (possibly the > same who moderates item 2), would manually check > all notifications. You don't need to worry about all that. It would only be a new *interface* to the SX sites (perhaps only the Emacs site as a pilot case). So you don't have to worry about doing everything SX does. You have only to make sure hooking to SX is done in the same way it happens when something is posted the ordinary way (i.e. with their web GUI). If you do that then SX will handle material the same way - how it originated (i.e. what interface was used) will not be considered - it'll be transparent to whatever checks and balances that kicks in at that point. Check out these extentions [1] to Emacs-w3m to see what I mean. Notice they mention Google, YouTube, different search sites like Wikipedia, the Urban Dictionary, and so on. Notice I don't do anything to replicate what functionality is on those sites - I only care about hooking to them the same way their web GUIs are. If you do that spotlessly they have no choice but to give ou what you want. If they don't, that means their own services are down. [1] http://user.it.uu.se/~embe8573/conf/emacs-init/w3m/w3m-unisearch.el http://user.it.uu.se/~embe8573/conf/emacs-init/isbn.el -- underground experts united http://user.it.uu.se/~embe8573