3 ms·
Your weekly reminder that 1. You should not have your development process on a centralized platform, at least not if you're doing anything that smells of copyr
by black_puppydog 6y ago
Your weekly reminder that
1. You should not have your development process on a centralized platform, at least not if you're doing anything that smells of copyright issues
2. If you do host on a centralized platform, have regular, decentralized backups of code and issue tracking.
3. Also, avoid US-centric hosting for this kind of thing. But really, refer to 1.
- marcosdumay 6y ago> at least not if you're doing anything that smells of copyright issues Or lets people communicate. Or broadcasts news. Or can filter messages or news. Or directly applies encryption to anything. Or is related to accounting. Or can be indirectly linked to health services. Or, well, you get the idea.
- a1369209993 6y agoOr in plainer terms: 1. You should not have your development process on a centralized platform, period.
- Deely123123 6y agoShould we count country and government as 'centalized platform'?
- orthecreedence 6y agoYes, I'm watching https://radicle.xyz/ https://radicle.xyz/ with great anticipation.
- cblconfederate 6y agothere will never be a safe country. The robust option is to mirror them in hostile countries. Divide them and conquer
- stjohnswarts 6y agoI'm sure the developers have the whole thing on their local machines and it would be terrible if it was uploaded somewhere in a country that doesn't give a squat about DMCA.
- zanny 6y agoI'm a contributor to gallery-dl and it occurs to me this exact same scenario can happen there. So I at least set up a cron job to backup the issues in case it gets trolled. Its the only really problematic part to get taken down from Github.
- frankzander 6y agoThanks ... your tool seems to be the solution for my problem :D