Awesome glad that worked out

Did you ever adjust your budgets in your settings for your account: https://github.com/settings/billing/budgets

I also have the free account, and I never touched the budgets section. In here, GitHub action budget is set to $0 and has Stop usage enabled.

If these settings are set to $0 and you got charged, then I guess you can open up a case support case, since that seems like a bug.

I think I read somewhere that this would be the default for new instances if they don’t have one of their own. On an existing instance, the server admin would have to remove the existing license which would then load this license. So this could affect more than just mastodon.social.

That being said, since this was brought up, it has been put on pause while it is reevaluated

Yeah, in my case, I wasn’t familiar with the settings for Cloudtrail Data Events, and didn’t realize you could select which events to log, based on the actor or resource, as opposed to all events in DynamoDB. That would have saved me a lot processing power to filter the logs to look for the actions I was looking for.

I enabled Cloudtrail to log all DynamoDB read/write data events when trying to troubleshoot an issue. Even though I only left this enabled for a few days, the Cloudtrail line item was $5k more than it should have been. My back of the napkin math with assumptions came out to be 100 times less than that, so I had a really awkward support email asking them to reverse the charges, which they did fortunately.

Is there a really a quota on the CSAM detection, or do you mean catbox would only get a free 1GB of storage? No one’s saying that Cloudflare would give away 1 PB of traffic for free, obviously catbox would have to pay for it. Still though, Cloudflare or another CDN adds a lot of value which would be hard to replicate.

At that volume, you need to scale a lot, which is what CDNs are designed to do. Moving 1 PB a month in traffic would be like a sustained upload speed of 3 Gbps for an entire month, which is huge for any ISP, and cost a lot. You’d probably need to divide the traffic going out which means multiple ISP connections, and more machines for redundancy. Probably at that scale, connections are coming from all over the world, so to reduce latency, you’ll need locations in multiple continents to serve quicker. As you can probably tell, this becomes more than just one time purchases and electricity costs.

CDNs have dedicated fiber links between geographic locations and negotiated volume discount rates on bandwidth with other ISPs. From a cost and a reliability perspective, it means you can deliver content for less than hosting it all on your own.

One issue is that browsers and other clients have a difficult time handling certificate revocation. Let’s Encrypt is stopping support for OCSP, and that had a lot of privacy implications where a CA could tell who is going to what site, based on the requests to check certificate revocation. Let’s Encrypt is moving to CRLs, but the size of the CRL is very large the more certificates you have. For Let’s Encrypt with only a 90 day validity period, their CRL is smaller than a CA which has certificates as much as 398 days old.

The size of the CRL is something not only CAs have to manage, on the client side, you may have to check a 10MB file to see if the certificate for the site you’re connecting to is still trusted by the CA. With many CAs, these CRLs will take up a lot of space on disk, and need to be updated often. Mozilla published a system called CRLite which uses Cascading Bloom Filters to keep track of revoked certificates in the browser, which will save a lot of space. Having a constrained set of revoked certificates is useful to ensure the bloomfilter won’t be too large for the browser to store and manage.

Clearly you didn’t read the article. The first paragraph is about Meta censoring LGBTQ+ content

On Monday, Taylor Lorenz posted a telling story about how Meta has been suppressing access to LGBTQ content across its platforms, labeling it as “sensitive content” or “sexually explicit.”

Posts with LGBTQ+ hashtags including #lesbian, #bisexual, #gay, #trans, #queer, #nonbinary, #pansexial, #transwomen, #Tgirl, #Tboy, #Tgirlsarebeautiful, #bisexualpride, #lesbianpride, and dozens of others were hidden for any users who had their sensitive content filter turned on. Teenagers have the sensitive content filter turned on by default.

When teen users attempted to search LGBTQ terms they were shown a blank page and a prompt from Meta to review the platform’s “sensitive content” restrictions, which discuss why the app hides “sexually explicit” content.

People who comment on articles without reading the article itself should take a long look into the mirror before implying other people are advocating censorship.