It’s literally in the article: They want to use client-side scanning. The client already has the data decrypted. This is much like what Apple wanted to introduce with CSAM scanning a while back. It’s a backdoor in each client and it’s a matter of time until it will be abused by malicious entities.
The existence of ArchWiki and the Arch User Respository (AUR). And rolling releases, if that’s your thing.
Speaking of which: I’m cooking up an app platform for this purpose on ESP32: https://github.com/ByteWelder/Tactility
No issues here with Gnome via Arch on a Framework 13. At 150% scaled if recall correctly.
It’s probably an SSD for a Fusion Drive setup: https://en.m.wikipedia.org/wiki/Fusion_Drive
It seems to check out for iMac in 2019.
Besides the other mentioned reasons: exposure through the app store can be a motivator too.
From StackOverflow:
Switches will send packets to all interfaces when using broadcasts or under extreme conditions (full MAC Address Table). This can lead to duplication if there is a loop between two or more switches and if the Spanning Tree Protocol is not used. So the answer is rarely.
https://stackoverflow.com/questions/9196791/duplicate-udp-packets-how-often-it-happens#9220574
It seems like this might break the GDPR rules for consent:
Any element of inappropriate pressure or influence which could affect the outcome of that choice renders the consent invalid.
https://gdpr-info.eu/issues/consent/
or if the performance of a contract, including the provision of a service, is dependent on the consent despite such consent not being necessary for such performance.
https://gdpr-info.eu/recitals/no-43/
I’m not a lawyer though, so maybe a legal expert can chime in.
edit: the jury is still out it seems:
https://techcrunch.com/2023/10/03/meta-subscription-vs-consent/
As an experienced Android dev and former iOS dev: pushing someone to Google products is not going to improve someone’s privacy. Apple is not “good” in terms of privacy, but Google is much worse. The only real options in that area are MicroG-based Android OS-es, or fully de-googled ones. However, custom ROMs are often not problem-free though. In that case, a Pixel phone is probably still the best option.
The cost effectiveness difference on the bottles versus sponges is probably much bigger than the video suggests, because a whole bunch of ink is likely sticking to the sponge and never coming out.
It works with my Subscribed and Local feeds. It crashes with the All feed. I’m guessing it has to do with a specific post that it tries to load.