@Deleted Account
Relays (5)
- wss://theforest.nostr1.com/ – read & write
- wss://haven.accioly.social/ – write
- wss://wot.codingarena.top/ – read & write
- wss://haven.accioly.social/inbox – read
- ws://192.168.7.24:3355/ – read
Recent Notes
And with this, I have an announcement of my own. Having left Haven in a good state, with an easy way to export data through JSONL to other relays, including the new work thatnnostr:@utxo the webmaster 🧑💻 is building, I’m retiring this npub and my presence on Nostr Kind 01 permanently.
At this point, Haven is robust, battle tested software used by hundreds of relay operators. I’m sure that, other than for potencial incompatible changes to the Nostr protocol, it should remain solid for, well, longer than it has even existed.
The V2 / nostrlib version that I often spoke about will not happen, at least not for now, and likely not under mine or utxo’s guidance. But, as utxo said, I have been working hard to give users most of the features they asked for before putting Haven into maintenance mode. Well, it is finally time... I will, of course, still keep an eye on GitHub for bugs, and I’m sure that the many developers who forked and contributed to Haven will maintain their forks and carry the torch. Maybe they will elect a new official fork, or at least keep their versions alive until users are ready to move on to the future vision that utxo, Fiatjaf, and other Nostr developers are building. At Nostr’s pace, this should not take long anyway.
Before I NIP-62 and NIP-09 my Nostr presence out of existence (at least on well behaved relays willing to respect my wishes), I just wanted to leave my contact details for anyone who would like to stay in touch.
I’ll keep my presence on ActivityPub / Mastodon, although I do not post there much:
https://accioly.social/@anthony
I’m also still on @cloud fodder’s noirc.net (nick: anthony) and in some Libera.Chat (aaccioly) channels. If you are an IRC enthusiast, I’m happy to chat there.
Finally, I’m on Signal / Molly if you would like to speak directly:
https://signal.me/#eu/cDGXbPN8BUyAyyhJ4LjhTxdftVPixKjvZ-IDdrN-QhTrPYC3lotILLNJE8RKlHom
I’ve met some incredible people on Nostr and would genuinely appreciate ways to stay in touch outside of it.
#accountRetirement #shrinkNostr?
At this point, Haven is robust, battle tested software used by hundreds of relay operators. I’m sure that, other than for potencial incompatible changes to the Nostr protocol, it should remain solid for, well, longer than it has even existed.
The V2 / nostrlib version that I often spoke about will not happen, at least not for now, and likely not under mine or utxo’s guidance. But, as utxo said, I have been working hard to give users most of the features they asked for before putting Haven into maintenance mode. Well, it is finally time... I will, of course, still keep an eye on GitHub for bugs, and I’m sure that the many developers who forked and contributed to Haven will maintain their forks and carry the torch. Maybe they will elect a new official fork, or at least keep their versions alive until users are ready to move on to the future vision that utxo, Fiatjaf, and other Nostr developers are building. At Nostr’s pace, this should not take long anyway.
Before I NIP-62 and NIP-09 my Nostr presence out of existence (at least on well behaved relays willing to respect my wishes), I just wanted to leave my contact details for anyone who would like to stay in touch.
I’ll keep my presence on ActivityPub / Mastodon, although I do not post there much:
https://accioly.social/@anthony
I’m also still on @cloud fodder’s noirc.net (nick: anthony) and in some Libera.Chat (aaccioly) channels. If you are an IRC enthusiast, I’m happy to chat there.
Finally, I’m on Signal / Molly if you would like to speak directly:
https://signal.me/#eu/cDGXbPN8BUyAyyhJ4LjhTxdftVPixKjvZ-IDdrN-QhTrPYC3lotILLNJE8RKlHom
I’ve met some incredible people on Nostr and would genuinely appreciate ways to stay in touch outside of it.
#accountRetirement #shrinkNostr?
Test with a different list of relays to blast that I know are broken
❤️1🔥1
Another Blastr attempt with shorter timeout
Cloudflare hosted bots have been the largest source of bad bot traffic on my network lately. I think I'm gonna have to make a blacklist.
I straight up blocked Cloudflare Functions from my relays as a lot of bots don't play nice (i.e., same software with a gazillion identities). Couldn't care less about bot traffic, even if it breaks a genuine tool or another.
1
Another Blastr list test
haven't gotten there yet, rawdog only
Burn some tokens on it when you can (if you can, before a first store release). It makes the concept of using AI generated stuff (even one written and thoroughly revised by a trusted dev) a bit more palatable to folks that can't or don't want to read Kotlin code.
❤️1👀1
About to drop the cleanest client ever
0) most important - it's smooth and silk and it just works. no missing notes, accurate numbers
1) implements nostr properly - no caching server, no lazy outbo...
I'll give it a go. Can I login with a NIP-46 Remote Signer?
2
Hi folks, a new Haven release candidate is out, with lots of bug fixes (thanks @Logen for helping me troubleshoot). Please take whitelists and blacklists for a spin and let me know if anything is still broken.
#haven #relay #whitelist #blacklist
#haven #relay #whitelist #blacklist
22❤️3🚀1🫂1
Sheesh I had no idea it was this bad
Yeah, the powers that br are happy to sacrifice all FOSS for the greater good of the slop machine:
https://www.osnews.com/story/141969/foss-infrastructure-is-under-attack-by-ai-companies/
Beyond infrastructure, AI slop is also becoming exhausting for maintainers and security folks:
https://hackaday.com/2026/01/26/the-curl-project-drops-bug-bounties-due-to-ai-slop/
https://github.com/orgs/community/discussions/185387
It has been increasingly fun to be an unpaid FOSS person out there 🤣. In a way, Nostr’s niche status and AI companies not coming so hard for data behind websockets (yet) help keep Nostr reasonably protected, aside from its own internal script kiddies, of course.
https://www.osnews.com/story/141969/foss-infrastructure-is-under-attack-by-ai-companies/
Beyond infrastructure, AI slop is also becoming exhausting for maintainers and security folks:
https://hackaday.com/2026/01/26/the-curl-project-drops-bug-bounties-due-to-ai-slop/
https://github.com/orgs/community/discussions/185387
It has been increasingly fun to be an unpaid FOSS person out there 🤣. In a way, Nostr’s niche status and AI companies not coming so hard for data behind websockets (yet) help keep Nostr reasonably protected, aside from its own internal script kiddies, of course.
1❤️1
It really is becoming a fully fleshed all-for-one relay!  An additional feature that I’m really looking forward to is possibly away for Haven relay runners to charge a fee to be added to their wh...
I think Utxo already wrote an alt relay for paid stuff somewhere (if not, there are certainly other commercial Khatru and non Khatru oferrings around). I rather keep paywalls away from Haven's main codebase, but now that we have whitelisting I'm sure you can vibecode something to do this. Just add a rest endpoint to Haven that adds an npub to the whitelist and refreshes the WoT (keep the endpoint private of course or it will get powmed), have your payment layer call this endpoint and you are done.
1❤️2
I've already banned a few IPs, I'll consider this if it continues to be a problem
Good luck!
I don’t know how things are right now, but when I did this last year there were simply too many crawlers to even try to block manually. Plus, they don’t play fair. Lots of scrapers were spoofing IPs and using a multitude of IPv4 and IPv6 addresses. Even my firewall on a 128 GB memory server started to struggle to keep up. Anubis helped a bit, but things were still quite painful. I did this before Cloudflare enhanced its bot protection features. Assuming analytics can be trusted, China and the US alone were sending more traffic to my Forgejo instance, which only had a bunch of empty projects, than what I typically get on Nostr, ActivityPub, and IRC combined in a month.
Keeping my internal repo and syncing to public forges like GitHub, GitLab, and Codeberg is a good enough compromise for my needs while GRASP (and other non Nostr alternatives) matures. It also helps with the problem of nobody wanting to report issues or contribute outside of popular forges.
I don’t know how things are right now, but when I did this last year there were simply too many crawlers to even try to block manually. Plus, they don’t play fair. Lots of scrapers were spoofing IPs and using a multitude of IPv4 and IPv6 addresses. Even my firewall on a 128 GB memory server started to struggle to keep up. Anubis helped a bit, but things were still quite painful. I did this before Cloudflare enhanced its bot protection features. Assuming analytics can be trusted, China and the US alone were sending more traffic to my Forgejo instance, which only had a bunch of empty projects, than what I typically get on Nostr, ActivityPub, and IRC combined in a month.
Keeping my internal repo and syncing to public forges like GitHub, GitLab, and Codeberg is a good enough compromise for my needs while GRASP (and other non Nostr alternatives) matures. It also helps with the problem of nobody wanting to report issues or contribute outside of popular forges.
1❤️1