On the contrary. China for example is known for accessing traveler electronics both during customs/immigration checks and in their hotels. Unless the victim carries their key on their person at all times without fault it can be cloned without them knowing.
The article’s author mentioned that the problem is not limited to Samsung TVs - someone reported the issue on their phone.
The article does not mention a root cause, but I have a theory that it’s likely a malformed subtitle track. I tend to watch with subtitles on so I run into related issues every once in a while. Most of the time it’s one of two things:
The latter can have multiple effects depending on what format the subs are in, but most of the time it’s a missing end time, meaning that the subtitle stays on. However, some formats also have cues as to who the speaker is, and that comes with a start and end tag like in HTML. I suspect that in this case the end tag is either missing or misaligned in the syntax tree, causing this one line of dialogue to be displayed over and over when the player reaches other lines matching the cue for it, but that don’t get shown because the user has turned subtitles off.
As to why this is bleeding into other shows: I suspect it’s an issue with how the software clients are caching the subtitle files. This would also explain why going back into the episode that caused this fixes things, because it would reset the cached file. Which in turn brings me back to pointing the finger at Amazon, not Samsung, because Samsung would just be loading Amazon’s software client to play the video and subtitles.
Transparent vs translucent.
Yeah, you’d have a LoadBalancer service for Traefik which gets assigned a VIP outside the cluster.
virtual IP addresses
Yeah, metallb.
The container is reproducible. Container configuration is in version control. That leaves you with the volumes mounted into the container, which you back up like any other disk.
It’s not that Seagate improved (which it may have), it’s more that WD has noticeably declined. It’s not a race to the bottom (yet), but there’s effectively no competition any more, so they aren’t incentivised to improve quality.
I think there’s a mistake, I can’t fit “neovim” into 8 across.
Figure out the uid/gid (numeric) for the user in lxc, then change the data permissions to those.
UNIX time uses a Julian calendar date as a reference, but is independent after that.
As for the 13 month calendar, it’s about as nice as cloverleaf interchanges: appealing because it’s symmetrical, terrible in practice. Having the days of the month always align to the same weekday means leap years would make things even worse because every 4 years the entire calendar shifts. And if you skip the leap day as a holiday then you just make calculating dates from an epoch like UNIX time even more convoluted.
User-serviceable switches would be so nice…
Deep fried AI.
The patients or their families don’t even get the gift card, that goes to the hospital.
They do have a bpf sensor. It’s still shite, managing to periodically peg a CPU core on an idle system. They just lifted and shifted their legacy code into the bpf sensor, they don’t actually make good use of eBPF capabilities.
If the sensor was using eBPF (as any modern sensor on Linux should) then the faulty update would have made the sensor crash, but the system would still be stable. But CrowdStrike has a long history of using stupid forms of integration, so I wouldn’t put it past them to also load a kernel module that fucks things up unless it’s blacklisted in the bootloader. Fortunately that kind of recovery is, if not routine, at least well documented and standardized.
Use -m and limit the build job’s memory so it doesn’t kill the docker daemon.
When I was younger and more naïve, I used to think a case was useless. I kept my phones in my pocket most of the time, and didn’t feel particularly clumsy or reckless. Then I got a phone that happened to have a glass back, and it broke not because I fumbled it, but because it slid out of my pocket onto time floor while I was sitting down. Glass backs on phones are bullshit.
I will never forgive JSON for not allowing commas after the last element in a list.