• 0 Posts
  • 20 Comments
Joined 1 year ago
cake
Cake day: July 14th, 2023

help-circle
  • Follow-up: teach them to learn to troubleshoot and search. Take the fear of breaking something from them by providing them with a VM with windows where they need to fix something or install a driver. Provide them with a Linux VM just for them to try too.

    Teach them mistrust. Make them upload things to a copy of Google docs or something, and then show how you have access to everything.

    Teach them about open source as a precondition for being able to trust software.


  • I would go with tasks where they get to “hack” or learn about each other. Give them usb sticks, make them put a silly trivia on an encrypted 7z with passwords that are somewhat crackable. Then, take their usbs from them, and distribute them randomly, and let them use jack the ripper or so. Twist, you would have added a virus or something into the USB stick, so they get infected with a “silly pop up” once they start jack the ripper. They get to play, and the exercise will stick with them.

    Teach them about 10 minute mails pages, to open a silly account t somewhere.

    Make them use a VPN like mullvad or some that you have set up to access a specific page or make web searches. They can notice the difference in content depending on the country they are exiting with. Twist: you control the VPN, provide them at the end with a list of accessed pages so they understand how the vpns do not ensure privacy. Explain simply what a VPN is (tunnel,etc).





  • That argument makes absolutely no sense. These server-side code does almost nothing. The only task it really has is passing around encrypted packets between clients.

    So it knows about all metadata, plus registration with phone number, etc. got it.

    The Signal protocol, which is used for client-side, local, on-device end-to-end encryption has always been fully open, and it can be used by any app/platform.

    you conveniently leave out how you need to use the client built by Signal, with dependencies from Google Services and the like, and you can’t use one built from the source they provide. Which at that point means they can introduce whatever they want in whichever version.

    Decentralisation is the only safe way.



  • Conservatism is dead. Climate change is scientifically proven to be catastrophic.

    If we do nothing, change will come to us, and fuck up everything. If we elect to change our society and systems, we save ourselves but our way of living changes.

    One way or another there’s change. There’s nothing to conserve. Stop yelling and kicking like an irrational kid trying to save conservatism and crony capitalism.













  • Evidence? OF COURSE!

    Have you even tried searching for it?

    Google even says so for Chromium on its own official page!

    https://security.stackexchange.com/questions/144289/privacy-with-chromium

    You don’t need to trust us. Trust Google, they are telling you legally if you want to listen.

    Also, look up the handful of open bugs on the Debian but tracker, where known people, with name and faces (I’ve met some on conferences), showcase and share how Chromium calls home and sends encrypted data. They share their Wireshark logs.

    https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792580;msg=53

    Look up how Debian removed Chromium for a time, until some of it got removed upstream.

    And all of this doesn’t mean that Google cannot re-introduce it or add different approaches in new updates.

    Plus, Google actively creates and pushes for their “standards” via Chrome(ium), which allows them to push for even more surveillance.

    In addition, Chromium is not a community project. It’s developed behind closed doors, with a secret roadmap, and a code dump happens on release. That’s no way to develop the 90% of web browser market that society needs in this day and age. But, don’t think you will care about that, do you? you are happy with papa Google for the foreseeable.