@erincandescent @julian @evan it does mention the @context name collision which is imo a real point of confusion
darius@friend.camp
Posts
-
Minutes from 3 October 2024 WG Meeting -
Minutes from 3 October 2024 WG Meeting@erincandescent @trwnh so by my reckoning, Mastodon and Misskey don't use context, akkoma does... ugh, I need to add more sources to my observatory
-
Minutes from 3 October 2024 WG Meeting@erincandescent @julian @evan can you give an example of the "context" property in use?
-
idk where to really put this (might turn into a blog post later or something).@trwnh Hmmm. In the open web we have a thing called a browser vendor whose job is de facto to act as the choke point where they are the ones who have to be aware of every implementation. Then as devs we get to black box it as "this is what web browsers support".
-
idk where to really put this (might turn into a blog post later or something).@trwnh This is related to my recent-ish realization (which I always knew on some level but never formulated explicitly) that AP simply does not have much to say about the mechanics of federation. And that there is basically nowhere that federation is defined; it is pretty much left as an implementation detail for the author of a server to figure out
-
Relaxing treatment of non-notes by Mastodon@trwnh @erincandescent dark magic that I leave to Christine
-
Relaxing treatment of non-notes by Mastodon@trwnh @erincandescent turing completion considered harmful
-
Relaxing treatment of non-notes by Mastodon@trwnh @erincandescent fwiw I'm 100% on board for following Collections exposed as streams. It seems to me the reasonable solution to the as:Listen-spamming issue here. If you subscribed explicitly to get as:Listen then it is completely reasonable to expect your client to know how to handle it in a way that is not annoying to the end user