Imo still worth reminding people that just because you run an apt/dnf upgrade running applications still map the now unlinked outdated version.

Anecdotal, but I researched something similar for a job I had almost 10 years ago. Next to the office we had a pretty big datacenter, which I know had ”district cooling”, so I wondered if this was fed back into the district heating network somehow?

Turn out no, mainly because the local thermal power plant is already fed into the district heating network, and that already produces was more east heat than nessecary to provide heating in the city.

Eventually they did an expansion and I was told the district cooling was scrapped in favor of local ”free cooling” units. Basically just dumping the waste heat directly to the air (This works in the right climate, so like not in Arizona or Texas)

Im okay with it tbh. The everything must be free on the internet mindset is what led ads working its way in everywhere.

At least it sounds like the 9.0 ones only affect systems that are running SMB Direct, which sounds like a pretty niche setup

That kind of is the proper way to handle this. You don’t want to hint bad actors where to look and give people some time to update.

Probably meatballs,

… or Surströmming.

I think the key here will be that the solution integrates into some actually adopted standard. In the context of a potential mandatory age verification for EU countries, this would have to be something that is integrated into the EUDI Wallet, which is supported to have support for zero-knowledge proof of certain attributes like is the person above 16? This way it should not be different from what people would encounter on every other social media platform.

Maybe it’s because I’m on mobile right now, but it looks like a lot of the descriptions are cut off without any way to expand it. Assuming that texts ending in ”…” is supposed to continue.

You might be onto something. Went to a new vet this time after our usual vet had to re-schedule the booking a second time. The old vet often seemed quite stressed and had a lot more to do, and the new vet seemed quite chill (and the visit went quite smooth)

Maybe it’s the cute paperclips holding the line!

I think that one of the biggest challenges you may face is that source code is probably one of the areas where corporate customers care the least about things like the CLOUD Act or FISA 702. Simply because the main legal issue comes from processing of customers personal data, and that data should never end up in a Git repo. The company I work for is pretty strict with EU data residency, to the point that we have products with strict EU data sovereignty requirements (i.e. no US providers in the chain), and looking to move workloads off US clouds… but nobody has ever cared about GitHub because in the end the source code is only classified as Corporate Confidential, not Sensitive or Highly sensitive.

That said, a possible selling point if you’re targeting EU companies might be DORA compliance. I am saying this because something that did come up was if we needed a DORA addendum with GitHub since we do a lot of GitOps… and GitHub did not want to sign any addendum.

Realistically your best option is a CDN with some layer of bot detection and blocking. Cloudflare is of course the most popular choice, https://bunny.net/ might also work but I haven’t tried their advanced Shield level so not sure how good it is.

Some commercial advanced firewall / WAF might also be an option. Seems most of them has Bot mitigation features, but I haven’t tried their never personally tried anything like that.