I believe that most people who are against capitalism are not so much against markets (systems for sharing) as they are against corporations which are effectively backed by monopolies, subsidies etc.
@rechelon Somewhat on tangent, but it was rather painful to see so many people shame Zuckerberg for his geekiness when shit hit the fan. He's an absolutely terrible person and all, but there are also plenty great people who have similar issues with social skills.
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.
@micahflee Thank you for doing the work! That's much better than nothing at all.
Anyone can cause `gpg --recv` fail for any key on keyservers: https://bitbucket.org/skskeyserver/sks-keyserver/issues/57 #gpg
@marsxyz Those are letters and files that document how CEO, James, is trying to take over the company by removing Daniel, the main CopperheadOS developer, from the company. Both have 50% shareholder stake.
@micahflee This is basically for the same reason: no validation on packets whatsoever. Packets that cause the key to be unimportable are clearly not RFC-compliant, but SKS still accepts those packets.
@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
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!