yardstick

How about

Allow git clone for free/unrestricted still.

Require the user to sign in to view html views. Sign in require a valid email or phone where a validation link is sent.

Or: Users signed in won’t see the Anubis. Users not signed in can still see the html views but have to use a very high work level?

Or: Limit unauthenticated requests from an IP to 5/minute. Authenticated requests can do a lot more before hitting the limit.

Busy servers generate more heat. Inefficient code makes servers busier. There’s a real physical outcome for bad performance code at scale.

But you don’t really want lots of idle or underused servers, aside from burst capacity management. So if they universally and consistently wrote more efficient code I’d expect a smaller datacenter. Full of still busy servers but just less of them.

Open source works just fine for this - take a look at geoacumen-country

https://github.com/geoacumen/geoacumen-country

Semi-related, there are some very cool converted datacentres in the UK.

The Bunker operates an underground datacentre out of a former military installation. Radar base if memory serves me. That’s definitely hardened from airplane attacks and I believe is used by some hyperscalers.

https://thebunker.net/wp-content/uploads/2026/02/The-Bunker-...

No idea, just answering the “Why not pick a location not within a "major airport flight path"? It seems much cheaper.” question.

London has lots of datacentres in Slough (near Heathrow) and Docklands (London City Airport, but also many LHR planes transit over).

AWS/Azure/GCP/etc Colo in Equinix/Telehouse datacentres there, and those Docklands locations in particular were picked based on location to LINX (major London peering/interchange), and LINX was put in Docklands out of desire for relatively proximity to telcos, and London’s banking/finance industry.

Thanks for the clarification. It’s a bit of a shame as going via ISE would have let the group move onto other endeavours. Maybe people will just refer to the draft name and that’s that.

DJB has orchestrated a vote rigging campaign against this WGLC, encouraging users to join the list and vote/express their opinion and providing the exact subject header to use. Have any other sides been saying, essentially, just join the group and say you’re for/against?

He’s been moderated during the last call because of his email disclaimer/footnote, and apparently refuses to respond on list during this time. Seems like he’s playing a few steps ahead where he can (yet again) cry foul on the system and cry foul on vote rigging. Despite him being a key instigator. I’ve already seen at least one poster reference a RFC explaining how IETF consensus works and how its not a pure numbers game (5 for and 100 against can still be consensus, depending on the circumstances; the inverse also applies).

What’s his next step if the authors publish as an information RFC? He can’t stop that, right?

I’m a passive observer on the same list and have been for at least several years. I don’t plan to comment on the WGLC currently going on… but I will be so extremely happy once the subject is done with.

It’s like watching a cybersecurity version of Dawsons Creek or The Young and the Restless or… Jerry Springer?! Insane

There used to be - probably still are - cameras that would digitally sign all their images. Used in crime scenes? Maybe we will end up seeing wider adoption of this, despite the privacy implications. Hackers attention then will focus (once again) on the certificate supply chain and crypto hardware.

There are some - albeit few - cars that tick most of this checklist.

MZS5 EV[1] checks most except the physical buttons, which is a half tick. There’s some physical buttons for some important things, but could do better. The previous model of had more buttons but essentially the same checklist-wise.

1. https://mgmotor.com.au/pages/mg-s5-ev

> Among software developers, and especially among those who work on security-sensitive systems, there is a well-known maxim: Don't roll your own crypto. This does not mean that nobody is allowed to write cryptographic code. Someone has to. It means that, for ordinary production software that protects sensitive data of users, we should not rely on a private, unreviewed implementation that has not been vetted by the wider software development community. We should use established, vetted software packages or tools wherever possible.

The great things about all these crypto libraries are:

- Minimal to no dependencies

- Coded by security conscious people

- Often externally audited

I wish more libs/deps are crafted like them. Until then the risk of rolling your own vs using a dep isn’t as different as it could be.

An eternal summer of CVEs is upon us

As a workaround, can Tailscale internally add multiple menu items and keep adding until one reports as visible?

Agreed. I suppose they could lookup based on your IP to pre-select a country (which you can still override if you need to aka VPNs and ordering from a different country), and based on that then ask for a postcode.

I agree.

20-something years ago, when I paid for my internet connection, I also got an email address (or 5…) and some personal web space (5MB maybe?) and access to their NTP servers as part of that. No ads.

Of course if I left the ISP I would lose access to it, as I stopped paying for it. I’ve long since left the ISP, and they’ve dropped all these value adds.

Presumably because people wanted cheaper plans and jumped to other providers which did internet access and nothing else.

There are people willing to pay a reasonable amount for fair services. I pay for various Google and Apple services, including for email. Those that don’t, have ads based plans.

Sounds like a bug in their css layout related to the smaller screen size

I see a white X in a blue box to the lower right of the modal. Is it that?

I don’t think it’s a silly question.

Before mobile phones, there were public phone booths. Along motorways there were often call boxes. There’s little to none of that anymore.

Also before mobile phones, if you had an accident in a remote area you were at the mercy of someone passing by and noticing you. Today, modern cars can call 911 on your behalf along with your location without you even being conscious. Or if you don’t have a car that does this, then your cell can be used. Let’s not also forget iPhones calling for help when they detect you had a fall at home.

Yes emergencies existed before mobile phones. I contend that the use of mobile phones has led to better outcomes when an emergency happens. I also admit mobile phones will have caused some of those emergencies (distracted driver etc).

No good when the upstream is some wifi connection provided by the building management, rather than a telco themselves.

May as well pick a single solution that works across all Internet connections and weird setups, be an expert in that, vs having to manage varying network approaches based on telco presence, local network equipment, operating country, etc.

On the later parts, VRF in my scenarios won’t scale.

Need to provide support access to 10k-50k locations all with the same subnet (industry standard equipment where the vendor mandates specific IP addressing, for better or worse). They are always feeding in data into the core too.

Much easier to just VPN+NAT.

The problem with talking to a telco, is you have to talk with not just one but any your customer may use. And if at the customer location there’s multiple routers in between the cameras and that telco router, it’s a shitshow trying to configure anything.

Much easier to drop some router on site that is telco neutral and connect back to your telco neutral dc/hq.

They’ve been planning this for a while. These datacentres and organisations don’t spring up overnight, especially at this scale.

I know at least one major European bank made it a requirement upon AWS to provide essentially this service. I believe back around 2020 or maybe a bit earlier.

> Or better still, this torrent file, where the bots would briefly end up improving the shareability of the data.

Depends on if they wrote their own BitTorrent client or not. It’s possible to write a client that doesn’t share, and even reports false/inflated sharing stats back to the tracker.

A decade or more ago I modified my client to inflate my share stats so I wouldn’t get kicked out of a private tracker whose high share ratios conflicted with my crappy data plan.

Do you take into account the iPhone not holding the original images of every photo? It will offload originals and just keep thumbnails if the library is too large.

Mine is approaching 1.5TB, I’ve got no hope of keeping that all on an iPhone, and also no guarantee that any given photo is fully available locally.

Or could just release the tool that issues new keys/serials/licenses.

It could have been action against any number of countries or people.

Russia, Iran, Syria, Yemen, North Korea, etc.

> burns out because he doesn't want to put up with a bunch of annoying work

It’s more than annoying work, it’s pointless work needlessly created by people other than him.

It’s like migrating from Java 8 to newer versions, the decision makers placed backwards compatibility at the back of their priority list. Literally a decade later it’s still griefing migrating users, all because “Jakarta not javax” nonsense. I’m greatly simplifying but that’s the essence of it.

Now we have some genius decision to I guess protect against untrusted code doing unexpected things. And at the same time Applets are gone and Security Manager is gone. And the reality is that Java applications aren’t run with untrusted code. The run scripts define all the jars/classes used. If there was some malicious code that wanted to run, I’m fairly confident it would also just modify the run scripts to include this new flag.

So all we’ve gained is support headache and pain, and no real net gain in practice.

From my own experience managing large numbers of routers, and troubleshooting issues, I will never use pool.ntp.org again. I’ve seen unresponsive servers as well as incorrect time by hours or days. It’s pure luck to get a good result.

Instead I’ll stick to a major operator like Google/Microsoft/Apple, which have NTP systems designed to handle the scale of all the devices they sell, and are well maintained.

Who knew I’d need to do this? I’d never needed to do this either my emails in the decades prior.

You’ve also got no idea what was in those emails. Could be some valuable knowledge or logs about some crazy rare bug or scenario, and would be useful to review today.

We just turned on S/MIME by default, to “be secure”, whatever that means. There was no warning in the email client about losing access to the email if you lost your keys.

Citing BOFH is all well and good inside certain circles. In the real world, people don’t like spending time or effort on poorly thought out and implemented solutions.