##### ⚓ A community devoted to in-depth debate on topics concerning digital
piracy, ethical problems, and legal advancements. 𝗣𝗜𝗥𝗔𝗖𝗬 𝗜𝗦
𝗘𝗧𝗛𝗜𝗖𝗔𝗟. — ### Rules • Full Version [https://rentry.co/piracy-rules] 1.
Posts must be related to the discussion of digital piracy 2. Don’t request
invites, trade, sell, or self-promote 3. Don’t request or link
[https://lemmy.dbzer0.com/post/18438] to specific pirated titles 4. Don’t harass
others, spam, or submit low-quality posts 5. Don’t post questions already
answered. READ THE WIKI [https://lemmy.dbzer0.com/post/10901] — Image
[https://take-me-to.space/VgXFZB2.png] — ### Loot, Pillage, & Plunder - 💀 Wiki
[https://lemmy.dbzer0.com/post/10901] - 📜 Megathread
[https://rentry.co/megathread] - 🪶 FAQ [https://rentry.co/piracy-faq] - 🪶 ISP
Complaints [https://rentry.co/piracy-isp-complaints] - 🪶 Rules
[https://rentry.co/piracy-rules] — 💰 Please help cover server costs
[https://ko-fi.com/db0]. —
What is why? What is the solution we’re trying to solve?
Lemmy being imperfect doesn’t change the fact that it does solve one big problem: it takes the big corporation and its influences out of the equation. It is not possible for a centralized solution to do this.
To be fair, while Lemmy is a step in the right direction, I don’t think it’s aimed quite right. It solves one problem while introducing a host of others. I’ve talked about this previously in various places, but ultimately I think it’s a mistake to bundle communities, user accounts, and moderation all into the same package. It’s easy from the standpoint of “Lemmy is just a mini Reddit” mental model, but then you run into problems like exactly what’s being discussed in this thread, where you have instance administrators making decisions about what federated content their users are allowed to access.
A better design would be to decouple users from communities. Communities should be hosted on super targeted instances with similar communities who all can agree on content rules with each other. That in combination with some kind of central registry of communities and a mechanism to repost content between communities that wish to be partnered with each other would take care of that part of the equation. I would also invert the relationship between user registries and communities. The community should be where the user goes to view content in that community, just with an account provided by a 3rd party, similar to how OpenID worked. The only tricky part is working on how to do a unified front page with content from many communities, as that would imply that all that content would live in one location, and then you run into the legal issues of nobody wanting to allow arbitrary federated content to be rehosted on their server.
I fully agree. User accounts should be separate and content should not automatically be hosted on all linked instances. It’s not scalable and will only lead to endless defederations.
again, this why i claim that lemmy is not the solution to the problem we are trying to solve.
What is why? What is the solution we’re trying to solve?
Lemmy being imperfect doesn’t change the fact that it does solve one big problem: it takes the big corporation and its influences out of the equation. It is not possible for a centralized solution to do this.
To be fair, while Lemmy is a step in the right direction, I don’t think it’s aimed quite right. It solves one problem while introducing a host of others. I’ve talked about this previously in various places, but ultimately I think it’s a mistake to bundle communities, user accounts, and moderation all into the same package. It’s easy from the standpoint of “Lemmy is just a mini Reddit” mental model, but then you run into problems like exactly what’s being discussed in this thread, where you have instance administrators making decisions about what federated content their users are allowed to access.
A better design would be to decouple users from communities. Communities should be hosted on super targeted instances with similar communities who all can agree on content rules with each other. That in combination with some kind of central registry of communities and a mechanism to repost content between communities that wish to be partnered with each other would take care of that part of the equation. I would also invert the relationship between user registries and communities. The community should be where the user goes to view content in that community, just with an account provided by a 3rd party, similar to how OpenID worked. The only tricky part is working on how to do a unified front page with content from many communities, as that would imply that all that content would live in one location, and then you run into the legal issues of nobody wanting to allow arbitrary federated content to be rehosted on their server.
I fully agree. User accounts should be separate and content should not automatically be hosted on all linked instances. It’s not scalable and will only lead to endless defederations.