*UNOFFICIAL* Frontier Forums Developer Posts RSS feed

Absolutely fine Athan. Thanks for keeping this going :)

Still wish you didn't need to though, but apparently an actually working Dev tracker is more complicated to do than I would of believed....
 
Hello Athan,
when you changed the feed’s cutoff time to 28 days you mentioned you’re going to set it back to 7 days at some point. Can I ask you to keep the 28-day cutoff, at least for the ‘precis text’ feed? I find your feed invaluable for catching up to E:D news when I’m away from the forums for an extended period of time. :)
 
Hello Athan,
when you changed the feed’s cutoff time to 28 days you mentioned you’re going to set it back to 7 days at some point. Can I ask you to keep the 28-day cutoff, at least for the ‘precis text’ feed? I find your feed invaluable for catching up to E:D news when I’m away from the forums for an extended period of time. :)
Yeah, I decided to just leave it at 28 days as it's causing me no issues to do so.
 
A couple of weeks ago I finally got around to writing the necessary code to scrape 'developer' posts from the Frontier Forums and produce an RSS feed from that data. I then updated it for the upgrade to the current version of the forums. It all seems to be working OK (high forum load today aside), so I thought it might be time to publicise the existence of the feed.

You can find details about the feed on https://ed.miggy.org/devposts.html (now present in my forum signature). As that page says... if you have an RSS Extension or your browser otherwise handles RSS feeds then you should see an icon in your URL/Address bar. Else use the URL in that page to add the feed to your reader by hand.

Any feedback or concerns about this RSS feed can be addressed to me in this thread, through PM, or to the email address: edrss@miggy.org (which is included in the feed details).

Also, kudos to Bewilderbeest for his dev post tracker which prodded me to actually complete work on this project.

ChangeLog
2014-10-30 ~22:15 UTC
- Fixed an issue where I was only picking up replies from devs, and not the post for when they started a new thread. All posts since midnight today re-imported to be sure.

eh, who am I kidding, just read the changelog on the main site https://ed.miggy.org/devposts.html
I'm not IT expert... I don't see the RSS feed on the URL address bar. How do I enable it? (I don't have administrator rights on this pc)
 
Depending on browser you might need an extension to have it pick up the link elements to show that. That's why the page lists the RSS URLs explicitly in the body as well.

Even with such an extension you'd then also need something to point at the RSS feed. Firefox stopped supporting such directly. Personally I use a Chrome extension and my own Tiny Tiny RSS instance. For most non-technical users it's probably easiest just to use feedly.com.
 
Any of you that have seen a splurge of falsely new articles, blame FDev for changing the forum URL format to include "index.php?" at the start. My code wasn't set up to handle that so it's caused both this issue and for the 'ignore forums' code to fail and thus non-ED related posts get through. I've fixed the code and will now clean up the database and the RSS files.
 
And after a little more fixup I think things should now be working properly again. This assumes that the older (initial XF2) style URLs without the 'index.php?' string will continue to work (testing currently shows them redirecting to the new version of the URL). If that stops working then I'll need to both adjust my code again and update the database to convert the stored values.
 
I'm aware that the fulltext feed isn't interpreting some BBCodes, such as:

Code:
[CENTER]
[ATTACH]
[COLOR]
[INDENT]
I'll take a look at this Soon™, no ETA.
I've just put some code live that should handle all of the above, plus tables and MEDIA tags. There might still be a few unhandled. I'll get to those when they crop up again (now I've figured out just how to get Parse::BBCode to accept custom handling).

NB: I've not yet gone back and fixed up older articles.
 
And now USER tags are handled as well.

I also added some fallback code in case some tags don't parse exactly how I expect. This means we'll still see BBCode for those tags instead of that section disappearing from the output entirely.
 
Top Bottom