Sure doesn’t seem like it. I went to a lot of effort to make the best of the mod API calls that are available and they go and remove a useful chunk of it. 😒
been selfhosting the smtp relay and using the app for quite a while. If you use it as a private chat for sensitive content, it is PERFECT. Really looking forward to its future development in group chats.
The only privacy setting I can encourage on any social media site is don’t share private stuff about yourself and never link to your account from other accounts
That is part of the problem though. Proper privacy allows you to express what you want to, without self censorship. The issue is not: don’t speak about x, but rather: speak about it and feel comfortable that you can do it in a safe environment. I fully agree with the account linking though
Lemmy has many privacy problems that have nothing to do with public comments you make. For example, the “hide posts that you have already read” option requires that the server track what posts you have read. There is no public activity involved in reading a post. So the Lemmy server should not track that info. If that feature is to exist at all, it should be implemented purely on the client. The same can be said about subscriptions, and for that matter about voting (server should discard voting info after a brief interval for abuse detection). The Lemmy software in many ways naive about this stuff.
I don’t disagree on those points, but I think it’s the nature of Lemmy being decentralized that makes all those things necessary.
server should discard voting info after a brief interval for abuse detection
What if the server has not federated out the votes yet? Some of that stuff can get backed up in a queue. There’s definitely a possibility that votes could get “lost” on the way. Hell, that already happens, and that’s with a system that tracks them.
Servers have to keep a lot of this info to pass to other servers. If I upvote something on Lemmy.blahaj.zone, it doesn’t mean that upvote has been federated outward to hundreds of other servers yet. I would assume this is part of how Lemmy is able to keep things “organized” between all servers.
In other words, a lot of the privacy complaints come from technical limitations of how Lemmy works. Lemmy, by it’s decentralized nature, has to transfer tons of data back and forth between all Lemmy instances.
However, there are technologies that are trying to work around this kind of technical limitation. You might be interested in something like Veilid. I’m not sure about the details of putting together a Veilid-based social-network, but I’m willing to believe it’s possible.
I don’t see anything in your post that indicates any reason to track what posts a person has read. That should not be tracked at all. Reading posts should be completely anonymous.
I don’t see why voting necessarily has to track who casts the votes. But, because untracked voting can be abused so easily, I can understand deciding to retain the info for let’s say 24 hours. Hopefully that is also enough to handle those propagation issues.
Really, imho, server instances shouldn’t have a web interface at all, just an API. Web apps would make API calls to the server and reformat the response for use by the browser. The API call to read a post should not require any identifying info or require the user to be logged in. Read tracking and subscriptions should be handled by the client, and in the case of a public client (web app shared by many users), the private user info should be encrypted in case of a server breakin or seizure. The encryption key would be based on the user password and transformed to a browser cookie when the user logs in, so it is never stored by the web app. With most people using mobile clients these days, alternatively, the info can be kept completely on the client device and maintained by the mobile app.
Tempo is gorgeous, it’s up there with Auxio in terms of aesthetics. That said, I wish it had the feature set of Musicolet. I love being able to switch between queues and never having my randomised playlists reorder the songs because they drop out of memory.
I understand the developer, but the complete lack of communication with the community is appalling. and even the subsequent app updates to ad-supported/tracker-packed versions is just disgusting. i understand why tibbi burned out, but the sale process was handled in extremely poor way
“However, we want to assure you that you are not at risk of anything similar with our apps. Instead, we bet on transparency and a fair approach to users … It is a small one-time fee that will ensure you use our apps forever – with no ads and no access to your data” 😂😐
github.com
Top