We have some in house software which runs in k8s. Total throughput peaks at about 1mbit a second of control traffic - it's controlling some other devices which are on dedicated hardware. Total of 24GB of ram.

The software team say it needs to run across 3 different servers for resilience purposes.

The VM team want to use neutronix as their VM platform, so they can live migrate one VM to another.

They insist on 25gbit networking, and for resilience purposes that needs to be mlagged

The network team also have to have multiple switches and routers, again for resilience.

So rather than having 3 $1000 laptops running bare metal kubes hanging off a pair of $500 1G switches eating maybe 200W, we have a $140k BOM sucking up 2kW.

When something goes wrong all those layers of resilience will no doubt fight each other. The hardware drops, so the VM freezes as it restored onto another host, so K8s moves the workloads, then the VM comes back, the k8s gets confused (maybe? I don't know how k8s works).

It's all needlessly overspecced costing 30 times as much as it should.

But from each individual team it makes sense. They don't want to be blamed if it doesn't work, they don't have to find the money. It's different departments.

It's generally accepted that red = hot and blue = cold, and there is a scale showing that anyway

It's quite obvious based solely on the site that this shows surface sea temperatures over 40 years, and it's far higher now than it was 40 years ago

But sure, just go on the "I'm only asking questions" crap.

1985 sure. Maybe 2000

But now?

Comancho saw the green shoot at the end and changed his mind.

That to me is what makes it utopian

Because ads are cancerous, it may make you a few dollars, it massively reduces the usage of the internet, it eats resources (energy, time) from the world, it helps breaks privacy, it continues to paint the normality of the internet as a cesspit

I think this is simply updating some api call which no longer works properly, coupled with the terrible "changelogs" that are the norm on the app store. Someone down thread mentioned certificate rollover.

A sensible changelog would be "update expired certificate", or "fix integration with ios 26.2", or "patch security issue"

An actual changelog would be "we're bringing you ever more great new improvements"

Here's the latest Audible one:

> At Audible, we're always making updates and improvements to make your listening experience better.

> If you're experiencing issues, please reach out to customer services. For feedback or suggestions contact us at audible.co.uk/help

This is the same every time, because these changelogs are meaningless.

If it doesn't store the fingerprints then how does it tell the difference between

5 identical looking browsers connecting from 5 different IPs

1 browser connecting 5 times from 5 different IPs

Your shitty ISP doesn't give you an ipv4 access, that's fine. ipv4 address blocks cost $20 an address and are cheaper today in real terms than in 2016, and have been coming down in nominal terms for years.

ipv6 makes sense at a global scale, it still makes no sense for many individuals with a good ISP, mainly because of how it was implemented, too much stuff still relies on ipv4. If you have to also run ipv4 then why run ipv6.

I have no services I use that are ipv6 only

I have services that are ipv4 only, so I have to run a 6:4 nat

I want a stateful firewall because it's not 1999

I want to handoff to multiple consumer ISPs, using PBR, not running BGP, so I need to use NAT66 (changing IPs isn't good enough, I want to round-robin based on various rules, send traffic to dropbox via one ISP, send udp via another, etc)

I have software which doesn't work on ipv6 on a client, so I have to run CLAT on the device

But not all my local devices can run CLAT, I thus have to run dual stack to use ipv6 successfully.

Thus as I'm running ipv4 anyway, and running NAT, there is no benefit over running ipv4 only. IPV6 adds more things to go wrong (NAT64/DNS64), but offers no benefits.

Even without the ipv6 client requirement I still need to run both NAT64 and NAT66. I have an ipv6 only network at home which I put phones on. It works, but there's no benefit other than keeping awareness of ipv6.

Now sure, the reason that ipv4 addresses are cheap is because other people are moving to ipv6 (especially mobile), and relying on 464 gateways, with 46 in their CPE and 64 on the ISP level. That's great.

But that doesn't change the equation for someone with a choice of ISPs, as they can choose an ISP which provides them with static ipv4 addresses.

The bad guy here is google. And the people that champion data collection by private companies because of free market == good.

Which is concerning. Until you realise I do the same thing a few days later and I'm still unique.

Last time I tried firefox on the iphone it was rubbish compared with safari. Same with some ad blocking app I had back in the day

I'm not signing up for a subscription for that journal, but paying a small amount for access to that one article is a no brainer. I don't subscribe to a newspaper either, but I'll happily buy one.

The New European did this a decade ago using "agate" (named after the smallest font you'd get in a newspaper), top up with a few quid, then pay for each article.

Sadly didn't catch on. TNE dropped it in 2019[0]. Agate still exists, having been renamed to "axate", but consumers aren't willing to pay with anything other than their time.

[0] https://pressgazette.co.uk/news/new-european-drops-micro-pay...

In your typical home environment, just set your ULA to fd00::12 instead of 192.168.0.12, or fd00:16:34 instead of 192.168.16.34

Yes you'll run into issues if you were to later want to merge your private IPs with someone else, and you should use fd12:3456:7890::12 instead, remembering those extra 10 digits, but its not a problem at home, and no more of a problem with business mergers than ipv4 clashes anyway.

It's about as easy to remember as 81.187.123.45//192.168.0.53

Almost all ipv6 addresses I encounter start with 2001, so I just need to remember my home prefix is 8b0:abcd, which is about the same length as my home public IP of 81.187.123.45

::53 means subnet zero host 53, which is easier to remember than which rfc1918 range I used (and basically is the equivalent of remembering the 2001:: prefix)

If I have an internal server I'd have on 192.168.4.12 I could address it with 2001:8b0:abcd:4::12 just as easily, with the "4.12" translating to "4::12", and the "81.187.123.45>192.168.x.y" translating to "2001:8b0:abcd:x::y"

Just because slacc gives you an extra 64 bits of randomness doesn't mean you need to use them.