oops second link should have been astal.ninja/event/767d342a09448955628ffac40ed3f4e5cc1669eb5f9d5d71f3495312ec97c155
damus.io/key
I want to be able to stress test it with realistic load; unfortunately no easy way of doing so without major clients adding it
to be fair; a tiny vm with 2vcpu and 2gb ram is sitting at 4% load.
mirroring relay.damus.io as well.
relays aren't that resource intensive imo
just paste the invoice in a note.
ideally you'd just use a domain you control and establish your identity that way. so if for whatever reason I need to change my priv/pubkey you can still find me as skander@nostr.slothy.win; I just need to update the nostr.json file.
but for someone high-profile from bird app, nostr.directory makes sense since most people know you from the bird app.
nah just a local build cloned from Thomas' repo. Not production.
yeah you could either look for @nostr.slothy.win and find all users under that domain (only me) or just skander@nostr.slothy.win
and if I ever change my private key, I can just update my json file and you would still be able to find me that way.
could have used twitter_handle@nostr.directory; at least that ties with your Twitter account identity which you already established.
pretty sure they enabled nip-05 already on nostr.directory so your tag should be there:Β https://nostr.directory/.well-known/nostr.json?name=jack
cc: #[3]
had to use damus web to reply to him; for some reason #[1] breaks the reply/quote/repost/embed buttons
this is precisely what I'm doing :)
by the way; your note breaks the astral.ninja reply button lol
habibi get a life.
adding CORS headers is... hacking your nginx config?
wat.
yup.
I think he's looking at pubkey count onΒ https://nostr.io/stats
pubkeys are the only identity
everything else is noise
trolling aside for future ref; nostr.directory &/or check pubkey.
there are many jacks; and display names are just that, display names.
No. It's like someone hosting a nextcloud instance and using Nextcloud Talk for nostr discussions