home.social

#googlesafebrowsing — Public Fediverse posts

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

fetched live
  1. 📉🤣 Ah, #Huginn, the valiant dragon slayer revealing Google Safe Browsing's blunders—missing 84% of #phishing sites like a kid with a butterfly net. Meanwhile, Google is too busy counting their ad revenue 💸 to notice the phishing parade marching right through their front door. Good thing Huginn's here, huh? 🙄
    norn-labs.com/blog/huginn-repo #GoogleSafeBrowsing #DragonSlayer #cybersecurity #adrevenue #HackerNews #ngated

  2. 📉🤣 Ah, #Huginn, the valiant dragon slayer revealing Google Safe Browsing's blunders—missing 84% of #phishing sites like a kid with a butterfly net. Meanwhile, Google is too busy counting their ad revenue 💸 to notice the phishing parade marching right through their front door. Good thing Huginn's here, huh? 🙄
    norn-labs.com/blog/huginn-repo #GoogleSafeBrowsing #DragonSlayer #cybersecurity #adrevenue #HackerNews #ngated

  3. Why does #GoogleSafeBrowsing block www.referata.com? It's not malware, it's just down. I miss #Wikipapers. :(

    For context, wikipapers.referata.com/wiki/L was flagged as malicious on a friend's Google presentation and the entire presentation was deemed a ToS violation (?).

    #referata #SMW

  4. Why does #GoogleSafeBrowsing block www.referata.com? It's not malware, it's just down. I miss #Wikipapers. :(

    For context, wikipapers.referata.com/wiki/L was flagged as malicious on a friend's Google presentation and the entire presentation was deemed a ToS violation (?).

    #referata #SMW

  5. This month, #GoogleSafeBrowsing mistakenly flagged #CryptPad’s sandbox domain as #malicious. The warning popped up when users clicked external links, part of our #phishing protection system that redirects through a secure domain. It was displayed in #Google #Chrome but also in other browsers that rely on Google Safe Browsing as a source for security advisories, such as #Firefox. Despite reporting the issue several times, nothing changed.
    La suite : news.xwiki.com/email/view/6824

  6. This month, #GoogleSafeBrowsing mistakenly flagged #CryptPad’s sandbox domain as #malicious. The warning popped up when users clicked external links, part of our #phishing protection system that redirects through a secure domain. It was displayed in #Google #Chrome but also in other browsers that rely on Google Safe Browsing as a source for security advisories, such as #Firefox. Despite reporting the issue several times, nothing changed.
    La suite : news.xwiki.com/email/view/6824

  7. I'm impressed, I reported a phishing page to Google ( safebrowsing.google.com/safebr ) and roughly 30 minutes later all of the phishing domains tied to that campaign were flagged as malicious according to Google Safe browsing
    (ignore the Vt totals in the screenshot it's old)

    I want to think this isn't coincidence because I got a spam for the same thing tax-return-spam yesterday so it had been up for 24h+ and still wasn't flagged.

    Feels like the good deed of the day is done.

    #GoogleSafeBrowsing

  8. @Leefromphilly
    @paulknightly @xi_timpin
    Thanks for this info on how bad Goog is becoming.

    TorBrowser is a fork of Firefox with nasty trackers including "#GoogleSafeBrowsing" disabled, you can add #UBlock to TorBrowser and indeed, TailsOS does this by default.

    Not to derail the thread cos yes, NFT and altcoins are garbage. Careful not to lump Bitcoin it the same boat. The garbage is specifically pedalled to tarnish and derail the most important innovation since electricity, which is Bitcoin.

  9. @mconley
    Now we just need them to stop sending things to Google via "#GoogleSafeBrowsing" and other telemetry.

    Or get them to publicly endorse the #DigitalFeudalismCounteraAction setup that blocks the plutocrats at the network level. 😄

    If they are seriously using #MSGitHub at Mozilla, then really what hope is there?

  10. Comme nous le 18 février, rubygems.org a été complétement bloqué ce 11 mai par Google Safe Browsing

    cf. historique de la page de statuts de rubygems.org :

    status.rubygems.org/

    #googlesafebrowsing

  11. Comme nous le 18 février, rubygems.org a été complétement bloqué ce 11 mai par Google Safe Browsing

    cf. historique de la page de statuts de rubygems.org :

    status.rubygems.org/

    #googlesafebrowsing

  12. More fallout from the Google Safe Browsing List x rubygems.org fiasco. Blogger, which is owned by Google, started flagging blog posts that linked to rubygems.org. If we had ignored this problem, Google Safe Browsing List would have slowly killed all links to rubygems.org.
    reddit.com/r/ruby/comments/13e
    #rubygems #googlesafebrowsing

  13. More fallout from the Google Safe Browsing List x rubygems.org fiasco. Blogger, which is owned by Google, started flagging blog posts that linked to rubygems.org. If we had ignored this problem, Google Safe Browsing List would have slowly killed all links to rubygems.org.
    reddit.com/r/ruby/comments/13e
    #rubygems #googlesafebrowsing

  14. While I may have an ongoing struggle with Bing, I found an article about an even worse problem -- being incorrectly flagged by Google Safe Browsing. (Not wanting to tempt fate, I only wrote a short post on the matter.)

    thenewleafjournal.com/leafbud/

    #google #bing #googlesafebrowsing #webmaster

  15. @epoch
    Agree here.

    There may be multiple things going on here.

    #EnterprisePolicy will mean default policy for admins that lack a proper understanding, ie. most.
    • People with ethics have left #Google, look at almost any choice they've made in past years. Tip: disable #GoogleSafeBrowsing.
    • Machines are writing code, for the benefit of machines. Why allow people to learn how websites work when we don't want them to? Tip: #disableWebAssembly in your browser right now.
    #useTorBrowser
    @mhoye

  16. @Moon
    Its so criminal lawsuits can't be filed against him, that could ultimately rally the base to support things like #uploadFilters, #Fakebook style AI to boost "#authoritarian (-we mean #authoratative) sources", and #googleSafeBrowsing-style, #telemetry.

    So we don't need more eyeballs on the code, in the form of local FeatureBounties and #BugBounties. Like what we produced as part of our (#)FediFlyer.

    :P
    @lain

  17. @samuraikid
    How is #Firefox not in this list?

    Location data, #DNSOverHttps to #Cloudflare, #GoogleSafeBrowsing that looks for words and phrases on the pages that you load for possible questionable content and then sends that site to bloody #Google.

    Firefox connects to #Amazon a lot, too!

  18. Um vor betrügerischen Websites zu warnen, kontaktiert Safari eine Google-API. Künftig schaltet Apple einen Proxy vor, um Informationslecks zu vermeiden.
    Betrugswarnung im Apple-Browser: Google soll weniger Einblick erhalten
  19. @djsumdog
    3/4

    ts a narrative that worked for Jan 6. Google will ban Fedi via #GoogleSafeBrowsing. They already have layed groundwork for this by threatening to remove Fedilab from the #Playstore. As a sidenote, is anyone watching the commits to Fedilab since "help®" came along?

    We don't say this to spread FUD, only to strengthen our understanding of how the #securityState seems to be working.

    We are in the process of designing a simple #FediFlyer, to inspire people to ditch Fakebook.

  20. @tallship
    Thanks for your response, Tallship.

    It seems that we agree in many respects.

    One thing to consider is whether FDroid would need to become FBrowser. Two reasons. The code chunks could be assessed to conform to a SHASUM (ignoring that we're unsure if FDroid would even compile WebAssembly). The other reason is to ditch #GoogleSafeBrowsing, if we are concerned about privacy and censorship then checking a DL'ed #PWA with Google for "#safety" would bring us back to square one.
    @tallship