Add ShareDrop in File Sharing (Worth Mentioning) #2326

Open
lrq3000 wants to merge 1 commits from lrq3000/sharedrop into master
lrq3000 commented 2021-06-02 02:01:24 +00:00 (Migrated from github.com)

Description

Resolves: #1828

Check List

  • I understand that by not opening an issue about a software/service/similar addition/removal, this pull request will be closed without merging.

  • I have read and understand the contributing guidelines.

  • The project is Free Libre and/or Open Source Software

## Description Resolves: #1828 #### Check List <!-- Please add an x in each box below, like so: [x] --> - [x] I understand that by not opening an issue about a software/service/similar addition/removal, this pull request will be closed without merging. - [x] I have read and understand [the contributing guidelines](https://github.com/privacytools/privacytools.io/blob/master/.github/CONTRIBUTING.md). - [x] The project is [Free Libre](https://en.wikipedia.org/wiki/Free_software) and/or [Open Source](https://en.wikipedia.org/wiki/Open-source_software) Software * Netlify preview for the mainly edited page: <!-- link or Non Applicable? Edit this in afterwards --> * Code repository of the project (if applicable): https://github.com/szimek/sharedrop
youdontneedtoknow22 commented 2021-06-09 00:52:12 +00:00 (Migrated from github.com)

I'm no expert but:
1- when the recipient had WebRTC blocked, he couldn't get the file
2- when the sender had WebRTC blocked, he couldn't send the file (even after enabling webrtc again, I couldn't send the file somehow lol. So someone might want to check that).
3- I couldn't use the site using Firefox for some reason. Maybe it's because one of the recommended tweaks? I'm not sure. It worked on Brave and Edge, but not Firefox (even when completely disabling uBO and Firefox enhanced tracking protection).
PTIO recommends using Firefox, and blocking WebRTC. So I'm not sure if that's the right website to recommend.

I tell my friends to use Tresorit with a password on their files. It's the only way nontech-savvy people would send me something (or recieve something from me). Other options could be: sending files using Signal or with a PGP encrypted email (automated for 2 protonmail or tutanota users)

I'm no expert but: 1- when the recipient had WebRTC blocked, he couldn't get the file 2- when the sender had WebRTC blocked, he couldn't send the file (even after enabling webrtc again, I couldn't send the file somehow lol. So someone might want to check that). 3- I couldn't use the site using Firefox for some reason. Maybe it's because one of the recommended tweaks? I'm not sure. It worked on Brave and Edge, but not Firefox (even when completely disabling uBO and Firefox enhanced tracking protection). PTIO recommends using Firefox, and blocking WebRTC. So I'm not sure if that's the right website to recommend. I tell my friends to use Tresorit with a password on their files. It's the only way nontech-savvy people would send me something (or recieve something from me). Other options could be: sending files using Signal or with a PGP encrypted email (automated for 2 protonmail or tutanota users)
lrq3000 commented 2021-06-09 02:32:18 +00:00 (Migrated from github.com)

I tested ShareDrop extensively with both Chrome and Firefox. It actually
works better with Firefox, but indeed webrtc was enabled.

I think the recommendation about disabling WebRTC should be re-evaluated,
some of the safest new encrypted web technology such as encrypted
multiparty videoconferencing requires WebRTC.

In any case this recommendation is not mandatory but optional ("it's
probably a good idea to disable WebRTC") so this shouldn't imho prevent
inclusion, furthermore there is no requirement for coherence across all
tips/softwares recommended on PTIO, eg, several recommended plugins can
break javascript but lots of recommended softwares use javascript.

Le mer. 9 juin 2021 à 02:52, youdontneedtoknow22 @.***>
a écrit :

I'm no expert but:
1- when the recipient had WebRTC blocked, he couldn't get the file
2- when the sender had WebRTC blocked, he couldn't send the file (even
after enabling webrtc again, I couldn't send the file somehow lol. So
someone might want to check that).
3- I couldn't use the site using Firefox for some reason. Maybe it's
because one of the recommended tweaks? I'm not sure. It worked on Brave and
Edge, but not Firefox (even when completely disabling uBO and Firefox
enhanced tracking protection).
PTIO recommends using Firefox, and blocking WebRTC. So I'm not sure if
that's the right website to recommend.

I tell my friends to use Tresorit with a password on their files. It's the
only way nontech-savvy people would send me something (or recieve something
from me). Other options could be: sending files using Signal or with a PGP
encrypted email (automated for 2 protonmail or tutanota users)


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/privacytools/privacytools.io/pull/2326#issuecomment-857289600,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIRFXRCMLPXN6Y7UJCY2IDTR23MRANCNFSM455ZLNTA
.

I tested ShareDrop extensively with both Chrome and Firefox. It actually works better with Firefox, but indeed webrtc was enabled. I think the recommendation about disabling WebRTC should be re-evaluated, some of the safest new encrypted web technology such as encrypted multiparty videoconferencing requires WebRTC. In any case this recommendation is not mandatory but optional ("it's probably a good idea to disable WebRTC") so this shouldn't imho prevent inclusion, furthermore there is no requirement for coherence across all tips/softwares recommended on PTIO, eg, several recommended plugins can break javascript but lots of recommended softwares use javascript. Le mer. 9 juin 2021 à 02:52, youdontneedtoknow22 ***@***.***> a écrit : > I'm no expert but: > 1- when the recipient had WebRTC blocked, he couldn't get the file > 2- when the sender had WebRTC blocked, he couldn't send the file (even > after enabling webrtc again, I couldn't send the file somehow lol. So > someone might want to check that). > 3- I couldn't use the site using Firefox for some reason. Maybe it's > because one of the recommended tweaks? I'm not sure. It worked on Brave and > Edge, but not Firefox (even when completely disabling uBO and Firefox > enhanced tracking protection). > PTIO recommends using Firefox, and blocking WebRTC. So I'm not sure if > that's the right website to recommend. > > I tell my friends to use Tresorit with a password on their files. It's the > only way nontech-savvy people would send me something (or recieve something > from me). Other options could be: sending files using Signal or with a PGP > encrypted email (automated for 2 protonmail or tutanota users) > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/privacytools/privacytools.io/pull/2326#issuecomment-857289600>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAIRFXRCMLPXN6Y7UJCY2IDTR23MRANCNFSM455ZLNTA> > . >
This repo is archived. You cannot comment on pull requests.
No reviewers
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#2326
No description provided.