• 0 Posts
  • 84 Comments
Joined 10 months ago
cake
Cake day: September 9th, 2023

help-circle















  • Maybe they’re still on a G Suite Business / Workspace with the storage quota exceeded. Until earlier this year, Google didn’t do anything about exceeded quotas, and many had more than the included 5TB stored in their drive. I’ve seen people who had 100s of TB! I myself “only” have ~25TB, which I’m finally downloading to my local storage these days. When Google began caring about the storage quotas, they froze all accounts with exceeded quotas, blocking any new uploads – but if you keep paying the subscription (~20€), they’ll retain the frozen files for an extended time period of a year or two (don’t remember) after they gave the first notice.




  • I like your way of thinking. This isn’t even limited to image. Comparing just a short snippet of the audio from a playing ad to a db could work very well too, thinking of how quickly Shazam etc. are able to identify a song if it’s in the db.

    App/plugin idea for the sad future right there: Shazadblock, tuneBlock Origin. Succesful ID leads to skip/mute/ragequit or whatever will kill the noise. Though, the downside of this method would be if an ad in the db uses licensed music that regular content creators use in their videos too, it will eventually lead to blocking some segments wrongly, unless the db excludes this, making it less effective at its purpose… Maybe image is better.


  • Oh, I think I misunderstood your comment. I thought what you said was that after installing GrapheneOS, you wouldn’t receive firmware updates from Google. What you actually said was, correct me if I’m wrong, that GrapheneOS will only be able to release updates for a device as long as Google itself does so, because they’re based on Google’s updates, right? Does this mean that other custom ROMS that are based on a different approach will be able to keep releasing updates for a device after Google stops at “EoL” after 7 years?