> These relationships were robust after adjusting for established risk factors for cardiovascular health, including physical activity, smoking, alcohol, diet, sleep duration, socioeconomic status, and polygenic risk.
It's so subtle I've for a long time wondered if it's something most people experience and don't notice, or they assume is normal, just because unless I think about it I don't really notice it either. I have been known to focus on details more than others do. Not sure if this contributes to my seemingly heightened sense of smell as well. But not being able to experience what others experience, makes me wonder if I'll ever know.
>It's so subtle I've for a long time wondered if it's something most people experience and don't notice, or they assume is normal
I wondered this myself too. One thing I do know is nobody was able to relate from friends and family when mentioning this. Visual snow syndrome (which according to affected people online can be very disabling) was only first described as late as 2015 according to wikipedia. So we may never know at this pace.
Seeing the GitHub link made me assume for a second this was open source, which it's disappointingly not. The LLM search is interesting, but it's not interesting enough for me when there's already an open source full text history extension that I've been using https://github.com/iansinnott/full-text-tabs-forever
> On one hand, understandable; on the other, again, the software is effectively useless because of this.
Just in case you didn't already know, you can use Flatseal[1] to add the symlinked paths outside of those in the default whitelisted paths.
I think it's a good thing Flatpak have followed a security permissions system similar to Android, as I think it's great for security, but I definitely think they need to make this process more integrated and user friendly.
It's a shame then that Google are moving away from ChromeOS in favor of Android. This also explains the improvements to desktop mode in the latest Android betas.
First, a disclaimer: I also overwhelmingly prefer ChromeOS over Android for a bunch of reasons and wish that if they had to merge them the result was a thin Android compatibility layer on the much more robust bones of ChromeOS.
That said... if Google wants to fold ChromeOS into Android, I think they'll have to make Android fully supported on x86 as a first-class platform (because most Chromebooks are x86). And if they do that, they should have little problem making a... Android Flex or whatever you'd call it that boots on normal PC hardware just like ChromeOS Flex does today and fills the same role.
Manythings like network/Bluetooth/Display server stack are better optimised in android. Low power long battery life.
If similar to ChromeOS it is directly updated by Google then it will be a huge win for all computer users. No pain from OEM. I mean some Gemini crap from Google but that is tolerable.
I think it's unfortunate given the audience I imagine will make up most of its purchases. For example, the NBN in Australia just announced earlier this year it's first 2 Gbps residential plans (previously 1 Gbps being the maximum) planned for availability some time next year[1].
I still don't understand why Apple haven't changed their update model to A/B partitions, so if an update can't boot, it boots the previous partition. Android has been doing this for a while and Fedora Silverblue/IoT does the same thing, both of which I've found really useful in the past. If communicated well, it would elviate the update anxiety many people I know have with their iPhones.
It will not be able to reliably work with the A partition once B boots the first time - the update process even for many minor releases will trigger local and cloud data upgrades, and there are security reasons to not leave the option to leave older/unpatched versions runnable.
I don't think I've had a software update fail since iOS 7 beta 1 - and that was an issue with updating local data on first boot, so any attempt to revert to the prior OS without a wipe would have been pointless.
I believe the point isn't to let you rollback at will, but it'll automatically rollback if it fails a boot check, so before anything is written to the filesystem. However, it's worth noting that Fedora Silverblue/IoT let's you rollback at will without problem.
Silverblue uses ostree, which AIUI uses hard links in a single filesystem. This is probably better most of the time, because it means minimal storage overhead, though it means you can't change filesystems over an update and you don't resist filesystem corruption.
I believe they did it because OSM in most places is very outdated or even non existent for businesses, which was probably one of the top uses of it in a search engine.
Having contributed quite a lot to OSM, I can say though that it was generally a lot better for hiking tracks than Google maps.
Agreed. For up-to-date info on businesses I rely on Google Maps, but for hiking it’s totally useless compared to OSM. I still buy some "official" paper maps of the area I hike in because I’ve had bad surprises with OSM, mostly because some mappers sometimes invent some paths based on outdated, blurry aerial imagery, with no real experience of the area. I wish there were a tag like checked_at on paths to mark those that were verified vs. those that were only drawn on Bing Imagery.
There's more details further in the article[1].
[1] https://www.medrxiv.org/content/10.1101/2025.06.20.25329961v...