Please don't read too much into this ;)
We moved from self-hosted Discourse to hosted Discourse.
The transfer was initiated late from the Mozilla side (my bad) and the automatic system from Discourse kicked in.
With all other recent news from Mozilla (large scale firings, multiple leadership changes, the new ToS and removal of the promise to never sell our data...), I won't read too much into it but simply add it to the list.
Is there any chance to move away from the Discourse? It's a bit too slow (on any page opening), but the biggest issue is its hostile habit of catching the browser "find in page" hotkey (replacing the local find with the remote site search).
I hate that feature with an intensity that's hard to describe.
I know you can press it again or something but for the love of $deity don't fuck with the defaults.
That said I'm equally angry my browser so happily allows this.
Sure if it's a proper web application like OnShape then sure, override default key bindings, but ask me first and remember my choice. If I say no then just don't feed those keystrokes to the webpage.
This. Just this. I'd say websites should be able to "offer" their own search, so when you do find-in-page it shows the default search with a button to "change to custom website search ([ ] remember)" or so.
While I do understand the frustration, I think the "find in page" hotkey isn't a big enough reason to change the platform. Myself, I am happy with the performances.
By the way, what would you replace it with?
Given Mozilla's continual frittering away of cash, would it not show some constraint to not pay for "cloud" hosted stuff for things that could easily be hosted by Mozilla and probably for less (with a less absurd choice of software) - it's already pretty much game over anyway, as a long time defender of Mozilla it is impossible these days to argue.
Please tell guys who is responsible for js engine to fix handling of large cookies that google is using to slow down youtube on firefox. It is impossible to watch youtube logged in because of that. God bless you sir.
In general, we quickly act on obvious bugs/regressions on major websites.
Often, such major issues on big websites are caused by certain add-ons or antivirus software.
Would you have more details to share? I don't experience such issues on github.
Clue: do you have some unusual addons which could change the behavior of Firefox?
Ahhh I wasn't familiar with this package in particular. I just have had a bunch of ... weird issues dues to some quirks in some packaged browsers. Basically it was never a standard install, and it sucked for ironing out issues. Glad to hear the Debian packages are doing great, not surprised either!
As you can see, these patches do not impact the quality of Rustc itself. Some could be forwarded upstream (it is a pain for packagers to maintain patches - so, we do have strong incentives to contribute upstream).
