@Paul https://federated.id/objects/7f48bff3-6db5-4c22-a4d8-9088d6ca0454

@julian @Paul everyone is worried that Facebook will bully the fediverse with EEE strategies, while failing to recognize that Mastodon already does this and nobody bats an eye.

@julian @Paul I doubt that forming a working group will make Mastodon devs put more resources into spec compliance. They had plenty of time to prove they can be a good member of the community and in my opinion, they failed. They rely on their leader position to have smaller projects implement their quirks instead of being a good neighbour and prioritizing spec compliance.

@js I realize I didn't explain what FedBOX uses it for. Like @julian intuited I use it show any special collection the user has. Specifically FedBOX has some "storage" collections for activities, actors, objects. They are only present on the top level actor that you saw.

@renchap I think sending Deletes just to followers is a decent solution, if combined with servers refreshing an actor every time it appears in an Activity or Object. Ie, if some server wants to send a Note to a bunch of recipients the server should refresh the actors, and then notify the user that they're trying to send the Activity to invalid actors for every received Tombstone (or even removing them all together from the recipients list).

@pkreissel

I often struggle with working on non-trivial, long standing projects because when I sit down to do the work after some hiatus, I can't seem to find the pain points I wanted to fix quickly enough.

It feels like trying to get a bandaid off when you can't find an edge where it comes unstuck easily enough.

The largest piece of bandaid that I wasn't able to get unstuck from the ActivityPub adjacent work is getting the HTTP-signatures working well with the rest of the fediverse (by which I mean Mastodon).

Today I might have got the corner of another little bit of bandaid unstuck which hopefully will help in the long run.

#ActivityPub #fedidev #GoActivityPub