> The only way to detect it from what I can see is to profile writes then append a "password:" string multiple times to measure the write-delay,
- Have the first check be a simple 8bit hash that filters out most passwords in microseconds, or use a customizable prefix instead of “password:”.
- have your password checking thread run in background at idle priority
- when you get an async password match, force usb disconnect and reconnect and the system will rescan the bus and mount your real drive.
Short of adversary dumping drive firmware (or them figuring out your hn account t, having a LLM scan the messages and finding this conversation) it’s not really easily detectable..
> hell Google doesn't either, and they're a lot bigger than them
It’s more likely that Google is trying to boycott EU initiatives to the extent it can since giving them any support would only turn the public opinion more favorable towards more US tech regulation, and that’s very much against Google’s own interests.
I think there should be mandatory courses the owner needs to take to own these breeds (and pass the exam with satisfactory marks), loose or not if one slip of a leash can lead to a kid getting mangled then it's not safe for the owner to walk even a leashed untrained dog.
They make robot dogs, e.g. famously Boston Dynamics but many others as well. And 6 is probably overkill for price/performance increase incremental to 4. Wheels are still much more practical and you can use them as feet in hybrid designs to be able to step over obstacles but still more agile than comparable bi/quadrupeds
Second stationary camera recording the screen meaning you just need to replace the screen with the virtual screen in the footage you send as the secondary camera feed, easy for a static camera because it’s an affine transform with fixed parameters. If you don’t wave your arms in a way where they overlap the screen region then it’s ridiculously easy, otherwise don’t forget to release the ‘cheating on’ foot pedal before doing that.
And with match/exec rules you can always connect to MyHost and make it conditional whether to use a jumphost or not, so it's like an on demand vpn.. only with ssh.
Match host="MyHost" exec "! grep Home ~/.wifi-loc-control/.current"
ProxyJump home-jumphost.mydomain.tld
Were I an enterprising enshittificator, I would certainly make sure to force being online as a prerequisite for basic functionality for any TV that has ever been seen online since that proves that it's capable of connecting. So.. be careful upgrading the shitware, you might get more functionality that you've bargained for. Functionality that you can't downgrade because you don't own the TV.
A cheap Android TV box. Between lack of proper hardware acceleration for 4K/Dolby Vision decoding and lack of sleep(!) support, I would never recommend that hardware, the ones that are actually recommended by the community are RP5 ($$$) and especially Intel Nx00 (N100 etc.) which are actually the gold standard of mainline(-ish in case of RPi) codec and hardware support.
If the box where I can’t set up a third party player to do the ‘replay last 5 seconds with subtitles on’ because it’s all locked down is the best then I don’t want to know what the worst is, I’ll just keep using LibreElec. At least if LibreElec does something I don’t like Claude can fix it.
> The Marquis de Lafayette and James Manor were just 18 when the revolutionary war started.
And Thomas “all men are created equal” Jefferson raped his slaves[0], and then enslaved the resulting children, but we don’t do that nowadays either, because I guess some things changed since 200+years ago?
Newer NVidia cards (H100 and up) support both in-memory model encryption and ‘trusted’ execution environment/remote attestation, not sure how widely used in frontier model deployments, but at least vendor claimed perf overhead is ‘3%’ [0]
I assume they’re encrypted/DRM’ed when deployed on inference hardware, so only core researchers/sec admins would potentially have some access to unprotected weights, and they are far too well paid to risk it leaking the model
- Have the first check be a simple 8bit hash that filters out most passwords in microseconds, or use a customizable prefix instead of “password:”.
- have your password checking thread run in background at idle priority
- when you get an async password match, force usb disconnect and reconnect and the system will rescan the bus and mount your real drive.
Short of adversary dumping drive firmware (or them figuring out your hn account t, having a LLM scan the messages and finding this conversation) it’s not really easily detectable..