[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120923180858.GZ9428@port70.net>
Date: Sun, 23 Sep 2012 20:08:58 +0200
From: Szabolcs Nagy <nsz@...t70.net>
To: musl@...ts.openwall.com
Subject: Re: Announcing ewontfix.com
* Rich Felker <dalias@...ifal.cx> [2012-09-22 21:21:58 -0400]:
> Comments work via Disqus, which I'm afraid some members of our
> community won't be big fans of, but it's a lot safer and less bloated
> than running message board software locally on the server. I'm looking
> for help setting up a way for non-JS browsers to use the comments, so
> let me know if you have any ideas.
>
they don't provide any static plain text or html summary of
most recent comments other than the rss feed:
http://ewontfix.disqus.com/$ID/latest.rss
so the only possibility is to register for an app key (PK) on
disqus.com and use their "rest api" (==broken, undocumented
api returning a huge redundant json response):
http://disqus.com/api/3.0/threads/listPosts.json?api_key=$PK&thread:ident=$ID&forum=ewontfix
with such http(s) queries one can get the comments and with
some pain render them into simple html but to have it on the
site this should run from a cgi script (with caching) or cron
job on some server
it's hard to parse json with unix tools so the html rendering
must be done with a script language available on the server
or in c
anonymous posting through html forms can be done as well
(the referer must match so it cannot be anywhere)
registered users may post replys and subscribe to comment
threads via email but non-registered users can't
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
