Nostr design

[metacatdud]

Would you like to keep the current nostr design?

I am asking because I have my doubts about the current design. I simply don't think storing data on the relay is a good idea and also don't think the current approach can scale altogether. I am trying really hard to see what other people see but I simply can't :( and idk if it's because I am unable to get it or simply because is nothing there.

It happened to me quite some times to try to read a long post and encounter "missing content" because that was probably published to another relay or removed, idk. Overall content feels pretty inconsistent. I think that is the reason each client ended up having its own relay as primary :) and this, in my books, beat all the purposes: for having this all together, for the idea of a relay, for the idea of generic, and the idea of censorship for that matter.

I think a relay should do exactly that, relay information to someplace else: another client or another app.

Another thing is I think there are some parties missing in nostr such as the user. There are not only clients and relays, there are users, clients, and relays. This is why as time passed adding your private key directly to the client didn't feel like such a good idea. You cannot trust the clients blindly.

The event body was designed for social media although now some people think it can be used for multiple purposes it cannot. Since I have joined I think the tags lost in part their meaning. The tags suppose to help an event find other things related to it, but at this moment I don't think that is the case. I was never been able to see the need of such tags

Strictly from my PoV, I think such a relay can have multiple purposes and benefits:

It can be public: Any app can subscribe to it as long as relay resources permit that.
It can be private:

• You can have a personal relay at home exposed to the internet via a ddns or use smth like wireguard or tailscale to access it
• The city hall can have such a relay underneath which a citizen can access its data or whatever information needed
• The "Insert country here" car registry relay where users can come with VIN numbers and check the cars

The relay will have these simple features and characteristics:

• Be an enabler by being a gateway for whatever apps
• Be an app store: Expose public apps so a client can search and use those apps
• Be generic
• Can be accessed by users/clients the old way: HTTP, TCP, or this very protocol

This might unlock several things such as pay-as-you-go/subscription:

• You have a relay with high availability setup professionally on a cloud for example and I have an app. I want to deploy that app in my home network and hook it to your relay and use it privately and for that, I will pay you a monthly fee. let's say I have limited infrastructure skills and I don't want to bother.
• I have a small relay and I want to let my friends use it for a pay-as-you-go file transfer.

Right now there is no way to create incentives in any way for anybody. With the suggestion above anybody can benefit.

• The relay owner can charge for what they see fit: traffic or app hosting
• The app creators can monetize exactly like they do today. Build the app take the cash :)
• Ordinary users can pay for what they want, how they want.

If we want to fully step into the "integration" era at least let's do it wisely, simply and clearly.

Curious to hear your thoughts on this :)

---

edit:// about event tags
edit:// typos