nos.lol is run by nostr:npub1nlk894teh248w2heuu0x8z6jjg2hyxkwdc8cxgrjtm9lnamlskcsghjm9c (a generous nostr OG). It has nothing to do with nos.social, a client nostr:npub1wmr34t36fy03m8hvgl96zl3znndyzyaqhwmwdtshwmtkg03fetaqhjg240 (a legend) and a team work on and their associated relay is relay.nos.social.

You can learn more about their OPTIONAL content warnings here: https://nos.social/tagr-bot

When you enter your npub and click join it shows the price but its 18,888 sats (or $14.99 if you pay in fiat) and it includes 1 month of https://filter.nostr.wine

🫂🍷

nostr:note1pydljw887ntqt6emxkhweazpsnlfqsjkkezcjuddq9y4dmyp5rjqt5agws

Yes - that’s basically the only thing I can come up with too. But still not everyone will be invited or be willing to pay so it seems incomplete.

But if you filter replies by WoT, how will you ever discover new users outside of your graph?

It’s great for browsing global but seems harsh for replies.

I think it’s going to be a challenge. I am actually fairly bullish on the network filtering side as part of the solution but unfortunately can’t use it for our aggregator. There are ways to circumvent it but it is easier to fingerprint connections than you might think, even with multiple IPs/ASNs.

I think relays will use social graphs based tools a lot but I’m not sure how to deal with new users. They will end up being very hard to discover if we apply strict rate limits/reduce their visibility until they gain followers/engagement.

We could encourage them to pay to “skip the early reputation line” but I don’t think PoW will prevent spammers. There needs to be a way to onboard without cost though. Perhaps some type of vouching from existing “reputable” users. Still can be gamed though. Lots to consider.

Hi! Happy to try to help you. I’m not sure exactly how the wallet selector works in Amethyst but maybe nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z can help.

In terms of paying for the nostr.wine relay directly - you can also go to https://nostr.wine and make the payment there using whatever wallet is most convenient. You can also copy/paste the lightning invoice elsewhere as needed.

Kind of. There are specs and there are blog posts and there are also existing implementations to review - but there isn’t a one size fits all solution, its more of a concept.

NIP-65: https://github.com/nostr-protocol/nips/blob/master/65.md

Mike Dillger’s post: https://mikedilger.com/gossip-model/

Hodlbod’s post: https://njump.me/naddr1qvzqqqr4gupzp978pfzrv6n9xhq5tvenl9e74pklmskh4xw6vxxyp3j8qkke3cezqq2nskt2w9vx6dznfdvj64rpw4mk5nmxf3v9xsd0gdy

Improving now. Seems to be getting pummeled by old events but mostly holding up. I’ll keep an eye on it.

Investigating increased latency on one of our US mirrors. It is still responding to notes just a bit slow (so may timeout with your client).

Yup, I’m sure we will get there. UI is very important here but also thinking about the relay side.

We need to prevent events/purge them, not just keep them from being seen otherwise spam becomes expensive to host eventually.

Well it depends. If you’re running the public relay that is being spammed, you can see what IP(s), ASNs, user agents, etc the spammer is using and rate limit on the network side.

If you’re an aggregator like filter.nostr.wine that doesn’t have that network view, then it’s MUCH more challenging. You need to focus more on the content/pattern of the messages and reputation of pubkey posting them.

Glad to hear that!

Primal uses their own proprietary cache to load most of their client so that makes sense.

Yes but it’s still all whack-a-mole. The best filtering is on the network level and for aggregators that don’t have access to the connection info it is challenging.

The only long term solution I can come up with is npub reputation where you face very strict rate limits initially.

Right - but it’s back to the same Fiatjaf experiment of months ago.

If the users didn’t rebroadcast it to large relays your reach would’ve been drastically impacted. Scaling via outbox requires the reach to happen without the rebroadcasting (so that all relays don’t end up storing all the same notes) so this feels like celebrating a fake win.

Hahahahah this is awesome nostr:note1p53p3m46wzwedr7lf48els77xd5ea7sy20659gp24nzcy7s9f82q3fvqw0

We usually tell people to use both since nostr.wine has regional mirrors and is faster, but notes do propagate to both so you can do that if you want.

There are benefits but they require performant clients (that don’t just connect to whatever relays they want) otherwise you won’t notice. If I run Damus or Amethyst and use only nostr.wine/filter.nostr.wine the speed is genuinely unreal compared to pulling the same notes from 10+ public relays.

Try this for a week and see how quick it is. After that check your battery use + data consumption. And all that is before you even use the built in (optional) WoT to browse global of 10+ large free relays (not all clients provide WoT out of the box).

This note is bothering me because the spreading around part is not the outbox model - it’s actually the opposite. It’s the “old school” broadcast model.

Outbox would be everyone reading it just from your relay, not rebroadcasting it all over the place…

So no problems? It gives you way more than nostr.wine, not sure why you think that. Have you read the readme? I get more than 75% of the notes I consume through filter exclusively, most users don’t pay for paid relays…