nostr:npub1k43tm7ehg8s2845crajkqdzhf7yuru0va33ky4swpaa6tuzq5twq3ta8eh nostr:npub1wm75dv8hfu6528lkvmy5nudnraczywl7c5dhn8ctnx6xk0983d0skclxpu There are some fediverse people under the banner of dweb, but mostly it's blockchain grifters. I would characterize a lot of this as being about adopting the superficial mannerisms of radicalism (wearing the T-shirt, etc), while actually being orthodox capitalists.

It would indeed be nice if accounts owned their replies collections in the same way that comments on blogs used to work. i.e. the blogger could moderate or remove comments as needed.

But Actually Existing #ActivityPub is the culmination of a lot of tradeoffs and battles that the contemporaneous tooters have never witnessed. Some things which seem to be unreasonable design choices to the newcomer are because of the events that went before. The exoduses, purges and brigading on the silo sites.

In the context of replies, with the traditional blog the commenter is someone with a browser and the blogger is the publisher fully in control of the site content. In the federated model both are publishers. So one cannot necessarily determine what version of events the other publishes. But things like object capabilities may help, and the pixelfed stuff which I've been adding support for also helps to communicate intentionality around replies and boosts.