• 2 Posts
  • 42 Comments
Joined 2 years ago
cake
Cake day: August 4th, 2023

help-circle

  • I wonder if there’s a way to prevent people from even knowing that two different votes came from the same user.

    What I outlined above should prevent anyone from knowing two different votes came from the same user… without specifically trying that user’s id on each. That’s what the salt (the comment/post id) is for.



  • TootSweet@lemmy.worldtoOpen Source@lemmy.mlIntroducing Lemvotes
    link
    fedilink
    English
    arrow-up
    14
    arrow-down
    2
    ·
    edit-2
    11 days ago

    Votes should be anonymous.

    I tend to agree, but the fact is that they aren’t anonymous. This tool just exposes the already-existing fact that Lemmy expressly does not guarantee anonymity for votes. The solution isn’t to not for the poster to not publish this tool. Believe me, such tools already exist in private even if none other than this one are published. Publishing this one only democratizes access to that information. (And not entirely, I don’t think. From what I’m seeing on the page, it looks like it still requires an admin account on an instance. Update: Actually, I’m not sure if it requires an admin account or not. Either way, though.) The solution is (if it’s possible) to make Lemmy itself protect voters’ anonymity.

    The reason why instances know who has up/down voted things (rather than only keeping an anonymized “total” for each post/comment) is so it can prevent double-voting.

    Maybe instead of usernames, the instances could store/trade… salted hashes of the usernames where the salt is the title or unique identifier of the post/comment being voted on? It wouldn’t be perfect, but it would allow the instance to figure out whether the currently-viewing or currently-voting user has already voted while also making it harder for anyone else to get that information. About the only way a tool could tell you exhaustively who had voted if that were how things worked that I can think of off hand is to try every username on Lemmy one-by-one until all the votes were accounted for.

    (Of course, malicious instances could still keep track of usernames or unique user ids who up/downvoted, but only on the instance on which the vote was cast. Also, one downside of this approach would be increased CPU usage. How much? Not sure. It might be trivial. Or maybe not. Dunno.)

    And there may be much better ways to do this. I haven’t really thought about it much. I also haven’t checked whether there is an open ticket asking for improved anonymity for votes already.

    (Also, full disclosure, all of the above was written after only an extremely brief skim of the linked page.)

    (One more edit. Something IHawkMike said led me to realize that the scheme I described above would allow instances to manipulate votes by just inventing hashes. Like, grabbing 512 bits of data from /dev/urandom and giving it to other instances as if it was a hash of a username or user id when, in fact, it’s not a hash of anything. Other instances wouldn’t be able to easily tell that it wasn’t the hash of a valid user id. I haven’t thought how to go about solving that yet. Maybe if it occurs to me, I’ll update this post.)





  • On Arch (which I’m kindof in the process of migrating away from, but anyway), I tend to use the version of vi that is pre-installed as part of the base system. And it segfaults not terribly infrequently and the fact that that hasn’t been fixed yet in all the years I’ve been using Arch makes me think it almost has to be unmaintained.

    I prefer something lighter than Vim, and that fits the bill. I used something called “nvi” at one time in the past, but it had some annoying quirks as well. On non-Arch systems, I just use Vim.




  • Originally posted here, quoted below for convenience:

    Real story.

    I was in my late teens. My parents were dragging me to a tiny, kinda culty church every fuckin’ weekend. Didn’t really have much choice. (Hell, I hadn’t even told anyone yet that I thought Christianity was 100% bullshit.)

    I had a reputation for knowing my stuff about computers. (Because normies – particularly boomer normies like Pastor Dipshit – don’t know the difference between programmers and PC support.)

    So, one Sunday after the service, Pastor Dipshit asks me to look at his computer. His Outlook was giving an error dialog. Something about not being able to find an email on disk. Clicking the “ok” button just resulted immediately in another dialog, and while the error dialog was present you couldn’t interact with the main window, so this rendered Outlook unusable.

    Turns out he’d gone and deleted a bunch of files from the filesystem. Like by navigating from “My Computer” down to the directory where Outlook stored its files. Rather than deleting emails through the Outlook GUI the way one is meant to.

    So, I mused “hmm, I wonder if it’s just giving one error message per email that was affected.” I could see in the window behind the error dialog that the total count of emails in his inbox was only a couple hundred or something.

    So I commenced to clicking as rapidly as I could. Probably about a minute of clicking later, no more error dialogs and Outlook was usable again.

    And everyone marveled at my “genius.”

    I wouldn’t be surprised if he didn’t learn his lesson and continued to delete random files from the filesystem, but he kindof lost what was left of his connection to consensus reality and scared even my culty family away and we quit attending that church not terribly long after that, so I couldn’t say for sure.