key

Doesn’t seem mutually exclusive. Replace the docker rm with compose down and the docker run with compose up.

You can try using openssl s_client -connect domain:443 to help debug what the issue is. Without your domain it’s hard to guess what specifically is causing a TLS issue.

Where did you get your certs? Do they match exactly the domain you’re using? Are they expired or self signed? Are your details in the double curly brackets all correct?

You can try to use ssllabs, check cipher compatibility with browsers and such… though I think that requires things are working to a certain level first.

XMSirius just changed their terms and subscriptions are no longer cancelable or refundable starting 3/15/24, even if you sell your vehicle and have no way to use the account.

That’s absurd and untrue. They’re decreasing when you can get a prorated refund. So (aside from a initial window) when you cancel midterm you don’t get money back. That’s not great but that’s a far cry from removing the ability to cancel a subscription.

They’re already being sued for their cancelation process being an utter pain in the ass, removing the ability to cancel would be tossed out immediately.

After the experiment, yes. Poor thing.

That will always happen with something exposed to internet. Attackers scan every IP and domain they can looking for vulnerabilities to exploit. There’s software you can put in place to block requests that look like exploit attempts. Cloudfare WAF is one example. But those are mitigations only and not perfectly effective. Beyond that there’s not much you can do. Always make sure anything you expose to the internet is configured securely and kept up to date. If it makes you uncomfortable, reconsider exposing it like that.

That’s certainly high enough to affect the feeling of responsiveness. It won’t feel as “snappy” as it would without the latency. However, it’s easy for a difference in server-side processing speed to dominate that degree of latency. Lemmy isn’t super optimized and different instances can run on wildly different hardware with different levels of care put on DB tuning.

So parents are supposed to put their kids in risky situations before letting them play with bubble wrap?

If you’re trying to turn that into a catchphrase I suggest replacing “kill” with “blast” for better branding.

There’s 6 of them

Details on active users count change:

https://github.com/LemmyNet/lemmy/pull/4235

Keep at it!

19 has federation bugs. Mainly outgoing but I’ve also seen incoming federation gradually fail. Restart the docker container routinely (cron job) until fixes come out.

Not sure I follow what the issue is, it sounds like permissions are working as expected. If you want your normal user account to have permissions you can create a group with ID of 1000 in the host OS, add your user to that group, and set permission to 770.

From the criteria you gave mastodon seems like the obvious option.

Makes me kinda wish that when defederating you could select a one word label for why. Like a fixed list with several options like pedo, spam, harassment, abandoned, etc and a default of other. Make it a bit easier with a big list like this to say, oh 1000 of these 1400 all selected “racism” when defederating so it’s probably very racist and I should also defederate. But if it’s a lot of “other” or inconsistent reasons maybe I should spend a bit of time digging.

Those aren’t hashtags, those aren’t even tags. That’s a freeform category system. What’s old is new again.

So it’s purely a political fork with nothing substantially different?

How about a cookie pizza?

How about zyx.wvutsrqponmlkjihgf.edcba.abcde.fghijklmnopqrstuvw.xyz

Very catchy

It’s in account settings. That is, left hamburger, settings then “Favrion settings”, there’s an option for default sort