I actually agree. For the majority of sites and/or use cases, it probably is sufficient.

Explaining properly why LE is generally problematic, takes considerable depth of information, that I’m just not able to relay easily right now. But consider this:

LE is mostly a convenience. They save an operator $1 per month per certificate. For everyone with hosting costs beyond $1000, this is laughable savings. People who take TLS seriously often have more demands than “padlock in the browser UI”. If a free service decides they no longer want to use OCSP, that’s an annoying disruption that was entirely not worth the $1 https://www.abetterinternet.org/post/replacing-ocsp-with-crls/

LE has no SLA. You have no guarantee to be able to ever renew your certificate again. A risk not anyone should take.

Who is paying for LE? If you’re not paying, how can you rely on the service to exist tomorrow?

It’s not too long ago that people said “only some sites need HTTPS, HTTP is fine for most”. It never was, and people should not build anything relevant on “free” security today either.

People who have actually relevant use cases with the need for a reliable partner would never use LE. It’s a gimmick for hobbyists and people who suck at their job.

If you have never revoked a certificate, you don’t really know what you’re doing. If you have never run into rate-limiting issues with LE that block a rollout, you don’t know what you’re doing.

LE works until it doesn’t, and then it’s like every other free service on the internet: no guarantees If your setup relies on the goodwill of a single entity handing out shit for free, it’s not a robust setup. If you rely on that entity to keep an OCSP responder alive for free so all your consumers can verify the validity of your certificate, that’s not great. And people do this to save their company $1 a month for the real thing? Even running the shitty certbot in compute has a larger cost. People are so blindly in love with this “free” garbage. The fanboys will never die off

the claims in some media that Telegram is some sort of anarchic paradise are absolutely untrue. We take down millions of harmful posts and channels every day,

Gotcha. Millions of harmful posts every day. That really does sound like a great place.

That is some next-level Minecraft you are playing over there

Okay, maybe I read you wrong. I agree that nobody will try to acquire details through mullvad to prosecute this.

I read the comment like downloading music is so irrelevant, you could skip the VPN, which I would disagree with.

I once downloaded an album I had already pre-ordered, but didn’t want to wait, no VPN. Got a letter from a media lawyer within the month. Felt pretty stupid.

Now this is some horrible advice. Bravo

That makes sense, but my understanding is, what Google considers Family content is not an add-on to regular content. Your content is not also for children, it is catered towards them. This implies using dedicated Google functionality, special SDKs, and so on, to comply with law. So your product needs to be designed in a very specific way to be eligible. I’m not aware of how Google Play restricts children from installing certain apps, but you can always install an app through a parental supervisor account.

To me, this story seems like a lot of crying over a situation that is not fully explained.

Why would you enlist a map app under the Families program in the first place though?

If you want to get into the scene, hopefully, you made this post from a clean account that can never trace back to you. Otherwise this shit will break your back at some point.

The people you want to be in contact with, don’t want to be in contact with you. People who want to be in contact with you, are cops or stupid people.

If you need to ask, then you shouldn’t know. People who offer help are likely to deceive you.

There is still value in watching https://en.wikipedia.org/wiki/The_Scene_(miniseries)

That being said, that material was highly likely already captured by existing professionals and nobody will care. Don’t risk anything for a bit of thrill. Actually releasing pirated material and actively breaking copyright law is no joke. You might think it’s good fun, but there are people who try to fuck you up as their full-time job. Pirates are often mentally ill or are motivated financially. There is no Robin Hood you could help for a greater good.

Thank you

Can’t disagree with any of that. But I still like doing it

Bro, I’m an AWS Cloud Solution Architect and I seriously don’t know what you’re talking about. And, no, when I waste time on Lemmy, then there is literally nothing better to do.

AWS made S3. People built software to integrate S3 as a storage backend. Other people didn’t want to do AWS, and built single-node imitations of the S3 service. Now you use those services and think that is S3, while it is only a crude replica of what S3 really is. At this point the S3 API is redundant and you could just as well store your assets close to your application. You have no real, global S3 delivery service anyway. What’s the point?

Most people misuse AWS S3. Using stuff like minio is even more misguided.

I don’t follow. S3 is an AWS service that these tools emulate locally by providing the same API. But I’m happy to accept that there’s just some misunderstanding 😃

Buy a different domain. Let them pay for this one until the end of time.

Fuck that. People like to act like running an SMTP server or a CA is some major shit, while everyone is fucking up on these subjects every single day.

S3 goes beyond the scope you describe. You disqualify yourself with such statements

I disagree. Local files access is always superior. If you disagree, your target solution is likely poor to begin with

So it compares to existing products, but it’s less mature? Why should anyone care?

S3 storage is simpler than local files? I think you need to elaborate

I roll out Step CA to my workstation with an Ansible role. All other clients on the lab trust this CA and are allowed to request certificates for themselves through ACME, like LetsEncrypt.

All my services on all clients on the network are exposed through traefik, which also handles the ACME process.

When it comes to Jellyfin, this is entirely counter-productive. Your media server needs to be accessible to be useful. Jellyfin should be run with host networking to enable DLNA, which will never pass through TLS. Additionally, not all clients support custom CAs. Chromecast or the OS on a TV are prime candidates to break once you move your Jellyfin entirely behind a proxy with custom CA certificates. You can waste a lot of time on this and achieve very little. If you only use the web UI for Jellyfin, then you might not care, but I prefer to keep this service out of the fancy HTTPS setup.