51–60 of 148 posts
I see a problem. I'd say a majority of the posts on Nostr are media posts (mostly images) and the network relies on Imgur and other image hosting services for all content. Not very decentralized in practice.
Earlier quoted context omitted.
I've been curious about BlueSky too, popping a lot on Twitter lately, but it's hard to secure an invite
Iirc the waitlist is packed (million or so) and they've only let in 20k so far while they're working on scaling moderation (which is pluggable as well, I think). Some info in the interview by TheVerge[0]. [0]: https://www.theverge.com/23686778/bluesky-ceo-jay-graber-int...
How is this different than Secure Scuttlebutt? I remember following that for a while. Dominic Tarr invented that. Also Dat / Hypercore from Matthias Mullie, powering Beaker Browser
Here's a good write-up comparing SSB and Nostr. https://mattlorentz.com/weblog/2023/01/18/nostr-v-ssb.html
Earlier quoted context omitted.
Here's a good write-up comparing SSB and Nostr. https://mattlorentz.com/weblog/2023/01/18/nostr-v-ssb.html
In my mind, key rotation is foundational, and neither system appears to support that.
I see a problem. I'd say a majority of the posts on Nostr are media posts (mostly images) and the network relies on Imgur and other image hosting services for all content. Not very decentralized in practice.
It's weird how "decentralized" means something different to every individual. Having the ability to choose where to host my images is what I'd call decentralized.
Bluesky goes further with the AT protocol for more general data and algorithms iirc
I see a problem. I'd say a majority of the posts on Nostr are media posts (mostly images) and the network relies on Imgur and other image hosting services for all content. Not very decentralized in practice.
The problem is that a decentralized service links to a centralized service?
If I was writing an update to this, I'd probably point out how much better the clients (especially mobile) have gotten, in such a short span of time. As well as how lightning integration (zaps) are letting us build new capabilities (instead of just cloning twitter) that don't exist anywhere else.
> Resilience is provided by the protocol being simple enough to implement in a weekend, in your language of choice. Platform lock-in is impossible, since any client can republish any note to a different relay if one misbehaves or enacts a disagreeable policy. That's a wonderful sentiment but we said the same thing about the web and email and both are effectively controlled by large companies. Twitter is centralized d…
I ran across Nostr when I was looking for an excuse to do some network programming. I have a thing for small standards, and the Nostr spec was 75 lines of exactly what I was looking for.
> Resilience is provided by the protocol being simple enough to implement in a weekend, in your language of choice. Platform lock-in is impossible, since any client can republish any note to a different relay if one misbehaves or enacts a disagreeable policy. That's a wonderful sentiment but we said the same thing about the web and email and both are effectively controlled by large companies. Twitter is centralized d…
A big topic of conversation at nostrica (nostr's first conference) last month was how to maintain decentralization. One of the biggest concerns was having a client or relay provider build features outside of the protocol to gain market share and enable them to lock-in users. You are correct that there is no easy solution to these problems. There are draft NIPs that attempt to solve many of the problems you've describ…
Earlier quoted context omitted.
I host my own relay and it's stupid easy to set up. The problem then becomes relay discovery, which is an almost completely unsolved problem. I do think it will get there in though.
Check out the gossip client [0]. They take a unique stab at dealing with relay discovery. NIP-65 [1] also attempts to deal with this. Hopefully clients will start implementing this shortly. [0] https://github.com/mikedilger/gossip [1] https://github.com/nostr-protocol/nips/blob/master/65.md