YouTube-operational-API
YouTube-operational-API copied to clipboard
Benjamin-Loison
Store this source code in a DMCA resistant manner?
The idea would be to have multiple instances hosting publicly the code and to encourage people to do so. Maintaining a list of instances hosting the code would make sense.
Light approach: https://git-scm.com/book/en/v2/Git-on-the-Server-Git-Daemon Heavier approach (but more complete as it contains issues, wiki, pull requests...): own Gitea instance
Various hosts like Tor would make sense.
Should investigate torrent and fediverse.
Related to #94 and Robust_image_source_identification_on_modern_smartphones/issues/23.
+3
I do not see much interest in encrypting Element space, as it has a few issues about synchronizing sometimes and the link to join is public and I want the history to be public.
I was thinking that could encourage people to share their links to backups with others but just encouraging everyone to backup on their side seems more correct, as the index of backups (Discord guild) may disappear.
Backup my online servers related to YouTube, as I may not have control and doubt about laws being carefully respected concerning those.
Consider also my Codeberg repositories. GitLab does not seem concerned as only have as private a repository https://gitlab.com/Benjamin_Loison/YouTube-operational-API.
Check to have Discord user ids to potentially recontact them if the guild is removed.
Related to #317.
Should investigate:
A second Yuzu fork, called Torzu, has also appeared. It is notable for having its main git repository and development done in the Tor darknet. While takedown notices from Nintendo have taken down mirrors of the fork from GitHub and similar services,[41] the Tor-based hidden services remain active.
Source: Wikipedia: Yuzu (emulator)#Forks (1250351555)
Using some decentralized plateform and redirecting to it without claiming on it being from me make C&D letter more complicated it seems.