[-] boulderly@lemmyadmin.site 0 points 1 year ago* (last edited 1 year ago)

hmm weird. This bot is announcing an 18.2 release (and I think people are installing it.) https://matrix.to/#/#lemmy-support-releases:discuss.online

But the repo is still showing 18.1 as the latest.

screenshot of releases widget on lemmy github

[-] boulderly@lemmyadmin.site 1 points 1 year ago

so consider a smaller local instance like I'm setting up. If it's ever anything more than me and my mom it's gonna be a bunch of people I know and their friends. And if my instance is their entry point to the fediverse then yeah I want it to be as private as we can make it for them.

But also, even if someone's IRL identity was masked, I've only been around a week and I'm starting to recognize handles on the fediverse. Ideally we make friends here and it's a community for us.

Now imagine how humiliating it would be if someone malicious gained control over an instance and published everyone's subscriptions/likes etc. Sure more savvy users probably do have separate accounts but honestly most will not.

[-] boulderly@lemmyadmin.site 1 points 1 year ago

what is the problem with votes btw? Someone else just mentioned those should be private too in the chat where I first raised this.

[-] boulderly@lemmyadmin.site 1 points 1 year ago

There, you've already found a reasonable way around it! 😀

[-] boulderly@lemmyadmin.site 1 points 1 year ago* (last edited 1 year ago)

lets take community subscriptions specifically. Here's a handful of rows from community_follower with my person_id. Why couldn't you hash community_id with my public key and then I provide my private key to whatever ui client I'm using to populate my feeds when I log in?

rows from the community_follower table

view more: ‹ prev next ›

boulderly

joined 1 year ago