It's got to be pure marketing - the British media certainly loves a buzzword, but I suspect that's more to do with their clickbait strategy. ("What is blishing? Have I fallen for it?"). Perhaps it helps some people compartmentalise, but I couldn't find any research that looks into any increased cognitive load.
Our workplace cybersecurity training introduces at least 1 new word each year. This year's was "vishing" which apparently is just social engineering/credential extraction that takes place over the phone. Of course, it's presented to non-technical users as a well-adopted term that is very important to know (for the checkbox quiz in 3 slides time).
I can't find any good information post-privatisation, but at least before 2013 the postcodes themselves were copyrighted by Royal Mail (likely Crown Copyright as with government data). There were attempts to enforce this in 2009[0]. I suspect the copyright is now owned by Royal Mail Group Ltd.
That aside, a practical issue is that Royal Mail still retains the rights to _allocate_ new postcodes for any new properties. Yet another failure of this particular privatisation.
For context, Thameslink operates a route through central London, and transitions from overhead power in the north to third-rail in the south. This happens when stopped at stations and is fairly quick - the pantograph/shoes are raised/lowered around the same time as the doors open - the dwell times seem the same as usual.
As for charging, Jago Hazzard has a video on a fast-charge trial[1] for a battery-only route. As it's using a modified tube train, I'd assume it's lighter and thus requires smaller batteries, but recharging from third-rail takes roughly 4 minutes.
I did this for a bit. The main issue was that air intake on my older model was through the keyboard, so clamshell mode was inadvisable - not sure if that’s true of the newer models and M1 should run cooler.
If you’re wiping it and installing Linux it’s like any other server, but if you’re running macOS you’re open to a wider spectrum of vulnerabilities that wouldn’t normally apply (desktop software). Your apps could also have vulnerabilities that expose access to personal credentials, etc (e.g. filesystems, apple id) depending on your setup.
You can insulate yourself a bit with tunnels/proxies to expose specific services (e.g. cloudflare, ngrok).
I had a lot more peace of mind buying an old, cheap computer, raspberry pis, and eventually NUCs.
Correlates with my experience of late 2013 MBP batteries (it might be the same model actually). My original Apple battery lasted until 2019. Both of the iFixit replacements have lasted a year until not holding original charge, and just last night I noticed a cell starting to swell.
I doubt I'll ever find factory original cells again for the 2013 but if Apple sells them I'd consider buying a MBP again.
> Nobody is forced to install the app at all (at least in the UK's case).
Unfortunately, that's not quite right. Citing the latest rules:
> The rules on what you need to do when a group enters your venue have changed. You must ask every customer or visitor to scan the NHS QR code using their NHS COVID-19 app, or provide their name and contact details, not just a lead member of the group. [0]
Delving into the rules, it appears this applies to all sit-in venues, while takeaway customers are exempt. A paper-based system should be available, if you trust the business to handle your data responsibly (or forge fake data if not).
This morning at a cafe I was asked to scan the QR code "or we can't serve you" for a takeaway order. Clearly some misunderstanding, and I didn't press about a paper-based list as I hadn't read the details myself. Hopefully it's an isolated incident, but it wouldn't surprise me if there was some simplified comms (/FUD) about "just get customers to scan the code".
Unfortunately, Google and Apple have effectively made it impossible to use the paper-based details in order to contact people and tell them to self-isolate if someone who used the app to check in tests positive by blocking this.
This feels like it's just designed to encourage rapid replies, like their chatrooms. I've always admired HN's time-delay on posting replies the deeper you get into a thread - it deliberately reduces engagement but seems effective at stopping things getting too heated.
You essentially run a little proxy server on your pihole setup, and configure pihole to use it as your upstream dns resolver.
E.g., a proxy server running at 127.0.0.1:5053 which uses the Cloudflare ipv4/ipv6 DNS over HTTPS endpoints. This can also use other DoH endpoints as desired:
Not OP, but I never got on with forced stops either. I had some success treating it like a mini-deadline to achieve flow-state - work on something for 25 minutes, and if I don't feel like I want to keep going, take a break and try again.
Our workplace cybersecurity training introduces at least 1 new word each year. This year's was "vishing" which apparently is just social engineering/credential extraction that takes place over the phone. Of course, it's presented to non-technical users as a well-adopted term that is very important to know (for the checkbox quiz in 3 slides time).