rockdoe

10 ms·

61.
by rockdoe 5y ago
It would have made no difference: the hang was in the networking code & process, not the telemetry code (and whatever process that is in). Anything that sent a message with the "bad" header type would have provoked the hang.
62.
by rockdoe 5y ago
>That's my cynical, entirely pessimistic outlook of it all anyway. Yes. I read the announcement totally different. They're keeping blocking webRequest because there's no other way to make good adblockers, and it will stay
63.
by rockdoe 5y ago
Couldn't it spin up another one from the old version by doing execve("/proc/self/exe", ...)? 99% of the Firefox code is in libxul.so, so you'd need to get the file handles from the original process or so
64.
by rockdoe 5y ago
I use it under KDE. Or are you on Wayland?
65.
by rockdoe 5y ago
For one the policies are quite different: non-open source channels need to be secret. This isn't a requirement on freenode.
66.
by rockdoe 5y ago
Talking about Matrix...matrix.org had an IRC bridge to the Freenode network. Is there any up for libera.chat? (The bridge is unreliable, but still very handy to stay connected to old friends)
67.
by rockdoe 5y ago
two libraries isn't substantial I've already disproven this assertion by pointing out those exact libraries are real life exploit vectors instead of theoretical weaknesses that most of the rest of the page talks about. Repeati
68.
by rockdoe 5y ago
This analysis assumes the camera was aligned perfectly parallel to the finish line, but offset from it. Unfortunately, there's no reason to assume this was true. Almost the opposite! If the operator did set up the camera correctly init
69.
by rockdoe 5y ago
Those Chrome CVEs are for single-digit version numbers from 10 years ago. Not that this has any actual relevance to the argument (which is that media decoding is a huge risk vector for browsers, and the kind of thing a threat model looks
70.
by rockdoe 5y ago
Would be interested to see threat models alongside these analyses. This is the key question. Nowhere is this more clear than in the final remark: Firefox also uses RLBox but this is only used to sandbox two libraries (Graphite and Ogg) w
71.
by rockdoe 5y ago
Welp, Twitter says Apple was using a 2003-era fork of this code.
72.
by rockdoe 5y ago
Netscape Portable Runtime (NSPR).
73.
by rockdoe 5y ago
Given that it's Apple hardware it wouldn't surprise me if it's doing some kind of authentication to check if it's a legit peripheral :-)
74.
by rockdoe 5y ago
Yes. "Netscape Security Services" (NSS) is one of the Mozilla libraries that's (somewhat) widely used by other software, and would be a candidate, but I've never heard about Apple using it.
75.
by rockdoe 5y ago
"Mozilla spokeswoman Ellen Canale said the company has no knowledge of any bug that was connected to the exploit." Firefox OS phones didn't have Lightning ports, so it's not clear what code from Mozilla Apple would be us
76.
by rockdoe 5y ago
To me this puts v2 in the same category as MIT/X11 and BSD: archaic licenses that no one should ever use except for the most trivial of projects. Isn't BSD widely accepted to have an implicit patent license? e.g.: https:/&
77.
by rockdoe 6y ago
Meanwhile, support for monitoring their Zen CPUs was backed out of the kernel in December because the interface is undocumented and buggy, and AMD isn't helping. AMD is a Big Company, could go either very right or very wrong.
78.
by rockdoe 6y ago
Yeah, but how do you assign a weighting here if you don't have the telemetry? Maybe Firefox usage is really like 25% power users, but most of those disable Telemetry, causing the priorities to be all screwed up (See the ALSA example!).
79.
by rockdoe 6y ago
2.5%-3% of the Linux users, not of the total ones. From https://data.firefox.com/dashboard/hardware Linux users are about 3% of the userbase, so that's 0.1% of total users.
80.
by rockdoe 6y ago
I think it's quite reasonable to suggest power users to use such a specific version. Especially as the signing is presumably to prevent non-power users from getting malicious ones, which is a real problem. As you admit, the Developer e
81.
by rockdoe 6y ago
If we do a field test of browser usage, do we expect the result to leave anything standing that allows typical power user workflows such as HN readers to work?
82.
by rockdoe 6y ago
Reminds me of this: https://chuttenblog.wordpress.com/2020/11/05/data-science-is... tl;dr Telemetry indicates ALSA is no longer used. Firefox removes ALSA. Said Firefox version reaches release. Audio complete
83.
by rockdoe 6y ago
if you use the well hidden unbranded builds available in no repos it's possible too This is a very weak argument given that it works in the Developer version.
84.
by rockdoe 6y ago
That seems to be why the experiment outlined is so valuable. It would default both options and look at cross-switching. A/B testing UX, basically?
85.
by rockdoe 6y ago
True. I found the other discussion: https://bugzilla.mozilla.org/show_bug.cgi?id=1698244#c1 Which says that the current Telemetry is not usable (and talks about the defaulting on).
86.
by rockdoe 6y ago
It seems like it's just FUD. According to the bug tracker the plan is to run an experiment (including defaulting Compact mode) and see which combinations are actually retained by users: https://bugzilla.mozilla.org/show
87.
by rockdoe 6y ago
I'm not telling the author to read the article, I'm telling them to read the actual rules which anticipated this trivial attempt to be clever. Per HN guidelines [1], it would have been better to do that than to post a shallow di
88.
by rockdoe 6y ago
The plugin license didn't allow hooking/injecting into the program to modify the behavior outside of the provided APIs. The reasons are pretty simple: those kind of plugins would break and cause crashes when the internals of the p
89.
by rockdoe 6y ago
The ideal AI compressor would encompass all human knowledge. That's what they're doing (in the constraints of defining all human knowledge ~ English Wikipedia). More refined models of representing all of our knowledge will beat
90.
by rockdoe 6y ago
Just read the rules. The size of the decompressor is included in the total size of the compressed data.

More ›