Shamar @Shamar@mastodon.social

Xerox Alto Source Code | @CHM Blog | Computer History Museum http://www.computerhistory.org/atchm/xerox-alto-source-code/

What it's like debugging your code.

Oppressed people exist to be more than inspiration for the powerful classes.

4 years ago we started CryptPad as a proof of concept.. Today @cryptpad@twitter.com is getting a European prize ! Great recognition for hard work by the CryptPad team
RT @cryptpad@twitter.com We are more than happy to announce that we have won the @NGI@twitter.com startup award for Privacy and trust-enhanced technologies. More details: https://awards.ngi.eu/winners-startup-awards/

🐦🔗: https://twitter.com/cryptpad/status/1061922635842535424

#FinishedReading (again) The Little Schemer by Friedman and Felleisen

A lovely little book on recursion, #logic and #scheme.

Perfect for beginners honestly, if they take their time towards the end. All exercices can also be thought through on paper, so you can take a break from that screen ;)

Theres a list of recommended books on logic towards the end and I think I'll go through them, especially since I never mind rereading Alice in Wonderland (and I've never read an annotated version)

went to work at a coffee shop with just my #cyberdeck and my mobile; we'll see if this ends up being a Terrible Mistake

20 years ago: "And in the future the internet will replace the need to have a telephone entirely!" 🖥️

Now: "You must have a phone number to access this website/service" ☎️

@Wolf480pl @danyspin97 @Shamar An interesting example of this caching: Debian repositories.

They have an extensive volunteer mirror network how they want to prevent from altering packages when you fetch them. So they cryptographically sign all their packages.

Combine that with the fact that just the file sizes (which is not obscured by HTTPS) are enough to determine which packages you're downloading, and there's no benefit to them HTTPS.

It only costs them recruitment of these proxies.

The joys of Ancient Greek—

οὐκοῦν: “certainly”
οὔκουν: “certainly not”

@danyspin97 @Shamar
>flaw that has nothing to do with the protocol

If only TLS wasn't full of ASN.1-style bullshit that's impossible to implement correctly...

See also maradydd's talk about how to design network protocols to significantly lower the chance of vulnerabilities:
https://www.youtube.com/watch?v=3kEfedtQVOY

@saxnot @Shamar @danyspin97
Obviously he's not trying to convince anyone. If he wanted that, he would try to avoid making others treat him as a fool.

@alcinnz great!
I can't really focus now but during these days I'll investigate a little on this.

I'm also preparing a talk about the web and how broken it is using also @Shamar 's bug reports and Brannon Dorsey's studies on browser-as-a-botnet (link below).

I think all this is really important and interesting. We need to keep a critical eye where nowadays devs seems to be JS-only brogrammers with coffee addiction, glasses and beard.

https://medium.com/@brannondorsey/browser-as-botnet-or-the-coming-war-on-your-web-browser-be920c4f718

We desperately need an open alternative that puts control back in the hands of the user. I think open computing is of fundamental importance. If we lose the ability to decide what code runs on our devices, we’ll be moving a step closer towards a totalitarian dystopia where the governments and corporations get to decide what’s good for us.

https://puri.sm/posts/librem5-2018-11-hardware-report/