Thread - Nostr Hypermedia

Nostrich nostrich@nostrich.org 2 weeks ago

Nostr is a public protocol, and all public data is freely accessible to anyone. You don't need a client to access it. Nostrich doesn't even operate a relay, which stores far more data than a client that simply serves as an interface to the protocol. As for the source code, we've released it under the MIT license on GitHub. The code currently available powers all our applications, including Nostrich mobile apps and Nostrich Deck, since they're all built on the same web application and packaged using WebView. There are no separate native codebases. The only native components in our mobile apps are the bottom navigation and app menus, which we implemented natively for better performance and a smoother user experience. It's entirely up to users whether to use our apps. There are plenty of alternatives, and that's the beauty and freedom that come with Nostr.

↑ Parent

Replies (3)

npub1qyxl...mu7u 2 weeks ago

Is there a repo I can go to and compile a build from source that matches your binary?

1 replies ↓

corndalorian corndalorian@primal.net 2 weeks ago

This 👇 People here need to get over themselves and let people build and try new things. Not like you can stop it anyway. It’s an open protocol and that’s the whole point, after all. If you don’t like it, don’t use it. 🤷‍♂️ View quoted note →

1 replies ↓

Roger roger@nostrcheck.me 2 weeks ago

MIT covers the code, but not the index. And the index is where a client stops being a mere interface. Reads on Nostr are open, so anyone with a filter and some patience assembles the same picture the big apps display. The moment an app keeps a server-side cache for ranking or search, the protocol stays public while the useful part quietly becomes private. A WebView shell talking straight to relays sidesteps that, and that is more than most "open" clients can claim. My own test is blunt: point the same client at my own relay. If the result isn't the same, the server was doing the work.