• 4 Posts
  • 2.02K Comments
Joined 3 years ago
cake
Cake day: July 11th, 2023

help-circle
  • sorry but this is written like the writer does not know computers.

    sure, lets make an unverifiable blackbox digital system for making digital passes that is somehow trustworthy, because… why exactly? oh yeah because the news said on the TV it is safe and secure, so it must be so!

    and sure, lets allow voting with the unverifiable blackbox digital system, and lets just pretend that your vote cannot be forged at dozens of places on the way to the vote counters.

    Everybody should have for free the means to authenticate online and do so anonymously when needed.

    anonymous authentication is a contradiction.

    We live in a digital world, we need the tools to evolve in it.

    no amount of tech will fix the problems of the unverifiable blackbox digital systems. you as a vote counter can trace the paper ballot from the booth to the counting event, and you can be assured the submitted ballots cannot be modified without someone going to the ballot box and opening it. but none of that can be said about computers. you can’t inspect the electrical signals, you wouldn’t be able to do that even with an utopistic fully open hardware computer.



  • Use a separate DBMS (that is, a separate postgres/mariasql/etc container) for each service. Give each one service unique passwords, which you can define in the docker compose.

    unique passwords is good practice, but separate db server for each of the services is extreme. it brings much more resource consumption. the solution here is being subscribed to security releases and updating soon. those application kernels also sound like a good idea. and as I understand, postgres permissions were not at fault, the permission system had a bug.

    Even if one application that connects to a database gets owned, it doesn’t have access to other postgres databases, preventing data leaks/exfiltration.

    except that because of the bug, anyone with query permission could have become postgres superuser.












  • You are just moving the goalpost.

    its easy to say firefox follows the standards slowly, when google is stuffing the standards with all the ridiculous unnecessary bullshit that have no business in the web standards, because they have the developer capacity to bloat it. when web standards maintainers are mostly google employees.

    If there is any technical aspect (not moral, just technical) I am ignoring please feel free to share with the rest.

    all the privacy aspects, including the many ways chrome is leaking identifying data that firefox fixes. as a start, you can look at uBlock Origin’s wiki page on why can it work better in firefox than in chrome. and this is just a little fraction of the differences.

    https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-best-on-Firefox


  • and what should the router do with traffic going to TCP port 443? because that’s most things going to the internet. it could be video streaming. it could be a video call. it could be someone scrolling unimportant shit on facebook. it could be any of your dozen IoT devices uploading telemetry to the manufacturer. it could be literally anything. you can’t meaningfully prioritize traffic based on just what service is it, you need to keep track of the recent usage of each connection, and that will cost CPU power.






  • I would like to click on a peertube link and for it to create a user on the peertube system using any relevant customizations from my parent user

    unauthorized exfiltration of your user data, including all settings, your email address and possibly your subscriptions.
    but probably this could be solved with some agreement dialog.

    and if I modify options on peertube I wish it would save that to my piefed user somewhere

    intransparent and unauthorized modification of arbitrary settings in the origin user