Mozilla engineers explain web technologies and Firefox internals, including WebAssembly, CSS engines, and rendering.
Commenters recommend it as the technical feed to follow, with detailed explanations of problems and solutions, unlike the press-release-heavy Mozilla blog.
Mozilla Hacks [0] is pretty much the only feed that makes sense recommending here. There's a lot of very detailed explanations for technical problems and their solution in there, which I find pretty interesting.
Otherwise, though, less so a specific feed and more a general idea what to put in there: YouTube channels.
There's a few channels which I follow, but I don't particularly fancy visiting youtube.com for it, and neither do I particularly fancy having a Google-account.
But YouTube offers RSS feeds for pretty much every channel, which solves both problems. Also has the added advantage of all the features that your RSS reader offers, particularly being able to filter out any video series that you don't care about has been incredibly useful to me.
If you want to migrate your subscriptions to RSS, there's also a button in YouTube to export all of them to an OPML-file, which you can then import into your RSS reader (if it supports import). Assuming Google hasn't changed the design of YouTube since last time visited, this button should be at the bottom of the "Manage Subscriptions"-page.
As for RSS reader recommendation, on desktop I use QuiteRSS [1], mainly because it's the most feature-rich RSS reader that I've found so far.
On Android, SpaRSS [2] is my preferred reader, with my main-criteria being that it supports at least filtering and OPML-import, is preferably FOSS, and plays nicely with my YouTube-usage (I use it together with NewPipe [3]).
[0]:…
> did you evaluate various information sources (Ghostery, etc.) before settling on Disconnect?
Monica Chew, the engineer who did the bulk of the work on this feature, did consider a number of available lists before settling on this one. The Disconnect list was the best freely-licensed (GPL) one at the time. Also, they now have a web form to let users suggest new trackers to block (https://disconnect.me/trackerprotection) so it should get even better.
> Does anyone understand why Mozilla publishes valuable information like this over random personal blogs, rather than a central place like a knowledge base (e.g., a wiki)?
It's pretty tricky to share information in the "right place" because of the amount of information produced by everyone at Mozilla. Someone's preferred channel is often another person's blind spot.
In this particular example, all of the information is on the wiki page I maintain (https://wiki.mozilla.org/Security/Tracking_protection) but it felt like a more accessible description of the overall system would also be useful. I put it on my blog because it seemed too detailed/technical for my team's blog (https://blog.mozilla.org/security/) or Hacks (https://hacks.mozilla.org/).
> It's worth making it explicit that many home computing tasks are highly parrallelizable because the work is actually completely separate programs.
That's a great point. At any point in time there are already dozens of processes running, of which only a fraction are tied to a GUI. Even GUI apps are currently resorting to launching multiple processes. For example, Firefox announced last year their new site isolation security architecture where they load each site as an independent process.
https://hacks.mozilla.org/2021/05/introducing-firefox-new-site-isolation-security-architecture/
Also, here's a link to a recent HN discussion on Firefox's recent announcement.
https://news.ycombinator.com/item?id=31355857
There is a way to sandbox native code without forking to a new process, and it looks like this
https://hacks.mozilla.org/2020/02/securing-firefox-with-webassembly/
Firefox employs processes for sandboxing but for small components they are not worth the overhead. For those they employed this curious idea: first compile the potentially unsafe code to wasm (any other VM would work), then compile the wasm code to C (using the wasm2c tool). Then use this new C source normally in your program.
All UB in the original code becomes logical bugs in the wasm, that can output incorrect values but not corrupt memory or do things that UB can do. Firefox does this to encapsulate C code, but it can be done with Rust too
From: https://hacks.mozilla.org/2022/03/mozilla-and-open-web-docs-working-together-on-mdn/
> Any revenue generated by MDN Plus will stay within Mozilla. Mozilla is looking into ways to reinvest some of these additional funds into open source projects contributing to MDN but it is still in early stages.
> A subscription to MDN Plus gives paying subscribers extra MDN features provided by Mozilla while a donation to Open Web Docs goes to funding writers creating content on MDN Web Docs, and potentially elsewhere.
It's not totally clear to me after a little research, but I think MDN is part of the corporation, not the foundation? (It's isn't listed as on the foundation website as one of their projects.
Nice. Did you use inolen/quakejs as a base, or new fork? Are you using WebRTC? Have you heard of HumbleNet? They also had a Q3 forked: https://hacks.mozilla.org/2017/06/introducing-humblenet-a-cross-platform-networking-library-that-works-in-the-browser/
For the curious, FTEQW has an emscripten port as well, and FTEQW allows you to play Q1, Q2 and most Q3 maps: https://github.com/fte-team/fteqw/blob/1f9f3635f0aef3b2eed6b40e35fcf6223c6ad533/engine/web/ftejslib.js#L13
Also, the LvL LiveView is a great way to check Q3 maps in your browser: https://q3js.lvlworld.com/play/2043/media/633a9623b1b6458735cad3d559a79fe6/8a69481c4e2215db479fe9a087c3d6f5?map%20phantq3dm1_rev
What a time to be alive. :)