191–200 of 267 posts
I need to send large file securely sporadically , I cant like pay for like 10 usages etc .. as long as its not time bound
Earlier quoted context omitted.
"We" as in "the people who knows how to use the command line". Unfortunately very few of the people I send files to knows that. There's https://webwormhole.io/ and https://file.pizza/ , but can I know what they really do behind the scenes? Native open-source software for this would be a dream come true. It's 2020 and I still wrestle with sending files between devices. And no, don't take this as a wish for creating ju…
webwormhole does everything on the client via RTC IIRC? https://github.com/saljam/webwormhole
Earlier quoted context omitted.
Easy ways to copy files between nearby computers: scp The python 3 equivalent of -mSimpleHTTPServer Samba Or maybe I’m missing something.
python3 -m http.server
---
$ python3.7 -m http.server --help
usage: server.py [-h] [--cgi] [--bind ADDRESS] [--directory DIRECTORY] [port]
positional arguments:
port Specify alternate port [default: 8000]
-h, --help show this help message and exit
--cgi Run as CGI Server
--bind ADDRESS, -b ADDRESS
Specify alternate bind address [default: all interfaces]
--directory DIRECTORY, -d DIRECTORY
Specify alternative directory [default:current directory]Earlier quoted context omitted.
I don't have any specific knowledge, but my general impression was that malware was a very real issue that nobody could come up with a realistic response to. Other than that, it seems like Send was a breakout success. (I work for Mozilla, but mostly on the JS engine.)
With the utmost respect, can somebody please tell if anyone thought of requiring a Firefox account? Or charge $2/mo and go from there? Products usually iterate on design and security, no? Not just give up right away? Some of us recommended a Firefox+ service that bundles Firefox Send, the VPN, etc. and charge a monthly premium. I would've paid a lot of money. Nothing makes any sense looking from outside!
Earlier quoted context omitted.
I don't have any specific knowledge, but my general impression was that malware was a very real issue that nobody could come up with a realistic response to. Other than that, it seems like Send was a breakout success. (I work for Mozilla, but mostly on the JS engine.)
2 questions: 1) how? 2) how did you know? I can't quite see how malware would be sent with this? An exploiter uploads a file, then gets someone to download it - where's the secret sauce, why does this work better than hosting the file; each file is only downloadable once IIRC? Next, how were Mozilla able to determine the contents of files shared (but not able to just drop by hash known malware, or run antivirus heuri…
As for how to identify it, because files were being encrypted before sending that probably was being done by seeing how much the service ended up in spam/phishing attempts - they may well have been able to get that information from filtering software vendors.
Earlier quoted context omitted.
Nearly all their "side projects" look like greenfields used by the project teams to boost their CVs so they can land better jobs. Those teams know very well that those projects have no use case, but they dont care. Foundation does not care either, since it is busy with increasing own remuneration and politics. Meanwhile their core product lost around 10 percentage points of market share (from 15% marketshare to 5%):…
It's so negative, why people keep being cynical towards Firefox Mozilla.
Earlier quoted context omitted.
They also don't understand how to make money. They think eating in the hand of Google is a viable financial strategy.
Google is giving them so much money, for such a long time, that it is hard to replace. Golden handcuffs. Donations and $10/mo "Firefox subscriptions" aren't going to make up for it. There are ways they could make money and leverage their browser, such as becoming a certificate authority (they're literally outsourcing profit) or making their own search engine (which would probably be a bad idea for other reasons). Not…
They've burned up billions with little to show for it (their declining market share is the proof of this) and now wonder how they will survive.
I really don't understand it. - Content was used to spread malware/illegal content - It was not profitable How are those two things something you find out after the fact? What was the reasoning for launching the product in the first place?
Nearly all their "side projects" look like greenfields used by the project teams to boost their CVs so they can land better jobs. Those teams know very well that those projects have no use case, but they dont care. Foundation does not care either, since it is busy with increasing own remuneration and politics. Meanwhile their core product lost around 10 percentage points of market share (from 15% marketshare to 5%):…
1) The majority of developers at Mozilla are working on Firefox. Many more than 50. It is true that we have fewer staff than Google has working on Chrome (Mozilla is less than half, I heard rumoured?).
2) We did kill XUL extensions, after resisting for years. It would have been a self-inflicted fatal wound not to. https://yoric.github.io/post/why-did-mozilla-remove-xul-addo...
3) Anyone who's had to make a decision of when to ship a product will be familiar with the things you need to juggle. There was a much earlier alpha that got close to shipping and then held back. You would have been less happy with that. There are later versions that would have been more complete, at the cost of maintaining two separate code bases longer. Massive opportunity cost. Was it shipped at exactly the right point? Almost certainly not.
1000 might seem like a large number to you, but we are a small organization relative to others in the same space; we can't keep a lot of extra bets going.
4) Superficially: uh, isn't that what bugs are? The only way to prevent your decisions from causing problems is to not make decisions, and then that's a bigger problem. Specifically with the signing, nobody forgot to sign anything, a cert expired. We screwed up.
The decision to sign addons had consequences, yes. A decision to not sign addons would have consequences as well -- which we knew intimately, because they were very, very real and growing rapidly. But I can't make anyone believe that if the starting point is the assumption of incompetence.
5) Shifting resources away from enterprise does not equal "not caring about the product at all". I've long taken issue with that particular (now changed) decision too, but I never assumed that I had enough of the full picture to be confident that I was right and the decision makers were wrong. Contrary to prevailing opinion, just "providing" something is not free. Enterprise support costs resources. Throwing something over the wall and saying "patches welcome!" when it doesn't work for people is worse than not pretending to support it in the first place.
Your beef with side projects is a little bizarre to me. Why do you think they take up such a huge percent of resources? Assuming 95% is not a good faith argument that I can even respond to. Maybe we could agree that 0% would be unhealthy and shortsighted?
I'll stop there. I will suggest that you at least stop repeating things like "development teams are not working on core product" since I know that to be objectively false.
(I'll admit that at present there is one fewer developer working on core product right now, but that'll be fixed as soon as I close this tab.)
Earlier quoted context omitted.
We still have Magic Wormhole though and it's awesome! (at least for techies) https://magic-wormhole.readthedocs.io/en/latest/welcome.html
"We" as in "the people who knows how to use the command line". Unfortunately very few of the people I send files to knows that. There's https://webwormhole.io/ and https://file.pizza/ , but can I know what they really do behind the scenes? Native open-source software for this would be a dream come true. It's 2020 and I still wrestle with sending files between devices. And no, don't take this as a wish for creating ju…
Also they're not very reliable. I tried to use both of those a couple weeks ago and it just didn't work. File.pizza crashed during initialization on a large file from a friend, and they both failed when I was trying to send a file that was only about 3GB.