This kind of stuff must happen at hardware level… wake on lan is in hardware.
Ethernet cards keep in getting packets (arp at very least) even if they are not directed for them. If the OS needs to check all packages it would be always on
That said… wake on lan is also a waste of energy if you don’t need (why powering the Ethernet cards?)
I researched this in (checking notes) 2009 or so… things may have slightly changed since (and my memory is fading away)
At the time there was a standard for sleeping. Microsoft was part of the standard… and then they decided to implement in a different way (classic Microsoft, of course).
Hardware producers then adjusted to windows because… well… we were dozens of us using Linux on laptops.
This created issues in Linux because there were some purist developers that wanted to follow the standards, others that were more pragmatic and wanted to implement the windows way. In the end nothing worked.
Fast forward to today, windows waking up constantly I guess it’s broken as expected because it wants to allow background processes to do stuff.
Linux not waking up sounds still the issue from 2009: there are multiple levels of sleep and the deepest was the most problematic. If I have to guess your laptop wakes up just fine if the battery is full and you left closed for few minutes… while it doesn’t when the battery is low-ish and/or you left sleeping for a longer period
Yeah you got the crux of the problem here!
Let‘s correct people that are saying the same with a bit of arrogance to have a dopamine kick and then let’s make a fight about this so we are pushing the other person away
God why everything has to be so divisive these days?!
Call me a weirdo but the more errors a compilers give me the happier (albeit a bit frustrated) I am.
That stuff generally surfaces in a way or another… and I prefer at compile time 🙂
That said I haven’t spent quality time with Rust yet… so not sure if there are a lot of nitpicks (ala go) or these are valgrind-level of “holy s*** I am so grateful to this tool” 😃
I guess you need a firebase id of sort… and firebase needs the device id… and firebase is an US Company… so it’s just an extra step but the result is the same. They have to store IDs that can link to devices
Not an expert but ephemeral IDs would not give you much.
AFIK under the hoods android notifications is just… a chat app (Ehehe classic google). So for sending a notification you need to send it to the ID of your mobile. Even if you manage to convince Android to register with an additional ephemeral ID Google would be able to map the ephemeral to the real since… well… it is running on the mobile
I am ok with “question everything”, the problem is that people don’t believe in reputable sources that don’t confirm their beliefs, they look (possibly unreliable) sources that confirm them
I think it is due to the echo chamber of social networks. People have constant confirmation of superficial “sources” and they continue to want that.
Incidentally it’s the reason I use lemmy where the algorithm is not optimised to the point of echo chambers (also looking for “all” helps)
Just leaving this here from the excellent !PurchaseWithPurpose@lemmy.world