@douwe@waag.social The protocol itself hasn't changed radically in the last 18 months. If you want to understand ActivityPub and ATProto's similarities and differences, you can't find a better analysis than Christine's. She is one of my co-authors on ActivityPub, and she really dug deep into both protocols.
definitely not a fan of this. tbh, there should just not be a global feed that new accounts see, because they see a lot of stuff they don't understand or know the community norms for, and that leads to bad engagement.
There is the Web Share API, and the future Web Share Targets API, but I think we could also align Web Share with FedCM and be able to say "I want to share to this type of application"
@douwe@waag.social The protocol itself hasn't changed radically in the last 18 months. If you want to understand ActivityPub and ATProto's similarities and differences, you can't find a better analysis than Christine's. She is one of my co-authors on ActivityPub, and she really dug deep into both protocols.
@reiver i think the disjunction between Object and Link was actually unnecessary. https://github.com/w3c/activitystreams/issues/666i also think there's too much emphasis on types when there really shouldn't be -- it's the *properties* that you end up using almost all of the time. pretty much the only types that actually matter are the Activity types (because you can't infer those).
definitely not a fan of this. tbh, there should just not be a global feed that new accounts see, because they see a lot of stuff they don't understand or know the community norms for, and that leads to bad engagement.