Feature Suggestion | Show supported platforms by OSes #1095

Open
opened 2019-08-04 14:13:14 +00:00 by dawidpotocki · 4 comments
dawidpotocki commented 2019-08-04 14:13:14 +00:00 (Migrated from github.com)

Related to https://github.com/privacytoolsIO/privacytools.io/issues/904

While amd64 is the most popular platform, there are people that use some ARM, POWER machines and even VAX or may consider alternatives, because of stuff like Intel ME.

My suggestion is to add "badges" which looks like contrib one. On distributions pages, sometimes it is hard to even know that they support them! Like on https://www.debian.org/distrib/ (which we find by clicking "Getting Debian" on navbar) we can only find amd64 and i386 I finally found it on https://www.debian.org/CD/http-ftp/#stable. So to make it less pain, these "badges" could <a href> to download page. When user would hover over it, it could say what it is, and where such platforms are mostly used.

Quick dirty example:
image

Related to https://github.com/privacytoolsIO/privacytools.io/issues/904 While `amd64` is the most popular platform, there are people that use some ARM, POWER machines and even [VAX](https://wiki.netbsd.org/ports/vax/) or may consider alternatives, because of stuff like Intel ME. My suggestion is to add "badges" which looks like `contrib` one. On distributions pages, sometimes it is hard to even know that they support them! Like on https://www.debian.org/distrib/ (which we find by clicking "Getting Debian" on navbar) we can only find `amd64` and `i386` I finally found it on https://www.debian.org/CD/http-ftp/#stable. So to make it less pain, these "badges" could `<a href>` to download page. When user would hover over it, it could say what it is, and where such platforms are mostly used. Quick dirty example: ![image](https://user-images.githubusercontent.com/38681822/62424443-0ecf0300-b6be-11e9-975e-1279ee8a63a1.png)
nitrohorse commented 2019-08-04 17:32:05 +00:00 (Migrated from github.com)

Hmm, I do like this idea. It increases maintainability to make sure the various badge links stay relevant but increases accessibility which could be really helpful for some users.

Hmm, I do like this idea. It increases maintainability to make sure the various badge links stay relevant but increases accessibility which could be really helpful for some users.
ggg27 commented 2019-08-22 19:23:08 +00:00 (Migrated from github.com)

Not a huge fan of the current implementation but I like the concept.
I've been trying to follow Risc-V and ARM processors but it isn't always apparent what will work.

Not a huge fan of the current implementation but I like the concept. I've been trying to follow Risc-V and ARM processors but it isn't always apparent what will work.
ggg27 commented 2019-08-22 19:26:13 +00:00 (Migrated from github.com)

Perhaps, we replace the OS section:

 o

And make it just list distribution methods (.deb, .rpm, flatpak, Port (BSD), .e.c.t)
Below that perhaps we then add links to inform users of each architecture.

Perhaps, we replace the OS section: ![ o](https://user-images.githubusercontent.com/52841257/63543507-8603f400-c512-11e9-8b7b-cf25d289d4ad.png) And make it just list distribution methods (.deb, .rpm, flatpak, Port (BSD), .e.c.t) Below that perhaps we then add links to inform users of each architecture.
Mikaela commented 2019-08-22 21:30:40 +00:00 (Migrated from github.com)

While I can imagine a demand for package managers and their privacy concerns (including delta updates, debtorrent, IPFS, Snap), I don't think changing the recommendations to package managers are going to help with privacy issues caused by the operating system such as Windows telemetry or things like sending all searches to corporation X by default.

While I can imagine a demand for package managers and their privacy concerns (including delta updates, debtorrent, IPFS, Snap), I don't think changing the recommendations to package managers are going to help with privacy issues caused by the operating system such as Windows telemetry or things like sending all searches to corporation X by default.
This repo is archived. You cannot comment on issues.
No Milestone
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#1095
No description provided.