• 0 Posts
  • 22 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle







  • This. And even then there should be procedures in place to essentially make it impossible to send the wrong inputs.

    It’s like when an intern accidentally drops the production database. It’s not the interns fault for sending the wrong command. It’s the managements fault for not restricting access in the first place.




  • This. I hate the whole left/right tribalism.

    Like I know that it can be used to get a rough idea of what political motivations someone might have and I know that where my own ideologies would mostly fall in that inaccurate one-dimensional linear spectrum but ultimately it is too inaccurate to use it to classify everyone’s political motivation.

    Worse it creates a whole us-vs-them divide. “Oh you aren’t right, when then you must be a commie”. “Oh you aren’t left, then you must be a fascist”. So you might consider yourself in a different position on a political spectrum and just see the differences to someone on the other end of a political spectrum even though you might have more in common then you think. Heck, if you are on complete opposite ends you might even have more in common then you think.

    Ultimately, the focus should be less on left/right and more on individual policies. Like should healthcare be public or privatized, should be build another road or another train track here, etc

    Why does political debate always have to turn into this tribalistic mud fight instead of proper discussion on how to best address the needs of citizens?





  • However, I don’t fully understand this part:

    there should be an easy way to also access that information in the front end to indicate to the user that what they up/down vote is in fact not private.

    But it’s true that my brain today doesn’t really want to work. You mean by some kind of API call can reveal these information?

    Basically what I meant is some way for the user to see who up/down voted what. Maybe hovering the up/down vote button shows a field you can click on that say votes or something and that then redirects you to a different page that shows who upvoted and downvoted that specific post/comment. The exact details don’t really matter. My point was basically that if something is accessible but only via hidden means that are not obvious to the end-user, they may wrongly assume that information is private. So by making it easily accessible to end-user, you also clearly indicate that that information is publicly accessible ^^


  • Why would you want to show all information stored on the frontend?

    I’m gonna start out by saying that I don’t know how lemmy’s federation code works. So if I host another instance and federate do I only see the upvote count or also who upvoted? Cause if the only person that can see the count is the admin of the instance the user belongs to, then there’s no need to show it in the frontend. If however all you need to do to see upvote count of all lemmy users, is to host your own lemmy instance, then there should be an easy way to also access that information in the front end to indicate to the user that what they up/down vote is in fact not private.

    So for me whether up/down voting is private is less of an issue as long as it’s clearly communicated. Again if only the instance admin the user is part of can see the count, then that’s essentially “private” as you are trusting that entity already ^^