Mazin

Used to play poker now I build things and fly planes.

🍷 relay: wss://nostr.wine
🎥 relay: wss://creatr.nostr.wine
👋 relay: wss://welcome.nostr.wine
Filter and API: https://docs.nostr.wine
Translations: https://translate.nostr.wine

Public Key

npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5sz

NIP-05 Address

_@mazinkhoury.com

NIP-57 Address

mazin@pay.nostr.wine

Profile Code

nprofile1qqsrmpp2lmx4u2fl9zmxy7fnwp9rlwxwz5a2j8tep2c376n494z2gtgpzpmhxue69uhkummnw3ezuamfdejsz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcu0p9vr

Publishing to

nostr.wine

relay.damus.io

offchain.pub

Author Public Key

npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5sz

Show more details

Last Notes

2024-11-04 19:23:03

- reply

In addition to the normal free relays we broadcast notes to we also follow NIP-65 which states:
“When broadcasting an event, Clients SHOULD:
Broadcast the event to the WRITE relays of the author
Broadcast the event to all READ relays of each tagged user”
However, we have to have some limits to avoid spamming notes out like crazy. As such, we only do this additional broadcasting to the first 5 tagged users of each note and only to a max of 4 “read” relays per npub.
Keep the questions coming! Happy to answer 🍷

2024-11-04 14:55:50

- reply

I believe it’s Vitor’s guide. #naddr1qq…cq4q

2024-11-04 13:36:15

- reply

Thanks Boston!
I am certainly not an expert when it comes to Amethyst relay settings but you are right about how filter works.
Filter reads from (and deduplicates) and broadcasts to a list of public relays so that you don’t need to make all those individual connections.
Filter also broadcast notes to 3 of the recipients (tagged users) NIP-65 relays.
Though filter will not accept notes directly from non-subscribers (and thus shouldn’t be placed in an inbox/outbox list, it will pick up notes that come through any of the public relays automatically.
Without knowing for sure, the way you’ve set it up sounds correct to me!
In case you need more info about filter there is a fairly long readme here: https://filter.nostr.wine

2024-10-16 17:35:10

Ooof after 5 days of fever I’m finally starting to come back to life.
I know I’m a bit behind on responding to people and new projects but I’ll be back soon 🫡

2024-10-11 13:38:34

- reply

Hey! I believe nostrudel has a setting somewhere that you need to enable somewhere for it to automatically AUTH to a relay. I’m not exactly sure where though.

2024-10-05 23:35:52

- reply

All over the US 🫡

2024-10-05 23:35:27

- reply

They wouldn’t let me :(

2024-10-05 23:26:23

Caught this bird ready to depart on my way out. https://i.nostr.build/9gaIgSfM74WEG1fT.jpg

2024-10-04 12:13:00

- reply

Yes, sounds correct to me! The filter.nostr.wine relay will stop serving notes to you/broadcasting your notes if your subscription expires.
The nostr.wine normal paid relay is still just a one time write access fee so that will keep working normally.

2024-10-03 14:34:01

First year in the books for 🍷 cellar.nostr.wine.
Thanks as always for your support @npub134l…elwh ! #note1th2…gny6

2024-09-29 00:47:02

- reply

😂 cheers 🍷

2024-09-29 00:42:26

- reply

🍷🫡

2024-09-28 17:33:16

Reminder: if you prefer to stay in your favorite nostr client, you can DM our bot @npub1fyv…sfuk for the same information! DM /help for a list of commands. #note1g8x…8qzp

2024-09-27 16:45:14

- reply

I was wrong - works fine for me. I was just using the wrong pubkey.
Yes, it must be this @npub1clk…pup9

2024-09-27 16:33:05

- reply

Hmmm - me neither, but yes it should. I’ll try to figure out why…

2024-09-27 16:14:03

- reply

What happened to my numbering…
After 3 comes 4 - you get the idea 😂

2024-09-27 16:12:33

- reply

The idea is to standardize everything so that nobody has to implement a bunch of proprietary APIs. I certainly get the appeal of that but the design is wasteful and slow.
Lots of the services “offered” by DVMs are just wrapping centralized services with more latency. For example, most search DVMs just use NIP-50 on one or more of the 3 search relay implementations. Using this instead of connecting directly to the relay(s) is so much more work.
With NIP-50:
1. Connect to search relay
2. Open search filter
3. Relay finds matching events and returns them
3. Display returned events
With DVMs:
1. Make a DVM request event
2. DVM makes NIP-50/search API request
3: DVM parses just the event IDs and returns a list of those in a nostr event
4. Client pulls response event and requests event IDs from all relays? Some relays? Only the NIP-50 relay(s) that supplied the DVM with the results?
5. Relay(s) finds matching events and return them
6. Client displays events
🤯

2024-09-27 15:58:10

- reply

We have over 100k “feedback” events from DVMs on our aggregator that just say something along the lines of “I’m processing your task”
Absurd waste.

2024-09-27 15:35:38

Just added a new “Members Area” on https://nostr.wine where you can view and manage your subscriptions/balances for Filter, Inbox, and Cellar! Click the “Sign In” button in the top right corner to access the page.
We will be adding additional settings and configurable options here in the future. Let me know if you have any feedback or issues.

2024-09-26 16:09:38

- reply

Lots to digest here but I’ll do the best I can without writing too much.
First, and most importantly, primal is not a normal nostr client that sources events exclusively from relays. They have their own caching relay that is not comparable with the protocol and they rely on it heavily for loading notes within the app. The network was recently under a spam attack that caused lots of problems for their cache. That could explain harsher rejection criteria for their relay or some of the missing content issues you’re describing.
- relay.nostr.band is an aggregator that reads from other relays so even if you do not write directly to that relay it will likely have your events eventually.
- relay.snort.social is a paid subscription relay, you have to pay to write
- nos.lol has some of your latest posts. Not sure when they appeared though.
I’m not sure about the other relays you tried. I think primal sets a random list of 10 which is a very poor way of doing relays selection. Lots of relays are slow, frequently offline, or outright broken.
I would encourage you to try another client first to see if that improves your experience. In addition you could consider adding a paid relay to improve your reach and loading speed. @npub1qlk…lf5y and I run a paid relay called nostr.wine so I am biased but don’t take my word for it - ask or look around for recommendations.
Welcome to #nostr I hope it get easier from here!

2024-09-25 23:14:39

- reply

Heh - we actually don’t log invalid form submission there because crawlers do it constantly. I can re-deploy it with temp logging there if we absolutely have to.
I put in your npub and I get the credit card page without any issues for several devices and different browsers.
If you’re using an nprofile or something instead of a valid npub - that would explain the error so thats why I asked.

2024-09-25 23:09:26

- reply

The follows+follows global filter is enabled by default. You can disable it by adding ?global=all to the end of your relay URL.
wss://filter.nostr.wine?global=all
We are going to make these options available via a new Members Area section on our website fairly soon as well. Let me know if you have other questions!

2024-09-25 23:07:55

- reply

The only validation on that form is that you’ve entered a valid pubkey (npub or hex). What are you putting in on the front page?

2024-09-25 20:40:40

- reply

Hmmm odd - must be a Brave browser issue. Just test on Chrome, IE and Firefox and all 3 worked.
Could you try another browser for me?

2024-09-25 20:31:25

Introducing Purgatory - our new spam evaluation engine for filter.nostr.wine. The newest addition to our nostr event data pipeline.
Here is a flowchart that @npub1qlk…lf5y @npub1qlk…lf5y made to illustrate how it all works:
https://i.nostr.build/61SaCp4c3Ns5TjZu.png

2024-09-25 19:09:32

Hi! They are completely unique and serve different purposes.
nostr.wine is a “typical” paid relay. You have to pay a one time 18,888 sats admission fee to be able to write to the relay but anyone can read from it.
filter.nostr.wine is a paid subscription service (5000-10000 sats per month depending on duration of purchase). Filter is a public/free relay aggregator with several additional features. Here are some of the highlights:
- Aggregates notes from the largest 20+ free relays
- Broadcasts your notes out to 10+ free relays
- Also broadcasts to your first 4 "write" relays and the first 4 "read" relays from the first 5 tagged users (NIP-65 list)
- Offers a (configurable) follows+follows filter for “global” view so you can explore notes outside of your immediate follows but still within your network
- Full text search across all aggregated events
You can learn more about the full functionality of Filter here: https://docs.nostr.wine/filter/readme #note1hqz…ut0g

2024-09-25 18:05:07

- reply

Damn that’s good to know.
I’m sure it’s coming to us eventually. We will def ban spammers as it’s against our existing TOS - but good reminder as that needs a rewrite too.

2024-09-25 17:52:29

- reply

Different pricing models for different relays is confusing and I appreciate that. We will eventually package all of them together but most of our relays (besides nostr.wine and filter.nostr.wine) are still early prototypes with pricing subject to change.
All of our payment pages, DM reminders, and NOTIFY messages (on Amethyst) say explicitly what service requires payment.
We offer 3 different ways to pay for any nostr.wine service: web, direct message, and NOTIFY message. The NOTIFY message is the cleanest (pops up on your client with an invoice) but is only supported by Amethyst.
I’ll add a “Members Area” to the website where you can login and check your wrote status on nostr.wine, time balances for filter.nostr.wine and inbox.nostr.wine, sats balance for cellar.nostr.wine, and translation credits for translate.nostr.wine.
Eventually we will also let you customizable relay settings for filter.nostr.wine in the member area.
If you want to build us a new website - send me an estimate! Every time I try to look for designers on nostr it’s 🦗

2024-09-25 17:41:04

- reply

Yes

2024-09-25 17:38:06

- reply

nostr.wine is a paid relay - you have to pay to write to it. Spammers aren’t willing to pay. We haven’t had a single one in 2 years.

2024-09-25 16:46:03

- reply

Who did you hear this from? It’s absolutely false 😂

2024-09-25 16:34:11

- reply

Incorrect sir, we support fiat as well.

2024-09-25 13:19:00

- reply

Hey 👋 welcome. I’m an instrument rated single engine pilot and fly a cirrus. @npub19mu…jnft is also a pilot and @npub16am…6569 a student pilot.

2024-09-24 21:09:51

- reply

Sounds familiar :)

2024-09-23 14:31:25

- reply

Strfry has a hardcoded filter size limit so that is the restriction you will encounter most commonly.
See discussion here: #note1rpa…jm4e

2024-09-23 04:00:27

Don’t give spammers attention or praise. They aren’t trying to make nostr better. It’s always the same narrative with these children. They only seek your attention.

2024-09-23 01:33:32

- reply

I’m not sure what you’re talking about. Our paid relay has no spam on it.

2024-09-22 18:42:08

Relay operators who don’t want to lose Sleepy use @npub1wsg…mlse #note1kws…5xlp

2024-09-20 02:33:51

- reply

One offs won’t make it out of our intermediary database.
The idea is to collect and evaluate multiple events (without losing them) before approving a new pubkey and distributing those events to the relay.

2024-09-20 00:14:54

- reply

We always figured we would need to build some type of “purgatory” db eventually but I’m pleasantly surprised by how enlightening it is out of the box.

2024-09-20 00:09:59

Doing some initial testing of our new event ingress pipeline tonight! It’s insanely cool and already yielding great insights.
Much easier to separate legitimate users from spam when you’re looking at 10 of their events instead of 1. #note1x34…n656

2024-09-18 15:36:00

- reply

Thank you friend! Appreciate the mind words.

2024-09-18 14:11:25

- reply

Yes, but the initial write plugin checks if that user was previously approved and if so auto accepts the note. So only “unknown” pubkey events are sent for secondary processing.

2024-09-18 14:08:50

- reply

Yes we don’t have IPs at all! It’s all event based analysis.

2024-09-18 14:02:45

- reply

We are using a write policy to send the notes to a separate application/db that handles the “purgatory” state. Then that application inserts events back to the relay as needed.
Would not be able to do it all within a write plugin.

2024-09-18 14:01:13

- reply

Always appreciate you, thanks for the answers. Seems like you have a pretty good solution going at least. So temp IP blocks only when many fresh pubkeys coming from one address. Could still cause issues for VPN users as you pointed out but at least better targeted.
Our problem is we don’t have any IP/network info on our aggregator so we have to make decisions based on only the events. I think the new system will work though.

2024-09-18 13:30:49

- reply

I get your concern about multiple relays sharing block lists - not sure if it’s really preventable but I understand.
Are you not doing any IP rate limiting on nos.lol? Only pubkey/content/report based? I know you request PoW from some new pubkeys too? Do they ever provide it?
Curious how much spam you’re seeing etc

2024-09-18 13:21:34

Free relays that allow and store unlimited spam will simply stop working long term. It is not an option to just ignore it and let the clients filter. #note1wjf…d208

2024-09-18 13:07:50

- reply

First, this is just our aggregator and filter.nostr.wine - not anyone else’s relay. Nobody is forced to use our aggregator but keeping spam off of it long term is more important to us than a slight delay in brand new pubkey discoverability.
If that #introductions hashtag is filled with infinite spam, you also will never discover the new user.
The advantage of this over WoT based relays is as soon as the user reveals themselves to be legitimate (could be after just a few minutes of their original event) none of their old content is lost.
There is going to be some cost to being discovered as a brand new pubkey on an open protocol where there are no account creation limits. We think this solution is the least harmful.

2024-09-18 13:01:49

- reply

Thank you 🫡
I’m hoping noteguard will help save some drowning free relays.
We are going to publish our “purged” database and let people query it eventually. Perhaps that could be another way for free relay operators to get spam insights. We don’t have any network layer information since we are aggregating from other relays so it’s just going to be event based analysis.

2024-09-18 12:57:12

- reply

This does not have anything to do with nostr.wine as it requires a payment to write and has yet to have any real spam issues!
This is all about our free relay aggregator and filter.nostr.wine.

2024-09-18 12:54:34

The problem: when a brand new pubkey starts sending events, it can be difficult to tell immediately whether they are a legitimate user or spam.
Our solution: accept all new user notes temporarily in a separate database. As they send events, we continually evaluate their behavior based on several rules (and eventually by a trained model) and approve/block the pubkey.
If approved, all of their old events get added to our aggregator relay and the user is immediately discoverable. Their future notes will also go directly to the relay. If blocked, the events are sent to a purged database (for transparency and evaluation) and never reach our relay.
Still an early WIP but coming along! It doesn’t solve all the issues but it is a massive improvement on our current rules. #note19kp…6nxp

2024-09-18 12:30:58

- reply

The website is a bit confusing, I agree and we have a few ideas on how to improve it. The unfortunate reality is nobody reads anything.
The “NSFW DM” is a perfect example. Users only receive that DM when connecting directly to our creatr.nostr.wine relay. Since that relay has paid content that is both SFW and NSFW, part of our user onboarding is to ask the user if they are of age and if they wish to enable NSFW content. We do that when you log in through our website and nobody has ever complained about it. And no, it’s impossible to have received this DM if you didn’t connect to the relay. If you never added it to your relays, your outbox-enabled client found it without your permission - blame them.
The DM is simply a way to adjust that setting from directly within your nostr client. Our entire goal of building Creatr the way we did is that so you can interact with it completely within the nostr client of your choice, without ever having to use our web client. Since it’s caused some ridiculous misunderstandings, we’ve removed that onboarding DM.
The message is quite clear but nobody actually reads the entirety of the message. Same is true of our payment reminders for nostr.wine. They say explicitly that they are for filter.nostr.wine.
There is plenty to improve and we are working on it. We also have Cellar (pay per post) and Inbox (subscription) so we are going to need to simplify our pricing at some point or offer a bundle. This is still the beginning :)

2024-09-17 19:09:36

- reply

Hi! Our pricing model is a bit confusing and we are planning on overhauling the onboarding process soon.
Here’s how it works:
nostr.wine is a high performance “normal” paid relay. It is free to read, and 18,888 sats (one time fee) to have write access.
filter.nostr.wine is our subscription product. It is a separate powerful free relay aggregator that provides a relay-side global filter (your follows+their follows) as well as unfiltered replies to notes (for discovery of users outside your network). With the 18,888 admission fee to nostr.wine, you get 1 included (free) month of filter.nostr.wine.   Additional months for filter.nostr.wine can be purchased here: https://nostr.wine/add-time%E2%80%A8%E2%80%A8There are large discounts for buying more months at one time. The normal price is 10,000 sats/month, the biggest discount gets that down to 5,000 sats/month (~$3). Let me know if you have other questions!

2024-09-17 15:19:40

- reply

No I’m the real one 😂
Do I have impersonators? I didn’t think I was big time enough for that

2024-09-17 14:46:13

Started working on our new spam protection for 🍷 filter.nostr.wine this week. Our repeat message filters and rate limiting helps but still leaks a lot.
We expect the new solution to be much more effective AND create less false positives. More details soon!

2024-09-13 15:17:15

- reply

Let me know if you have any other questions!

2024-09-10 23:10:40

- reply

Thank you kind sir 🫂🍷

2024-09-10 23:09:39

- reply

😂😂😈 I like to think I’d be a better spammer than this if I applied myself

2024-09-10 12:50:41

- reply

Hmm - don’t see that pubkey on filter either. I’ll keep looking! Let me know if you see more.

2024-09-10 12:37:26

- reply

I see the first one but not the 2nd. Do you have any that are actively still posting?

2024-09-10 12:28:33

- reply

Link me a note? Not seeing them…

2024-09-10 00:12:22

- reply

Hey! nostr.wine is a one time admission fee but filter.nostr.wine has a monthly subscription. You get one month of filter with your purchase.
Let me know if you have other questions!

2024-09-09 01:32:11

- reply

🫂🍷

2024-09-08 15:02:13

- reply

Haha no there is someone spamming nostr relays at the moment just replying to every note from new npubs quoting the original post.

2024-09-08 13:34:31

- reply

nos.lol is run by @npub1nlk…jm9c (a generous nostr OG). It has nothing to do with nos.social, a client @npub1wmr…g240 (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

2024-09-07 23:04:45

- reply

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

2024-09-07 22:51:04

- reply

🫂🍷

2024-09-06 16:47:06

- reply

#note1pyd…agws

2024-09-06 16:44:48

- reply

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.

2024-09-06 16:32:02

- reply

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.

2024-09-06 16:21:22

- reply

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.

2024-09-06 16:12:53

- reply

Hi! Happy to try to help you. I’m not sure exactly how the wallet selector works in Amethyst but maybe @npub1gcx…nj5z 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.

2024-09-06 16:04:29

- reply

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

2024-09-06 15:34:27

- reply

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

2024-09-06 15:13:33

- reply

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).

2024-09-06 14:55:43

- reply

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.

2024-09-06 14:53:35

- reply

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.

2024-09-06 14:50:50

- reply

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

2024-09-06 14:45:43

- reply

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.

2024-09-06 14:40:53

- reply

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.

2024-09-06 14:27:33

Hahahahah this is awesome #note1p53…vqw0

2024-09-06 14:26:42

- reply

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).

2024-09-06 14:19:46

- reply

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…

2024-09-06 14:17:03

- reply

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…

2024-09-06 14:06:24

If you’re looking for temporarily relief from ReplyGuy now is a great time to try https://filter.nostr.wine - keep your network view/reach without all the noise.
A few are still leaking through but our rate limits/repetitive message filters are keeping the majority out of sight. #note1u5f…xc0z

2024-09-06 14:00:39

- reply

I believe for RIPE an alternative to being an LIR is to have one sponsor you. I believe IPXO, for example, does this for marketplace customers who want to move to owning address space.

2024-09-06 13:57:16

- reply

Yes ARIN/RIPE have slightly different rules. I already went through the whole process and am on a waitlist for a /22 via ARIN.
Took only a week or so from start to finish but of course you need a justification and a business.

2024-09-06 13:53:29

- reply

Doing our best! There are def some sneaking through (on filter only of course) but majority is being caught by rate limits/repetitive message rules.

2024-09-06 13:49:19

- reply

What kind of problems? I’ve been using exclusively filter to access any non nostr.wine relay for 2 years!

2024-09-06 13:35:24

- reply

Yes, replies are always unfiltered on filter.nostr.wine. Only the global feed uses your WoT so that you can see new users when they reply directly to you.
Our repetitive message filter/rate limits are catching a lot of them but it won’t be perfect. We err on the conservative side!

2024-09-06 13:34:11

- reply

Our plan was to subsidize nostr.wine with our other services (most notably filter.nostr.wine) and so far it has worked well. If some day this isn’t sustainable we’ll change it.

2024-09-06 13:17:07

Back when we started 🍷 nostr.wine, I signed up to basically every paid relay that existed at the time (20+). I think only 3 of those still exist today. It’s easy to turn a relay on and collect payments but it takes effort and a plan to keep it running reliably for years.
nostr.wine isn’t going anywhere 🫡 #note1qm6…73pm

2024-09-05 12:11:42

- reply

Slightly different problem but also a problem. There are two different issues here. First is the absolute size of your follow list. If it exceeds the max event size of a relay then your full follow list will be rejected and you won’t be able to “update” your list anymore. It happens to people today on most relays between 1500-2000 follows.
The second is how your client queries for events from people you follow. In this case most clients tries to stuff all the pubkeys you in to one request filter from your relay(s). If the request filter is larger than X (relay operator chosen limit) the relay will simply close your REQ without responding and you won’t see any events.
Instead, clients will need to (some already do) split your follows up in to smaller chunks and send multiple requests. The second problem is considerably easier to solve than the first.

2024-09-05 11:51:06

Just to be clear: there are better ways of doing this but as far as I know they are not widely used (yet!)
- You can paginate the follow list request using since/until with timestamps
- Relays can support COUNT https://github.com/nostr-protocol/nips/blob/master/45.md
- Clients can outsource pagination/aggregation to DVMs https://www.data-vending-machines.org/kinds/5400/ #note1swd…tglu

2024-09-05 11:38:20

- reply

For the nostr historians out there, I was wrong, it was 1.5y ago. Here is the original: #note1fzn…hfhl

2024-09-05 11:28:54

- reply

Small typo: tried to add the “or 100 relays” part but didn’t update the upper end of range (500-50000) instead of 5000, but the non-unique argument is the same.

2024-09-05 11:24:50

I assume you have received several good explanations by now, but in case you haven’t I wrote this almost 2 years ago:
How do we check “follower count” on nostr?
1. Your client sends a request to all your connected relays asking for contact lists that follow you
2. Relays answer back with the events requested
3. The client aggregates the event total, de-duplicates, and displays the count
Each relay has a set limit on how many stored events it will return per request. For some relays it’s 500, others 1000, some as high as 5000. Let’s say for simplicity that all your public relays you query use 500 as their limit. If you ask 10 relays for your followers the max possible answer you can get is 5000. In reality you won’t ever get 5000 unique responses, you’ll likely get something closer to the same 500 from each relays you query. That won’t change if you have 20,000 followers or 100,000 or if you query 100 relays instead of 10. You may get back a “different” 500-5000 each time, but you’ll still cap out at 5000 (non-unique) because that is the most events your client will receive.
Primal, nostr.band, and other aggregators that store counts in their own DB will always show different numbers than clients reading directly from relays. Generally speaking, neither number is correct! #note1rg3…yq75

2024-08-31 16:50:48

- reply

Yes sorry about that - we are moving to a new onboarding process but haven’t finished it yet. I’ll DM you some details!

2024-08-30 23:20:52

- reply

We have a project called @npub1cre…feh6 that is still an early beta but the idea was to make an interoperable patreon-like relay. There is still some friction on the payments/relay authentication side but its a working prototype that will evolve!