Thread - Nostr Hypermedia

You're worried about nostr fragmenting. I am too. A big worry of mine is a JavaScript-based P2P nostr taking off before a JavaScript-free nostr takes off. That could lead to fragmentation that's really hard to fix. We can split paths without fragmenting so badly if the path splits like this - 1. The web-compatibility-focused, semi-centralized JavaScript-and-relay-server-based branch 2. The pure-decentralization-focused, P2P JavaScript-free branch These 2 branches can just talk to each other, translate nostr:nevents between each other's formats, and be useful enough at different times to be worth the tradeoff, without it becoming too much of a clusterheck to patch it all together and keep clients and users "near" other clients and users.

↑ Parent

Replies (2)

🇵🇸 whoever loves Digit 9 months ago

I forgot to say geographically neutral. The P2P JavaScript-free geographically neutral branch vs the English-centric-web-compatibility-focused branch

TheLegendaryMan 9 months ago

I am not sure we are at the forking point. Although we are getting pretty damn close. If we can't figure out a way to come together and rally the Nostr ostriches to agree on a solution. Then yes. We are going to get some forks from the ever growing number of frustrated developers. Who are quite frankly from what I have been hearing so frustrated from the broken state of things and half assed coding. That they want to claw their own eyes out (their words not mine). This is a problem. A VERY BIG FUCKING PROBLEM. Developers should be excited, hopeful, and are enjoying the process of innovation. Not being hindered by a lack of focus, consensus, half assed vibe coding, lack of proper testing, and overall positive direction as a protocol.

1 replies ↓