Updated PRISM Break's file storage & sync category to only include end-to-end encrypted software: https://prism-break.org/en/all/#file-storage-sync
Unless we insist on server not having access to user data, people will just rent VPS, use it as sync server, and think their data is safe. Only few have trusted physical always-on hardware, and even that is a liability (what if someone's house gets raided?).
Apparently, refusing to promote a neo-nazi den is censorship now: https://gitlab.com/prism-break/prism-break/issues/2055
Feel should've handled that better somehow.
Anyone can cause `gpg --recv` fail for any key on keyservers: https://bitbucket.org/skskeyserver/sks-keyserver/issues/57 #gpg
@micahflee Another SKS bug. Anyone can make a key unimportable: try `gpg --keyserver pgp.mit.edu --recv-keys 0x4F3F50786C401DCE`, it will fail. Also see https://pgp.mit.edu/pks/lookup?op=vindex&search=0x4F3F50786C401DCE
Pushed a fake UID to SKS keyserver signing key: https://pgp.key-server.io/search/0x41259773973A612A Source code (crawler next up): https://gitlab.com/yegortimoshenko/sks-tools (cc @micahflee)
Usually this requires a proprietary SWD debugger like ST-Link/V2. @email@example.com has recently implemented bbg-swd, a SWD debugger on top of OpenOCD that runs on BeagleBoard devices using PRUSS (auxiliary real-time processors on TI SoCs).
I'm using PocketBeagle and some Dupont wires. Hope this would work without any soldering.
Free software developer, mutualist, transhumanist, vegan. Consulting for Clojure/Nix at https://transumption.com . NixOS and PRISM Break maintainer. They/them.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!