pull down to refresh

150 sats \ 4 replies \ @optimism 17 Apr \ parent \ on: Mastodon Exit Interview (with Bluesky entrance interview) nostr
May be an unpopular opinion but I have come to believe not everything scales and silos or communities have value.
This. Communities have massive value and the good ones are diverse enough to not be an echo chamber. But not fully inclusive. Can't cater to everyone in discussions because we're all emotional beings in the end (except the gpt copy pasta people but eff these guys)
Nostr is much closer to this than anything else.
Because its a protocol. Its very young though. May need a v2 at some point in the near future to get rid of inherent inefficiencies.
No guarantees that Nostr will succeed. I think its kinda up to us.
It is. I wish I had time to build proper federation. I think this has been the best constructive criticism (to my knowledge @petertodd was among the first to mention it) that I've seen. Censorship resistance needs a means to talk relay-to-relay and not miss anything.
I don't really think it needs a NIP to truly implement it (though a well designed protocol could help if at some point optimization is needed to reduce load on relays.)
write
preview
133 sats \ 1 reply \ @sambuca 5h
It does need a v2, but I think it's either very close to (or already past) the point where a v2 can be implemented without both killing the V1 and dooming the V2 to failure. If there is still time I also don't know how a v2 (several breaking changes) gets done, besides someone influential simply forking it and successfully marketing their fork.
reply
50 sats \ 0 replies \ @optimism 2h
Protocol handshakes to establish versions is the easiest way and has been used for ages; every https connection you start to read this message performs a handshake.
Software implementations may be strict or non-strict about versions supported. It's not hard; just needs someone with experience to champion it.
reply
100 sats \ 1 reply \ @kepford 18 Apr
Yep, relays to relay talk would be a massive improvement and it seems like something that could be done outside of the NIPs.
reply
55 sats \ 0 replies \ @optimism 18 Apr
I've seen some proxy implementations but that just sits at the front-end (at least that's what it did when I looked at it). The real power would IMHO be in having a community federated relay - think for example an SN relay that only tracks SN users' known npubs and the surrounding events, and stores these. Can serve back via a read only relay.
SN provides NIP-05 services too so we know which relays to look at for the content of each npub...
reply