21–30 of 285 posts
Do they share my files and "anonymized" upload history with a third party (edit: was "advertising company") for this service as well?
They share it with RiseUp, the radical-left organisation they fund. Don't worry my friend, your files are safe with them.
It really is a shame that there still isn't a easy way (A person whose computer knowledge extends to using facebook), that I know of, of sending arbitrarily large files that isn't tethered to a specific cloud service and is also reliable (can tolerate connection dropping). It seems that bitorrent protocols are pretty close, but I don't think there is a seamless client that allows for "magical" point to point transact…
You're at a computer. You need to connect to another computer. First you need to know a route to that computer. If it has an externally reachable IP address and you know that, then great. If it has an externally reachable IP address and a DNS entry and you know _that_, then also great. If you don't know the IP address or domain name of the other computer then you'll have to do some kind of lookup/exchange to find it.…
then you're clearly not the person we should be asking to build this kind of thing are you? :-)
my proposal actually solves two important problems with peer-to-peer systems, and I barely have to write any new code to make it work! the solution? i2p! it's an anonymous mix network, much like Tor, but completely decentralized. using an intermediary dex mix network fixes the nat issue and prevents you from leaking your IP address to other peers.
It really is a shame that there still isn't a easy way (A person whose computer knowledge extends to using facebook), that I know of, of sending arbitrarily large files that isn't tethered to a specific cloud service and is also reliable (can tolerate connection dropping). It seems that bitorrent protocols are pretty close, but I don't think there is a seamless client that allows for "magical" point to point transact…
You're at a computer. You need to connect to another computer. First you need to know a route to that computer. If it has an externally reachable IP address and you know that, then great. If it has an externally reachable IP address and a DNS entry and you know _that_, then also great. If you don't know the IP address or domain name of the other computer then you'll have to do some kind of lookup/exchange to find it.…
Three examples of this, implemented and working:
- https://www.sharedrop.io/ - https://www.justbeamit.com/ - https://file.pizza/
Do they share my files and "anonymized" upload history with a third party (edit: was "advertising company") for this service as well?
You can see exactly what they collect here https://github.com/mozilla/send/blob/master/docs/metrics.md and decide for yourself. I think it's misleading to refer to Google as an advertising company when talking about Analytics since this data won't be used for targeting ads.
https://www.reddit.com/r/firefox/comments/74n0b2/mozilla_shi...
Earlier quoted context omitted.
You're at a computer. You need to connect to another computer. First you need to know a route to that computer. If it has an externally reachable IP address and you know that, then great. If it has an externally reachable IP address and a DNS entry and you know _that_, then also great. If you don't know the IP address or domain name of the other computer then you'll have to do some kind of lookup/exchange to find it.…
WebRTC solves all the issues you're mentioning, and is available in Chrome and Firefox (in some for in Edge, and soon in Safari). Three examples of this, implemented and working: - https://www.sharedrop.io/ - https://www.justbeamit.com/ - https://file.pizza/
Earlier quoted context omitted.
You're at a computer. You need to connect to another computer. First you need to know a route to that computer. If it has an externally reachable IP address and you know that, then great. If it has an externally reachable IP address and a DNS entry and you know _that_, then also great. If you don't know the IP address or domain name of the other computer then you'll have to do some kind of lookup/exchange to find it.…
I'm not aware of any entirely decentralised system which would allow two computers which are behind NAT to find and then talk to each other. Or any obvious design which would work there. then you're clearly not the person we should be asking to build this kind of thing are you? :-) my proposal actually solves two important problems with peer-to-peer systems, and I barely have to write any new code to make it work! th…
(Serious question - I've not used it myself, and I'm intrigued at the process.)
Earlier quoted context omitted.
They share it with RiseUp, the radical-left organisation they fund. Don't worry my friend, your files are safe with them.
In another comment you say the donated money to that organisation. Why do you think user data would be shared with them?
Mozilla does not have the ability to access the content of your encrypted file [...]
https://testpilot.firefox.com/experiments/send
Earlier quoted context omitted.
You're at a computer. You need to connect to another computer. First you need to know a route to that computer. If it has an externally reachable IP address and you know that, then great. If it has an externally reachable IP address and a DNS entry and you know _that_, then also great. If you don't know the IP address or domain name of the other computer then you'll have to do some kind of lookup/exchange to find it.…
Two thoughts: - IPv6 kind of helps here, at least if we hope that no NAT standard ever makes it into IPv6. Crossing my fingers. - There does exist at least one NAT hole-punching technique that can traverse two NATs with no central server using ICMP-based holepunching and UDP. Obviously, like all hole punching techniques, it only works on certain kinds of NATs, and firewalls can kill it.
The fact that it doesn't support NAT is seen as a risk in such environments ( which rightly or wrongly consider it as a second level of firewalling ). Some deployments that I've seen use only site-scoped with no globally-routed prefixes. Everything Internetty has to go over IPv4, which makes the Security team's job easier; drop all IPv6 at the DMZ and drop all non-NAT IPv4.
Earlier quoted context omitted.
You're at a computer. You need to connect to another computer. First you need to know a route to that computer. If it has an externally reachable IP address and you know that, then great. If it has an externally reachable IP address and a DNS entry and you know _that_, then also great. If you don't know the IP address or domain name of the other computer then you'll have to do some kind of lookup/exchange to find it.…
Two thoughts: - IPv6 kind of helps here, at least if we hope that no NAT standard ever makes it into IPv6. Crossing my fingers. - There does exist at least one NAT hole-punching technique that can traverse two NATs with no central server using ICMP-based holepunching and UDP. Obviously, like all hole punching techniques, it only works on certain kinds of NATs, and firewalls can kill it.
I think you're referring to this? Clever hack indeed. https://github.com/samyk/pwnat