OCI

Reddit is free. Other people paying for your free service is a very weak argument to bring up. If Lemmy dies today, nobody but hobbyists and amateurs will care. Just like with LE.

I’ve been there. Not every CA is equal. Those kind of CAs were shit. LE is convenient. There are more options though.

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

People who used left-pad deserved everything that happened to them. But, very valid point.

There is no honor system. If your code is open for commercial reuse, that’s it. If you have any expectations that are not in line with that, then yes pick a different license.

I guess I agree with you, I’m just phrasing it from a different perspective.

I feel like most people base their decision on license purely on anecdotes of a handful of cases where the outcome was not how they would have wanted it. Yet, most people will never be in that spot, because they don’t have anything that anyone would want to consume.

If I had produced something of value I want to protect, I wouldn’t make it open in the first place. Every piece of your code will be used to feed LLMs, regardless of your license.

It is perfectly fine to slap MIT on your JavaScript widget and let some junior in some shop use it to get their project done. Makes people’s life easier, and you don’t want to sue anyone anyway in case of license violations.

If you’re building a kernel module for a TCP reimplementation which dramatically outperforms the current implementation, yeah, probably a different story

GitHub is a place you can use to easily put a copy of your code online. Many people just want to build a working solution and move on. Building a useful GitHub project, with fancy stuff like releases, is work that isn’t really solving any issues. Many people don’t like doing it. Many people especially don’t want to invest time in proprietary solutions like GitHub. They might not even accept pull requests on GitHub.

Quality assessment though 😄

Possibly relevant: https://en.m.wikipedia.org/wiki/List_of_wealthiest_religious_organizations

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?

Thank you

CrowdStrike effectively bricked windows, Mac and Linux today.

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