That's actually an important part of the theory of Roko's Basilisk. The danger of being tortured only applies to those who are aware of it. Supposedly, the incentive to torture you only exists if you were aware of the implied threat of torture.
Source? I haven't been able to find info on this. I get resuls on nocturnal tachycardia and such. Nothing on elevating a sleeping person's heart rate and observing the result, though.
With respect to this idea, I'm not particularly interested in either of those goals. More the general longevity and health improvements that come with regular exercise irrespective of weight loss or muscle gain [1].
I haven't been able to find much in the way of research on the tolerability of EMS during sleep. I would be surprised if the idea is actually feasible. It just seems like it would be such a big win if it was.
Personally, I frequently toss and turn and breath heavily, and wake up with a high heart rate. But then, my sleep quality is terrible and when I got a sleep study the sleep phase diagram looked like a seismograph reading during a 4 hour long earthquake, so...
Well, it's causing muscle contractions. At high enough intensity, it should raise your heart rate. It's just a matter of what intensity level is tolerable during sleep (and the effect on sleep quality), no?
I'd love to find out if electrical muscle stimulation while sleeping could effectively provide exercise without causing excessive sleep disruption. Could be a zero-effort supplemental form of exercise for sedentary people.
Interesting, I've got a Sony Google TV and it's been the best smart TV experience I've had in a long time. Prior to that was Samsung TVs and a Roku TV (forget which manufacturer) and they all had massive decay in performance over time.
There is a setting on my Google TV (I think it is 'Disable Personalization' or similar) that gets rid of most of the ad-space and turns the home screen into just a list of apps that I actually have installed.
It is easy to sideload apps like SmartTubeNext, and the Plex client works well, so that covers 100% of my needs.
Another question: how does this approach compare to trying to repair the pathogenic variants in the cancer? I asked here about that approach recently and the response was mainly about delivery difficulties: https://news.ycombinator.com/item?id=48285386
Depending on how the LNPs are designed, would resistance also potentially cripple the cancer cells? Like, it stops surfacing some cholesterol receptor because the drug is being delivered by LNPs that target that receptor, and now the cell is starved for cholesterol?
I've heard about drug resistance in bacteria leading to slower growth / reduced virulence. Maybe the same would occur with cancers. A drug that could effectively switch an aggressive cancer into a slow-growing one wouldn't be the worst thing.
Seems like that's... one more substantive meeting?
First link is announcing the initiative was submitted, second is a private meeting where the initiative was presented to the comission by the organizers.
Then there was a public meeting on 16 April 2026 and a public meeting on 20 May 2026.
Is there a specific part of one of those meetings that indicates they want to go a different direction than the California bill?
From the last link:
> If designed responsibly, most games that connect to the internet can operate indefinitely without publisher support. This has been a customer expectation for over 50 years. We are open to any solution that solves the problem. We are flexible on specifics and implementation by publishers. We understand that not all game features may be operable in a discontinued game. We are not seeking ongoing support from publishers after a game has been discontinued
This sounds like the California bill would address these issues.
edit: Particularly, I'm wondering if there is any serious push for release of binaries / source code prior to the end-of-life of a game, which seems to be of particular concern.
If a game is popular enough for anyone to care, some turbonerd will get the server running on a massive cloud instance, and then people will be able to play the game.
Fans have reverse-engineered and stood up servers for tons of games with no access to the server binaries. The idea that they wouldn't figure it out when given much better resources (server binaries or source code) is crazy.
Imagine if every tweet had to go through a one-at-a-time queue before being persisted. There's about 6000 tweets per second, so you would have to be able to save them at <0.17ms per tweet or else you would become backlogged. If you are getting backlogged, you have to buffer those incoming tweets somewhere until they can be writted, and eventually that buffer gets full and you start losing tweets.
> You'll note that even Java now recognises that "public static void main(String[] args)" was pointless ceremony.
There is still the part of the ceremony that actually mattered: having a single entrypoint instead of the option to litter side effects throughout the file and having those side effects execute automatically on import.
> It sucks, but what's the alternative?
3.0 was a big missed opportunity to kill a lot of the deprecated cruft.
I'm sure there are degenerate cases, but I'd bet a relatively small model could do the job.