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 🫡 View quoted note →
Mazin
_@mazinkhoury.com
npub18kzz...x5sz
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
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
- Clients can outsource pagination/aggregation to DVMs https://www.data-vending-machines.org/kinds/5400/ View quoted note →
GitHub
nips/45.md at master · nostr-protocol/nips
Nostr Implementation Possibilities. Contribute to nostr-protocol/nips development by creating an account on GitHub.
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! View quoted note →
Who are the other pilots on #nostr ? I know @unclebobmartin is one of my cirrus brothers. Who else? View quoted note →
Ughhhh just drove to the airport for a flight and my battery was dead 💀
Knew it was dying a few weeks ago and bought a new one but forgot to bring it with me this morning 🤦♂️
All done and deployed to our load balancer. West coasters - enjoy the improved response times! View quoted note →
Over 13 million events currently stored for paid nostr.wine users. View quoted note →
Working on deploying a new beefy west coast 🍷 nostr.wine mirror today!
🚀
Quick restart in progress for @npub1crea...feh6 and @npub1wsgu...mlse
Anyone jumped through the hoops to get an ASN from ARIN or RIPE and get on one of the IPv4 waitlists?
Seems like ~2 years is the average wait time atm or you can pay ~$30 per IP to buy a subnet from a 3rd party 💸
The network provider experienced a large DDoS attack that resulted in connectivity issues for <30 minutes. Everything is back to normal now 🫡 View quoted note →
We are currently experiencing intermittent connectivity issues with our Japanese 🇯🇵 nostr.wine mirror.
We have reached out to the provider and are working with them on a solution.