Ask me no questions and I’ll tell you no lies. It asks much less of my instance admins if it’s understood that my information was never private to begin with.
I prefer the complete lack of privacy settings because it is open and honest about the reality of what Lemmy is able to provide.
Even if you’re running your own instance, you are necessarily submitting your data to another party. I don’t have to trust the platform as much when my data isn’t private. It’s much easier to engineer a system around that assumption.
If we suppose that anything I submit to Lemmy is submitted to the public, I can’t be misled. My data cannot be leaked because I’m presenting it to the world already. Lemmy is a young social project with many problems to solve, still trying to gain traction and hold on to users and with an uncertain future. In brief: bigger fish to fry.
Maybe privacy controls could be on the list, but I don’t think it addresses the main problems or applications of the platform and creates its own set of issues. Keep it simple and stupid.
It took me like a week to download what I think is all of them from a decent cable connection. I do intend to watch this but it’s going to take me like a year given that I have a job.
However, I’m very privileged in a sense. I get to watch them for the first time. How many fans would love to rewatch episodes for the first time?
How about this then. While your neighbors are using wine, it attracts more commercial attention to develop the open source projects that you do actually use. It’s so impactful that you measurably benefit directly from its contributions, like optimizations to the Linux kernel.
You don’t have to agree with it, but you cannot deny the increased investment in open source projects it causes.
For a painfully blatant example see: Steam Deck.
Also for the binary blob purists, how do you feel about all that closed source firmware underpinning your pure world? Isn’t it practically impossible to get completely open source firmware down to the silicon? And even then, do you trust the silicon? Are you running everything on FPGAs?
It was a solution to a Lutris bug. Basically, flatpak containers can use these things called portals to gain access to specific files and directories via a file chooser rather than broad access or manually assigned access.
In this case, my wine installation was crashing because some part of it was trying to obtain a lock on a directory object, which is an unsupported feature when accessing a directory through a portal. The error message is something completely unrelated like can’t draw window with a string of hex values. It took me a few hours to track down the real root cause.
Oh well. Works on my machine. Also, there’s a fix on the development branch now. I made a write-up, posted it, and it’s all gone. I should have known better honestly. It works great for some people but anybody can arbitrarily receive unfair treatment with no recourse at any time. I’m satisfied knowing that eventually the fix will get out to everybody eventually. It’s just a shame I couldn’t leave a signpost behind.
Man that place. I know it’s cliche to talk about it like talking about your ex on a date, but I posted there for good reason.
I found the solution to a rare bug that was bothering a group of people. I posted the solution, and my account was immediately banned sitewide for violating the terms of service, whatever that means.
I thought to myself: yeah… it was a mistake coming here. Leave it to the bots to have conversations with themselves.