Let's say Nostr explodes and there are a million relays and the currently popular relays aren't important and I follow 3000 people and there is some overlap. Can that work in a browser? Wouldn't I needs more than the amount of websocket connections one browser will give me? #nostr #protocol
I agree. And I don't even think a large part of the Fediverse disagrees, just a large enough group that complains and makes it a big deal
In some ways Nostr is a decentralized and social CDN
Search implies someone is using an algorithm to filter results. Just wondering if the users want the relays to do that as well. Maybe. But I could see someone considering relays like they consider internet service providers and net neutrality. I suppose it won't be an issue if the concerns are kept separate and transparency is maintained. DVMs are just services (AFAICT) but they are requested and delivered within the protocol
I wonder if some feel relays shouldn't be involved with search and stay neutral, leaving search up to something like a DVM or other service. I guess as long as relays don't become consolidated and there is wide support for search, those arguments go away. Haven't really formed an opinion on it yet
ttps://www.techpolicy.press/the-word-censorship-has-an-actual-meaning-a-defense-of-content-moderation/
I'm curious in what case that a relay with less than 100% verification would be acceptable or is that a normal occurence even for reputable relays?
My top #newstr stories today
Guess it'll be Dan Dan Noodles for lunch today
Congrats!
"Choose your interests" has never made sense to me. I'm interested in anything I find interesting.
Only want to talk about #Bitcoin? That's BS. People also talk about Nostr
Thanks for the link. Hadn't heard of them yet.
I think they have one point right, a lot of companies might need to be hand held for a while. Micropayments has a reputation of "tried it" and "doesn't work" largely because the mentality in media is "brand loyalty"
Might take a couple years to come around
I've got newstr working decently well. Today's top story for me. Need to work on why it thinks Figma is an article. They are using og:type = article so I'll have to introduce more metadata into the filter 
Some thoughts about Nostr & Custom Feeds
A bunch of nostr apps have custom feeds, but theyâre oddly one of the few things which arenât reusable across apps. Over on bluesky, theyâve got 40k custom feed algorithms and itâs a really popular thing.
For example, hereâs a feed of just pictures of moss: https://bsky.app/profile/did:plc:x3cya3wkt4n6u4ihmvpsc5if/feed/aaacynbxwimok
In particular though, thereâs feeds for different takes on what should be for you, trending, top, etcâŚ
We donât have that in Nostr, and i wish we did. Iâm going to outline a way in which i might be possible for us to get there.
First off, weâve got to understand how the third party feeds work in bluesky. The way it works is that each user has a single PDS (think relay) where they post their content. That relay is then indexed, by a global index server (there can be multiple), which may or may not keep a cache of a users content.
An index is a third party service which clients can connect to and say, iâm bob and i want the feed âonly posts by bobsâ. That feed service does not keep a copy of the content, nor does it provide it to the clients. Instead when user Bob requests the âonly posts by bobsâ feed, it checks the user requesting, then itâs indexes of content, and returns an array of message idâs (hashes) for what it thinks is a good bobs feed. The clients then request that actual content from the relay (PDS) servers, or their caches. Thereâs even a service for no-code creation of custom feeds, skyfeed.app.
This would be pretty easy to make. A nostr relay service that instead of serving the full content, just lets you request a feed, and it would return message event idâs for the events in that feed. Youâd then go request that content from relays that are hosting content. We could do it with dynamic lists too, but then we wouldnât be able to customize it per user.
Iâd like an easy way for developers to make and deploy custom feeds without having to have the whole own nostr app the way they need to do it now. As an app developer, iâd love people to be able to build their own feeds without me doing the work of tight integration.
I know that Damus has nostrscript which does some of this in the client, but it only works on one nostr client, and hasnât really taken off yet. A server based solution might be a lot better. Something we can support that works with nostr, but lets people make many feeds.
Thoughts?
My projects are very much interested in this.
It seems to me that if a user is trusting a third party to create a filter, then they can trust the third party to be the author of the nostr events needed.
So if a client can look up an event authored by the feed service, that is indexed with a tag of the pubkey of the user requesting the feed, that event itself could contain list of events in the feed
And it could be indexed by any old relay.
So,
1. User indicates to client the feed service it wants to use by pubkey
2. Client requests event created by the feed service that has the users pubkey in a tag
3. The event contains the list if ids for the feed. If the event isn't there (the first request) I guess a DVM is needed to generate the initial file
4. Client requests those ids and displays to user
Anyway, it's a way to utilize existing relays
