MastodonTech.de

boredsquirrelA few counterarguments on <a href="https://tux.social/tags/LocalMess" class="mention hashtag" rel="nofollow noopener" target="_blank">#LocalMess</a> (<a href="https://tux.social/tags/Facebook" class="mention hashtag" rel="nofollow noopener" target="_blank">#Facebook</a> <a href="https://tux.social/tags/Instagram" class="mention hashtag" rel="nofollow noopener" target="_blank">#Instagram</a> <a href="https://tux.social/tags/Yandex" class="mention hashtag" rel="nofollow noopener" target="_blank">#Yandex</a> <a href="https://tux.social/tags/LocalhostTracking" class="mention hashtag" rel="nofollow noopener" target="_blank">#LocalhostTracking</a>), why this would make <a href="https://tux.social/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#Android</a> worse than <a href="https://tux.social/tags/iOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#iOS</a>:This vuln seems to only have existed on Android, but not everyone would need to be affected by it.I see <a href="https://tux.social/tags/GrapheneOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#GrapheneOS</a> as a perfected form of the Android idea (stripping the <a href="https://tux.social/tags/Advertizing" class="mention hashtag" rel="nofollow noopener" target="_blank">#Advertizing</a> and Tracking from it, and adding needed permissions).1/8

Kevin Karhan :verified:<a href="https://mstdn.social/@BrodieOnLinux" class="u-url mention" rel="nofollow noopener" target="_blank">@BrodieOnLinux</a> <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener" target="_blank">@torproject</a> <a href="https://social.librem.one/@guardianproject" class="u-url mention" rel="nofollow noopener" target="_blank">@guardianproject</a> At this point I'd like to ask when <a href="https://ec.social-network.europa.eu/@EUCommission" class="u-url mention" rel="nofollow noopener" target="_blank">@EUCommission</a> and other <a href="https://infosec.space/tags/regulators" class="mention hashtag" rel="nofollow noopener" target="_blank">#regulators</a> start <a href="https://infosec.space/tags/banning" class="mention hashtag" rel="nofollow noopener" target="_blank">#banning</a> <a href="https://infosec.space/tags/StasiBook" class="mention hashtag" rel="nofollow noopener" target="_blank">#StasiBook</a> and other <a href="https://infosec.space/tags/GAFAM" class="mention hashtag" rel="nofollow noopener" target="_blank">#GAFAM</a>|s for their blatant actions as <a href="https://infosec.space/tags/OrganizedCrime" class="mention hashtag" rel="nofollow noopener" target="_blank">#OrganizedCrime</a> to violate <a href="https://infosec.space/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#privacy</a> standards in the <a href="https://infosec.space/tags/EU" class="mention hashtag" rel="nofollow noopener" target="_blank">#EU</a> and elsewhere?<a href="https://infosec.space/@kkarhan/114733606176520273" translate="no" rel="nofollow noopener" target="_blank">https://infosec.space/@kkarhan/114733606176520273</a>Cuz at this point the €32B fines at maximum are a joke. <ul><li>I think that people espechally in Germany who may be affected [I'm not!] consider seeking legal advice and potentially file charges for said <a href="https://www.gesetze-im-internet.de/stgb/__202c.html" rel="nofollow noopener" target="_blank">digital espionage</a> and <a href="https://www.gesetze-im-internet.de/stgb/__303b.html" rel="nofollow noopener" target="_blank">computer sabotage</a> against <a href="https://infosec.space/tags/NSAbook" class="mention hashtag" rel="nofollow noopener" target="_blank">#NSAbook</a>! </li></ul>Simply because this isn't a mere violation of <a href="https://infosec.space/tags/GDPR" class="mention hashtag" rel="nofollow noopener" target="_blank">#GDPR</a>, <a href="https://infosec.space/tags/BDSG" class="mention hashtag" rel="nofollow noopener" target="_blank">#BDSG</a> and other standards, but literal <a href="https://infosec.space/tags/malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#malware</a> that has been deployed against users in the wild... <ul><li>Anything but actual prison sentences & arrest warrants against the persons responsible would be undue leniency.</li></ul><a href="https://infosec.space/tags/Spyware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Spyware</a> <a href="https://infosec.space/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#InfoSec</a> <a href="https://infosec.space/tags/ComSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#ComSec</a> <a href="https://infosec.space/tags/ITsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#ITsec</a> <a href="https://infosec.space/tags/OpSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpSec</a> <a href="https://infosec.space/tags/LocalhostTracking" class="mention hashtag" rel="nofollow noopener" target="_blank">#LocalhostTracking</a> <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Govware</a> <a href="https://infosec.space/tags/StasiBook" class="mention hashtag" rel="nofollow noopener" target="_blank">#StasiBook</a> <a href="https://infosec.space/tags/Facebook" class="mention hashtag" rel="nofollow noopener" target="_blank">#Facebook</a> <a href="https://infosec.space/tags/Meta" class="mention hashtag" rel="nofollow noopener" target="_blank">#Meta</a>

Kevin Karhan :verified:The fact that <a href="https://infosec.space/tags/NSAbook" class="mention hashtag" rel="nofollow noopener" target="_blank">#NSAbook</a> is literally developing <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Govware</a> to track users and bypass <a href="https://infosec.space/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#Android</a> <a href="https://infosec.space/tags/sandbox" class="mention hashtag" rel="nofollow noopener" target="_blank">#sandbox</a> as well as <a href="https://infosec.space/tags/tracking" class="mention hashtag" rel="nofollow noopener" target="_blank">#tracking</a> them regardless of <a href="https://infosec.space/tags/VPN" class="mention hashtag" rel="nofollow noopener" target="_blank">#VPN</a>, <a href="https://infosec.space/tags/Cookies" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cookies</a> or <a href="https://infosec.space/tags/IncognitoMode" class="mention hashtag" rel="nofollow noopener" target="_blank">#IncognitoMode</a> use or blockage.<a href="https://www.youtube.com/watch?v=LUtctMShGJw" rel="nofollow noopener" translate="no" target="_blank">https://www.youtube.com/watch?v=LUtctMShGJw</a> via <a href="https://mstdn.social/@BrodieOnLinux" class="u-url mention" rel="nofollow noopener" target="_blank">@BrodieOnLinux</a> More to readup upon. <a href="https://redact.dev/blog/meta-yandex-localhost-tracking" rel="nofollow noopener" translate="no" target="_blank">https://redact.dev/blog/meta-yandex-localhost-tracking</a> <a href="https://www.zeropartydata.es/p/localhost-tracking-explained-it-could" rel="nofollow noopener" translate="no" target="_blank">https://www.zeropartydata.es/p/localhost-tracking-explained-it-could</a><a href="https://infosec.space/tags/Spyware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Spyware</a> <a href="https://infosec.space/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#InfoSec</a> <a href="https://infosec.space/tags/ComSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#ComSec</a> <a href="https://infosec.space/tags/ITsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#ITsec</a> <a href="https://infosec.space/tags/OpSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpSec</a> <a href="https://infosec.space/tags/Malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Malware</a> <a href="https://infosec.space/tags/LocalhostTracking" class="mention hashtag" rel="nofollow noopener" target="_blank">#LocalhostTracking</a> <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Govware</a> <a href="https://infosec.space/tags/StasiBook" class="mention hashtag" rel="nofollow noopener" target="_blank">#StasiBook</a> <a href="https://infosec.space/tags/Facebook" class="mention hashtag" rel="nofollow noopener" target="_blank">#Facebook</a> <a href="https://infosec.space/tags/Meta" class="mention hashtag" rel="nofollow noopener" target="_blank">#Meta</a>

m_berberich<a href="https://social.heise.de/@heiseonline" class="u-url mention" rel="nofollow noopener" target="_blank">@heiseonline</a> <blockquote>Die Chats selbst sollen davon aber nicht betroffen sein, beteuert das Unternehmen.</blockquote>Nur zur Info: Das ist das gleiche Unternehmen, daß mit localhost tracking die Sicherheitsmechanismen von Android umgangen hat um Benutzer besser tracken zu können·<a href="https://infosec.exchange/@isotopp/114663960595107813" translate="no" rel="nofollow noopener" target="_blank">https://infosec.exchange/@isotopp/114663960595107813</a><a href="https://infosec.exchange/tags/Meta" class="mention hashtag" rel="nofollow noopener" target="_blank">#Meta</a> <a href="https://infosec.exchange/tags/Whatsapp" class="mention hashtag" rel="nofollow noopener" target="_blank">#Whatsapp</a> <a href="https://infosec.exchange/tags/localhosttracking" class="mention hashtag" rel="nofollow noopener" target="_blank">#localhosttracking</a>

larsLocalhost Tracking: Eine Erklärung und seine potenziellen Konsequenzen für Meta In der digitalen Welt von heute ist Datenschutz ein zentrales Anliegen. Ein aktuelles Thema, das viel Aufmerksamkeit erregt, ist das sogenannte “Localhost Tracking”. Meta, das Unternehmen hinter Facebook und Instagram, hat ein System entwickelt, das es ermöglicht, Nutzer auf ihren Mobilgeräten zu identifizieren, selbst wenn sie einen VPN-Dienst nutzen, den Inkognito-Modus ihres Browsers aktiviert haben oder Cookies ablehnen oder löschen. Diese Praxis könnte Meta teuer zu stehen kommen, […] <a href="https://dasnetzundich.de/localhost-tracking-eine-erklaerung-und-seine-potenziellen-konsequenzen-fuer-meta/" rel="nofollow noopener" translate="no" target="_blank">https://dasnetzundich.de/localhost-tracking-eine-erklaerung-und-seine-potenziellen-konsequenzen-fuer-meta/</a>

Murteza YesilAs a tech enthusiast, I am sad to say that even I couldn't see how disgusting Facebook can be. And given their track record, they probably something else in the works that will make my jaw drop in the future. Facebook's only competition at being evil is Facebook. <a href="https://edmontonian.social/tags/Meta" rel="nofollow noopener" target="_blank">#Meta</a> <a href="https://edmontonian.social/tags/Facebook" rel="nofollow noopener" target="_blank">#Facebook</a> <a href="https://edmontonian.social/tags/Instagram" rel="nofollow noopener" target="_blank">#Instagram</a> <a href="https://edmontonian.social/tags/localhostTracking" rel="nofollow noopener" target="_blank">#localhostTracking</a> RE: <a href="https://mastodon.social/users/Gargron/statuses/114661991523456008" rel="nofollow noopener" target="_blank">https://mastodon.social/users/Gargron/statuses/114661991523456008</a>

quaffIf you're on Android and you have any Meta apps installed, you need to remove those immediately and use the web versions (or just deactivate your accounts). iOS won't have this issue, but for good measure, do it anyway.Meta has been running background localhost services via their Android apps. The Meta Pixel trackers on websites post back to these services.Allowing them to track you when not using their apps. <a href="https://arstechnica.com/security/2025/06/meta-and-yandex-are-de-anonymizing-android-users-web-browsing-identifiers/" rel="nofollow noopener" translate="no" target="_blank">https://arstechnica.com/security/2025/06/meta-and-yandex-are-de-anonymizing-android-users-web-browsing-identifiers/</a><a href="https://thecanadian.social/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#cybersecurity</a> <a href="https://thecanadian.social/tags/meta" class="mention hashtag" rel="nofollow noopener" target="_blank">#meta</a> <a href="https://thecanadian.social/tags/facebook" class="mention hashtag" rel="nofollow noopener" target="_blank">#facebook</a> <a href="https://thecanadian.social/tags/localhosttracking" class="mention hashtag" rel="nofollow noopener" target="_blank">#localhosttracking</a>

quaffIf you're on Android and you have any Meta apps installed, you need to remove those immediately and use the web versions (or just deactivate your accounts). iOS won't have this issue, but for good measure, do it anyway.Meta has been running background localhost services via their Android apps. The Meta Pixel trackers on websites post back to these services.Allowing them to track you when not using their apps. <a href="https://cybersecuritynews.com/track-android-users-covertly" rel="nofollow noopener" translate="no" target="_blank">https://cybersecuritynews.com/track-android-users-covertly</a><a href="https://thecanadian.social/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#cybersecurity</a> <a href="https://thecanadian.social/tags/meta" class="mention hashtag" rel="nofollow noopener" target="_blank">#meta</a> <a href="https://thecanadian.social/tags/facebook" class="mention hashtag" rel="nofollow noopener" target="_blank">#facebook</a> <a href="https://thecanadian.social/tags/localhosttracking" class="mention hashtag" rel="nofollow noopener" target="_blank">#localhosttracking</a>

Hacker News"Localhost tracking" explained. It could cost Meta 32B<a href="https://www.zeropartydata.es/p/localhost-tracking-explained-it-could" rel="nofollow noopener" translate="no" target="_blank">https://www.zeropartydata.es/p/localhost-tracking-explained-it-could</a><a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#HackerNews</a> <a href="https://mastodon.social/tags/LocalhostTracking" class="mention hashtag" rel="nofollow noopener" target="_blank">#LocalhostTracking</a> <a href="https://mastodon.social/tags/Meta32B" class="mention hashtag" rel="nofollow noopener" target="_blank">#Meta32B</a> <a href="https://mastodon.social/tags/DigitalPrivacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#DigitalPrivacy</a> <a href="https://mastodon.social/tags/TechNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechNews</a> <a href="https://mastodon.social/tags/DataProtection" class="mention hashtag" rel="nofollow noopener" target="_blank">#DataProtection</a>

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#localhosttracking