I don’t have to explain to this audience why one would want to avoid “big tech”, that is your Google, Amazon, Facebook, and so on.
I’m working with a group to create a skill tree for dropping big tech, but could use some more ideas. A skill tree is a chart with actions and skills, ordered from easy to advanced, where you can check which skills you already have and be inspired with other skills. An example: https://github.com/sjpiper145/MakerSkillTree/blob/main/Makerspace Skill Trees/Makerspace Skill Tree.png More Maker skill trees: https://github.com/sjpiper145/MakerSkillTree
We want to make it easy for people to switch, and motivate people towards a more open and ethical (tech) world. We already have a list of general actions for the tree, ranging from general concepts like “learn what Open Source means” to specific actions like “search with DuckDuckGo”.
I want this to be a good list that actually helps, that is fun and interesting, easy to use, and inspiring, which is why I’m asking you for help. Can you think of things that should definitely (or definitely not) be on this list? I would appreciate all the help I can get.
(x-post from Ask Lemmy since this might be a good audience for the topic)
Microsoft is big tech, and GitHub is owned by y Microsoft.
And it’s not even a compellingly better alternative than the other options. Gitlab, or gitea, or forgejo are all great.
True. It’s not all black and white.
But I’m sure you understand the general idea behind the project.
It would help to know what you already have on the list. Then we can find what’s missing.
Here’s a list:
- learn about federation and decentralisation
- understand the Free Software Definition
- find out the difference between “Open Source” and “Proprietary.”
- learn the difference between “free” and “libre”
- research how popular free services make money
- find a recent list of privacy-respecting software or Open Source applications
- switch to a privacy-focused search engine like DuckDuckGo and set it as your default
- install an ad blocker in your browser
- try a privacy-respecting email provider
- use a privacy-friendly browser
- start using a privacy-focused messaging app
- install LibreOffice for office documents
- download an Open Source app from F-Droid
- share a document using the OpenDocument format
- find and follow friends on the fediverse
- delete accounts on big tech platforms
- talk to a friend about why they should try Open Source
- experiment with chat solutions like IRC, XMPP, or Briar for offline mesh communication
- host a small group video call using Jitsi
- organise a “Switch Party” to help friends adopt new platforms
- de-Google your phone by installing a custom ROM (e.g., GrapheneOS, LineageOS, /e/OS)
- use an encrypted email client
- set up your own cloud storage with NextCloud
- compare two privacy-friendly email providers
- discover how to report issues in Open Source projects
- write to a company or government agency asking for documents in OpenDocument format
- host your own Mastodon server
- develop or contribute to Open Source tools
- find and explore the source code of an Open Source project
- replace the battery in your phone
- bring an old device back to life with Open Source software
- try a “dumb phone”
- find a device manufacturer who shares the source or design of their hardware/software
- spend two days without social media
- shop at a physical store instead of online
- use cash instead of digital payment methods
- convince a coworker to share a document in an open format
- convince your employer to share documents in an open format
- give a talk about the importance of public services and open technologies
- write or share a guide for switching to privacy-respecting software
- organise a local meetup or workshop to help others switch
I forgot one: “brush Richard Stallman’s beard”.
That probably goes in the “advanced” area. ;-)I would add how to use censorship circumvention tools like Tor.
Will do, thanks.
There’s more options there, from Tor to ad-blocking yet privacy-respecting VPNs to mirrors of websites and paywall circumvention tactics.
That’s almost as big as my whole life plan…
I would add, learn to format comments so they don’t print as blocks of barely readable text and don’t use line seperators like dashes if your text has dashes in it because it makes it harder to read when it prints out as a block of text.
It should be perfectly valid MarkDown, and it displays just fine on the webpage.
maybe their client does not use the github flavored markdown. originally to render a line break you have to end the line with double space. because of that, their client might not understand that the - signs are supposed to be list items
Alright, I’ve added the spaces.
