Really? That’s not how I interpret it.
Relay feed to me, I select a relay, and only see notes from that relay.
Like how Jumble started. It was amazing, the. Something happened and it became confusing.
Discussion
right, but what is the point of viewing a relay as a feed? It would only make sense if it’s a curated feed of people. An algo.
Ah. I get your point.
That could be a good way to interpret it.
To me it’s to filter out the noise.
For example, if I only want to see posts from bitcoindistric.org folks whitelisted on the relay. I tap my nip address in Damus and see my friends notes.
Same with nostrarabia.com, one click and I’m with my group isolating all the noise.
I do the same thing in Damus universe relay filter. But the UX is not really designed for the purpose.
I guess you can call that algo. It’s a filter for me.
Not necessarily. A festival is a good example: the venue operates a relay & only accepts notes posted by people who have write access via invite code on their ticket or something. People are posting & sharing what's going on at the venue with eachother & only viewing eachother's notes, but they can still switch to their home feed to see if the babysitter is actually playing on their phone instead of cooking dinner.
Meanwhile, anyone following the attendees is also seeing what is being posted... cuz outbox. They think it looks fun, want to attend the next festival, whatever... they can reply & stuff... cuz outbox.
The venue doesn't have to worry about partnering with a client or having their own app and all that. They can wipe it & reset for the next night. Attendees don't have to worry about installing another app. They can just sign in & use whatever relay feed supporting app they use & go.
Any place or thing could have its own live social media feed instead of or in cunjunction with a typical website. It's kind of curated but not really. Things just aren't that far along yet. Curation, algos, and interesting ways of interacting are a good start. Sorting & discovering needs work but there needs to be enough relay diversity to do it.
a curated set of notes, like wss://relays.land/spatianostra;
an algorithm that fetches data from other relays and sorts them somehow, like wss://algo.utxo.one;
a relay where people intentionally publish exclusive notes to, like wss://imp.relays.land or wss://topic.relays.land/praise;
a semi-closed community, like wss://pyramid.fiatjaf.com;
a personal utility service, like wss://bookmarks.relays.land or wss://personal.relays.land;
a set of people self-selected according to some filtering criteria, like wss://nostr.wine or wss://nostr.land;
a semi-open public relay with intentional directed posts but strict moderation, like wss://relays.land/bitcoindev;
Don’t bother, been asking Will for topical relay explorer for over a year, he doesn’t it.
there’s a round about way of doing it in global by turning off all relays except for the one you want to see, but very bad UX
I very much get it, thanks. which is why our meetings this morning was about the best way to add it that isn't confusing.
I think you are misunderstanding what I'm saying. I am not saying its a bad idea, i'm trying to reverse engineer what users actually want vs what relay explorer/selection is affording as a feature.
I didn't think you were saying it was a bad idea, you were one of the first people to talk concretely about custom relay feeds if I remember correctly.
I was just using the opportunity to make a list.
There are probably a ton of other use cases, like internal relays, temporary relays for conferences and closed events, more utility use cases like I don't know you publish something there and the relay prints your message and mails it to you (silly example, this doesn't even make sense as a feed).
I'm trying to have more crazy ideas, but I bet other people will have them better once the possibility is unlocked in their minds. But also only in the scope of the relay classes listed above we already have enough room to fulfill many more interesting use cases.
Just communities and curation are already enough to justify having relay-feed-capable clients. The curation case is infinitely useful. Almost every one of the "whatever-on-Nostr" use cases (music on Nostr, business listings on Nostr, geocaching on Nostr, uber on Nostr, wikipedia on Nostr, livestreaming on Nostr etc) would benefit drastically from having curated relays, and it could become a profitable thing eventually, as I probably wrote on nostr:naddr1qqyrze35vscrzvfcqyghwumn8ghj7enfv96x5ctx9e3k7mgzyqalp33lewf5vdq847t6te0wvnags0gs0mu72kz8938tn24wlfze6qcyqqq823c0z85e2 (but I didn't reread). There is also the case for "publications"/magazines which I've seen many people talking about and to me that is a textbook example of a curated relay.
Many of the DVM use cases could also be reframed as relays with special functionality and they would work much better and be simpler.