IVPN is now on Nostr.

Following a conversation at Baltic Honeybadger with  nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424 regarding the pros and cons of 'company operated accounts on Nostr' + hearing talks on the future of free speech online, we are convinced that this is the right place (or rather, protocol) to be for us.

We've maintained a reserved, low-key presence on other social channels for many years. We as a team and as individuals prefer not to shout louder in a cacophony. While some companies thrive on oversharing for engagement and treating social communities as marketing funnels, such tactics don't align with our straightforward, no-bullshit approach.

For Nostr we are trying something different, without any compromise on these values. Expect more posts with direct opinions, in-depth analysis, privacy/VPN consultation and anything else that contributes to the community.

To anyone we've met at Bitcoin and other conferences over the years - hello! Nice to see you here. We are ready to continue the hundreds of conversations we had around trust, transparency, sovereignty, open-source ideals, LN merchant adoption, circular economy for Bitcoin and new radical ideas.

Reach out in public or private if you have any questions, ideas or suggestions. Let's do this!


LET'S GO!


Yuge


Welcome!! Awesome to see you here


Unable to receive zaps? Let's correct this, shall we


Welcome!


NIP-05 verification is failing for me https://image.nostr.build/be9bb0d5ff4a9f93fbc3d3d0c17aa776adac7daef71aef9d4eca2b770beeede0.jpg


Welcome


Same


Welcome
nostr:nevent1qvzqqqqqqypzqa7d2upjgy9qzatz3df407n9tv06e6454ljhguemhhxwmyudaydzqqsq0lzt9a6euwlvxhj89fuzvwvzpg7j3rtetz8wppfmfs950uj4qlsfq79c6


nostr:npub1utx00neqgqln72j22kej3ux7803c2k986henvvha4thuwfkper4s7r50e8 is your man on the relay front. His WoT and Haven relays are brilliant.

Also, welcome. 👌🏻


welcome 👋


Nice 👌


They did speak to me in Riga. They do have the correct public key listed in their nostr.json file. It's probably a CORS issue. It's almost always a CORS issue.

https://www.ivpn.net/.well-known/nostr.json


Interesting, welcome 💜


Well I am not using web client but an #Amethyst, so CORS should not apply to me?


Finally I did figure out the reason why verification fails - it is due to redirect from ivpn.net to www.ivpn.net

```
$ curl -I https:///ivpn.net/.well-known/nostr.json
HTTP/2 301
server: nginx
date: Mon, 30 Sep 2024 19:55:13 GMT
content-length: 0
location: https://www.ivpn.net/.well-known/nostr.json
x-varnish: 953443322
content-security-policy: default-src 'self' *.ivpn.net;img-src * data:;script-src 'self' 'unsafe-inline' 'unsafe-eval' *.ivpn.net *.braintreegateway.com  *.braintree-api.com *.paypal.com *.paypalobjects.com *.cardinalcommerce.com;style-src 'self' 'unsafe-inline' *.ivpn.net;connect-src 'self' *.ivpn.net *.cardinalcommerce.com *.braintree-api.com *.braintreegateway.com *.paypal.com  api.coingecko.com;frame-src 'self' *;
strict-transport-security: max-age=63072000; includeSubdomains; preload
x-content-type-options: nosniff
```


adding it to the list - will work on it


based.

nostr is winning


Nice!