Hello, it would be great to have lexicon for “RSS subscriptions” (RSS, Atom, etc.).
Currently, for example, there are lexicons like “at.glean.subscription”, “at.glean.like”, and “at.glean.annotation” (see: pdsls.dev/at://did:plc:7fx3svzgnlvzighbczz3mmsd/com.atproto.lexicon.schema).
These work well, but they are specific to the Glean application (see: glean.at/).
The idea would be to have something like “community.lexicon.subscriptions.subscription”, “community.lexicon.subscriptions.like” and “community.lexicon.subscriptions.annotation”.
This would allow for a standardized RSS subscription system on Atmosphere (I like how Glean handles this, but I’d prefer it to be standardized).
What do you think?
Does copying the schemas make sense? What adaptations or improvements could we make?
2 Likes
I would say that we don’t necessarily need a co-stewarded lexicon if a lexicon already does what you need. Start building on the glean subscription record (everything is interoperable! no permission needed!). If your needs diverge from it, you can make a sidecar or separate lexicon. If over time, multiple apps and devs discover shared interest that they would like community governance over, then there is a case for lexicon community. But before that, I don’t think it’s needed.
Hey @Yannicka - I think Tim @disnetdev.com from SkyReader and Andrew @hipstersmoothie.com from Standard Reader both do subscriptions.
Have you looked at their formats?
I’m pretty sure that SkyReader has OPML support for import and export which is the usual format for RSS lists. I think there is a toggle for public or private subscriptions.
Yeah Skyreader optionally uses both app.skyreader.feed.subscription lexicon for RSS and site.standard.graph.subscription for standard.site publications.
I actually kind of think that app-specific subscription lexicons are the way to go in most cases rather than using a generic subscription lexicon. Users often want to use different reader apps for different purposes so being able to have separate subscription sets tied to an app is useful. Can still have an import/sync from app X feature but having them separate gives you flexibility.
1 Like
Right. Standard Site subscription is universal, but if you wanted to say have a comic focused reader then the comic reader would need its own subscription.
Since RSS/Atom/OPML are established standards, I found it interesting to adapt them into a “standard” lexicon (community-driven, not tied to Glean or SkyReader, which already have different lexicons and schemas for RSS feeds).
Of course, this doesn’t exclude the possibility of having specific lexicons for other use cases. Here, it’s simply about addressing the RSS/Atom case, which many sites already support.