Caelish

In between e10s, Servo, and the new developer theme in the current Nightly, I feel like Firefox is finally starting to become more competitive to other browsers again. I switched to Chrome because it seemed like Firefox was becoming more and more dated in comparison, both in terms of technology and UI. I still have some gripes with Firefox at the moment, but I'm beginning to seriously consider switching back.

This is obviously anecdotal, but both e10s and the Nightly in general have been remarkably stable during the time I've tested them.

Yeah, I'm at that weird spot where I need to do bulk actions often enough to be bothered by losing them, but not often enough to justify figuring the API out. Appreciate the reply though, definitely glad it's being looked at :)

I suppose so, yes; I very often use the dashboard specifically to do that.

I think part of it is just that I'm not used to the new one yet - it takes time to find options which I could previously find more easily - but at the same time, if I want to put a bunch of sites into development mode to name one example, I now need to individually go into each specific domain's page, click the "caching" nav icon, and change it there. I feel like it essentially takes a single page two-click mechanism and changes it to a three-click mechanism across multiple pages that forces me to think about where I'm going much more than previously.

Does anyone else feel like this is a downgrade in terms of actual usability? I might just not be used to it yet, but I'm finding it takes a lot more clicks to get things done on the new dashboard. The dock of apps seems cluttered to me. Maybe it'll grow on me, but I'm not a huge fan of it at the moment.

Since there's not a lot of images of the full dashboard page in the article, I made two quick additional screenshots to compare the two. [1]

[1] https://imgur.com/a/bnx8j

The implication in the article seems to be it's a GET/POST flood though, not DNS-based. Granted, for DNS amplification, having big enough pipes starts to matter a lot more, which is where providers like OVH shine because of how much network capacity they have, but it's not like DNS traffic can't be filtered. I haven't read the research papers you're referring to though, so I may be overlooking something obvious.

Depends on the attack and how sophisticated it is. For most layer 7 attacks like this one, you can filter e.g. specific user agents or protocols. One thing that often works (but has some false positives with simpler search engines) is dropping all HTTP/1.0 traffic, because any remotely modern browser uses HTTP/1.1. Essentially you block anything that's unusual, like specific user agents (reflected attacks from user agents containing 'Wordpress' and 'PHP' come to mind a lot especially), HTTP headers, and so forth. Ideally as far upstream as possible, but it can be done on the server level as long as you have enough horsepower to throw at iptables or the web server, and your connection doesn't get saturated. The right IP blacklists can help a lot as well.

I actually sent an email offering to help (I have a lot of experience mitigating DDoS attacks) but never received a reply. I imagine they must already have something in the works to resolve this.