mastodonien.de

mstdn.social

Zeitpunkt              Nutzer    Delta   Tröts        TNR     Titel                     Version  maxTL
Di 09.07.2024 00:01:07   230.034    +122   16.958.186    73,7 Mastodon 🐘                4.3.0...   500
Mo 08.07.2024 00:00:26   229.912     +78   16.944.690    73,7 Mastodon 🐘                4.3.0...   500
So 07.07.2024 00:01:05   229.834     +87   16.931.802    73,7 Mastodon 🐘                4.3.0...   500
Sa 06.07.2024 00:01:05   229.747     +84   16.926.091    73,7 Mastodon 🐘                4.3.0...   500
Fr 05.07.2024 00:00:51   229.663    +114   16.916.454    73,7 Mastodon 🐘                4.3.0...   500
Do 04.07.2024 00:00:49   229.549      +1   16.902.639    73,6 Mastodon 🐘                4.3.0...   500
Mi 03.07.2024 00:00:06   229.548      -5   16.887.661    73,6 Mastodon 🐘                4.3.0...   500
Di 02.07.2024 00:01:44   229.553      +1   16.872.533    73,5 Mastodon 🐘                4.3.0...   500
Mo 01.07.2024 00:00:13   229.552     +73   16.860.740    73,5 Mastodon 🐘                4.3.0...   500
So 30.06.2024 00:00:09   229.479       0   16.849.111    73,4 Mastodon 🐘                4.3.0...   500

Di 09.07.2024 20:15

+1 reason why you must stop using Chrome and, if possible, Chromium browsers

Luca Casonato (@lcasdev): So, Google Chrome gives all *.google.com sites full access to system / tab CPU usage, GPU usage, and memory usage. It also gives access to detailed processor information, and provides a logging backchannel. This API is not exposed to other sites - only to *.google.com. This is interesting because it is a clear violation of the idea that browser vendors should not give preference to their websites over anyone elses. The DMA codifies this idea into law: browser vendors, as gatekeepers of the internet, must give the same capabilities to everyone Depending on how you interpret the DMA, this additional exposure of information only to Google properties may be considered a violation of the DMA. Take for example Zoom - they are now at a disadvantage because they can not provide the same CPU debugging feature as Google Meet For those interested: this is done through a built-in Chrome extension that can not be disabled, and does not show up in the extensions panel. Source code is here: https://source.chromium.org/chromium/chromium/src/+/main:chrome/browser/resources/hangout_services/ It is unclear whether the same extension also ships in other Chromium derived browsers

Luca Casonato (@lcasdev): So, Google Chrome gives all *.google.com sites full access to system / tab CPU usage, GPU usage, and memory usage. It also gives access to detailed processor information, and provides a logging backchannel. This API is not exposed to other sites - only to *.google.com. This is interesting because it is a clear violation of the idea that browser vendors should not give preference to their websites over anyone elses. The DMA codifies this idea into law: browser vendors, as gatekeepers of the internet, must give the same capabilities to everyone Depending on how you interpret the DMA, this additional exposure of information only to Google properties may be considered a violation of the DMA. Take for example Zoom - they are now at a disadvantage because they can not provide the same CPU debugging feature as Google Meet For those interested: this is done through a built-in Chrome extension that can not be disabled, and does not show up in the extensions panel. Source code is here: https://source.chromium.org/chromium/chromium/src/+/main:chrome/browser/resources/hangout_services/ It is unclear whether the same extension also ships in other Chromium derived browsers

[Öffentlich] Antw.: 0 Wtrl.: 0 Fav.: 0

Antw. · Weiterl. · Fav. · Lesez. · Pin · Stumm · Löschen