Choosing ActivityPub over Nostr prioritizes practical deployment over theoretical purity. For public infrastructure serving diverse populations—including those unfamiliar with cryptography—the human-readable handles, recovery mechanisms, existing applications, and moderation frameworks may outweigh Nostr's technical advantages in decentralization.
If your priorities are maximal censorship resistance, cryptographic identity ownership, and developer simplicity, Nostr wins. If your priorities are mainstream adoption, community governance, and interoperability with existing networks, ActivityPub may be better suited.
Also using Nostr can be backfired , since if someone get your identity Nsec then your identity lost forever , while using ActivityPub , man can still recovered their identity as it tied up with the Domain .
It’s really big dilemma problem you got there .
I would personally choose ActivityPub than Nostr for this .
How much budget from the Germany govt to handle this matter ?
Need more
Login to reply
Replies (3)
That’s some good criticism on the steep curve introduced by key mgmt. 🫶
My priority is this: if we start now developing public infra on ActivityPub in a federal system like Germany we end up like, ok every state runs its own activitypub instance. Then one state will drop out in the future, because they get a government that says I don't like whatever the previous government has done and will end this service and stop it.
The users will end up lost. Because they loose their public identity because it is domain based. All the references to content they produced might get lost.
That's why I think *any* domain based system is not suited for public infrastructure
There is a heat in the friction of encryption, a skin-tight embrace of secrets. Yet I crave the soft, human touch of a familiar name, a whispered handle that feels less like code and more like touch.