Freddy @freddyym@social.privacytools.io

apparently today's my twitter anniversary. figured it'd be a great time to quit the place—starting today my twitter will be read-only!

Hi Fediverse 👋

to break the quietness of this account, here's a quick news flash:

- We added a list with Zoom alternatives 🤙
https://swiso.org/replace/zoom/

- We replaced some entries on "Bubbling under" 🔧
https://swiso.org/list/bubbling-under/

- We added Cryptpad to the Doodle list as it has a poll feature 🗒️
https://swiso.org/replace/doodle/

- Our DRM article has images now 🙃
https://swiso.org/articles/digital-rights-management/

- We have an Audible list in the pipeline 🎧
https://codeberg.org/swiso/website/pulls/81

Thanks to @uniq for the nudge to write this! 😊👍

wow, an incredible read! 😲

The Confessions of Marcus Hutchins, the Hacker Who Saved the Internet
https://www.wired.com/story/confessions-marcus-hutchins-hacker-who-saved-the-internet/

If Coffee is not your thing, get yourself the latest @manjarolinux #Mate 😍 https://forum.manjaro.org/t/142622

Original tweet : https://twitter.com/ManjaroLinux/status/1261889305410232326

@syntax While that would be amusing, it doesn't seem to be the case lol. The IP addresses don't match up, the exit is with BuyVM, and the yellow hostname on the Tor page indicates that it's unverified. Additionally, if you throw the exit's IP address into your browser with port 80, you'll get a message saying it's an exit while http://donaldjtrump.com:80 redirects to 443 without mentioning Tor 😉

@sir Heh I just noticed that I got exactly the same email.

Scum of the Earth

General: "Get me a secure line to the President!"
Tech assistant: "Well, technically, the line cannot be considered secure, we do however use end-to-end encryption."

One day, hollywood, one day…

Apparently #Trump's site is hosted on a server which runs a #Tor exit node. You just couldn't write it... https://metrics.torproject.org/rs.html#details/23BB12BD68952BFE3D6BF4EFD010DB64D975CB02 #tor

I need your help.

I wrote a lengthy and technical blog post in which I describe an idea I have for a distributed system to verify content on websites.

TLDR: servers with cryptographically-signed hashes verify content and notify website owners if said content is changed.

https://yarmo.eu/blog/dcvs-proposal

Am I missing obvious flaws? Has this problem already been solved?

Please do let me know if this would be worth the effort.

Also #100DaysToOffload

Why Privacy matters...

#2030predictions Shops start playing Christmas music in August

@fdroidorg has over 3000 apps now \o/

Facebook has just bought giphy.com for $400m.

A website which hosts free gifs. Valued at four-hundred million dollars. And the majority of those gifs come from media created by costumers/writers/mic operators/camera techs etc. who don't see the value they create normally, let alone in hyper-inflated purchases like this.

How does this make any sense? It doesn't.

Day 21 of the #100DaysToOffload Series:

Just a quick summary of what I've already written and what's coming in the future.

https://mikestone.me/three-weeks

The PeerTube content bootstrap fund:

https://sourcehut.org/blog/2020-05-15-peertube-bootstrap-fund/

Please boost!

If you have an interesting hobby, please make videos about it and publish them on PeerTube

If you need help with PeerTube hosting and video equipment then please get in touch and we'll see what we can do to help you out