• 0 Posts
  • 84 Comments
Joined 1 year ago
cake
Cake day: July 16th, 2023

help-circle
  • If they’re really just after data at all costs, they could easily spin up an instance that has no apparent link to threads and federate secretly. I agree with other arguments about not federating with them but idk, all these data privacy arguments against federating with threads are so dumb. If they want it, they’ll get it because getting it is so absurdly easy.
















  • Huh? I mean I’d argue that the local authorities have the most responsibility in this case. I don’t really think google is too responsible here. I guess you could make an argument that people tried reporting it but ultimately the local authorities should have clearly blocked it off. It’s really no different than using an old physical map; it shows you the way but things change so you always need to use discretion. I can’t count how many times I’ve followed my GPS only to be blocked by construction or something along those lines. In those situations, there needs to be clear signage or a barricade which is basically what I’m arguing is applicable here.





  • Given that there weren’t any signs or barriers, it sounds like the local authorities are the ones at fault here. It could even be that that didn’t file the proper paperwork to indicate that it collapsed. Google gets it’s information from some database and if their sources aren’t accurately reporting data as they should, google wouldn’t have any way of knowing that the bridge collapsed. Ultimately, hazards like this should be clearly blocked off. Google doesn’t have the power to do that.