-
-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Atom vs RSS 2.0 in a Microblog Context #31
Comments
To be honest, I have thought a lot about this. I still prefer Atom from an idealistic point of view and consider it a nicer format to read. It is true though, that the world has mostly expanded upon RSS and Atom is more of a niche spec. It makes total sense to at least include RSS in the mix of feed formats. In fact I have begun work on a feed in If you like, you're welcome to draft |
Not surprised to hear you've already been thinking about some of the things that had occurred to me in terms of refactoring the feed functions into their own library. I'm in also in full agreement that Atom is a nicer format, it's unfortunate there have been no tweaks to the spec since 2005. I think |
One thing that's been weighing on me for a while since discovering this project is that you chose to implement the xml feed with Atom rather than RSS 2.0. This surprised me because Atom specifies that every post must have a title and a defining feature of RSS and the microblog effort is that titles are optional. One of the things I'm thinking about working on next is getting the xml feed closer to parity with the json feed with image attachments support, but my inclination is to do the work in a new rebuild_rss_feed() function and leave the Atom support alone. Does that sound reasonable to you? An RSS implementation could also allow for micro podcast support in the future as well if we just passed entries with audio attachments.
The text was updated successfully, but these errors were encountered: