Post Az1ayr19mYZn7PccTY by jackwilliambell@rustedneuron.com
 (DIR) More posts by jackwilliambell@rustedneuron.com
 (DIR) Post #Az0ohKJdJog4yLqBAu by silverpill@mitra.social
       2025-10-08T21:48:05.513204Z
       
       0 likes, 0 repeats
       
       @jackwilliambellI want something much simpler anyway. But I don't want to use JSON-LD, so no direct interop will be possible.It's hard to find a developer who wants to use JSON-LD in a social application. But the good news is that JSON-LD is not required, and not even used: our servers produce and consume plain JSON documents. Yes, these documents have @context property, but for most implementations this is purely ceremonial thing.Here's some test data: https://funfedi.dev/support_tables/hashtag_jsonld/That's what I meant when I said that the flavor of ActivityPub we use in Fediverse is already quite close to 'Really Simple ActivityPub'. Nobody wanted an over-engineered protocol, so it was simplified and optimized by early adopters.
       
 (DIR) Post #Az1ayr19mYZn7PccTY by jackwilliambell@rustedneuron.com
       2025-10-08T21:59:02Z
       
       0 likes, 0 repeats
       
       @silverpill Gotcha. But compare and contrast to:- Atom – http://www.atomenabled.org/OR- JSON Feed – https://www.jsonfeed.org/version/1/And ask yourself why you need a type and name and a list consisting of names and URLs for hashtags. URLs which are then ignored by the implementation (Mastodon in my case) and given URLs on the local server? IOW? Why even have hashtags as part of the protocol? Why not let the implementation decide how to parse and handle them in the first place?
       
 (DIR) Post #Az1aysCXNjH2mzxDqy by silverpill@mitra.social
       2025-10-09T06:49:14.472519Z
       
       0 likes, 0 repeats
       
       @jackwilliambellURLs which are then ignored by the implementation (Mastodon in my case) and given URLs on the local server?The URL is added because the originating server has a different view of hashtag. You can visit it and discover other posts with that tag that your server doesn't have.Not all implementations rewrite tag URLs in post content.Why even have hashtags as part of the protocol? Why not let the implementation decide how to parse and handle them in the first place?Tags may not be present in post content. And I think it's nice that parsing HTML on the server side is not necessary.