Mazin

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

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

Public Key

npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5sz

NIP-05 Address

mazinkhoury.com

Profile Code

nprofile1qqsrmpp2lmx4u2fl9zmxy7fnwp9rlwxwz5a2j8tep2c376n494z2gtgprpmhxue69uhhwetvvdhk6efwdehhxarj9emkjmn9y3e29w

Publishing to

welcome.nostr.wine

Author Public Key

npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5sz

Show more details

Last Notes

2025-04-25 02:10:44 GMT

Experimental support for multi-user AUTH is now available on nostr.wine and inbox.nostr.wine 🍷
https://github.com/nostr-protocol/nips/pull/1881

2025-04-09 00:29:25 GMT

- reply

Yes - that challenge is exactly why we needed to evolve our approach. If you’re interested, this photo shows how our “purgatory” data pipeline works today.
Welcome only looks for new user posts within a very short period of time after the creation of their kind 0 event. Since their posts are often stuck in purgatory during that period of time, welcome misses their posts when they are later added to our relay. I could make changes so that these new user events are also sent to the welcome relay at that time.
https://i.nostr.build/61SaCp4c3Ns5TjZu.png

2025-03-27 12:15:07 GMT

Filter.nostr.wine was just down for ~100 minutes. The issue has been resolved and everything is back up. Apologies for the inconvenience.

2025-03-20 14:46:19 GMT

- reply

Thanks for the kind words Dawn! We appreciate you 🍷

2025-03-04 15:45:03 GMT

- reply

I can manually delete your events if you’d like but without deletion requests it’s possible for them to be rebroadcasted and stored again.

2025-03-04 15:22:56 GMT

- reply

We may eventually but I don’t have any timeline atm. You can send individual delete requests for events.

2025-02-25 15:38:09 GMT

- reply

What model are you using for nsfw detection? We’ve tried a few of the lightweight ones and found them to be really poor on average.

2025-02-25 15:31:23 GMT

- reply

Hahah yes but if you read the actual proposal you can’t believe any of these “possibilities”.
The entire purpose is to simple reduce an extra roundtrip from the onboarding process. Instead of having to leave our site, go to your NWC wallet, create and copy a URI, then come back and paste it to us all you have to do is scan a QR code from our website and approve the request on your wallet.
Do you really think this flow improvement killed mutiny? Who knows indeed lol

2025-02-25 15:18:38 GMT

- reply

The implementations that worked at the time were listed here: https://github.com/nostr-protocol/nips/pull/851#issuecomment-1879569550

2025-02-25 15:09:50 GMT

- reply

Well 2 of those implementations were Mutiny Wallet run so the proposal has died with them it seems. They were the only wallet provider that supported it. Alby used to say they would implement it (and presumably would if it had been merged). Now it feels fully abandoned.
We have just moved on with using the flawed onboarding flow and as such virtually no services interact with NWC at all.
I don’t think it can be merged as is anymore unfortunately. I think Alby is working on some other flow now 🤷‍♂️

2025-02-25 14:39:42 GMT

- reply

Ben did a lot of nagging back when he was actively trying to get it merged. He responded to a lot of feedback and kept pushing it for months.
There isn’t even much constructive feedback in the thread just a lot of confusion. The proposal was (more or less) ready to merge from the beginning and was quickly supported by multiple implementations (both on wallet and service side).

2025-02-25 14:23:09 GMT

I’m sad https://github.com/nostr-protocol/nips/pull/851 never got merged. We built a nostr.wine NWC service that relied on this improved onboarding flow in December of 2023. At the time Mutiny was leading the effort.
I don’t understand why it wasn’t merged then when we had 4 working implementations. It is the only reasonable NWC on-boarding flow I’ve seen for services (like nostr.wine).

2025-02-06 17:59:17 GMT

I need to go clean the plane but having some serious motivation issues.
What’s your strategy for getting out of the house on lazy days?

2025-02-06 17:47:13 GMT

- reply

Heh - actually the regex in the php library doesn’t even validate if there is a reason phrase, only that there is a space after the status code. That regex leaves a lot to be desired and it’s an easy fix for them!

2025-02-06 17:39:30 GMT

- reply

We took a long look at this today. There are multiple layers of our tech stack that do not support reason phrases anymore. There are some ways for us to hack it back in, but given that reason phrases are optional and not required by any other client or the spec, this would be a considerable amount of work with limited gain.
It seems like this php library doesn’t do anything with the reason phrase besides check that it exists so perhaps it should be made optional there?

2025-02-03 18:25:25 GMT

https://media1.tenor.com/m/DKB4fw7EACwAAAAd/true-correct.gif #note1dlm…5g9q

2025-01-30 23:25:43 GMT

- reply

https://youtu.be/_3gD_lnBNu0

2025-01-30 14:54:35 GMT

Still trying to process last nights DCA mid-air. Horrific. https://youtu.be/CiOybe-NJHk

2025-01-15 02:27:35 GMT

- reply

Yessir 🫡 🍷

2025-01-11 23:11:12 GMT

- reply

Thanks for the kind words! Let me know if you have any questions @npub1tla…x3y7

2025-01-06 15:01:45 GMT

Purgatory helps us keep filter.nostr.wine free from spam while aggregating events from large free relays.
New users still have a way in and we preserve their events in purgatory so that when they are approved all their event history is immediately available on our relay. #note1dcq…edem

2025-01-05 16:15:23 GMT

- reply

https://www.nytimes.com/2024/11/27/upshot/airlines-flight-times-padding.html

2025-01-04 00:59:47 GMT

- reply

Let me know if you have any issues! It’s been stable for nearly a year now I think.

2025-01-04 00:49:02 GMT

👋 https://i.nostr.build/q3RTiGkGGvSrpjCO.jpg

2025-01-03 14:58:59 GMT

- reply

Brief restart in progress to update that machine now that we are talking about it :)

2025-01-03 14:53:47 GMT

- reply

There is also a known bug where if the application breaks for any reason it triggers an offline/online alert for all the relays. Usually less than one a month. Besides that it’s been mostly stable for a year.
I’ll fix a few things when I get a chance though! Let me know if you have other ideas or issues.

2025-01-03 14:10:57 GMT

- reply

@npub1wsg…mlse is free 😉

2025-01-01 01:50:35 GMT

- reply

🍷🍷

2025-01-01 01:50:28 GMT

- reply

Appreciate that - thanks for the support 🍷

2025-01-01 01:49:50 GMT

- reply

🍷💜

2024-12-24 23:38:37 GMT

Merry Christmas and Happy Holidays friends. 🎅🎊

2024-12-20 15:55:32 GMT

- reply

Thanks Daniel. @npub1k6f…tryn I’ll take a look for you in a few min and send you a DM.

2024-12-10 00:52:36 GMT

Good evening nostr. Climbing through 19k feet this evening on my way across the pond ✈️

2024-12-03 12:17:54 GMT

- reply

This design has been working well for our aggregator. Not a solution for every public relay of course.
#note1dcq…edem

2024-11-20 23:05:22 GMT

- reply

Welcome 🍷

2024-11-11 21:55:27 GMT

🍷 Glad to hear you like it - sorry it took us so long! #note1qhc…usax

2024-11-05 19:48:58 GMT

- reply

Thanks! It’s my least favorite part so it gets the least attention unfortunately.

2024-11-05 17:18:44 GMT

- reply

Yes, what @npub1fjq…leku said! And now you can Sign in on https://nostr.wine and see your dates/balances of all our relays.

2024-11-05 16:59:53 GMT

- reply

It is a one time write access fee.

2024-11-04 19:54:11 GMT

- reply

Honestly the only Mac/iOS app I know of that works well with AUTH is Nostur. https://github.com/nostur-com/nostur-ios-public
Damus works ok for most things but it does not handle AUTH race conditions or CLOSED messages correctly so it loses initial filters that it doesn’t retry making the notifications/DMs inconsistent.
I can’t stand any of the web clients tbh.

2024-11-04 19:23:03 GMT

- 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 13:36:15 GMT

- 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-30 13:42:56 GMT

One of our hosting providers is having a massive west coast outage. We are trying to get more information from them at this time. They are total clowns.

2024-10-28 14:45:32 GMT

Rolling restarts across a few services in progress for updates!

2024-10-28 03:12:28 GMT

- reply

filter.nostr.wine is a subscription aggregator/broadcaster relay with an optional WoT global filter. https://docs.nostr.wine/filter/readme
nostr.wine is our regular paid relay. Free to read, pay to write.

2024-10-19 01:38:45 GMT

- reply

RelayGuardian.com - its free too!

2024-10-18 14:43:00 GMT

- reply

And yea, the spacing thing is more of a bug than “clients not showing kind 1 notes the same”

2024-10-18 14:41:46 GMT

- reply

I get your frustration, but even where to display images is a client choice. Some users prefer them in-line and some users prefer them in a carousel at the bottom. Different clients will suit different needs.
If nostr requires client conformity to succeed it is a failure out of the box.

2024-10-14 12:35:46 GMT

- reply

Thanks! Sorry about that @npub1y2s…vr89 - I broke the form a while back and got distracted with other things. I’ll DM you.

2024-10-05 23:35:52 GMT

- reply

All over the US 🫡

2024-10-05 23:35:27 GMT

- reply

They wouldn’t let me :(

2024-10-05 23:26:23 GMT

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

2024-10-03 14:34:01 GMT

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 GMT

- reply

😂 cheers 🍷

2024-09-29 00:42:26 GMT

- reply

🍷🫡

2024-09-27 16:45:14 GMT

- 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 GMT

- reply

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

2024-09-27 16:14:03 GMT

- reply

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

2024-09-27 15:35:38 GMT

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 GMT

- 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 GMT

- 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 GMT

- 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 GMT

- 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 GMT

- 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 GMT

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 GMT

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 17:41:04 GMT

- reply

Yes

2024-09-25 13:19:00 GMT

- 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 GMT

- reply

Sounds familiar :)

2024-09-23 04:00:27 GMT

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-20 02:33:51 GMT

- 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-18 14:11:25 GMT

- 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:02:45 GMT

- 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 13:07:50 GMT

- 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 12:54:34 GMT

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 GMT

- 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 GMT

- 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 GMT

- 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:53:10 GMT

I wanted to clarify how filter works because there has been some misinformation.
By default we use your WoT (follows+follows) to filter the global feed our subscribers see when they connect to filter.nostr.wine. We do NOT filter replies to notes by WoT so that users outside of your network can be discovered. This can allow in unwanted spam too.
This new solution will not change that design but instead improve upon it.
Learn more here: https://filter.nostr.wine #note19kp…6nxp

2024-09-17 14:46:13 GMT

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-10 23:10:40 GMT

- reply

Thank you kind sir 🫂🍷

2024-09-10 12:37:26 GMT

- reply

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

2024-09-10 00:12:22 GMT

- 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-08 15:02:13 GMT

- 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-07 23:04:45 GMT

- 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-06 16:32:02 GMT

- 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 GMT

- 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 GMT

- 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 GMT

- 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 GMT

- 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 14:19:46 GMT

- 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:06:24 GMT

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 13:53:29 GMT

- 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 GMT

- 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 GMT

- 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 GMT

- 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 GMT

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 11:38:20 GMT

- 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:24:50 GMT

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-30 23:20:52 GMT

- 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!