Post B6jHIdu6LjDGsIcGGm by IzzyOnDroid@floss.social
 (DIR) More posts by IzzyOnDroid@floss.social
 (DIR) Post #B6jBjoXYJR9FxMdsTQ by IzzyOnDroid@floss.social
       0 likes, 0 repeats
       
       Wow, new record: less than 3 days for the next false positive. What do the folks at #Google #SafeBrowsing have as profession? How many clowns do they have for breakfast? 🤦‍♂️OK, "same procedure as every year, James". Tell me y'all have turned off this fake security setting, and I simply stop playing their game…https://gitlab.com/-/snippets/4909577#google-safebrowsing
       
 (DIR) Post #B6jDCcl1IdAVlUF86a by geotux@social.tchncs.de
       0 likes, 0 repeats
       
       @IzzyOnDroid No " #safebrowsing " here ... #fairphone with #murena #eos
       
 (DIR) Post #B6jHIdu6LjDGsIcGGm by IzzyOnDroid@floss.social
       0 likes, 0 repeats
       
       @inawhilecrocodile Yes, we had such suspicion as well in the past. What speaks against this _currently_ is which site is being reported. It's not the subdomain hosting our repo, but a different subdomain to the same second-level one 🤷‍♂️ Not saying it "cannot" be. And maybe it's multiple things, who knows.Still, marking a website "red" without any verification (and how will you verify an empty URL field), is neither sensible nor responsible.
       
 (DIR) Post #B6jTPGcWVwoO8hJrbU by IzzyOnDroid@floss.social
       0 likes, 0 repeats
       
       @inawhilecrocodile Thanks! Reading this confirms what we figured so far. And no, those solutions do not work for us, unfortunately. There will certainly be some restructuring on our end, though (to get the remaing stuff over from _my_ domains to the IzzyOnDroid domains), but that will take time. And funding (currently we spend more our of our own pockets than incoming contributions cover).