• 1 Post
  • 18 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle


  • Votes are public to not just to the original instance admins though but to any instance admin, right? If you setup your own instance and federate with another, then you should be able to view the votes for any communities on the one you federate with. The only privacy is that the default UI doesn’t display it, but a different UI could:

    e.g. the one for this post on kbin.social that shows Lemmy upvotes as favorites.

    I feel like this should be more prominently disclosed to Lemmy users.


  • More specifically:

    The each state gets two seats in the senate, no matter how many people in it. In the house of representatives, each state gets a proportional number based on population, with a minimum of one, and those districts should have a roughly equal population within each state. Due to the cap on representatives and the minimum of one though, it can end up with an uneven number of people represented by each elected official when you compare between states.

    If they control the legislature of the state though, they can also control the redistricting process that decides where the boundaries are for the federal house of representative districts and thus can gerrymander things. See this for an explanation of how one can produce districts that don’t resemble the underlying population: https://en.wikipedia.org/wiki/Gerrymandering











  • Considering this proposal is used for the key exchange, they definitely need to update both the client side and server side part to be able to make use of it. That’s the kind of thing that may take years but luckily it can fall back to older methods.

    It also needs to be thoroughly vetted so that’s why it’s a hybrid approach. If the quantum resistant algorithm turns out to have problems (like some others have), they’re still protected by the traditional part like they would have been, with no leaking of all the data.