Discourse, the software that powers this forum, has an RSS Polling plugin, and we have enabled it here already. This means that we can have on-topic RSS feeds create topics automagically with the syndicated content (title, body, images, links…) and then users can like and comment these posts as if they were natively published here.
Therefore: if you want to recommend an on-topic RSS-feed to import, or other RSS import related ideas, please reply. We want to be very selective importing RSS feeds since they can quickly overshadow genuine local discussions, but I’m sure there are useful RSS feeds out there that would make total sense to import here.
(Discourse also generates loots of RSS feeds to syndicate our discussions in other places. Please create a topic if you have ideas about this.)
We could consider following release feeds for the major platform projects (faircamp, mirlo, bandwagon et al) whereever they’re made. I could imagine that would save devs the effort of making release announcements in yet another place (here) while giving users a place (here) to discuss releases adjacent to the release announcements. (Should probably be dev preference…?)
@bandwagon@simon and anyone else with a project website or a code repository (I believe they also have RSS to announce new releases), what do you think?
Having a couple of real projects with RSS would be very useful to test and showcase this feature to others.
Sure! Our blog’s RSS feed is this but it includes all of our announcements, not just technical features. And we don’t really publish releases of our software yet as such, though we probably should if we’re talking about versioning and having other people use it. We’re not quite there yet though!
I would just advocate that this happens in a channel that people can mute
I’m digging into this now. It may be because of the different feed formats Emissary uses. The default format is JSON-Feed, but you can switch to RSS or Atom a couple different ways.
I’ve just changed the default to RSS, to see if that helps, and cleaned up a couple of small formatting issues. Could you please try the Bandwagon RSS again?
@bandwagon Am I copying the right RSS feed? I go tom Bandwagon.fm - Blog , ni RSS icon is to be seen but the browser offers an RSS and an Atom feed. I have tried both and none of them validates. See the report from the W3C validator.
Ah shoot, we just pushed API Keys to our API (which means apps need to register to be able to use it, rather than it just being open to anyone in the world) but there’s been some endpoints that do need to be open to the world (the RSS ones being a major one). Looking into it now.
It looks like the W3C validator is caching responses, because when I go to the page directly, it’s now returning XML-formatted RSS and not JSON-Feed. Bitches.
You can FORCE this by adding ?format=rss to the end of the URL. So try following Blog if you’re still having trouble. (Here’s the W3C validator link to show this working)
Also: @simon - the struggle is real; congrats on the update. Do you have your API documented anywhere?
But there is something still not normal (or at least not usual, maybe you designed it this way). Only an excerpt is imported. And if the user tries to “Show full post” then the response is “Forbidden”.
Sorry this is so tedious. I can certainly include the full content in the RSS feed. That’s probably the right thing to do in general.
But I’m not sure what’s causing the Forbidden error. Perhaps a weird URL translation somewhere along the way? I’ll take a look at our generated RSS and see if there’s anything “weird.”
@bandwagon If the full content is provided in the RSS, then users won’t have any “Show full post” button to click, and hence no chance of triggering the “Forbidden” not even if it was still reproducible. In other words, if the full post is served, problem solved (I hope).
I’ve just double-checked the RSS feeds. They are already providing the full article content. Is is possible that your RSS reader is truncating this to make a summary?
The RSS also includes a summary field, but that’s not what’s displaying on the Discourse website. Perhaps I should try removing this summary altogether? Maybe that would trigger Discourse to use the full article content?
Er… my bad! True, the corresponding setting to truncate imported posts was enabled. I didn’t see any posts truncated on Topics tagged lorenzos-music-podcast-feed (there’s even an image!) but that’s because… their full texts are simply short – nothing to be excerpted.
Ok, I have deleted the posts and they should be imported again with full texts next time the cron runs, in 30 minutes or less. Sorry for the distraction and false accusations!
True, the corresponding setting to truncate imported posts was enabled. I didn’t see any posts truncated on