5 ms·

I don't think it was mentioned in the repo readme, but this will most likely get your account banned. Be careful

by issafram 2y ago

s3arch 2y ago
can you help me understand more.
- 01HNNWZ0MV43FF 2y ago
  It stores file data as calendar events, sort of like that YouTube FS from a while back This is probably considered abuse under the ToS since you're using more storage than any typical user, and they can't use it for whatever they normally sell customer data for
  - exe34 2y ago
    > they can't use it for whatever they normally sell customer data for Bottom line, you don't want to mess with their bottom line.
    - darby_nine 2y ago
      I seriously doubt this kind of stuff has ever messed with their bottom line. I think they just really resent users trying to do more with their service than they intended.
      - exe34 2y ago
        they would prefer that you pay them for storage rather than store white noise on YouTube from which they can't earn ad money.
      - 01HNNWZ0MV43FF 2y ago
        If they didn't crack down, people would start pushing it harder, until some company relied on this for cloud storage
        darby_nine 2y ago
        I think this is a ridiculous sentiment, but I understand why it's so common. Proactively trying to head-off any and all possible problems before they cause measurable impact is not a great way to manage a product. Maybe they did see impact, but I still would have rewarded non-abusive loyal customers for using the product—maybe restrict access based on resource-usage rather than hitting people with TOS violations. Instead this attitude (plus their generally very poor track record at supporting and improving their own products) has caused me to abandon all google products outside of work.
        exe34 2y ago
        exponentially slower access and start corrupting them by flipping cases.
lvkv 2y ago
Yeah, I’ll update the README to be more specific about this. This is also why I didn’t provide instructions on how to use the tool :)
- issafram 2y ago
  This isn't exactly clear about the dangers of using the tool https://github.com/lvkv/whenfs/commit/618d6c343b2660567256faff78fc1f4ed6439536 https://github.com/lvkv/whenfs/commit/618d6c343b2660567256fa...

I don't think it was mentioned in the repo readme, but this will most likely get your account banned. Be careful

s3arch 2y ago

can you help me understand more.

01HNNWZ0MV43FF 2y ago
It stores file data as calendar events, sort of like that YouTube FS from a while back This is probably considered abuse under the ToS since you're using more storage than any typical user, and they can't use it for whatever they normally sell customer data for
- exe34 2y ago
  > they can't use it for whatever they normally sell customer data for Bottom line, you don't want to mess with their bottom line.
  - darby_nine 2y ago
    I seriously doubt this kind of stuff has ever messed with their bottom line. I think they just really resent users trying to do more with their service than they intended.
    - exe34 2y ago
      they would prefer that you pay them for storage rather than store white noise on YouTube from which they can't earn ad money.
    - 01HNNWZ0MV43FF 2y ago
      If they didn't crack down, people would start pushing it harder, until some company relied on this for cloud storage
      - darby_nine 2y ago
        I think this is a ridiculous sentiment, but I understand why it's so common. Proactively trying to head-off any and all possible problems before they cause measurable impact is not a great way to manage a product. Maybe they did see impact, but I still would have rewarded non-abusive loyal customers for using the product—maybe restrict access based on resource-usage rather than hitting people with TOS violations. Instead this attitude (plus their generally very poor track record at supporting and improving their own products) has caused me to abandon all google products outside of work.
        exe34 2y ago
        exponentially slower access and start corrupting them by flipping cases.

lvkv 2y ago

Yeah, I’ll update the README to be more specific about this. This is also why I didn’t provide instructions on how to use the tool :)

issafram 2y ago
This isn't exactly clear about the dangers of using the tool https://github.com/lvkv/whenfs/commit/618d6c343b2660567256faff78fc1f4ed6439536 https://github.com/lvkv/whenfs/commit/618d6c343b2660567256fa...