Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove Signal until Removal of Proprietary Software #922

Closed
wants to merge 3 commits into from

Conversation

Projects
None yet
5 participants
@ghbjklhv
Copy link
Contributor

commented May 11, 2019

Description: Signal uses non-free software. I would like to push the notion to remove them until all non-free dependencies have been resolved.

"[Signal] currently has a proprietary dependency on Google libraries. Helping the project remove this dependency and operate the necessary infrastructure is a high priority. " - FSF

@netlify

This comment has been minimized.

Copy link

commented May 11, 2019

Deploy preview for privacytools-io ready!

Built with commit 173e0ee

https://deploy-preview-922--privacytools-io.netlify.com

ghbjklhv added some commits May 11, 2019

@ghbjklhv ghbjklhv changed the title Remove Signal untill Removal of Proprietary Software Remove Signal until Removal of Proprietary Software May 11, 2019

@Mikaela
Copy link
Member

left a comment

I don't think this is a good idea as Signal is currently possibly the easiest E2EE messaging solution.

I am selecting "Request changes", because there is no "Disapprove" button.

@Mikaela Mikaela requested review from BurungHantu1605, blacklight447-ptio, JonahAragon and privacytoolsIO/editorial May 11, 2019

@angela-d

This comment has been minimized.

Copy link

commented May 11, 2019

Another days' old account requesting removal of one of the (arguably) most private chat apps.

My tinfoil hat is tingling.

If this was a legit user that just got into privacy, why not post the concern on Signal's repo? Asking a guide site to flat out remove it 'until..' is highly suspect.

Why not request a warning or badge to communicate the concerns? Why flat out remove it?

@ghbjklhv

This comment has been minimized.

Copy link
Contributor Author

commented May 11, 2019

I don't think this is a good idea as Signal is currently possibly the easiest E2EE messaging solution.

I am selecting "Request changes", because there is no "Disapprove" button.

I understand that this seems to be a popular narrative.
But I must say that clients RetroShare are just as easy and arguably more private.

Another days' old account requesting removal of one of the (arguably) most private chat apps.

My tinfoil hat is tingling.

If this was a legit user that just got into privacy, why not post the concern on Signal's repo? Asking a guide site to flat out remove it 'until..' is highly suspect.

Why not request a warning or badge to communicate the concerns? Why flat out remove it?

My account it fairly new because I support free software and don't generally use Github.

And the PR doesn't fully remove it, just comment out the card.

@blacklight447-ptio

This comment has been minimized.

Copy link
Member

commented May 11, 2019

As far as I know, privacytools.io does not have any strict open source requirement, so does not have to be removed because of that. Also, Signal is open source and fully reproduciable if you use the apk version, sure it may has google in the google play version, but at that point your already running google play anyway, which makes it pointless. I would vote to reject this pull request.

@JonahAragon

This comment has been minimized.

Copy link
Member

commented May 11, 2019

privacytools.io does not have a free software requirement. We are recommending the best overall tools in each respective category. To discuss the removal of Signal lets stick to the open discussion issue #779. Closing this PR unless that issue is resolved first or @privacytoolsIO/editorial disagrees.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.