So, here's the thing. Using a cname, that will 'work' but only if you don't mind that the cert is still gonna be for nostr1. The other option is you have a proxy that serves SSL for mleku.dev and reverse proxies to the nostr1 url..
I can't add wiki.mleku.dev to my cert chain because .. reasons.. tho I could look to see if it's theoretically possible..
meh, doesn't matter, mleku.nostr1.com is fine
if the relay had its own IP address i could bounce it using my reverse proxy but i presume you only have one or a few IPv4 addresses
so, never mind for now, it would cost more to do better than this, i know how this is and the speed at which it got bombed with global content before i got the policy settings right was astounding
somebody is camping your 10002s
yeah, haha, interesting way to describe it, what pissants
If you have a reverse proxy that would work. Just set it to the https for mleku.nostr1.com and it'll shuttle traffic back and forth. That's what I do for nostr21
oh, that's easy!
i'm quite pleased with my VPS setup... it only has public access via the reverse proxy on 80/443 and some arbitrary port number in the 5 digits that is my wireguard, and that's the only way to get to the SSH, so i never have logs full of login attempts, no key, no workee
haha, funny, instantly the whitelist of npubs are sending to my relay too... (you and stella) lololol
Haha! Ah ya cause I use blastr from amethyst. 😎😂 Nostr.watch picks up new 10002s very quickly from the nostr1 cohort relays it seems 🐳
Although wait, I think you have nip42 auth turned on so I dunno how blastr would be getting through unless they added auth support 🤔🤔🤔
But they can't, hm very strange
yeah i just turned it on, because i know that the people on my whitelist also use clients often that can do it now
prime example of why nip-42 is so important and useful... totally kills spam if you have a second level whitelisting by auth, but restricting publication by npub also is pretty powerful, but not as flexible
i'll probably relax the nip-42 tho, but it basically stops anyone reading from it without a client/bot-app that knows how to do that
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..
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
