I've been thinking about the source:account element. Having service as a string like "instagram" makes sense because it's a single instance. For "mastodon" it's okay because the domain of the service is in the username. But I'm wondering if this will become an issue as more small services get spun up.
Should service be a URL to the service homepage? Maybe the service is on a specific port or running from a folder on the server. I know there isn't anything in the spec that says it can't be a URL, but would it be useful, since this is being parsed by a feed reader?
If we want to keep it just a label for the service, should there be an optional url or href element linking to the service homepage?
Andrew -- I'm interested. Is there a use-case you have in mind.
Not sure I would add anything to this element, but could create another element, and the use-case will give me an idea how to present it.
In general I don't like to add features until I have an actual use for it.
That said, I want encourage you to look over the source namespace and make comments and suggestions.
Right now, I'm figuring out what might be the best way to implement rss.chat standards in WordPress without reinventing everything that comes with WordPress. As I've been going through the elements, I've been thinking, "How would a consumer use this?" and this was one of my questions.
So if I were a feed reader and I pulled in the feed from demo.rss.chat and I had an item with `<source:account service="demo.rss.chat">dave</source:account>` I'm trying to think through what I'd do with that.
The first thing that comes to mind would be linking to the user's profile page, but we don't have an html profile as far as I can tell. We do have the user's RSS feed, and it's in the `` element. The feed, interestingly enough, uses the user's homepage as the channel `` and not a URL where you'd see the user's posts.
So right now I have more questions than answers, but this is where my line of thinking is going.