The Collective Sensemaking Project
3.3K posts

The Collective Sensemaking Project
@csmproject
Firm believer that society needs better solutions to process the ever increasing flood of information. YouTube: https://t.co/U0O3Wmnwnq


Jetzt ist es eindeutig: die Aufzeichnung von der Veranstaltung der Bad Nauheimer Gespräche über die Corona-Zeit: „warum haben wir uns das angetan?“ , wurde von der Landesärztekammer Hessen zensiert. Das Video, das nach langem Vorlauf von sechs Wochen kurz vor Weihnachten dann doch online ging, wurde bereits Anfang Januar wieder auf privat gestellt und kann seitdem nicht mehr angesehen werden, weil, so hörte ich, Beifall von der falschen Seite kam. Ich bin ein absoluter Freund der Meinungsfreiheit und verlinke dieses Video hier zum Download als einen weiteren Beitrag von mir zur Aufarbeitung der Coronazeit und gegen Zensur: my.hidrive.com/lnk/W6d6OPKQP






Wir haben zwei sehr unterschiedliche Urteile gründlich gelesen und mit allen Seiten gesprochen. Ergebnis gibt es morgen online und im Radio.

How are EU laws made? Three key players work together to come up with a plan, discuss, tweak and finally pass a law ✅ Find out how ↓


Neue Details zum zivilrechtlichen Teil des Gesetzes gegen "digitale Gewalt": Gerichte sollen die Anonymität im Internet aufheben lassen können und auch die Vorratsdatenspeicherung soll eine Rolle spielen. Von @markus_sehl. buff.ly/om4TA5z

A woman was legally required to kill her baby in the third trimester because the “commissioning parents” for the surrogacy demanded it, and threatened a lawsuit. The baby was missing two fingers, so the people purchasing this precious child demanded it be aborted, per their contract. This is eugenics. It’s murder. It’s a baby trade, and it needs to be criminalized.

Jag har en fråga till dig. Om du hade vetat allt om covid vaccinet som vi gör idag, hade du fortfarande tagit det?








.@vonderleyen "The European #AgeVerification app is technically ready. It respects the highest privacy standards in the world. It's open-source, so anyone can check the code..." I did. It didn't take long to find what looks like a serious #privacy issue. The app goes to great lengths to protect the AV data AFTER collection (is_over_18: true is AES-GCM'd); it does so pretty well. But, the source image used to collect that data is written to disk without encryption and not deleted correctly. For NFC biometric data: It pulls DG2 and writes a lossless PNG to the filesystem. It's only deleted on success. If it fails for any reason (user clicks back, scan fails & retries, app crashes etc), the full biometric image remains on the device in cache. This is protected with CE keys at the Android level, but the app makes no attempt to encrypt/protect them. For selfie pictures: Different scenario. These images are written to external storage in lossless PNG format, but they're never deleted. Not a cache... long-term storage. These are protected with DE keys at the Android level, but again, the app makes no attempt to encrypt/protect them. This is akin to taking a picture of your passport/government ID using the camera app and keeping it just in case. You can encrypt data taken from it until you're blue in the face... leaving the original image on disk is crazy & unnecessary. From a #GDPR standpoint: Biometric data collected is special category data. If there's no lawful basis to retain it after processing, that's potentially a material breach. youtube.com/watch?v=4VRRri…


Die gesamte Hackerszene ist wie ein Schwarm Piranhas über die neue Altersverifizierungs-App der EU hergefallen und hat sie bereits vollkommen zerlegt. Ich frage mich wie viele hundert Millionen hier verblasen wurden.







Bypassing #EU #AgeVerification using their own infrastructure. I've ported the Android app logic to a Chrome extension - stripping out the pesky step of handing over biometric data which they can leak... and pass verification instantly. Step 1: Install the extension Step 2: Register an identity (just once) Step 3: Continue using the web as normal The extension detects the QR code, generates a cryptographically identical payload and tells the verifier I'm over 18, which it "fully trusts". This isn't a bug... it's a fundamental design flaw they can't solve without irrevocably tying a key to you personally; which then allows tracking/monitoring. Of course, I could skip the enrolment process entirely and hard-code the credentials into the extension... and the verifier would never know.





