Live data from Hacker News

DownThemAll (2019)

addons.mozilla.org

101–110 of 133 posts

Re: DownThemAll (2019)

#101
post #11

Earlier quoted context omitted.

Maybe have a look at these: https://addons.mozilla.org/de/firefox/addon/aria2-integratio... https://addons.mozilla.org/de/firefox/addon/ff2mpv/

Thanks. The first one seems to rely on the fact that aria2 can be remotely controlled. This is good, and in case of aria2 may be even the preferred way of using the combo, but it's not the substitute for the basic launching of one program from the other with some data passing. The second one needs the "native client" which I mentioned above. It uses effing python to pass the link from the browser to the player! It's…

(I'm the author of ff2mpv.)

Yeah, it's unfortunate that it needs the Python (or Ruby) script as a shim to MPV. But it's not an inherent requirement: the extension could execute MPV directly if MPV understood the weird length-prefixed JSON protocol that Firefox and Chrome use.

Re: DownThemAll (2019)

#102
post #40

Wow. Didn't expect this :) I was the author of this tiny extension back in the days (extension #201, I still remember it) together with a friend who recently passed away, Federico Parodi. We hacked the first version when we still didn't know much about JS, but it immediately exploded (500k daily users). Donations were super helpful at that time, being 22 years old with a newborn. After a couple of years (iirc) Nils M…

> Thanks for making my day! :)

No, thank YOU for building and maintaining DTA for all of us, even after the webext framework overhaul! Been a happy user since the old days.

Re: DownThemAll (2019)

#103
I was a very happy user of DownThemAll at work for a few years. I had to retrieve boatloads of documents from $BIGCO's godawful Sharepoint site on the regular. After a couple sessions wearing out my carpal tunnel mousing around, right clicking on icons, and going through the File Save dialog hundreds of times, I knew there had to be a better way. DownThemAll was that better way. Thank you for your work.

Re: DownThemAll (2019)

#104

Earlier quoted context omitted.

Yeah, I don't see how the maintainers can patch security vulns or add support for newer web features (e.g. CSS variables) when the upstream fork is no longer maintained. They would have to write the fixes themselves, which just does not scale for a project that has 1 or 2 developers working on it part-time.

I think we're at a point where there are enough sites out there that we can avoid a good portion of them (i.e. ones written without progressive enhancement in mind) and still be happy. For example, I am quite happy with visiting only sites which do not require JavaScript, do not use cookie banners, paywalls, and registration prompts. For my purposes of browsing Teddit, HN, and my own websites, there are more than 20…

I understand. But I think as the years go by, you may have fewer and fewer sites that meet your criteria. I hope I’m wrong.

Re: DownThemAll (2019)

#105

It's a nice extension, and there was a time when I used it frequently, but the thing is - it should be completely unnecessary. I already have software which downloads anything I want fast, the issue is, I can't simply connect it to Firefox anymore. Same goes to using external players to view media (I need more nuanced control over rate and pitch of the playback). I understand it's done in the name of security, but I…

You can use Firefox Developer Edition and make your own addon. It isn't exactly straightforward, especially the "communicate with external software" part (e.g. in Windows you need to put some entry in the registry to let Firefox know what program you need to communicate with) and communication has to be via JSON which in practice means you need to write some sort of proxy app. But it is possible. I have made my own l…

Any specific reason to use FF dev edition? You can use your own addon with regular FF by signing it with web-ext CLI tool.

Re: DownThemAll (2019)

#106
post #28

Earlier quoted context omitted.

Meanwhile, Youtube-DL is continuously being updated, because they have to work around obstacles raised by Google to prevent automatic downloading.

Actually, youtube-dl is dead at the moment for reasons of private life of the maintainer. So people now use a fork called yt-dlp. Which is ironic, because most people moved when google started to use a new harsh speed-limitation.

Does yt-dlp fix the speed limitation problems?

Re: DownThemAll (2019)

#107

Earlier quoted context omitted.

I just want to point out that you casually dismissed "a few hundred thousand" users whose lives were impacted as a non-issue. This is exactly the type of attitude which gives software dev such a bad rap. I personally support every single user of my products and never force a new version on them.

> casually dismissed "a few hundred thousand" users whose lives were impacted as a non-issue. I did not intend that. My intention is this: "the cost of maintaining a browser with up-to-date standards and security is enormous". A few hundred thousand users who are unlikely to pay anything for such a browser is just financially not viable.

Just to put into perspective, maintaining a full browser (with its own engine etc) costs at minimum $300M/year (judging by the size of Chrome/Firefox/Safari's teams). That means that 300k users would need to pay more than $80 a MONTH to make that sustainable. That's insane.

Re: DownThemAll (2019)

#108
post #40

Wow. Didn't expect this :) I was the author of this tiny extension back in the days (extension #201, I still remember it) together with a friend who recently passed away, Federico Parodi. We hacked the first version when we still didn't know much about JS, but it immediately exploded (500k daily users). Donations were super helpful at that time, being 22 years old with a newborn. After a couple of years (iirc) Nils M…

Your extension is one of the only reasons I keep Firefox installed, thank you.

Re: DownThemAll (2019)

#109
post #84

Earlier quoted context omitted.

Mozilla’s self-sabotaging actions made it seem to me that it was Google’s money talking. That it was a Google funded plan to kill everything that made Firefox great. Really enjoyed Firefox’s heydays and DTA. You guys were a part of saving the internet from IE.

I don't know where this conspiracy theory keeps coming from, but as someone who was there it's definitely untrue. Apply Hanlon's razor. If Googlers could mind-control Mozilla employees, they wouldn't be sabotaging the browser. They'd be getting Mozilla developers to rubber-stamp their W3C proposals so they could look good on performance reviews.

I agree, it's untrue. In my opinion, most of the problems Firefox has stem from mismanagement and utter lack of vision.

This has a lot to do with mozilla losing their leaders and rock star devs at a rapid pace in the last 10 years. Some golden-parachuted out to the FAANGs, others just shrugged seeing the Mitchell Baker Club got more and more influential in a bad way and looked for less toxic places to work, and of course Eich prominently got cancelled for being against gay marriage and his departure rippled through the entire community. I was subscribed to planet.mozilla and there was a constant stream of "it's been fun, I am moving on" blog posts by names I immediately recognized.

The Code of Conduct situation caused a minor exodus especially in the volunteer community, especially outside of the US. A lot of rather important people, who were the ones building the local communities, just had enough with mozilla corp leadership unilaterally pushing stuff on them without soliciting any feedback first. mozilla was supposed to be this community of equals and Corp dictating more and more things really did not sit well with a lot of folks. Some outright (and sometimes rather publicly) left, others just dialed back their volunteer time a lot. This left especially the Western European communities in shambles.

The WebExtensions switch caused a lot of extension developers (who often were also volunteering in different areas of mozilla) to move on.

The loss of extensions, themes and customization options made a lot of the power users very unhappy. And those power users were exactly the kind of people who kept telling friends and family to use Firefox, driving Firefox adoption. While they often kept using Firefox themselves, they also quite often stopped advocating for Firefox in their circles.

All of this put together, mozilla losing leadership, volunteer, power user and dev mindshare at such a rapid pace then translated directly into a loss of market share.

Major failures such as FirefoxOS and BrowserID furthermore have been very demoralizing, making mozilla leaders very cautious, to the point where you had very little innovation going on from the top down. These failed projects - especially FirefoxOS - furthermore took away a lot of developers from the core product, leaving Firefox in a place where for years they had to play catch up with Chrome.

Things like Rust and servo where went more of a bottom-up direction, with bright engineers pushing it, not so much the leadership. And then these things were the first ones on the cutting block last year.

Google only "helped" in so far that they kept mozilla busy playing catch up, making the situation worse by a ton of (experimental) features and new specs that Firefox then had to implement, thus taking developers from other areas that needed improvement. I think most of the time it wasn't Google's intention to fuck with mozilla tho, it just happened to be the outcome.

Re: DownThemAll (2019)

#110

Earlier quoted context omitted.

> casually dismissed "a few hundred thousand" users whose lives were impacted as a non-issue. I did not intend that. My intention is this: "the cost of maintaining a browser with up-to-date standards and security is enormous". A few hundred thousand users who are unlikely to pay anything for such a browser is just financially not viable.

Just to put into perspective, maintaining a full browser (with its own engine etc) costs at minimum $300M/year (judging by the size of Chrome/Firefox/Safari's teams). That means that 300k users would need to pay more than $80 a MONTH to make that sustainable. That's insane.

Two things:

- that would go from my tool budget paid by work as soon as it is better since my browser is my second most important tool.

- as mentioned above I propose starting with a soft fork, as set of patches to be applied to the latest Firefox

Post reply on HN