Ya I'm confused, that's ok tho. I don't have this relay in my outboxen so I duno how it would get messages from me unless the auth didn't turn on..
Discussion
i just turned it off, it was turned on only because of the pornspambot, but the policy is set right now so they can't post
also, it's now in my inboxes, wiki.mleku.dev so if your client knows nip-65 it may publish to it now
OHhhh nice 😎😎😎😎
yeah, this tech is awesome... the big improvements are invisible to the normies, but they are so pervasive in their effect
there is no doubt in my mind that this tech will eventually eat the social internets, the silos ain't got nothing on this
If you're happy I'm happy 🎉 back to my cave of writing this awesome nip66 latency measurement bot with arm64 support for a mesh of distributed relay monitors 🦎🦎🦎😎🐳
carry on my man, you are the administrator, can i get a little taxi number?
Jammin out to these on the PA 🐳
Lol, man I duno you may be pointing at your own relay still.. I ran a strfry scan it says 0 kind 1s in there .... 😁
i am not running my relay, it runs at 100% cpu after about 24 hours
that's why i've been reworking a lot of code in the last 3 weeks to eliminate memory allocation
after i'm done doing that in my spare time (i'll be back on the clock after 2 july) i'm adapting the best of the many go relays i have seen on github - in terms of simplicity, then i will add the fast badger data store with GC and then the whole shebang will be shunted into replicatr because it needs to be fixed
i'm just not being paid to get past MVP, it was ok for the demo, but it's not ok for production, i haven't been entirely forthcoming to my employer about this but i've been working my tail off to make it right because i want to trounce all the object oriented retards
next.nostrudel.ninja knows both nip-65 and nip-42 so if that's your client you will be able to post to it because i also whitelisted your npub