![after help incident github dmca process after help incident github dmca process](https://files.speakerdeck.com/presentations/12c91ba04b2b0132f287624d3aca0ff3/slide_16.jpg)
It has boomed the development of business, and even the history of humankind. The invention of the LLC has greatly encouraged people to innovate, create, and build. Had not been for the LLC, nobody would create companies to make cars. You'd be personally broke, too you and your company would be in an irrelevant place in the car market from which you would never return. If your company couldn't pay the penalties, you must. In the case of limited liability companies, the liability of members to contribute to the debts of the company is limited to the amount of their investment in the company and does not extend to personal assets.īefore LLC, if you were a car company and your customers had accidents and sued you, you'd be held with unlimited reliabilities. If the scenario above doesn't resonate with you very much, think about the limited liability company (LLC.) Since the possibility of being held liable for user-generated content could be very harmful to service providers, who dare to provide those services? Now you see where I'm going with this: if there are hundreds or even thousands of infringements, you are doomed. You know, one single copyright infringement can cost you up to $150,000. Although it's not exactly YOU who published that copyrighted work, your platform stores and serves it. So, it's easier to just sue you instead since you are the service provider and you should be responsible for your users.
![after help incident github dmca process after help incident github dmca process](https://i.stack.imgur.com/UnLtq.jpg)
It's not easy for the owner to find the user who actually posted that content, but it's easy to find you since you are the service provider, not a random person around the globe. If the owner of that copyrighted work sues you, you are done. One day, a user copy-pasted some copyrighted work and published it on your platform under his name. Your service got popular and a lot of users decided to publish content on your platform. Sounds familiar, right? I know bear with me. In certain cases a third- party aggregation service is used for up to 90 days, then backed up to Amazon S3 indefinitely.Let's say you created an online service that allows users to publish up to 140 characters of content they wrote or a service where users upload video clips they created. Logs are primarily stored in Google Cloud cold storage indefinitely. Operational data for other OSF services are backed up in primary cloud file storage for 60 days. Further, the OSF database is maintained in encrypted snapshots for an additional 60 days. The OSF database is backed up via streaming replication 24 hours a day, and incremental restore points are made twice daily.
![after help incident github dmca process after help incident github dmca process](https://user-images.githubusercontent.com/53317395/62233558-32810900-b39f-11e9-9fcd-ce6473ba8d1a.png)
Please refer to Google Cloud documentation for details about the other robustness features Google Cloud provides. File backups are hosted in regional coldline buckets, and there are twice daily backup jobs performed. We keep MD5 hashes for files and use cyclic redundancy checks to prevent and mitigate any data corruption. Files uploaded to OSF Storage are stored in various storage locations, configurable per user. OSF Storage uses Google Cloud for both active and archival storage.