Post #1619577
2026-04-23 11:27 UTC
Replies (4)
-
@mnot@techpolicy.social 2026-04-23 11:29
Implementation as a browser extension here: https://github.com/mnot/feedmenu-extension
-
@liaizon@social.wake.st 2026-04-23 11:47
@mnot this looks interesting, excited to see people working on standards like this. my first thought looking at the draft is the part about languages feels off, and much too minimal. "Publishers generally SHOULD NOT mix languages in the same feed menu document, although there may be cases where this is done intentionally."
-
@jyasskin@hachyderm.io 2026-04-23 13:51
@mnot 2 thoughts: 1. If an origin contains many logical websites, as in the old example.edu/~user/, well-known becomes inappropriate, or at least needs a way to dispatch to the logical units' feed lists. App Manifests would be a way to deal with this. 2. Re the localization discussion downthread, App Manifests made the "just content negotiate" argument for a long time, but have recently added inline translations. It'd be worth checking whether the same reasons apply.
-
@paulehoffman@infosec.exchange 2026-04-23 19:58
@mnot Is the choice of JSON instead of XML because "everyone does JSON these days"? I would have thought XML because "the consumer of this information already knows how to parse XML". Otherwise: good idea, I agree with the other posters about language, and I'll certainly support the idea when it is DISPATCHed.