Looks like Mozilla is becoming VPN company shifting it's previous focus which was on browserware. Mozilla VPN seems to be just rebranded resell of Mullavad VPN with Mozilla Goodies. Mozilla Monitor seems to use https://haveibeenpwned.com/ (also as seen in Firefox desktop) Mozilla Firefox Private Network looks like another Cloudflare Warp's rebrand (with litte good additions maybe?) seeing that it uses Cloudflare . Mo…
Update on Firefox Send and Firefox Notes
161–170 of 203 posts
Re: Update on Firefox Send and Firefox Notes
#162Earlier quoted context omitted.
If they switched to webkit there'd be no more reason to use it over degoogled chromium.
Unless there are very significant differences that are noticeable to mass user base, the engine is not a relevant factor in browser market share. When chrome came charging in, Microsoft had let IE fall so far behind that even to my 74-year-old opa, chrome was noticeably better. People largely don't choose firefox over non-degoogled chrome today. All browsers on iOS are reskinned safari with different accounts for syn…
Although I suopose there is still manifest v3...
I fear that if Firefox switched to webkit or blink, they might lose a significant number of existing users without a clear way to win back more.
Re: Update on Firefox Send and Firefox Notes
#163Sad! Developer of `ffsend` here. I've built `ffsend` as CLI tool for Send to securely share files from the command line. It has been a great success! Thanks Mozilla, for building and providing this amazing service! For the interested: https://github.com/timvisee/ffsend I'm currently hosting a public Send instance myself to ffsend keep working. Let's see how long I can keep this going (and funded).
Your tool is very useful for me. Have used it since a long time. First transfer.sh and now Firefox Send are closed. What service should I trust to send file quickly and securely.
Re: Update on Firefox Send and Firefox Notes
#164Earlier quoted context omitted.
Servo was never actually the heir-apparent to Gecko.
Never officially. But I think once they started to migrate components into Firefox it seemed obvious that the experiment was a "success" and that it was on the path to replacing gecko (starting piece by piece and maybe eventually making a switchover).
The Gecko team was mostly spared from the layoffs. There is no intention to cease Gecko development.
Re: Update on Firefox Send and Firefox Notes
#165Hm, been spending a while creating a 'Firefox Send' copy, attempting to host files. Check out a new verison at: - https://v2.femto.pw/ Looking for some help if anyone can, :) - https://github.com/femto-apps/web-file-uploader The old copy ( https://femto.pw/ ) has been used over 100 million times and sent over 13PB of data!
Check out this project as well: https://github.com/kern/filepizza
Re: Update on Firefox Send and Firefox Notes
#166Sad! Developer of `ffsend` here. I've built `ffsend` as CLI tool for Send to securely share files from the command line. It has been a great success! Thanks Mozilla, for building and providing this amazing service! For the interested: https://github.com/timvisee/ffsend I'm currently hosting a public Send instance myself to ffsend keep working. Let's see how long I can keep this going (and funded).
Your tool is very useful for me. Have used it since a long time. First transfer.sh and now Firefox Send are closed. What service should I trust to send file quickly and securely.
I just rent a VPS, temporarily host the file on there, and give whoever it is a link.
Edit: If my threat model were to include protecting the contents of the file from the VPS provider I would probably encrypt it client side with GPG or something similar.
Re: Update on Firefox Send and Firefox Notes
#167Earlier quoted context omitted.
This is only necessary because the company has been honorably mismanaged for so long and lacks any sort of consistent vision. Maybe Mozilla should also look into reducing leadership compensation or at least have it reflect the performance of the company.
> lacks any sort of consistent vision I have no insider knowledge of how well it’s been managed so I’ll leave that to other commentators. However I’d say that their vision for openness is part of their curse. Google in developing Chrome are not held to the same community expectations. It’s expensive to build and maintain a modern day browser and the competitors have deep pockets to the extent of it being worth comple…
Google was forced to do it by themselves.
>If the community won’t let them charge for anything they do, and claim “extraction/extraction!” with every move they are destined to go under.
I dont ever see that from Mozilla community. No one is bashing them for starting side business or charging for something other than the Browser. The problem is none of their side project were successful in business terms.
Re: Update on Firefox Send and Firefox Notes
#168Hate to say it, given that I've been using Firefox as my browser since before it was called Firefox, but I think Mozilla is done if they can't find a way to monetize these services. There's just a complete of leadership. I hope there's a non-Mozilla fork of Firefox that keeps it going. A big challenge I know but Google gets all your data once Firefox is dead.
A couple of good options.
Re: Update on Firefox Send and Firefox Notes
#169Looks like Mozilla is becoming VPN company shifting it's previous focus which was on browserware. Mozilla VPN seems to be just rebranded resell of Mullavad VPN with Mozilla Goodies. Mozilla Monitor seems to use https://haveibeenpwned.com/ (also as seen in Firefox desktop) Mozilla Firefox Private Network looks like another Cloudflare Warp's rebrand (with litte good additions maybe?) seeing that it uses Cloudflare . Mo…
I am getting very much downvoted. Any fallacy in my reply? Please tell me so that i can correct it in future
And I dont see any of your comment about diverging into other product market a bad thing at all.
Re: Update on Firefox Send and Firefox Notes
#170Earlier quoted context omitted.
Like it’s a pseudo-public file storage system. If you’re not going to put up the moderation effort and block the spread of malware, cp, phishing attempts, and spam then the people who would get kicked off of, say Dropbox, will migrate to your service and now you’re the company whose links are inherently sketchy. It’s not really a moral panic so much as it’s damaging to Mozilla’s reputation.
You're missing the point. Dropbox isn't E2E encrypted. Send was. The technology is E2E encrypted file transfer via a central server. It doesn't matter whether the response is due to a moral panic or an attempt to protect their reputation. The end result is the same - reduced public availability of while the bad guys generally continue using it the same as before.
Until trust is solved, running and using such a service remains problematic. It needs not be solved via content inspection, though; if I could verify the sender, I won't care about phishing links (and such links would cease to be useful for scammers and disappear). But this is a separate significant undertaking.