And it always causes issues.
Anyway, I hope the main joke got spotted too.
Let's Encrypt now does IP certs: https://letsencrypt.org/2026/01/15/6day-and-ip-general-availability
Certbot doesn't seem to be up to the task yet, but lego works.
But I'll probably change it to some image host later, because I have no idea what I am doing.
Why does it not work... It embeds when creating the post.
Seems fine too, it's HTTPS after all, should work.
OK, seems that it's just the default LemmyUI that doesn't like it, which is strange for the number of pict-rs requests in access.log.
Also by the number of 429, 5r/s is probably too low. Was. Anyway...
OR, that's why there is the burst option. Right.
It's gotten better but I'm not v6 only, I just don't have v4. I have NAT64 which basically uses your IPv6 as the private address in a traditional NAT setup, allowing you to continue to access the legacy internet without IPv4 inside your network. Catch is you can't connect to IPv4 addresses because it relies on a DNS64 server to generate IPv6 AAAA records from the IPv4 address when a domain only returns IPv4 so only DNS based services work. Basically it lets you have all the befits of a v6 only network with few of the drawbacks.
you gotta get clatd on your computer
I deliberately don't want or use a clat, the goal is to avoid IPv4
i see. does that meaningfully reduce the amount you use nat64? i ask because for me, most things go through dns anyway
No not really, I just don't like having the address on my interface, ironically it doesn't break half the stuff that removing 127.0.0.1 does...but I do that too XD
i guess you're living about 30 years in the future