home.social

#webenvironmentintegrity — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #webenvironmentintegrity, aggregated by home.social.

  1. Andres @[email protected] ·

    well that's nice github.com/ungoogled-software/

    #chromium #WebEnvironmentIntegrity

    #chromium #webenvironmentintegrity
  2. Andres @[email protected] ·

    well that's nice github.com/ungoogled-software/

    #chromium #WebEnvironmentIntegrity

    #chromium #webenvironmentintegrity
  3. Andres @[email protected] ·

    well that's nice github.com/ungoogled-software/

    #chromium #WebEnvironmentIntegrity

    #chromium #webenvironmentintegrity
  4. Andres @[email protected] ·

    well that's nice github.com/ungoogled-software/

    #chromium #WebEnvironmentIntegrity

    #webenvironmentintegrity #chromium
  5. Andres @[email protected] ·

    well that's nice github.com/ungoogled-software/

    #chromium #WebEnvironmentIntegrity

    #chromium #webenvironmentintegrity
  6. Crazy-to-Bike :Firefish: @[email protected] ·

    @[email protected]

    Was meinst du?
    Startpage greift auf Googleergebnisse zurrück. Man bleibt aber gegenüber Google anonym, weil Startpage "dazwischen sitzt".

    Aktuelles Problem ist aber, dass Google daran arbeitet, durch die Wahl des Browsers oder eingesetzter Datenschutzaddons noch besser bestimmen zu können, ob du dann gewisse Inhalte überhaupt ausgeliefert bekommst.
    Das Stichwort lautet     #WebEnvironmentIntegrity” (#WEI)

    https://digitalcourage.de/blog/2023/google-web-environment-integrity

    @[email protected]

    #webenvironmentintegrity #wei
  7. Crazy-to-Bike :Firefish: @[email protected] ·

    @[email protected]

    Was meinst du?
    Startpage greift auf Googleergebnisse zurrück. Man bleibt aber gegenüber Google anonym, weil Startpage "dazwischen sitzt".

    Aktuelles Problem ist aber, dass Google daran arbeitet, durch die Wahl des Browsers oder eingesetzter Datenschutzaddons noch besser bestimmen zu können, ob du dann gewisse Inhalte überhaupt ausgeliefert bekommst.
    Das Stichwort lautet     #WebEnvironmentIntegrity” (#WEI)

    https://digitalcourage.de/blog/2023/google-web-environment-integrity

    @[email protected]

    #webenvironmentintegrity #wei
  8. Stefan Bohacek @[email protected] ·

    "We’ve heard your feedback, and the Web Environment Integrity proposal is no longer being considered by the Chrome team."

    android-developers.googleblog.

    Via arstechnica.com/google/2023/11

    #tech #news #google #chrome #drm #WebEnvironmentIntegrity #OpenWeb

    #openweb #tech #news #google #chrome #drm
  9. Stefan Bohacek @[email protected] ·

    "We’ve heard your feedback, and the Web Environment Integrity proposal is no longer being considered by the Chrome team."

    android-developers.googleblog.

    Via arstechnica.com/google/2023/11

    #tech #news #google #chrome #drm #WebEnvironmentIntegrity #OpenWeb

    #openweb #tech #news #google #chrome #drm
  10. Stefan Bohacek @[email protected] ·

    "We’ve heard your feedback, and the Web Environment Integrity proposal is no longer being considered by the Chrome team."

    android-developers.googleblog.

    Via arstechnica.com/google/2023/11

    #tech #news #google #chrome #drm #WebEnvironmentIntegrity #OpenWeb

    #tech #news #google #chrome #drm #webenvironmentintegrity
  11. Stefan Bohacek @[email protected] ·

    "We’ve heard your feedback, and the Web Environment Integrity proposal is no longer being considered by the Chrome team."

    android-developers.googleblog.

    Via arstechnica.com/google/2023/11

    #tech #news #google #chrome #drm #WebEnvironmentIntegrity #OpenWeb

    #openweb #webenvironmentintegrity #drm #chrome #google #news
  12. Stefan Bohacek @[email protected] ·

    "We’ve heard your feedback, and the Web Environment Integrity proposal is no longer being considered by the Chrome team."

    android-developers.googleblog.

    Via arstechnica.com/google/2023/11

    #tech #news #google #chrome #drm #WebEnvironmentIntegrity #OpenWeb

    #openweb #tech #news #google #chrome #drm
  13. Cory Doctorow @[email protected] ·
    CW: Long thread/13

    It's a reminder that what a monopolist thinks of as "security" isn't what you think of as security. Oftentimes, *their* security is antithetical to *your* security. That was the case with #WebEnvironmentIntegrity, a plan by Google to make your phone rat you out to advertisers' servers, revealing any adblocking modifications you might have installed so that ad-serving companies could refuse to talk to you:

    pluralistic.net/2023/08/02/sel

    13/

    #webenvironmentintegrity
  14. Cory Doctorow @[email protected] ·
    CW: Long thread/13

    It's a reminder that what a monopolist thinks of as "security" isn't what you think of as security. Oftentimes, *their* security is antithetical to *your* security. That was the case with #WebEnvironmentIntegrity, a plan by Google to make your phone rat you out to advertisers' servers, revealing any adblocking modifications you might have installed so that ad-serving companies could refuse to talk to you:

    pluralistic.net/2023/08/02/sel

    13/

    #webenvironmentintegrity
  15. Cory Doctorow @[email protected] ·
    CW: Long thread/13

    It's a reminder that what a monopolist thinks of as "security" isn't what you think of as security. Oftentimes, *their* security is antithetical to *your* security. That was the case with #WebEnvironmentIntegrity, a plan by Google to make your phone rat you out to advertisers' servers, revealing any adblocking modifications you might have installed so that ad-serving companies could refuse to talk to you:

    pluralistic.net/2023/08/02/sel

    13/

    #webenvironmentintegrity
  16. Cory Doctorow @[email protected] ·
    CW: Long thread/13

    It's a reminder that what a monopolist thinks of as "security" isn't what you think of as security. Oftentimes, *their* security is antithetical to *your* security. That was the case with #WebEnvironmentIntegrity, a plan by Google to make your phone rat you out to advertisers' servers, revealing any adblocking modifications you might have installed so that ad-serving companies could refuse to talk to you:

    pluralistic.net/2023/08/02/sel

    13/

    #webenvironmentintegrity
  17. Cory Doctorow @[email protected] ·
    CW: Long thread/13

    It's a reminder that what a monopolist thinks of as "security" isn't what you think of as security. Oftentimes, *their* security is antithetical to *your* security. That was the case with #WebEnvironmentIntegrity, a plan by Google to make your phone rat you out to advertisers' servers, revealing any adblocking modifications you might have installed so that ad-serving companies could refuse to talk to you:

    pluralistic.net/2023/08/02/sel

    13/

    #webenvironmentintegrity
  18. Christian Pietsch (old acct.) @[email protected] ·

    @Natanox Du musst aufs Datum achten. #WEI wurde vor wenigen Tagen erst abgesagt. Der von mir übersetzte Rant ist vom August und kann deshalb noch nicht auf diese neue Entwicklung eingehen.

    Wie der auf Android-Apps beschränkte WEI-Nachfolger zu bewerten ist, würde ich gern hier diskutieren. Bisher erschließt sich mir der Sinn nicht.

    #WebEnvironmentIntegrity

    #webenvironmentintegrity #wei
  19. Christian Pietsch (old acct.) @[email protected] ·

    @Natanox Du musst aufs Datum achten. #WEI wurde vor wenigen Tagen erst abgesagt. Der von mir übersetzte Rant ist vom August und kann deshalb noch nicht auf diese neue Entwicklung eingehen.

    Wie der auf Android-Apps beschränkte WEI-Nachfolger zu bewerten ist, würde ich gern hier diskutieren. Bisher erschließt sich mir der Sinn nicht.

    #WebEnvironmentIntegrity

    #webenvironmentintegrity #wei
  20. Christian Pietsch (old acct.) @[email protected] ·

    @Natanox Du musst aufs Datum achten. #WEI wurde vor wenigen Tagen erst abgesagt. Der von mir übersetzte Rant ist vom August und kann deshalb noch nicht auf diese neue Entwicklung eingehen.

    Wie der auf Android-Apps beschränkte WEI-Nachfolger zu bewerten ist, würde ich gern hier diskutieren. Bisher erschließt sich mir der Sinn nicht.

    #WebEnvironmentIntegrity

    #webenvironmentintegrity #wei
  21. Christian Pietsch (old acct.) @[email protected] ·

    @Natanox Du musst aufs Datum achten. #WEI wurde vor wenigen Tagen erst abgesagt. Der von mir übersetzte Rant ist vom August und kann deshalb noch nicht auf diese neue Entwicklung eingehen.

    Wie der auf Android-Apps beschränkte WEI-Nachfolger zu bewerten ist, würde ich gern hier diskutieren. Bisher erschließt sich mir der Sinn nicht.

    #WebEnvironmentIntegrity

    #wei #webenvironmentintegrity
  22. Christian Pietsch (old acct.) @[email protected] ·

    @Natanox Du musst aufs Datum achten. #WEI wurde vor wenigen Tagen erst abgesagt. Der von mir übersetzte Rant ist vom August und kann deshalb noch nicht auf diese neue Entwicklung eingehen.

    Wie der auf Android-Apps beschränkte WEI-Nachfolger zu bewerten ist, würde ich gern hier diskutieren. Bisher erschließt sich mir der Sinn nicht.

    #WebEnvironmentIntegrity

    #webenvironmentintegrity #wei
  23. Nachtaktiv :fckafd: :nonazis: @[email protected] ·

    @chpietsch
    Der nächste Angriff auf Demokratie und Menschenrechte.

    #WebEnvironmentIntegrity #WEI #Google #Privatsphäre #privacysandbox

    #webenvironmentintegrity #wei #google #privatsphare #privacysandbox
  24. Nachtaktiv :fckafd: :nonazis: @[email protected] ·

    @chpietsch
    Der nächste Angriff auf Demokratie und Menschenrechte.

    #WebEnvironmentIntegrity #WEI #Google #Privatsphäre #privacysandbox

    #webenvironmentintegrity #wei #google #privatsphare #privacysandbox
  25. Nachtaktiv :fckafd: :nonazis: @[email protected] ·

    @chpietsch
    Der nächste Angriff auf Demokratie und Menschenrechte.

    #WebEnvironmentIntegrity #WEI #Google #Privatsphäre #privacysandbox

    #webenvironmentintegrity #wei #google #privatsphare #privacysandbox
  26. Nachtaktiv :fckafd: :nonazis: @[email protected] ·

    @chpietsch
    Der nächste Angriff auf Demokratie und Menschenrechte.

    #WebEnvironmentIntegrity #WEI #Google #Privatsphäre #privacysandbox

    #privacysandbox #privatsphare #google #wei #webenvironmentintegrity
  27. Nachtaktiv :fckafd: :nonazis: @[email protected] ·

    @chpietsch
    Der nächste Angriff auf Demokratie und Menschenrechte.

    #WebEnvironmentIntegrity #WEI #Google #Privatsphäre #privacysandbox

    #webenvironmentintegrity #wei #google #privatsphare #privacysandbox
  28. MOULE @[email protected] ·

    Web Environment Integrity got cancelled 🙌

    github.com/RupertBenWiser/Web-

    #WebEnvironmentIntegrity #WEI #WebEnvironmentIntegrityAPI

    #webenvironmentintegrity #wei #webenvironmentintegrityapi
  29. MOULE :Logo: @[email protected] ·

    Web Environment Integrity got cancelled 🙌

    github.com/RupertBenWiser/Web-

    #WebEnvironmentIntegrity #WEI #WebEnvironmentIntegrityAPI

    #webenvironmentintegrity #wei #webenvironmentintegrityapi
  30. MOULE :Logo: @[email protected] ·

    Web Environment Integrity got cancelled 🙌

    github.com/RupertBenWiser/Web-

    #WebEnvironmentIntegrity #WEI #WebEnvironmentIntegrityAPI

    #webenvironmentintegrity #wei #webenvironmentintegrityapi
  31. MOULE :Logo: @[email protected] ·

    Web Environment Integrity got cancelled 🙌

    github.com/RupertBenWiser/Web-

    #WebEnvironmentIntegrity #WEI #WebEnvironmentIntegrityAPI

    #webenvironmentintegrityapi #wei #webenvironmentintegrity
  32. MOULE :Logo: @[email protected] ·

    Web Environment Integrity got cancelled 🙌

    github.com/RupertBenWiser/Web-

    #WebEnvironmentIntegrity #WEI #WebEnvironmentIntegrityAPI

    #webenvironmentintegrity #wei #webenvironmentintegrityapi
  33. Gokul Das @goku12 ·

    And Google has abandoned . Yay! The End!

    Mm... No! Google has 'heard your feedback' and has instead created 'WebView Media Integrity API' that is 'narrowly scoped' and 'only targets' .

    Think about it - now they don't have to listen to anyone's 'feedback'. And if you think the scope is going to remain narrow, boy! I have news for you! /Topics anyone? Fool me once - shame on you! Fool me twice...

    android-developers.googleblog.

    #webenvironmentintegrity #androidwebview #floc
  34. Gokul Das @[email protected] ·

    And Google has abandoned #WebEnvironmentIntegrity. Yay! The End!

    Mm... No! Google has 'heard your feedback' and has instead created 'WebView Media Integrity API' that is 'narrowly scoped' and 'only targets' #AndroidWebView.

    Think about it - now they don't have to listen to anyone's 'feedback'. And if you think the scope is going to remain narrow, boy! I have news for you! #FLoC/Topics anyone? Fool me once - shame on you! Fool me twice...

    android-developers.googleblog.

    #webenvironmentintegrity #androidwebview #floc
  35. Gokul Das @[email protected] ·

    And Google has abandoned #WebEnvironmentIntegrity. Yay! The End!

    Mm... No! Google has 'heard your feedback' and has instead created 'WebView Media Integrity API' that is 'narrowly scoped' and 'only targets' #AndroidWebView.

    Think about it - now they don't have to listen to anyone's 'feedback'. And if you think the scope is going to remain narrow, boy! I have news for you! #FLoC/Topics anyone? Fool me once - shame on you! Fool me twice...

    android-developers.googleblog.

    #webenvironmentintegrity #androidwebview #floc
  36. Gokul Das @[email protected] ·

    And Google has abandoned #WebEnvironmentIntegrity. Yay! The End!

    Mm... No! Google has 'heard your feedback' and has instead created 'WebView Media Integrity API' that is 'narrowly scoped' and 'only targets' #AndroidWebView.

    Think about it - now they don't have to listen to anyone's 'feedback'. And if you think the scope is going to remain narrow, boy! I have news for you! #FLoC/Topics anyone? Fool me once - shame on you! Fool me twice...

    android-developers.googleblog.

    #floc #androidwebview #webenvironmentintegrity
  37. Gokul Das @[email protected] ·

    And Google has abandoned #WebEnvironmentIntegrity. Yay! The End!

    Mm... No! Google has 'heard our feedback' and has instead created 'WebView Media Integrity API' that is 'narrowly scoped' and 'only targets' #AndroidWebView.

    Think about it - now they don't have to listen to anyone's 'feedback'. And if you think the scope is going to remain narrow, boy! I have news for you! #FLoC/Topics anyone? Fool me once - shame on you! Fool me twice...

    android-developers.googleblog.

    #webenvironmentintegrity #androidwebview #floc
  38. Vivaldi Browser @[email protected] ·

    We'd opposed #Google's 'dangerous' Web integrity API proposal. Now they are backing off!

    This is massively positive for the neutrality of the open Web. Though Google is so heavily driven by its interests rather than the benefit of the Web in general, it remains to be seen (and we strongly suspect it won’t take long) what they choose to replace it with.
    Are they, for example, preparing a seemingly less obnoxious spec that is actually just as harmful to users (as they did with #FLOC & #Topics)?
    It is highly suspicious that it coincides with their recent announcement to move from pay-per-click to pay-per-impression for ads.
    Generally, Google hasn’t shown itself to be a trustworthy custodian of the web & we can’t let this apparent victory lure us into resting on our laurels.
    A strong diversity of browsers & browser engines is going to be crucial to counteract any future attempt by a single party to dictate the future of the web.

    For more on this, head to our blog. ⬇️
    vivaldi.com/blog/googles-new-d

    #WEI #WebEnvironmentIntegrity

    #google #floc #topics #wei #webenvironmentintegrity
  39. Vivaldi Browser @[email protected] ·

    We'd opposed #Google's 'dangerous' Web integrity API proposal. Now they are backing off!

    This is massively positive for the neutrality of the open Web. Though Google is so heavily driven by its interests rather than the benefit of the Web in general, it remains to be seen (and we strongly suspect it won’t take long) what they choose to replace it with.
    Are they, for example, preparing a seemingly less obnoxious spec that is actually just as harmful to users (as they did with #FLOC & #Topics)?
    It is highly suspicious that it coincides with their recent announcement to move from pay-per-click to pay-per-impression for ads.
    Generally, Google hasn’t shown itself to be a trustworthy custodian of the web & we can’t let this apparent victory lure us into resting on our laurels.
    A strong diversity of browsers & browser engines is going to be crucial to counteract any future attempt by a single party to dictate the future of the web.

    For more on this, head to our blog. ⬇️
    vivaldi.com/blog/googles-new-d

    #WEI #WebEnvironmentIntegrity

    #google #floc #topics #wei #webenvironmentintegrity
  40. Vivaldi Browser @[email protected] ·

    We'd opposed #Google's 'dangerous' Web integrity API proposal. Now they are backing off!

    This is massively positive for the neutrality of the open Web. Though Google is so heavily driven by its interests rather than the benefit of the Web in general, it remains to be seen (and we strongly suspect it won’t take long) what they choose to replace it with.
    Are they, for example, preparing a seemingly less obnoxious spec that is actually just as harmful to users (as they did with #FLOC & #Topics)?
    It is highly suspicious that it coincides with their recent announcement to move from pay-per-click to pay-per-impression for ads.
    Generally, Google hasn’t shown itself to be a trustworthy custodian of the web & we can’t let this apparent victory lure us into resting on our laurels.
    A strong diversity of browsers & browser engines is going to be crucial to counteract any future attempt by a single party to dictate the future of the web.

    For more on this, head to our blog. ⬇️
    vivaldi.com/blog/googles-new-d

    #WEI #WebEnvironmentIntegrity

    #google #floc #topics #wei #webenvironmentintegrity
  41. Vivaldi Browser @[email protected] ·

    We'd opposed #Google's 'dangerous' Web integrity API proposal. Now they are backing off!

    This is massively positive for the neutrality of the open Web. Though Google is so heavily driven by its interests rather than the benefit of the Web in general, it remains to be seen (and we strongly suspect it won’t take long) what they choose to replace it with.
    Are they, for example, preparing a seemingly less obnoxious spec that is actually just as harmful to users (as they did with #FLOC & #Topics)?
    It is highly suspicious that it coincides with their recent announcement to move from pay-per-click to pay-per-impression for ads.
    Generally, Google hasn’t shown itself to be a trustworthy custodian of the web & we can’t let this apparent victory lure us into resting on our laurels.
    A strong diversity of browsers & browser engines is going to be crucial to counteract any future attempt by a single party to dictate the future of the web.

    For more on this, head to our blog. ⬇️
    vivaldi.com/blog/googles-new-d

    #WEI #WebEnvironmentIntegrity

    #webenvironmentintegrity #wei #topics #floc #google
  42. Vivaldi Browser @[email protected] ·

    We'd opposed #Google's 'dangerous' Web integrity API proposal. Now they are backing off!

    This is massively positive for the neutrality of the open Web. Though Google is so heavily driven by its interests rather than the benefit of the Web in general, it remains to be seen (and we strongly suspect it won’t take long) what they choose to replace it with.
    Are they, for example, preparing a seemingly less obnoxious spec that is actually just as harmful to users (as they did with #FLOC & #Topics)?
    It is highly suspicious that it coincides with their recent announcement to move from pay-per-click to pay-per-impression for ads.
    Generally, Google hasn’t shown itself to be a trustworthy custodian of the web & we can’t let this apparent victory lure us into resting on our laurels.
    A strong diversity of browsers & browser engines is going to be crucial to counteract any future attempt by a single party to dictate the future of the web.

    For more on this, head to our blog. ⬇️
    vivaldi.com/blog/googles-new-d

    #WEI #WebEnvironmentIntegrity

    #google #floc #topics #wei #webenvironmentintegrity
  43. Christian Pietsch (old acct.) @[email protected] ·

    Gut: #WebEnvironmentIntegrity ist tot!

    Schlecht: Android-User bekommen #WEI trotzdem: android-developers.googleblog.

    Wir haben uns fast schon daran gewöhnt, dass #Google in jedem Quartal einen neuen Angriff auf unsere #Privatsphäre oder auf das offene Web startet. Gern mit einem orwellschen Euphemismus benamt wie #privacysandbox.

    Ein Rant: digitalcourage.de/blog/2023/go

    #privacysandbox #privatsphare #google #wei #webenvironmentintegrity
  44. Christian Pietsch (old acct.) @[email protected] ·

    Gut: #WebEnvironmentIntegrity ist tot!

    Schlecht: Android-User bekommen #WEI trotzdem: android-developers.googleblog.

    Wir haben uns fast schon daran gewöhnt, dass #Google in jedem Quartal einen neuen Angriff auf unsere #Privatsphäre oder auf das offene Web startet. Gern mit einem orwellschen Euphemismus benamt wie #privacysandbox.

    Ein Rant: digitalcourage.de/blog/2023/go

    #privacysandbox #privatsphare #google #wei #webenvironmentintegrity
  45. Christian Pietsch (old acct.) @[email protected] ·

    Gut: #WebEnvironmentIntegrity ist tot!

    Schlecht: Android-User bekommen #WEI trotzdem: android-developers.googleblog.

    Wir haben uns fast schon daran gewöhnt, dass #Google in jedem Quartal einen neuen Angriff auf unsere #Privatsphäre oder auf das offene Web startet. Gern mit einem orwellschen Euphemismus benamt wie #privacysandbox.

    Ein Rant: digitalcourage.de/blog/2023/go

    #privacysandbox #privatsphare #google #wei #webenvironmentintegrity
  46. Christian Pietsch (old acct.) @[email protected] ·

    Gut: #WebEnvironmentIntegrity ist tot!

    Schlecht: Android-User bekommen #WEI trotzdem: android-developers.googleblog.

    Wir haben uns fast schon daran gewöhnt, dass #Google in jedem Quartal einen neuen Angriff auf unsere #Privatsphäre oder auf das offene Web startet. Gern mit einem orwellschen Euphemismus benamt wie #privacysandbox.

    Ein Rant: digitalcourage.de/blog/2023/go

    #webenvironmentintegrity #wei #google #privatsphare #privacysandbox
  47. Christian Pietsch (old acct.) @[email protected] ·

    Gut: #WebEnvironmentIntegrity ist tot!

    Schlecht: Android-User bekommen #WEI trotzdem: android-developers.googleblog.

    Wir haben uns fast schon daran gewöhnt, dass #Google in jedem Quartal einen neuen Angriff auf unsere #Privatsphäre oder auf das offene Web startet. Gern mit einem orwellschen Euphemismus benamt wie #privacysandbox.

    Ein Rant: digitalcourage.de/blog/2023/go

    #privacysandbox #privatsphare #google #wei #webenvironmentintegrity
  48. Pierre \ Ra-Mon :vivaldi_blue: @[email protected] ·

    Tiens, il semblerait que G👀gle ait décidé d'abandonner son projet fou dit #WebEnvironmentIntegrity 👍

    9to5google.com/2023/11/02/goog
    “Web Environment Integrity proposal is no longer being considered by the Chrome team.”

    #WEI #ViePrivée

    #webenvironmentintegrity #wei #vieprivee
  49. Pierre \ Ra-Mon :vivaldi_blue: @[email protected] ·

    Tiens, il semblerait que G👀gle ait décidé d'abandonner son projet fou dit #WebEnvironmentIntegrity 👍

    9to5google.com/2023/11/02/goog
    “Web Environment Integrity proposal is no longer being considered by the Chrome team.”

    #WEI #ViePrivée

    #webenvironmentintegrity #wei #vieprivee
  50. Pierre \ Ra-Mon :vivaldi_blue: @[email protected] ·

    Tiens, il semblerait que G👀gle ait décidé d'abandonner son projet fou dit #WebEnvironmentIntegrity 👍

    9to5google.com/2023/11/02/goog
    “Web Environment Integrity proposal is no longer being considered by the Chrome team.”

    #WEI #ViePrivée

    #webenvironmentintegrity #wei #vieprivee