RE: https://toot.community/@dyne/116018338049205915
interesting read in defense of Nostr's architecture. really seems like there is a renewed battle between ATproto, ActivityPub and Nostr lately
Discussion
Loading...
Discussion
@liaizon Woah the stuff on dyne.org seems very confused…
@despens @liaizon Also, I find it very hard to ignore that nostr is cooked up by a bolsonarista, embraced by dorsey (https://www.businessinsider.com/jack-dorsey-fiatjaf-nostr-donation-2024-6) but it seems the author manages fine.
@rra @despens I agree those points should not at all be overlooked. I still think it's needed for "us" on the fediverse to understand the parts of their architecture that might actually be working in ways that we have not made solutions for. I wish their project wasn't majorly made by people who's idiologies are mostly fascist or fascist aligned
@liaizon @rra The strongest point made about nostr here is about technically enabling a "sovereign single identity" that can exist without a server. While this might be architecturally more robust in a certain world view, the sovereign single identity in itself is a weird concept. Why would anybody want only a single identity? Why would it be sovereign, rather than tied to a community in which one acts? I'm with @shusha here about "first choose your community, then your identity within that community".
On the rest of dyne.org, Cypherpunks generally get a good rep. and I think celebrating that identities are build on cryptographic keys exactly attracting the types of "there's no such thing as society" people we see on nostr, and has all the issues described in the article, such as no deniability, difficult key management, etc.
That Mastodon has no encryption at all and potentially endangers community members is of course terrible, but I would propose that its identity model is better.
@liaizon when I first looked into nostr, I thought it had an interesting architecture, which was a completely moot point on a network completely overrun by cryptogrifters
The are many good things about Nostr. And, there are things the Fediverse can learn from Nostr.
Although technically, the Fediverae COULD already work a lot more like Nostr.
More recently @HolosSocial has been doing just that.
@liaizon it's very interesting to me that the author here considers federation to be entirely a downside.
as far as local community, moderation, sharing costs, etc having an opinionated instance (versus transparent relays) seems pretty important to me. i strongly prefer _not_ being totally independent.
(that said i agree that we really need some kind of portable identity/history support on the fediverse to enable better migrations)
@d6 I think it really depends on what your history of how you were using the network. I think a lot of people got dumped on many random instances and then basically had random admins that were into hosting stuff as their overlords. if you are on an instance that is actually set up and treated like its own community you end up having a very different view of what the network dynamics are
(don't worry I am still on team fediverse) though we realllllly need to decouple our identity systems with our hosting and indexing
@liaizon and this can be done with @nextgraph and @activitypods
for it to actually work for the fediverse we would need it to be done in standardized protocol driven way along the lines of what @silverpill is working with their FEP. Saying you can do it with @nextgraph + @activitypods is missing the part where it needs to be done in a way that hundreds of different code bases in different languages can implement and interoperate with the new way of addressing
@liaizon @silverpill @activitypods Yes I know. Silverpill knows me and my work a bit, and I would like to discuss it with all of you. we have solutions of DID in ActivityPub, and also for an easy way to build social apps on top of it, similar to what Lexicon and PDS does, in the ATproto world. Would love to starting working on a FEP about that
@nextgraph @silverpill would love to see it! getting some of the stuff you are already trying to do with @activitypods written up in FEPs and generalized so that other implementations could start to play with it would be amazing.