The Guide to Peer-to-Peer, Encryption, and Tor: New Communication Infrastructure for Anarchists
"An exhaustive anarchist overview and guide to various apps and tech that utilize peer-to-peer and encryption.
Shhhhh
This is a discussion about digital tools for communicating securely and privately. To begin, it must be stressed that a face-to-face meeting, out of sight of cameras and out of earshot from other people and devices, is the most secure way to communicate. Anarchists were going for walks to chat long before encrypted texting existed, and they should still do so now, whenever possible."
I'm overdue for an #introduction, especially with all you new followers…so here goes.
I'm a software engineer with a degree in Anthropology. I highly recommend the combo.
Most recently I was tech lead for Scaled Human Review at Meta. I worked in the Integrity Foundation (what other companies call "Trust and Safety") on Better Engineering initiatives and #Metaverse integration, with the teams that build human review software for the 30-40K external reviewers. I'd sworn I’d never work at Facebook, but I decided to see if I could make a difference. I couldn’t. And it wasn't a good fit for either of us. But I learned a lot about how the sausages are made and why they have such a hard time with #contentmoderation.
I've been on #socialmedia for four decades (seriously, I saw someone catfished in chat in 1978—this stuff isn't new), and virtually everyone I know I met online somewhere—many I've still never met in person. Needless to say, that's made me pretty passionate about making online communities safe for everyone, and especially marginalized groups.
I'm now a freelance #consultant, working on my own projects (I'll write more on that later), and with my wife's #consulting company (see below). I'm planning to do a lot more writing about #society and #technology (as well some #SFF), and to travel more.
I tend to write long posts (like this one). They may get shorter once my blog is back up. I don't stick to one topic, but I'll try to tag them so you can filter. I post about tech stuff (recent, as well as old geeky #Unix stuff), #social issues, #LGBTQ issues (especially the T), pretty #photos, and random personal anecdotes. When I boost, it's because I think it's something that might be interesting to someone, or some group, that follows me. Those tend to include all the above topics, plus SF&F-related things, and cool science stuff.
I'm #pan, #poly, #nonbinary (or #genderqueer, if you prefer). I prefer "they" for pronouns, but "he" is fine. I spent most of my life thinking I really was a straight cis man who just happened to be a bit quirky and a passionate and tearful ally, so I'm not too picky about how you refer to me. I'm also more than happy to answer any questions about all that, public or private.
I grew up mostly in #Maine and then lived in Massachusetts for a long time, but I now live on sovereign #Swinomish land in #WashingtonState (US), on the edge of the San Juan islands. Despite my first name (that's a story) and current location, I'm not Native American, although I focus a lot on Native American rights. My parents were both active in that area, and that was my introduction to civil rights in general.
I've been a #software engineer at various levels (from programmer to CTO to company founder) for 40+ years. I learned BASIC in high school, taught myself Pascal, FORTRAN and PL/1 in college, learned C as an intern at Bell Labs (Murray Hill, one floor up from the Unix crew), and went on from there. In college, I majored in #Anthropology with a concentration in #Psychology, and that's influenced the way I look at software ever since. Software is designed for people. Software systems build communities (whether intended or not). Anyone who does that damn well better understand how people and #communities work.
I've worked for Bell Labs (psych stats), Sperry Research (window systems, UX design), Apollo/HP (programmable shell, windowing systems, Unix porting, UX design), Bright Ideas (cookbook, educational games), OSF (windowing standards), Alfalfa (multimedia email - SMTP and X.400 :)), Wildfire (phone-based voice assistant), Utopia/USWeb (web and security consulting), Saroca (small boats), Messagefire (anti- #spam software), MessageGate (corporate compliance software), Somewhere (software consulting), ZeeVee (web video aggregation, metadata scraping), TiVo (video content correlation, #metadata pipelines), and Meta. Plus a few others.
I've been with my wife, Dr. Mollie Pepper, for over a decade. She's a #sociologist with a focus on #refugee migration, #gender, and violence; the kind of work that gives you PTSD. She did her dissertation on women's roles in the (now extremely defunct) peace process in #Myanmar (aka #Burma). A year ago she was at a military base frantically processing thousands of Afghan refugees and managing translators. She has a consulting company that specializes in evaluating and designing refugee service and placement programs. You can find her at https://carlsonpepper.com/. Everything I know about #feminism, #intersectionality, #queer theory, #CRT, and #racism I either learned from her, or she gave me the theoretical underpinnings to understand them properly.
I have two grown daughters from my first marriage with Nassim Fotouhi; a kick-ass software engineer/engineering manager who came to the States just before the Iranian revolution.
Shadi Fotouhi is an artist (see my profile background photo, go look up the drug codes and compare them to the mermaids' behavior) turned software engineer; building dynamic room installations will do that to you. She worked in QA at a gaming company, and then at Jibo; a robotics startup. Now she's a senior software engineer at Wayfair--Kubernetes, release configuration, and all that fun stuff.
Shireen Hinckley is a documentarian, digital image technician, video editor, and co-founder of Somewhere Films (https://www.somewherefilms.com/shireen-hinckley); a womxn's filmmaking collective. She works for #Beyoncé at Parkwood Entertainment, where she's an editor and post-production supervisor for all of their video releases. She worked on "Black is King" and just about every video since then, whether it's for Instagram, Times Square, Tiffany's, the Oscars, or Chloe x Halle. No, I can't tell you when the Renaissance visual album will be out—but it will be amazing.
I'm incredibly honored to have those wonderful women in my life. I wouldn't be who I am without them.
A couple other things that may come up, especially in my photos. My mother is an artist who lives in Maine in a round house she designed, and the family built, when I was in high school. And I'm part owner of a #lighthouse on Cape Cod.
Mastodon - the distributed social network - has two interesting challenges when it comes to how users share links. I'd like to discuss those issues and suggest a possible way forward. When you click on a link on my website which takes you to another website, your browser sends a Referer1. This says to …
Facebook Meta - like many other tech titans - has institutional Shiny Object Syndrome. It goes something like this:
Launch a product to great fanfare
Spend a few years hyping it as ✨the future✨
Stop answering emails and pull requests
If you're lucky, announce that the product is abandoned but, more likely, just forget about it.
Open Graph Protocol (OGP) is one of those products. The value-proposition is simple.
It's hard for computers to pick out the main headline, image, and other data from a complex web page.
Therefore, let's encourage websites to include metadata which tells our services what they should look at!
OGP works pretty well! When you share a link on Facebook, or Twitter, or Telegram - those services load the website in the background, look for OGP metadata, and display a friendly snippet.
Facebook Meta were the driving force behind OGP - and have now left it to fester.
And, that might be fine. Facebook Meta are a small company with limited resources. They can't afford to fund standards work indefinitely. And, anyway, OGP is complete, right? It has all the tags that anyone could ever possibly want. Why does it need any improving?
This is annoying for developers. Now we have to write multiple different bits of metadata if we want our links to be supported on all platforms.
Standards work is never "finished". Developers want to add new features. Users want to interact with new forms of content.
Tomorrow someone is going to invent a way to share smells over the Internet. How does that get represented in an Open Graph Protocol compliant manner?
<meta property="twitter:olfactory" content="C₃H₆S"> or <meta property="facebook:nose" content="InChIKey/MWOOGOJBHIARFG-UHFFFAOYSA-N"> or <meta property="og:smell" content="pumpkin spice"> or...
We know from bitter experience that having several mutually incompatible ways to implement something is a nightmare for developers and provides a poor user-experience.
So we create standards bodies. They're not perfect, but a group of interested folks can do the hard work to try and satisfy oppositional stakeholders.
This is my plea to Facebook Meta. If you're no longer interested in improving OGP, OK. You do you. But hand it over to people who want to keep this going. Maybe it's the W3C, or IndieWeb, or Schema.org or someone. Hell, I'm not busy, I'll take it on.