Noch nicht, kann ich aber gerne machen!
Ja, zumindest habe ich einige getestet: Alby, BlueWallet, Breez, Phoenix, WoS
Hat überall funktioniert. Als Identifier wird natürlich eine andere Domain angezeigt, aber das ist ja bei einer Proxy-Lösung auch der Fall.
Eine .htaccess-Datei kann fast jeder Hoster, bzw. wenn das nicht, gibt es ja meistens auch Weiterleitungen auf einer Verwaltungsoberfläche.
Not the current version in App Store, only the TestFlight version has it currently!
Spricht eigentlich etwas dagegen nur ein HTTP Redirect zu nutzen – außer natürlich, dass dadurch das Ziel sichtbar wird?
Yes, it is nice, definitely. But I do like the all those possibilities with modern mirror-less ILC! :-)
Only digital, but the light captured is still analog! 😁
## How to setup your own relay with nip05 authentication
I'm using a contabo CLOUD VPS M with NVMe and I'm using nostr-rs-relay with sqlite.
nostr-rs-relay does not work on ubuntu 20.04, so I'm using ubuntu 22.04
I mainly followed
https://github.com/BlockChainCaffe/Nostr-Relay-Setup-Guide
Addionially I needed to install protobuf
apt install protobuf-compiler
and I added
proxy_read_timeout 1d;
proxy_send_timeout 1d;
to the nginx conf in location / { } of listen 443 SSL;
The config.toml needs to be changed and
[verified_users]
mode = "enabled"
must be added.
let me know if you have questions are getting stuck during setup.
Thanks for sharing! I have a similar configuration on my paid relay, but the vCores are bored as hell currently! 😅 So I am thinking of running a second relay, like yours, with nip-05 identification. Even the domain would be similar, just *.at! ;-)
Good to know that there is a domain blacklist implemented as well!
How does nip-05 requirement work for fighting spam? It seems your global feed is okay. But there seems to be some not verified accounts from the last hours.
Yes, that’s a possibility!
It seems block 777771 and 777770 were so late, that alby will be available again for 777777!
