gavanm

Having recently done a timer replacement on a Dualit, I think that might literally be a Dualit timer module. Looks identical in the packing box photo. It wouldn’t surprise me if the heating elements were the same as well (haven’t checked) though those are probably more commonly available as generic items.

He would definitely would - though I’d imagine that most his travel would be done on a diplomatic basis - so it’s possible the Vienna conventions might apply and preclude detention. (not really sure, I’m not a lawyer).

I could see that potentially being an Anti-Trust issue for them.

Given the controversy over the Activision acquisition, acquiring one of the major engine platforms, having a major game studio, and already owning the XBox platform might make for great end to end strategic alignment / platform control - but I think it would also be a big regulatory/political fight to get done.

I suspect rz2k means that when the plant was operating, they couldn’t even see the towers because of the smoke/smog.

Now that it is closed, and there is no smoke - they can see not just the towers, they now see a long way behind them as well.

In Australia, after you change your licence address, they mail you a small sticker with the updated addres, that is then stuck onto the back of your licence.

There's a small section marked on the back that is specifically for it.

I guess if you move multiple times within the expiry period, you can pull the old sticker off and replace it.

Instead of a the tree structure, think about it as Data Center -> WAN -> Site Server -> LAN -> Client

By having a proxy/repeater/site server, you are reducing the amount of WAN traffic you need to send.

BofA is like Bank of America. VDI is virtual desktop infrastructure (like Citrix)

You've already included the answer - "using their machines as remote terminals, doing most their actual work on some remote server".

The developer uses MFA (TOTP, Push Notification, Yubikey etc) into a virtual desktop inside the organisation (Citrix, VMWare Horizon, etc).

From there, the developer can SSH / whatever into their development environment - which is hosted "inside" the corporate network, or their cloud provider, via internal links.

All code, and dev boxes live "inside" the corporate network, and only keypresses, mouse movement, and screen diffs are sent back and forth.

Most remote access packages can prevent clipboard, USB device, file transfer etc.

If you need a password manager for work purposes, then it lives on the corporate managed network - not your remote laptop/desktop - and to be really paranoid - you only ever "copy/paste" those passwords - you don't type them in.

If you really want to lock it down further, give the remote workers dedicated corporate equipment that they only use to access the remote desktops, so you can prevent some things like screen capturing, and really lock down the software to prevent things like keylogging software/malware.

You also should have the entire development environment segregated from the "business" corporate network as well.

It's only really an issue if you want to have offline developers - in which case I don't have any thoughts ready to hand - (but would expect it to be a very locked down machine, possibly with an even more locked down VM inside it).

As someone who regularly uses multiple layers of Virtual Desktop -> Virtual Desktop -> Remote Desktop, provided the network can handle it (on both your local network, and the corporate network), it works surprisingly well.