Made my website prettier.
Here is a link, and it is a good time to talk about this particular link:
You will notice that it is just an IPv4 address, but that it is using https. Also behind the scenes this IPv4 address is approved by a certificate authority.
What this means is that when your browser goes to this site it should open the site without any warnings.
This wasn't something that was always easy to do in a way that the typical browser will like.
When you rent or put a computer online you get an IP address, and you can put up
right away. It will work, but the typical browser will throw a hissy-fit and scare off 90% of the normies out there. Also having encryption on your connections is a nice thing to have.
Well the Electronic Frontier Foundation has just recently made it much easier to have a website with a certificate for an IPv4 or IPv6 address. If you're interested in more detail, here is a good place to start:

Electronic Frontier Foundation
Certbot and Let's Encrypt Now Support IP Address Certificates
(Note: This post is also cross-posted on the Let's Encrypt blog)As announced earlier this year, Let's Encrypt now issues IP address and s...
My personal goal is to try to be as sovereign as possible. While using IPv4 and IPv6 is not as sovereign as using TOR or FIPS, it is a great intermidate step. Not only do you not have to get permission to rent a domain name, the site ends up being faster and more private because the user doesn't have to access the DNS system in order to access your site.
It would be nice to see many more relays on nostr using wss with an IP address. It is a great use case, without much hassle.
Here are my other links to the same page which include even more sovereign means.
[domain]
[ipv4]
[ipv6]
[tor]
http://kn2jam4kyz6s5wacyozo3do3d2zsvh4to45uh7xliulwdust6zjuvnad.onion
[fips]
http://npub1crpldvy49ef8z34wlacwujnfudy4nd7k96aqdx5wgn6ckztz7z8q9t59ud.fips
[n-site]
https://npub1rmz9gu6de0m0u4ysrn39crrud099ahvfgs6pvasl4hpjr5ud7yus54xv06.nsite.run