I've gone back and forth on whether relays should be infrastructure or communities, and by now I'm firmly in the "infrastructure" camp. They should be a boring implementation detail that users should ...
well, time to go either back or forth again, because you are wrong.
But the response needs an article i notice.
TLDR for article not yet written:
>You have: Things(events), People(Npubs), Places(relays).
>''To Nostr'', on the read side, is to query, and you can play around with the specification surrounding things, people and places in that query depending on what it is you looking for/want.
>But you will always have to specify either people or location at least to avoid spam.
> When specifying authors/npubs, what relays should be automated/outbox.
> When specifying location, user has to have awareness of places/relays to begin with.
>> people being aware of location/relay is NOT an issue, people understand websites just fine for example, all they need is an intuition for the new paradigm.
@grimoire does it best. Clients (all clients, from a read perspective) are just renderboxes for queries (or spells). A ''feed'' is just a spell that is being cast. Performing the spell should obviously be automated, but constructing the spell should be something most users CAN do, or at least understand. The nice things about queries/spells/feeds, is that they can be exchanged.
Relay feeds are just a simple type of spell, so are follow feeds; either being location or people based respectively.
You are a wizard harry, a wub wub wizard.
Nostr.
But the response needs an article i notice.
TLDR for article not yet written:
>You have: Things(events), People(Npubs), Places(relays).
>''To Nostr'', on the read side, is to query, and you can play around with the specification surrounding things, people and places in that query depending on what it is you looking for/want.
>But you will always have to specify either people or location at least to avoid spam.
> When specifying authors/npubs, what relays should be automated/outbox.
> When specifying location, user has to have awareness of places/relays to begin with.
>> people being aware of location/relay is NOT an issue, people understand websites just fine for example, all they need is an intuition for the new paradigm.
@grimoire does it best. Clients (all clients, from a read perspective) are just renderboxes for queries (or spells). A ''feed'' is just a spell that is being cast. Performing the spell should obviously be automated, but constructing the spell should be something most users CAN do, or at least understand. The nice things about queries/spells/feeds, is that they can be exchanged.
Relay feeds are just a simple type of spell, so are follow feeds; either being location or people based respectively.
You are a wizard harry, a wub wub wizard.
Nostr.
1❤️1❤️1
