People have difficulty comprehending the amount of #Linux Distributions: they see 1000+1 versions advertising themselves as "xxx OS".
I think that the #Linux naming scheme should be better. A fork of #fedora gets its own name like "Ultramarine OS". This implies that it is a standalone #Linux distribution, from scratch. This is not the case, as it is just #fedora with little, little tweaks and pre-adjustments.
Some forks:
change desktop environment,
remove or include bloat,
add a few preinstalled apps,
use a different theme,
test it,
change wallpaper, calling it a day and almost branding it as their own.
You can litterally automate the abovementioned tasks (downloading apps and desktop environment, theming and remove bloat) and get the same result.
I don't think this "issuance" of brand identities should be that easy (yes, they've scarcity).
It is like the ship of Theseus. How much can you change while being the same?
I think Linux distributions should be classified using these factors:
- upstream or independed presence
(#linux distributions like "GrapheneOS" that really help create solutions)
- extensibilty (download manager etc)
(Biggest usability difference)
- why it stands out
(special features like 'yast' from #opensuse or homebrewed contributions)
- purpose
(servers, users, lightweight, bitcoin, supercomputers, mobile, stability, etc)
- philosophy
(to predict where the project is and will be going.)
I think that the name should always tell if it is using #linux kernel/#bsd.
then, the name of the independend distribution.
then, the other upstreams and its own name.
#Linux>independend distro>upstreams and own name
(could be in a different order.)
So Examples Given:
#Pop_OS! --> #Linux #debian #ubuntu pop
#Fedora --> #Fedora #Linux
#Linux #mint #debian edition --> #Linux #Debian #mint
#Android --> #Android #Linux
#Manjaro --> #Linux #Arch #Manjaro
#ChromeOS --> #Gentoo #Chrome #Linux
#Ubuntu --> #Linux #Debian #Ubuntu
#Void #Linux --> #Linux #Void
As you can see, some distro's will get a really absurd name, implying that it is a fork of a fork, which is in my eyes pointless.
or it could be something like
`Linux Mint.deb`, `Linux Bitkey.deb`
It would make it alot more understandable for new users and also limit the pointless forks so that it is easier to focus code review and audits.
https://github.com/bluewallet/bluewallet
I think it is, although I don't see them advertising it. Which is strange.
Use a classic watch. They are nice
What app? Then I know which one to avoid
A viable FOSS set for any degoogled Android:
- Launcher: KISS Launcher, Text launcher, lawnchair
- App sources: F-Droid + FFUpdater + Obtainium
- File manager: Amaze, material files, DroidFS (encrypted)
- Keyboard: Thumb-Key (unless you have a physical one), 8vim, tiny keyboard
- Browsers: Mull/Mulch, fennec, Firefox Focus, Tor Browser (all via FFUpdater), Pocket Gopher, Buran, lagrange (gemini)
- Email client: K-9 Mail
- Camera: Open Camera, camera inside DroidFS
- OTP app: Aegis
- CLI environment: Termux
- Media players: VLC, Xmp Mod Player, Clipious, aves libre
- Communications: Conversations, aTox, Element, Linphone, Jitsi Meet, Nostr, SimpleX
- Crypto wallets: Unstoppable, Monerujo, Ywallet, blue wallet
- Smartwatch interaction: Gadgetbridge, Casio G-Shock Smart Sync
- Utils: Orbot, Orientation Faker, Wasted, insular (workprofile), invizible pro
#foss #opensource
what do you think about those additions?
I REALLY WOULDN'T CARE ABOUT IT TO MUTE SOMEONE OVER IT. BUT I DO UNDERSTAND IF OTHERS FIND IT HARD TO READ.
Use bitcoin circular economy as starting point. People will get used to the idea and then it becomes easier. Eventually it is like a browser comharison but for money.
Would you need to know how many users are on the network to know the price then?
I will loov into it.
Set up a bitcoin wallet and let them have it to store bitcoin.
Who has followed this advice? And who is already using #foss #open-source #encryption for files?
#security
because you can easily search trough it. A search bar is the most important. Not on the server, but just local. In the browser or text editor.
This would be my top documentation experience:
I have a problem, I visit documentation site, I see everything in plain text and thus I can search in an instant trough all text to find what I need. I might even easily copy all text at once, paste it into vim or another text editor, and use advanced search. I could even use `git grep "search string"` if the documentation is a github repo.