Everything old is new. I've worked on this quite extensively at Mediamatic in 2008-2011. Have a look at <https://ralphm.net/blog/2011/02> and <https://ralphm.net/publications/fosdem_2011/>.
On 11 November 2025 10:13:41 CET, Schimon Jehudah <[email protected]> wrote: >Good day > >I have elaborated about it to the Movim project. > >https://github.com/movim/movim/issues/1488 > >And I have two additional rationals. > >* Utilizing Activity Streams would allow to set icons and photos to > Atom Over XMPP feeds, which is currently not possible because Atom > Over XMPP only include element "atom:entry", and does not include > element "atom:feed". > >* Utilizing Activity Streams would also to set a different icon and > photo representations by *context* (e.g. family, sports, traveling, > exploring, et cetera). > >And this is an argument for future concerns. > >* As with Atom Over XMPP (XEP-0277 and XEP-0472), some people might > justly ask for RSS Over XMPP; and adopting Atom Activity Streams > would significantly assist in refuting an argument to add a new XEP > for RSS Over XMPP. > >Kindly, >Schimon > >On Mon, 10 Nov 2025 08:36:38 +0200 >Schimon Jehudah <[email protected]> wrote: > >> Good day. >> >> I have explored the "Atom Activity Streams" documents of Friendica. >> >> https://activitystrea.ms/specs/atom/1.0/ >> >> I have further added rendering capabilities to an RSS extension. >> >> https://greasyfork.org/scripts/465932-newspaper-syndication-feed-reader >> >> >> Proposal >> -------- >> >> Since Atom Activity Streams documents can be delivered as a single >> "atom:entry" element, as so with XMPP PubSub Node Items; then, it >> might be beneficial to mention "Atom Activity Streams" in the XEP >> specifications of Atom Over XMPP (XEP-0277 and XEP-0472). >> >> >> Rational >> -------- >> >> Even though, as it seems, an Atom Activity Streams document is, as >> with Atom Over XMPP, a single "atom:entry" element, with a couple of >> XML namespaces, this would stimulate people to: >> >> * Utilize XMPP PubSub Node Items in an independent fashion, without >> compiling an Atom Syndication Format document; and >> >> * Consider interoperability with Friendica and other platforms that >> produce Atom Activity Streams documents, and also Json Activity >> Streams documents, which Nostr utilizes. >> >> * Consider interoperability of projects with XMPP. >> >> * Motivate projects, such as Friendica to extend support of XMPP. >> >> >> XML Namespace >> ------------- >> >> The namespaces that are utilized by Friendica, and may be relevant, >> are: >> >> xmlns="http://www.w3.org/2005/Atom"; >> xmlns:at="http://purl.org/atompub/tombstones/1.0"; >> xmlns:activity="http://activitystrea.ms/spec/1.0/"; >> xmlns:dfrn="http://purl.org/macgirvin/dfrn/1.0"; >> xmlns:georss="http://www.georss.org/georss"; >> xmlns:media="http://purl.org/syndication/atommedia"; >> xmlns:ostatus="http://ostatus.org/schema/1.0"; >> xmlns:poco="http://portablecontacts.net/spec/1.0"; >> xmlns:statusnet="http://status.net/schema/api/1/"; >> xmlns:thr="http://purl.org/syndication/thread/1.0"; >> >> >> Sample >> ------ >> >> Herein attached an Atom Activity Streams document. Source: >> >> https://my-place.social/display/feed-item/107999490.atom >> https://my-place.social/display/1c9fc4fa-f51b9f6f654d0bd7-7c3a0251 >> https://piaille.fr/@movim/115519544289510132 >> >> >> Kind regards, >> Schimon >_______________________________________________ >Standards mailing list -- [email protected] >To unsubscribe send an email to [email protected]
_______________________________________________ Standards mailing list -- [email protected] To unsubscribe send an email to [email protected]
