I just upgraded a few minutes ago.

All went smooth except for an ssh script I use, because the ssh algorithms changed. It was easy to fix though.

The Free Software Foundation is a good place to learn about open source licensing and they can assist with enforcement if needed.

Here's the rest of the thread (should open entirely from the first link, but posting all 6 links just in case):

(1/6) https://fosstodon.org/@gabrielesvelto/110592904713090347

(2/6) https://fosstodon.org/@gabrielesvelto/110592906325095640

(3/6) https://fosstodon.org/@gabrielesvelto/110592907269834415

(4/6) https://fosstodon.org/@gabrielesvelto/110592908903430968

(5/6) https://fosstodon.org/@gabrielesvelto/110592909828889441

(6/6) https://fosstodon.org/@gabrielesvelto/110592910420926394

Here's the rest of the thread (should open entirely from the first link, but posting all 6 links just in case):

(1/6) https://fosstodon.org/@gabrielesvelto/110592904713090347

(2/6) https://fosstodon.org/@gabrielesvelto/110592906325095640

(3/6) https://fosstodon.org/@gabrielesvelto/110592907269834415

(4/6) https://fosstodon.org/@gabrielesvelto/110592908903430968

(5/6) https://fosstodon.org/@gabrielesvelto/110592909828889441

(6/6) https://fosstodon.org/@gabrielesvelto/110592910420926394

I'm in the same boat! I have tried, really tried, the only things I like are the extensions support on mobile browser, and the sync with the Wolvic on the Quest VR, but it feels old and some websites render weirdly on it, plus the lack of support for PWAs really make it tough.

I like Brave best, with Edge as a second choice, as weird as that sounds. I miss Firefox when it was the modern and most secure browser.

cnames do not point to IP address, they point to a resource on another domain, in this case azureresource.azure.-com for example.

Say you have a temporary webpage called flashsale.example.-com you created a cname pointing that subdomain to an azure resource that shows your desired content. Then you remove the azure resource, but leave the cname in place.

If a create another azure resouce with whatever public azure url you used before, and I make it look like your current website, say I impersonate your current login.example.-com on that azure resource, now your cname flashsale.example.-com os pointing to it, but you don't control the azure resource now, I do.

Now I can try to phish your customers by sending emails with real links, like: Dear customer, your account will be charged $900 for your last purchase, if this purchase was made in error or was not authorized by you, sign in to flashsale.example.-com immediately to cancel it. And now I have your customer's credentials.

And that is just one example, there are many more ways to exploit an orphaned cname subdomain, like using it to serve malware, using it to control bots without being blacklisted, etc.

I don't share (or like) anything that I don't want made public, so I don't mind who follows my profiles on social media. But some people would rather keep a lower profile or be more selective of who can interact with them, so it's better to have the option available.

The problem I was having was related to IPv6, there seems to be a misconfiguration with IPv6 at the moment since the new server went live sometime this morning. https://lemmy.ml/comment/584801

Thanks for mentioning the IPv6, I've been banging my head all day trying to figure out why I kept getting the 502 yet no one was complaining anywhere and isitdown was showing the server as Up.

I forces my DNS to resolve only IPv4 for lemmy.ml and now I can use it.

My suspicion is that nginx is misconfigured and not listening via IPv6. Or maybe the AAAA record is pointing to the wrong IPv6 address.

@nutomic Thanks for upgrading the server!