Add Hardware section #616
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "gjhklfdsa/Hardware-Section"
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
Summary: Re-add Hardware Section
Why? Software is only half the privacy battle.
What are you recommending to add to the section? I would like to note finding decent privacy respecting hardware manufacturers is VERY hard, that being said, I added Technoethical, Purism, and ThinkPenguin. I made sure to add a caution tab displaying current vulnerabilities in the process of finding Open Source Hardware. These companies are all widely know in the field.
I have a suggested change! Great! Plz make a comment so that it may be reviewed. Edits from maintainers are welcomed.
Edit: Vikings.net is added to the worth mentioning.
Screenshots
Edit: I added some worth mentioning products, tell me what you think:
@beardog108 I'd like to hear your opinion on this topic.
@gjhklfdsa Take a look at #331
Looks very nice to me, at the end of the page for the "hardcore" users. I'd just suggest that the caution be done using the alert-warning banners we use on the other sections. That'd also mean removing the links though, I'm not sure how we should do that, put them in and make this banner different than the rest or keep a comment on how to check the Open Source certification in the place it's now.
Also, taking into account Intel ME and that type of chips, I believe we could also (or instead) reformulate the caution to indicate that free as in freedom hardware is hard to find and these were our "best" alternatives.
@hugoncosta I think it could definitely be useful to alert the user that Think Penguin may run non-free on the device (very few of their products have been certified/endorsed) and that Purism still has non-free in the ME.
It already has a caution section.
However, I'm unaware of any issue with Technoethical.
What do you think @Shifterovich ?
I agree with @hugoncosta.
@beardog108 thoughts please?
I didn't comment before but I did look at this. I also agree with @hugoncosta.
@Shifterovich I appear to be having some compiling issues. But, it should now fully work and have warning flags.
@Shifterovich @hugoncosta @gjhklfdsa Most of the projects have RYF certification.
http://ryf.fsf.org/
This would mean that the FSF certifies them on a number of areas.
Including spyware, here is a statement by them:
There is a merge conflict due to section splitting.
@Shifterovich So where we at for this PR?
Please merge gjhklfdsa/privacytools.io#2 to (hopefully) bring this PR up-to-date.
@JonahAragon Thanks!
Deploy preview for privacytools-io ready!
Built with commit
b6e0332293
https://deploy-preview-616--privacytools-io.netlify.com