[Feature] Add Contrib/Non-free Tag #687
No reviewers
jonah
Labels
No Label
🔍🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
No Milestone
No Assignees
1 Participants
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#687
Loading…
Reference in New Issue
No description provided.
Delete Branch "patch-14"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description: Add contrib tag to software that recommends or depends on non-free software.
What is contrib? Contrib is a term created by the Debian Foundation to discern from software that is free software but may depend on non-free software.
But, isn't everything listed on privacytools.io only free software? Nope, especially not OSes of which many will auto-install non-free firmware like QubesOS.
Please add the labels the same way Brave's experimental label is added.
Note that you can't use
"or,in the labels attribute. I will write a wiki page about this sometime.For commas you can use
,.Should something be done to apps that are free and use free servers, but where server is not configurable, for example Signal?
With Wire we warn about plaintext metadata. If Signal's open source frontend encrypts everything, there's nothing to warn about.
@Shifterovich Done!
You left the HTML in the description here.
You left the HTML in the description here.
You left the HTML in the description here.
You left the HTML in the description here.
You left the HTML in the description here.
@Shifterovich Would you mind plz explaining the requested changes. I do not understand. :)
You added the
labels=...but kept the<span class="badge badge-warning" data-toggle="tooltip" title="This ...in thedescription.@Shifterovich Hmm, try re-pulling. I only see it for LineageOS. I made sure to fix that. :)
Thank you so much for your help!
This is outdated, I fixed this in the Minor Fix commit.
This is outdated, I fixed this in the Minor Fix commit.
This is outdated, I fixed this in the Minor Fix commit.
Yeah, the issue with the description is now fixed.
How do you mean recommend?
@Shifterovich So, one example would be that Ubuntu "recommends" non-free software like Steam.
The main issue with the items I want to currently add this to is firmware but if an OS/App recommends a user to install non-free software you could use the same tag.
Preferably, it would have a more specific warning like:
It is meant to warn the user that although the app is free software it may ask to install non-free software.
In what way does Ubuntu recommend Steam? (If it does, I haven't noticed.)
During installation they show many apps available for Ubuntu, many are non-free. They also have many non-free apps in their App Store.
The FSF/GNU has a good article on this:
Source: http://www.gnu.org/distros/common-distros.html
Is there a reason you changed those?
Could you please add some screenshots?
Since is no painful escaping is solved by this, this should be reverted to be consistent with the include's other properties.
@Vincevrp @Shifterovich Done! (
fa6f752fe4)If I remember correctly, the reasons I did this was because ' " ' was in the description. Therefore I had to switch on order for it to compile properly. But, this should no longer be a problem.
Hopefully this gives you kinda an idea:
@Vincevrp @Shifterovich
hi guys, whats the status here?
This PR seems to have became outdated/merge conflicting due to the website update. I would also like to see how this looks in practice and I think Netlify integration would kick in and bring a preview when the PR is updated.
@Vincevrp
I don't think we need this feature at the moment.
There is still a merge conflict.
I think especially the privacy concious users of https://github.com/privacytoolsIO/privacytools.io/issues/880 might appreciate this.
Deploy preview for privacytools-io ready!
Built with commit
ace1ef623bhttps://deploy-preview-687--privacytools-io.netlify.com
Thanks! This should be fixed in last commit/PR.
@Mikaela
Why the change of " to ' ?
Seems fine to me👍
This seems fine at a cursory glance but I don't want to approve any changes without @BurungHantu1605 or @privacytoolsIO/editorial looking at this.
There are three OKs (including yours), but @blacklight447-ptio didn't catch the review approval button being in top right of "files changed".
I'm more just not 100% sure if noting
contribon not completely free tools is in-scope for this project. It might make people more wary of using certain tools when in reality if people used any of the tools we recommend it would be a significant net benefit to privacy overall.But I also don't have any problem with this being added.
A downside is that it will pollute the source code and the site with a ton of
contriblabels.We should only add things if there's a benefit to adding them.
@Shifterovich I'm not sure I understand, this is already part of my PR.
I didn't add it to all the non-free search engines and hosting sites. I also didn't add it to services like Signal or the tons of VPNs with proprietary back-ends.
If anybody would like discussing adding the label to these, I'de be open to it.
But adding it to OSes is an important role. Many sites and resources don't list it.
Personally, I don't want non-free firmware installed. I don't use my laptops built-in Bluetooth because it requires drivers I cannot audit or change.
I also rely on my OS's repos to be transparent and remove or warn me of software that isn't free or may be a security risk.
People just don't understand the flaws with OSes like Ubuntu and Qubes.
Warning people allows them to make their own choice. It adds what is very similar to a warning label.
OS's like Qubes, OpenWRT, pfSense, Tails, Ubuntu Touch, e.c.t aren't made for every day people.
They were made for people either with extensive computer knowledge or people who are willing to take the time to research.
Very few people will take the time to load OSes like OpenWRT on their routers.
If you want an easy-to-use privacy-focused OS you run an OS like Debian or Trisquel.
OSes like Qubes or Tails aren't very beginner friendly.
Qubes was my first Linux OS and almost made me quit. It slows down applications and it makes it very difficult to run packages like Snap without running in a template or standalone VM. Too many terms to learn IMHO. I will say, it is a great OS for security experts.
Tails (and other live USB OSes) is easy to use, but very specialized. I don't see people switching because of a "contrib" tag.
:)
I didn't look at the diff and automatically assumed the label was added to a ton of cards, sorry.
My opinion is the same as @JonahAragon's.
This is a relatively minor change to the operating systems sections only, so I'm okay with merging this.
There appears to have been couple of OSes with non-free kernels I must've forgotten to add the label to.
(mainly just DD-WRT, Whonix, and SubgraphOS)
But, wanted to inform you on why the extra commits.
@Shifterovich @JonahAragon @Mikaela @blacklight447-ptio
Like Before, OSes like Arch that list free'd alternatives don't need to tag.
Since, they say state that they aren't fully free in their description.
Aye, I was just curious if any of the past reviews have changed.
If they have, is there any changes that you would like undone or reverted or changed?
There hasn't been a discussion here is a while. :)
@JonahAragon @Shifterovich @Mikaela
I overall approve of this PR but it has some strange code style related things that should be fixed.
I'd also like to know this? Seems inconsistent.
This is not good style.
It does seem to make any difference to the visual side.
I'll commit suggestion.
Should be fixed in later commit. :)
Thanks!
Okay well, I suppose I'll go ahead and merge this 🤞