The difference is that because they expose this very simple compatible interfaces the access to these websites becomes very programmable and allows clients to do crazy things like connect to a bunch of different websites and fetch only a specific common part of them, then mash these things together, fetch other related things from other websites and display the result (plus a ton of other possibilities).

Reply to this note

Please Login to reply.

Discussion

Instead of having little "trending" sections at the corner of apps or stuff like that we could just have some configurable (with defaults perhaps) relay feeds.

You don't need Nostr for that. People do it without Nostr already. They use bits of design, code, load data. Why the hell would I need Nostr for this if I still have to monitor everything myself anyway.

I am not aware of people doing it at all, so I have to assume you have the wrong "it" in mind. What are you thinking about here?

I am talking about automating following updates from people on different websites (relays), automating fetching opinions about some other thing from different relays, automating publishing to different relays, automating discovering new content and new relays etc.

Also let me know what do you think Nostr is good for then, and why you're here.

Nostr is good in situations where you need to transmit some stuff through a relay without asking anyone's permission and without any guarantees of delivery or receipt.

Sad answer, for a moment I thought this could be a fruitful discussion, but you didn't even answer my other question.

I understand that your vision of Nostr is broader 🤔 But every time I want to use Nostr somewhere, I just don't see the point in it. Right now I want to launch an internet radio, and it will have Nostr, but it's not needed there at all. I'll just add it for the sake of it, but it won’t provide any real benefit.