savetheinternet / Tinyboard

The better imageboard software

Home Page:http://tinyboard.org

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

RSS / ATOM feeds

mitsukarenai opened this issue · comments

[improvement]

As-is, Tinyboard makes it hard in low-activity boards to track new or updated threads, or automatically mirror threads. To follow a thread, people need to copy-paste the URL and check randomly, or use a HTML-parsing script to get alerts.

By default Tinyboard should keep the ephemeral scheme like many other imageboards (where feeds aren't relevant), but maybe there should be an option to enable and include feeds for "Q&A boards" (I'd prefer ATOM, better syntax), where:

  • 1 general feed to track new or new+updated threads
  • 1 thread-specific feed to track new posts

Would it require too much work ?

Should be fairly easy to implement using themes, you can base your code on
a sitemap theme. See templates/themes/sitemap

About watching, my tinyboard fork https://int.vichan.net/devel has a
watch.js javascript, which lets you enable watchthread and watchboard. Be
aware that it may be incompatible with the upstream tinyboard, so if you
wish to enable it, you would need to use it as a whole (which isn't a big
problem, because mostly the code is compatible and everything is to be
enabled using config).
15 maj 2014 18:05 "mitsukarenai" notifications@github.com napisał(a):

[improvement]

As-is, Tinyboard makes it hard in low-activity boards to track new or
updated threads, or automatically mirror threads. To follow a thread,
people need to copy-paste the URL and check randomly, or use a HTML-parsing
script to get alerts.

By default Tinyboard should keep the ephemeral scheme like many other
imageboards (where feeds aren't relevant), but maybe there should be an
option to enable and include feeds for "Q&A boards" (I'd prefer ATOM,
better syntax), where:

  • 1 general feed to track new or new+updated threads
  • 1 thread-specific feed to track new posts

Would it require too much work ?


Reply to this email directly or view it on GitHubhttps://github.com//issues/176
.