BuildTheRobots

It's a good question, and I wondered the same. I don't know, but I'd postulate:

As it stands at the minute, the clocks are a mere 5 microseconds out and will slowly get better over time. This isn't even in the error measurement range and so they know it's not going to have a major effect on anything.

When the event started and they lost power and access to the site, they also lost their management access to the clocks as well. At this point they don't know how wrong the clocks are, or how more wrong they're going to get.

If someone restores power to the campus, the clocks are going to be online (all the switches and routers connecting them to the internet suddenly boot up), before they've had a chance to get admin control back. If something happened when they were offline and the clocks drifted significantly, then when they came online half the world might decide to believe them and suddenly step change to follow them. This could cause absolute havoc.

Potentially safer to scram something than have it come back online in an unknown state, especially if (lots of) other things are are going to react to it.

In the last NIST post, someone linked to The Time Rift of 2100: How We lost the Future --- and Gained the Past. It's a short story that highlights some of the dangers of fractured time in a world that uses high precision timing to let things talk to each other: https://tech.slashdot.org/comments.pl?sid=7132077&cid=493082...

> The boss doesn't see that you can't properly paste a piece of code in the chat

Of all my many gripes with Teams, it usually handles code surprisingly well. Single `inline` and triple backtick blocks usually render as you'd expect.

OneNote on the other hand doesn't support a code-block at all, and is worse (if you can believe it) than storing cli commands in Word docs.

I wonder how much of it is low quality adapters vs poor drivers. Whatever Bluetooth module they used in my £20 Chinesium car stereo connects quicker and works with less niggles than any other device I've tested in the last 20 years.

> I've often thought about that when there's a work crisis: If I'm the second on the scene, what can I do to support those fighting the fire right now, before jumping in.

A lot of it depends on the size and skill-set of your team and the escalation routes available to you, but in general (and off the top of my head):

- Get the first people on scene to give a summary of the problem as they know it. Make sure everyone actually agrees on what the problem is and what symptoms have been observed. Understand what areas people are currently investigating and make sure they aren't trampling over each other or actually making the situation worse [1]

- Make sure the situation hasn't evolved whilst the first on scene have been investigating the initial symptoms. It's easy to get lost in the weeds digging into a handful of monitoring alerts only to look up and realise there's now 300 and the original problem is only a small part of what's going on.

- If there isn't one already and you're not better doing something else, become incident commander. When done right it's an extremely important and useful role.

  - Take over external communication and protect the team from distractions
  - Start assessing escalation options
  - Take copious notes and keep a timeline 
  - Act as a shared memory and keep people honest 
  - Have a less panicked, wider (non minutia) view of the problem
  - Start collating and pulling up documentation/schematics so the people at the coalface can quickly query it rather than getting distracted searching for it.
  - Be ready to jump, for when someone inevitably asks "can someone check..." or "does anyone know"
  - Keep track of the "shared truth" of the incident as it evolves. What have we witnessed, what do we believe is the cause, _why_ do we believe that? Have we invalidated anything, do we need to reassess, are we sure logical lynchpins aren't confirmation bias or dyslexia?
  - Onboard new people and hand over if appropriate.

Being at the coalface when it's on fire is a very different view of the world to watching other people panic and singe their fingers. It's also very easy to get lost in a chain of technical problems [2] when it's mostly irrelevant to the wider picture.

If you get a moment, it can also be a good time to assess how useful your monitoring is during an actual event.

[1] "Hey, server x has flagged on monitoring and my ssh session is hung waiting for a login prompt!" I've been round the houses enough to know this is probably OOM and if I just wait, I'm likely to finally get in. I also know that saying this in a room of 20 technical people, means the server is now processing 22 new ssh sessions and now no one is getting anywhere.

[2] The famous Malcolm in the Middle intro where Hal is tasked with changing a lightbulb and ends up repairing the car. Except in my example the bulb is actually fine and there's a power cut we missed. https://www.youtube.com/watch?v=AbSehcT19u0

Except unpowered SD cards (and SSDs for that matter) don't claim to hold data for more than a couple of years.

I'm a big believer in thinking you have backups being worse than knowing you don't, so anything that encourages people to believe $(flash memory) is suitable as long-term cold storage is actually, really bad.

I agree there's no need to copy & wipe cards immediately, but treating them as "film" is inherently flawed and setting yourself up for failure. The amount of people that turn up in data recovery forums unable to access old, important, "backed up" (memory card/ssd on a shelf) photos is depressingly high.

It's something I've done myself in the past. First sort is because it needs to be sorted for uniq -c to count it proper, second sort because uniq doesn't always give the output in the right order.

It was one of those situations where the internet was part of the lease, and the property owners got the MSP to provide for multiple companies on the site. Sadly I wasn't a customer of either Juniper or the MSP, and it wasn't something they ever actually claimed to support.

Juniper themselves stated in the manual that this base model device didn't support SCTP, though on ever other level it was faster, more capable and more featureful than the mid-range but much older device it replaced. The MSP didn't have a clue that we (or anyone else for that matter) used SCTP so missed the single footnote mention that the command to enable SCTP forwarding might not be available on some base-level devices.

In their defence, I'm not sure _I'd_ have thought to check if SCTP was supported and I had it running on my network. It works over the internet, it's basically IP, how could it not be suppo---oh.

It did see a lot of use. I forgot to say, but the majority of 3G UMTS and 4G LTE radios (operator level and even down to tiny things like femtocells) required it to connect back to the $(core network) and encapsulated a mix of control and user data through it (though often also encapsulating SCTP in a VPN). That is to say, there were a lot of devices out there that used it in anger. If you made a call or used a cellular data session for over a decade, your traffic was likely getting encapsulated through it.

Very interesting.

I had a similar problem a few years back with a technophobe Grandma who wouldn't use whatsapp and a stingy aunt who'd moved to the states.

Used a Fritz!Box as it'll act as a DECT<->SIP server so my grandma could keep picking up her usual handset. Had a rule which matched the aunt's phone number so it got bounced via my FreeSwitch server rather than her PSTN, and some least-cost routing rules to pick a US based provider SIP provider with a +01 PSTN number so my aunt saw the incoming call looking local and could ring back if necessary at a cheap rate.

Honestly, the weird technical abominations we come up with to try and serve family members. The same Grandma went through a phase of falling, not being able to get up and then waiting hours for an ambulance to arrive. Would she tell the family? Would she sod. Was her regional ambulance service still dispatching jobs via pager message? You betcha. Did this end up with an SDR, POCSAG decoder and a regx looking for her postcode? Absolutely not; why would you ask such a thing?

Coming from the telecoms space, I was slightly amazed to see how little well known SCTP actually is in the networking world.

My old company/offices had site internet provided by one of the top 50 UK Managed Service Providers. They swapped out the on-site router not many years ago as the fibre to site was being upgraded from 100mbit to gigabit and so a new Juniper firewall with GBE ports was required.

Turns out the newer, faster, shinier, though albeit lower model numbered'd Juniper SRX fundamentally didn't support passing SCTP data and suddenly we lost access to all our remote stuff that used it. Ended up on a call with the MSPs Head of Networks (who was not a stupid person), but their opening gambit was "Are you sure you mean SCTP? Oh. What is that then?"

There was also numerous weird kernel bugs with implementations on CentOS 5, 6 and 7 which all would manage to get themselves into weird states where only a reboot would clear - not really what you want from a multi-endpoint, 'copes and recovers well from network weirdness' tunnelling protocol.

Bigger orgs for the most part use whatever vpn solutions their (potentially decade old) hardware firewalls support. Until you can manage and endpoint a Wireguard tunnel on Cisco, Juniper, Fortigate (etc) hardware then it's going to take a while to become more mainstream.

Which is a shame, because I have a number of problematic links (low bandwidth, high latency) that wireguard would be absolutely fantastic for, but neither end supports it and there's no chance they'll let me start terminating a tonne of VPNs in software on a random *nix box.

My understanding is that they're glitching the game to inject data into memory, in this case processor instructions. And then they use another glitch to jump to and execute that code. No modifications needed to the hardware or ROM, you're just being extremely selective about how to play the game to cause memory to get flipped.

This video is done by hand and explains a bit more about how and why it works: https://www.youtube.com/watch?v=hB6eY73sLV0

Not just swappable, but in a lot of corporate laptops with a locked down CMOS, the swappability is still one of the shortcuts that a user level user can change in the BIOS.

I thought Ctrl being in the right place on the new keyboard would be nice - sadly it seems to be the worst Thinkpad keyboard I've ever used... not even sure why, but all the spacing just seems slightly but very noticeably wrong.

Yep, you're totally right. I had double and triple on the brain from the Fisherman's; standard climbing knot is but a simple figure-8.

HowKnot2 have been making empirical testing videos on climbing knots and gear which have proved fascinating and often unintuitive.

If you'd like to see a break-strength test comparing single, double and triple fisherman’s knots, you might enjoy: https://www.youtube.com/watch?v=5CAjUi47QMY

For reference, a 100kg climber is unlikely to be able to cause more than 14kn of force on a dynamic rope, (in reality, significantly less,) even if they go out of their way to find the worst case fall-scenario. Most belay loops are rated at 15kn, human bodies start breaking at 8-12kn and HowKnot2 says that a double-figure-8 (the standard rope<->harness knot) all break at around 14kn https://www.youtube.com/watch?v=g4CVFRE0pRg&t=500s

There's also the Iodine project if you want to tunnel raw IPv4 over DNS [53]

[53] https://github.com/yarrick/iodine

Interesting. It prompted me to install the microsoft store version which, when launched manually is identical to the web version. As the keyboard key brought up a web window telling me to install it, I assumed it just launched that.

We get Copilot at work. From what I can see the Copilot app is just the Copilot web interface in its own container and webview, though I've not gone poking at it.

Considering the web page in a browser can easily eat >5gb RAM just to display a single conversation (it's honestly mind boggling; how can something use 5gb of memory and a noticeable amount of CPU just to display relatively little and lightly formatted text?), having it self-contained makes killing it to reclaim memory easy.

For those of you wanting to get more angry, the "menu key" on my new Thinkpad has the default action of Copilot and the Copilot logo printed on it. On the other hand, he Ctrl key is finally in the -r-i-g-h-t- left place at least...

The magnets work too well. Having one Thinkpad Yoga sat on top of another closed Yoga tricks the sensor into thinking it's in tablet mode and it disables the keyboard. I only lost 30min or so trying to work out what was happening...

There's decent reasons to over-engineer some of these sensors so they can't be unduly tricked by external influences.

> The absolute lack of self awareness [...] Did you forget that...

I think I forgot that some people have an absolute lack of sarcasm awareness :\

> What I do instead is scan my QR codes into two apps on different devices when I make them

Amazingly, I'd never even considered this as a possibility. Thank you for the paradigm shift.

You really shouldn't. The colloidal silver probably isn't that harmful in small quantities, Jäger's just herbs, but there's some really nasty chemicals in those energy drinks.

They kinda do - microcode translates x86(_64) into micro-opts for actual execution. If you go back far enough to the P6 the actual execution core was essentially RISC [1]

[1] https://news.ycombinator.com/item?id=36380149

> I always thought these workarounds were odd - does God have no objection to using proxies to get around the rules? Then again, my friend is not Jewish, so perhaps he can freely break the Sabbath because he’s outside the scope of the rule? Or is damned anyway?

There's a lot of crossover between Judaism and DnD player mentality. You're very much encouraged to learn the source material, the commentary and to discuss and debate it. Workarounds don't actually break the rules; and you need to put a lot of study into doing them properly.

Sometimes you need to take a sensible decision and choose to just flat out break the rules. In those situations one is encouraged to do so in an uncommon or abnormal way so it doesn't become habitual. This makes sense to me - I didn't smoke inside for the first 3 years of moving into my house, but the first time I did break that rule it made breaking it much easier the second, third, or subsequent times.

In your example given I can see a situation that isn't actually a risk to life (which comes under different rulings), but is still serious enough you need to take some action before waiting for Shabbat to end. A burst pipe would be a good example; it's not going to kill anyone but it could cause extremely serious damage if left. Asking for help rather than just picking the phone up and treating it like a regular day sorta makes logical sense in that context, though it's probably not what I'd choose to do.

Jewish laws only ever apply to Jews [1]; they have no expectation, want or desire for it to apply to anyone else, through conversion or otherwise. If your friend isn't Jewish then he's welcome to do what he wants. There is no damnation in the Christian sense for anyone, Jewish or otherwise. It's also possible to get into Jewish heaven without being Jewish, but you do have to obey a small subset [1] of the laws.

[1] https://en.wikipedia.org/wiki/Seven_Laws_of_Noah

"It would have been the year of the Linux desktop too, if it wasn't for those pesky trans hackers!"

Post hoc ergo propter hoc. I think your logic is backwards. Parent isn't saying the freedom of online technical spaces turns people trans, but that trans people in those spaces are more likely to make themselves obvious because of the freedoms.

There's also high overlaps between trans and non-neurotypical types. I'd suggest there's the same crossover between non-neurotypical and tech circles so makes sense there's a higher instance of trans in tech.

I'd also suggest that on some level coming out as trans is basically hacker mentality. "This hardware/wetware doesn't look/perform correctly. Let me get a soldering iron/rewrite some code/clothing/hormones/surgery and change that."

> I’m on the board overseeing Linux graphics. Half of us are trans. If all you care about is Linux, resist the attacks on trans people. > If you have any decency, fight back.

https://web.archive.org/web/20250520182445/https://rosenzwei...

I'd worry it's only a small sector of the counter-fitting operation.

It'll let me keep a folder in sync, automatically, across multiple machines. There's no faffing with accounts, it has a GUI simple enough for me to talk entirely non technical people through setting it up and it doesn't matter if one of more of the endpoints is behind NAT.

Once running, it's just a case of copying or editing files in a folder and they're everywhere else. No manual intervention, no trying to remember which computer has the latest copy, it doesn't get upset if I throw terabytes of media at it, it doesn't get upset if I `git init` inside multiple folders and suddenly I have my coding projects ready to go on whatever laptop I pick up.

It also does some nice additional bits, like making it possible to have machines that store a copy of the data but never have decryption keys, so I can use a cheap VPS without worrying about it having a plain-text copy of my data. There's also the ability to store multiple revisions of changed files, should you want it. It's also, at the end of the day, actual plain files on your filesystem which can save a lot of headaches.

It also does a pretty good job of finding the best path to a different box. It shares IPs (that you run the service on), so same lan, different vlan, via a VPN, via a double nat'd someone else's wifi; it doesn't care and usually does the right thing (and is configurable if you wish/need).

The comparison isn't rsync. SyncThing is a host-your-own dropbox/onedrive/other alternative without a requirement for a provider, accounts, fees or your data belonging to someone else, and stunningly low barriers to entry/usage by non technical people.

By 99 it wasn't that bad. I remember screaming along with V.92 56k modems. Futurama episodes were about 50mb encoded as RealVideo and took a mere two and a half hours to download o.0

(and it really was v.92; I still have the double-bong towards the end of the handshake emblazoned in my memory)