iv-org/documentation
1
0
Fork 0
mirror of https://github.com/iv-org/documentation.git synced 2024-10-01 01:35:51 -04:00
Code Issues Packages Projects Releases Wiki Activity

Takedown-Notices - Enhancement and typos fixes

Browse Source
This commit is contained in:
TheFrenchGhosty 2022-03-13 16:07:13 +00:00 committed by GitHub
parent 44e591b611
commit d401cf0945
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/Takedown-Notices.md
View File

@ -1,8 +1,8 @@
# Takedown Notices # Takedown Notices
While running Invidious, it is very possible you will receive a takedown notice at some point. A copyright agent will probably search the ID of an infringing video on a search engine and see an Invidious instance appear. At least in the United States and in Europe, Invidious instances should in theory be immune those kind of takedown. If you are running a public Invidious instance, it is very possible that you will end up receiving a takedown notice at some point. A copyright agent will probably search the ID of an infringing video on a search engine and see your instance appear. At least in the United States and in Europe, Invidious instances are, in theory, legal.
Do note that most requests are invalid and technically illegal since they aren't sent by a lawyer, so you can, in theory, never replies to them (unless they are a company/law firm). If you want to be safe you can obviously counter to all of them. Do note that most requests are invalid and technically illegal since they aren't sent by a lawyer, so you can, in theory, never reply to them (unless they are a company/law firm). If you want to be safe you can obviously counter all of them.
To counter them "easily", we decided to provide templates depending on where your instance is located. To counter them "easily", we decided to provide templates depending on where your instance is located.