Doesn't the AMA serve the medical industry? They don't have to make profits themselves. If a byzantine coding process raises medical treatment costs, they'll do it. Just like how they intentionally cap med school admissions to keep doctors in demand and inflate their salaries.
The AMA is functionally the trade union for doctors. They work to maximize the income of their members. Maintaining a shortage of doctors is one of their primary tools.
If this also helps the medical industry, it's an accidental side effect.
I don't know if this is useful for you, but getting my MTHFR and COMT genes sequenced has been incredibly helpful for managing my own mental health. Since getting these results, I've been able to understand my own neurology better.
I'm sorry to hear about your issues with sleep - and can relate to them. In particular, my slow COMT means that my baseline cortisol is higher than most. Taking phosphatidyl serine before bed helps me a lot, and lets me sleep through the night.
I added 6 mosquitofish to my 110 gallon container pond two months ago. There are now nearly 100 in there, and the mosquito count in my back yard has definitely diminished.
Cool mosquitofish facts:
- An adult female can eat between 300-400 mosquito larvae in a single day.
- They're highly tolerant of low-oxygen and high-temperature water. They're hardy fish.
- They're native to North America, so pose little risk to getting into the water system, as they're already there.
- They're so effective at reducing mosquito populations, some local governments give them out for free.
This Web Security lecture by Feross Aboukhadijeh has a great example of Zoom's zero-day from 2019 that allowed anyone to force you to join a zoom meeting (and even cause arbitrary code execution), using a local server:
It's not clear to me from Google's proposal if it also restricts access to localhost, or just your local network - it'd be great if it were both, as we clearly can't rely on third parties to lock down their local servers sufficiently!
edit: localhost won't be restricted:
"Note that local -> local is not a local network request, as well as loopback -> anything. (See "cross-origin requests" below for a discussion on potentially expanding this definition in the future.)"
It will be restricted. This proposal isn't completely blocking all localhost and local IPs. Rather, it's preventing public sites from communicating with localhost and local IPs. E.g:
* If evil.com makes a request to a local address it'll get blocked.
* If evil.com makes a request to a localhost address it'll get blocked.
* If a local address makes a request to a localhost address it'll get blocked.
* If a local address makes a request to a local address, it'll be allowed.
* If a local address makes a request to evil.com it'll be allowed.
* If localhost makes a request to a localhost address it'll be allowed.
* If localhost makes a request to a local address, it'll be allowed.
* If localhost makes a request to evil.com it'll be allowed.
The above comment is getting downvoted, and I suspect it's due to a misunderstanding of their intent. Yes, high speeds can make collisions (especially, as another commenter points out, to pedestrians and cyclists) more dangerous. However, just as human drivers subconsciously speed up when part of a group of cars, they are not often conscious of the environmental queues informing the speed at which they drive. Given the poster's allusion to 'stroads', I suspect that they're in favor of traffic engineering patterns that encourage speed reduction based on safe context queues without solely relying on an unenforced and often unobeyed traffic speed.
Lane narrowing, raised walkways, curves in the road (chicanes), etc. are all environmental queues that enforce safe traffic speed based on context, without relying on conscious human compliance.
I ordered the KO-II for a friend, after reading about it on Hacker News. I love Teenage Engineering's playfulness and creativity, but was disappointed when the KO-II had quality issues with its input nob, making it unusable.
They were quick to issue a refund, but I would have loved to see them fix the underlying issue and offer us another unit. I'd have the same concerns about this model, since it looks like it uses the same base hardware.
I haven't seen this mentioned in the comments yet, so I'll mention it here. For the last year, I've seen health pundits (Huberman, etc.) recommend delaying caffeine intake for two hours after waking, for the purpose of allowing adenosine to clear from the brain first.
Ever since I've adopted this strategy, I find myself avoiding a mid-morning crash, and generally feeling more alert in the mornings. I wonder if the deleterious impact on grey matter could be mitigated in part by delaying consumption until fully awake.
