David 📻 🔭 🌟 @david@librem.one

"Milosevic's well-researched study... points towards new policy solutions... [The author] argues that cyberbullying should be viewed... as part of the larger social problem of the culture of humiliation." #harassment #libremsocial #toread

https://mitpress.mit.edu/books/protecting-children-online

Very much enjoying Nicky Case's explorable explanations and thought-provoking minigames! #freeculture

https://ncase.itch.io/wbwwb

@af Thanks, there are a number of infrastructure issues we are addressing, and this is one of them. I'm aiming for a nice blog post to highlight the hard work of our sysops team!

https://en.wikipedia.org/wiki/System_Administrator_Appreciation_Day

"Moving forward, we aim to make simple security the default. Security features are enabled and cannot be disabled; enhancements are applied when you update. Experimental security features are disabled by default, but you can enable them at any time." #libremone #security #ux

https://puri.sm/posts/librem-one-design-principles-simple-secure-applications/

@af I meant *my* blog post! 😢 😢

@af On the roadmap but no ETA. See https://matrix.org/blog/2019/07/19/privacy-changes-to-new-vector-identity-servers for some recent news.

But... what did you think about the blog post? 😢

@davidrevoy Your illustrations bring the user personas in our recent blog post to life! Thank you 😺

"In this post we will outline the touchstones we have used to do just that–engineer trustworthy services that everyone can use... We hope it will facilitate communication with friends and colleagues as we hack towards a common goal…" #libremone #userstory #userpersona

https://puri.sm/posts/librem-one-design-principles-services-you-can-trust/

Client-side heuristics beat human-maintained lists in #PrivacyBadger - perhaps they could be useful elsewhere? #designpattern

https://www.eff.org/deeplinks/2019/07/sharpening-our-claws-teaching-privacy-badger-fight-more-third-party-trackers

"The techniques used by trackers are always evolving, so Privacy Badger’s countermeasures have to evolve, too. In the process of developing the new cookie-sharing heuristic, we learned more about how to evaluate and iterate on our detection metrics."

This is a fantastic long read from Valentina Pavel via @privacyint

"If we keep our focus primarily on figuring out data ownership, we face the risk of sidetracking the discussion onto a very questionable path. This is an open invitation to develop new language for clearer conversations and to better shape our demands for the future we want to see." #scenario4 #datarights

https://privacyinternational.org/long-read/3088/our-data-future

@switchingsocial@mastodon.at Dongles (hardware-based multi-factor authentication) are a great replacement for users and site owners. See https://www.dongleauth.info/dongles/ for a list. This also decentralizes "single" sign-on!

If hardware is not an option (yet), site owners should probably ask their framework-development community for a locally-hosted replacement such as https://django-simple-captcha.readthedocs.io/en/latest/ - any replacement that is not locally hosted is not really a solution.

Happy to discuss more by email.

@privacyint Great visualization! I hope you eventually host a twin here in the fediverse 🤖

@switchingsocial@mastodon.at Don't forget https://lutris.net 😁 I recently helped someone use them as a bridge from GOG (like itch.io, proprietary but DRM-free). I couldn't find a fediverse account though. #lutris

@monc Great! It had a different name before (I forget) and was basically "strict mode", but now they've made it "strict mode with an escape hatch" 😀

Just revisited "Encrypt All Sites Eligible (EASE) Mode" in #httpseverywhere

Great workflow that 1) warns you when visit an HTTP-no-S domain and 2) allows you to disable the warning for that single domain, if you trust it... and all intermediaries. 😲

I tested with http://internetbadguys.com since example.com uses HTTPS these days. 🔒

Read more here: https://www.eff.org/deeplinks/2018/12/how-https-everywhere-keeps-protecting-users-increasingly-encrypted-web

"WebRTC WG has asked for privacy and security considerations around the disclosure of a user's local IP address in #webrtc "

https://www.w3.org/wiki/Privacy/IPAddresses

You can prevent this with, for example, #ublockorigin or #privacybadger - see https://github.com/gorhill/uBlock/wiki/Prevent-WebRTC-from-leaking-local-IP-address for some discussion.