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. nostr:note1u5fyx2k2f3vfh9hca3mlxhw39ukl982dzfu7fz6e70xzwu5pjupqtkxc0z

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.

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.

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.

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

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!

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.

Yes! Because if you’re taking payments from users you (should) feel more obligated to keep it online/functional. You’re more likely to shut down a paid relay if you no longer have time/interest in dealing with it or if it’s costing you money.

People who choose to run free relays have a more set it and forget it mentality. It has tradeoffs but they tend to stick around longer because they aren’t as short term profit/break even motivated.

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 🫡 nostr:note1qm6l4lz7jfj2akjtwc6fv9wj9y5753q7sdxvyaspxy48dhlqvf9sft73pm

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.

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/ nostr:note1swd6s64mjk8mfys9m7n78s5j6q0szqp984sdlcmtfv799tnr4ltsj3tglu

For the nostr historians out there, I was wrong, it was 1.5y ago. Here is the original: nostr:note1fznjkjza8qecvflvn4p8tq64r7d0fuqkcuum3mqdvvf4gz5tzt8swrhfhl

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.

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! nostr:note1rg39c6hwy29eucrztq7hupd7gtvqjtfeansgsqresh9dx9jqt8gsklyq75

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

We have a project called nostr:npub1creatr06r4vr7rzx22f4kawdfj82yt09vw5rqw0kan8sr43h608s3dfeh6 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!

Updated nostr.wine NIP-50 to check tags as well. {"search": "trump gif", "kinds": [1063]} works now.

Hey sorry for any confusion! Coracle requires you to enable authentication with relays in settings -> app settings which is required to use filter.

Perhaps the users could be asked if they want to enable AUTH if they add a relay that asks for one? nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn

Definitely possible. Significant wind shear near the ground is one of the more dangerous things in aviation.

Only some airliners and some airports have auto landing capability. It wouldn’t be used for windy conditions, only when visibility is very poor or for testing/proficiency.

On the contrary, autopilot systems will often automatically disconnect in bad turbulence.

Also nostr:npub16amr0pgqzl8l57npcupjmv8j3055042g07w4qj4tu3zf4yd48nlsh96569 is a (student?) pilot and foreflight dev!