Just a lvl 29 guy from Finland. Full-stack web developer, Scrum Master and a team facilitator by trade, but actually more into server-side programming, networking, and sysadmin stuff.

During the summer, I love trekking, camping and other hiking adventures. Also somewhat of an avgeek and a huge Lego fanatic.

A furry or something. Why be yourself when you can be a fluffy raccoon on the internet?

  • 0 Posts
  • 10 Comments
Joined 3 years ago
cake
Cake day: June 20th, 2023

help-circle

  • Well, if we wanna still have voting actions federate between instances and different services (meaning everyone can see the total vote counts, not just the votes given by users on single instance), that information has to be publicly sent to other instances. Like I said, I believe there have been some discussions about ways to anonymize outgoing voting actions, but I imagine there would be quite a few issues to think about. For instance, doing so would probably make it much easier for bad actors to send bogus votes.

    The difference of opinion is that Lemmy’s devs believe that services receiving voting data from Lemmy shouldn’t publicly display individual votes, but only the aggregate counts (just like Lemmy itself does). Many others, myself included, think this approach creates a false sense of privacy, potentially leading some users to believe that their votes are private when they actually aren’t, especially given that services like Lemvotes exist.


  • Votes are not private and never will be.

    There have been some discussions about whether Threadiverse software should only federate out the number of votes and perhaps some anonymised voter IDs, rather than information that identifies individual users. This would prevent vote snooping via sites like Lemvotes. However, even if something like that were implemented, instance admins would still be able to snoop on their own users if they so wished. So imo, it’s better to just accept that votes are public information.

    Personally I don’t see the issue with it. My principle when it comes to voting is upvoting stuff I want others to see and only downvote things I don’t think anyone would want to see (like spam). So if for some odd reason someone is interested enough to check my voting history, I don’t care. What’s the worst that could happen? Someone on the internet disagrees with my votes? Oh no! How will I ever survive?!

    As a side note, Lemmy’s developers seem to have a strong opinion that voter information shouldn’t be displayed publicly. For example, here’s an issue they opened in the Mbin repo. While I disagree with their stance on vote visibility, Nutomic has a valid point there: Lemmy doesn’t mark voting activity as public when federating it out, so there’s an argument to be made that other software should not display individual votes coming from Lemmy.







  • It works great when you log in as a user like you normally would on a Windows pc. But on a server you want it to run as a service, starting automatically in the background and/or being managed by the failover cluster without requiring a user to log in.

    The solution back then was to use netplwiz autologon. Obviously a hack and bad for security, but fine for a homelab. After googling it now, it looks like some other “solutions” are documented in the GitHub issue about this.


  • Asking out of curiosity: is there a specific reason you’re running Windows on your server? I used to do the same on my home servers because that’s what we used to have at work, and I wanted to learn and test some stuff. But it was a difficult road, to put it mildly. Simple things, like getting Docker autostart on boot seemed almost impossible. At some point I just gave up and switched to Linux.