ixfo

No - toothpaste is in part an abrasive. If it's wetter, the abrasive is less effective at removing biofilm/plaque, and the chemical components are diluted in situ. Your mouth is plenty wet enough as-is.

My experience is that working in an office is _much_ worse for distraction. Even if you're lucky enough not to be in open plan, the shoulder taps and quick chats easily demolish any chance of focus for me. At home I can knuckle down for a few hours and deal with something complex easily.

Environment visibility is easy to get. If you pwn a box which has foo.internal, you can now impersonate foo.internal. If you pwn a box which has *.internal, you can now impersonate super-secret.internal and everything else, and now you're a DNS change away from MITM across an entire estate.

Security by obscurity while making the actual security of endpoints weaker is not an argument in favour of wildcards...

"You can use adblock" is a pretty chunky benefit over Chrome

Trust. OpenAI's ignored everyone's copyright and legal usage terms for the rest of their training data, what lawyer is going to trust them to follow their contractual terms?

Doing in-database computation can be very advantageous for some applications, and writing those functions in Rust would be fantastic for some uses, not least for the library ecosystem. I did some work on video similarity search with in-DB search which would've certainly benefited.

There were some legal challenges likely for the relevant statute, and doing it this way is much more in keeping with Singapore's approach to keeping politics "in politics".

It's carefully coordinated and done in a way that most conservatives can't really attack. In line with .sg's usual approach to doing things carefully and slowly in a controlled manner.

Assa Abloy's eCliq stuff (similar to this) uses asymmetric crypto for some parts and symmetric for short-lived stuff. The lock cylinders in that system are updated with new CRLs when inserting a key which has been updated, and authorisations are typically pretty short-lived (we use 1 day for most stuff - engineers sync up their key via an app in the morning and then they're set - and only 15 minutes for high security things, which is enough to go find signal and get back if you're in an area with spotty 4G). The keys also pull access logs off cylinders whenever they're inserted and sync up to the server next time they're synced with the app.

Dunno if this system works the same way. We went through a few of these sorts of things before settling on the Abloy solution, and most of the stuff we saw was atrocious from an infosec perspective (let alone physical). The Abloy system uses CR2032s in keys, which last a year or two, whereas this seems to do some sort of low-power networking off of mechanical energy harvesting?

It's enabled by default, actually, but otherwise about right.

https://www.blocked.org.uk/ is a useful resource on this front.

QGIS will, for raster basemaps, fetch the detailed version to get you your high DPI detail but this of course involves stitching together lots of tiles from the basemap's lower zoom levels - which then have small labels. For raster maps which are not labelled, it makes complete sense and produces a much better result than the alternative (picking the "scale based" zoom level and interpolating).

This is kind of the only "right" answer when dealing with raster basemaps. It's either pixellated or going to be rendered "too small" for the zoom level.

Vector basemaps don't have this problem, and QGIS supports them, so that's the way to go if you can get data. QGIS can then render at the required DPI in full clarity but with elements scaled/positioned appropriately.

We do a huge amount of very complex analysis and entirely run QGIS. Looked at ArcGIS and decided it wasn't anywhere near worth the money, and getting into their ecosystem at all makes it borderline impossible to interop with e.g. QGIS sensibly.

The internet basically only works because small entities have as much standing and control as large entities. This is also why things like RPKI are required, to prevent small (and large!) actors causing disruption through malicious or accidental configuration of e.g. BGP.

Whereas in a blockchain, if you assume the participants are the same set of actors - which would make sense - then it would be very easy for a majority of network control to be held by a Google, an AT&T, a China Telecom, etc.

Introducing third-parties who are not neccesarily involved in the operation of networks to said blockchain also opens up BGP operators to a whole new raft of attacks. Want to blackhole an ASN? If you can convince a smart contract that the routing policy for that ASN is "drop all traffic" then you don't even need to compromise people's routers or muck around with all that messy DDoS stuff.

Bad, bad idea. Just like 99% of stuff with the word "blockchain" in it.

UK? Pick any county within an hour or so of London. Oxfordshire and Berkshire is full of systems/tech people.

The company commissioned to build it were FM Conway. That should have been a bright red flag. FM Conway do roadworks. They fix infrastructure, and rebuild streets. They're a civil engineering firm at best, not structural engineers, nor gardeners; in other words, a deeply inappropriate choice for the company to make it happen. But I would bet good money that WCC have a great relationship with them for other contracts, and I would bet good money that whoever handed out the contract got some great tea money for their site visits.

Because we do take people's licenses away if they repeatedly cause accidents?

Treat the Tesla FSD as a human driver and it would've had its license revoked many years ago. It's only through close supervision by humans that accidents have been as infrequent as they have been.

The clip in question, if a human hadn't been paying attention, FSD would've knocked a cyclist over - at best. Do that enough times as a human - not many - and you'll be disqualified from driving pretty promptly in most civilised countries.

So it is huge, but well within historic capabilities - and materials science has come a long way since then. I'm quietly hopeful for this.

Well, no, it's not perfectly possible to recreate a singular human vision system and capture and reproduce imagery to match that.

But actually, we have lots of excellent, well-researched and proven standards for accuracy in imaging. Cameras generally target those standards, certainly professional ones. Many cameras - quite clearly - can produce very accurate photographs.

The more worrying trend is that of pervasive post-processing, where we depart from reality and entertain aesthetics.

Yes, CCSDS Magenta and Blue reference books mandate AES-256-GCM as a minimum for data encryption and mandate that encryption and authentication should be used, particularly for commands/uplink. Sliding scale of requirements based on application of course - your cubesat's imaging system is less critical than the flight termination system on a manned mission, for instance.

Red tape in the medical trials domain is forged from blood.

Human experimentation is limited and carefully managed for very good reasons. Killing people to extend other people's lives is not a good tradeoff.

The linked article (and government push to do this) completely ignores the fact that this is done frequently now.

It's used to get the last few metres into the home, e.g. from the boundary to the inside of the house. You put a swept tee in at each end, after the stopcock. Water off, dig down adjacent to stopcock, cut pipe, shove a drinking water rated duct down the pipe through the small port on a swept tee. Shove some chlorine tablets in the pipe and couple up to the new swept tee. Repeat interception at other end outside or indoors, and then use standard fibre cable blowing through the inner microduct, and away you go.

There's a huge amount of disused water pipes in most developed nations which are frequently used, similarly using sub-ducting, and you can run cable through mains - but have to come out every time there's a valve, so practically it's usually cheaper to dig. Where it comes in handy is where there's areas you can't practically dig up, e.g. major roads with old pipes underneath.

Source: Have done a bunch of this for a major UK telco.

https://www.craley.com/craley-in-pipe-fibre

Not OP but it very much depends on which bit of Azure you're using. Some bits are very polished and work great, some are a dumpster fire.

Behringer's goal has always been to make stuff cheap enough that people can afford. Which is noble, except they do this entirely by ripping off other people's R&D and undercutting lots of people including smaller players.

Also Uli Behringer himself is completely mad and appears to be pretty chill with antisemitism. https://www.gearnews.com/uli-behringer-responds-to-the-corks...

tl;dr don't support Behringer, please.

Openreach in the UK are deploying 0% new Huawei for FTTP and have basically stopped using them for FTTC because of the 30% rule. EE still use Huawei for new 5G deployments - but only in the access leg and for no more than 30% of their new builds.

They've already forced removal from core/security-critical roles, but that takes serious time to actually implement.

Just so you know, the original source of the expression would be The Hitchhiker's Guide to the Galaxy.

VOGON GUARD: I’ll mention what you said to my aunt.

[Airlock door closes and locks]

FORD: Potentially bright lad, I thought.

ARTHUR: We’re trapped now, aren’t we?

FORD: Er… Yes, we’re trapped.

ARTHUR: Well didn’t you think of anything?

FORD: Oh Yes.

ARTHUR: Yes?

FORD: But, unfortunately, it rather involved being on the other side of the airtight hatchway they’ve just sealed behind us.

Absolutely. I use loads of those features including regexp in nano all the time and it works fantastically well. For me it's the fact that it's small (so available on nearly every platform) and the command interface is so quick. It's light, fast, and snappy to drive - no context "shifts" to get to commands, and I can do "power user stuff" with just a simple key shortcut _which is written on the screen so you can see it_ most of the time. It's easy, and that's worth more than a thousand vims. See also the success of Visual Studio Code.

As I understand it, it was a mailbox installed at Amazon's insistence under very specific conditions. It looked thoroughly dodgy through and through, though of course legally was probably kosher. Amazon aren't dumb, and they have good lawyers.

This is definitely something I'd love to see. We have a lot of data in EPSG:27700 and having to reproject everything to 3857 to display to users is A) wrong and B) seriously messy and intensive for the backend servers, especially with raster tiles...

Collecting passwords and dumping the storage is likely all they did. 3 months is fairly prompt for any kind of "cyber" in the UK to even get a brief look at, due to huge processing backlogs in the overworked departments whose job it is to deal with it.

I'd suspect that what happened here is they thought they had an easy win, went through the motions, determined fairly rapidly from interviews etc it wasn't actually a viable lead, and didn't pursue further. But the machinery is set in motion by the initial conversation, for fear of prompt deletion if the storage is left with the would-be perp.

Or police reading a timestamp from a website, not realising it's actually a non-local timestamp so offset by X hours, and then requesting based on the wrong timestamp. Fairly sure that's happened before.

100% this. With NVMe and higher bandwidth NICs, fast and plentiful PCIe lanes are increasingly important and Intel have just been so far behind in this (or gated equivalance at hilarious price differentials from AMD - like having to go to $4k Intel parts (and beyond) to match AMD prosumer desktop parts).