nostr:nprofile1qqsflmrj64um42nh9tu7w8nr3dffy9tjrt8xururype9ajle7alctvgppemhxue69uhkummn9ekx7mp0qyg8wumn8ghj7mn0wd68ytnddakj7qg4waehxw309ahx7um5wghx77r5wghxgetk9uukdx2g has some rare limits and polices on nostr.mom, e.g., my Haven instance can no longer Blast to it either. On nos.lol I at least get a message like minimum PoW required, no idea which filter / policy caught you.

Reply to this note

Please Login to reply.

Discussion

what is your relay's IP that blasts to mom?

It is an IPv6 range, but I think whatever you did to fix stuff for Vitor also worked for me. I've sent you a NIP-17 message with further details on August 18.

i disabled v6 to keep things simpler. you must be using v4 to connect? if that's a personal relay you probably had the same 1984 bug effect you and it is not related to IP. its fixed now.

Yes, I'm running dual stack, and since your fix above everything is working. Still, in the long run it would be great if you could re-enable IPv6.

I realise this comes with an increased attack surface and several issues for the benefit of a relatively small number of users, but ultimately Nostr needs to be IPv6-friendly if we want resilience, global reach, personal relays running on mobile phones, and so on. IPv6 support is a necessary step for long-term sustainability.

Do you a repo (or set of repos) with your settings / customisations / plugins / etc to strfy somewhe?; It would be interesting to understand what you are doing around NIP-56, WoT, etc.

i still use nostr-sdk 0.12.1 :)

people would be shocked by my tech and coding style :)

Whatever you are doing, I dount Its worse than some of the code that I'm making public out there (I'm shameless) 🤣. Not trying to pressure you to OSS it though. But for small time relay devs like me it would be interesting to get an idea on how the big relays are handling stuff.