padenot

12 ms·

61.
by padenot 7y ago
Yes, we (the media team at Mozilla) know about this, and we're having a look. The algorithm we use it not the best (and I think it's not the only cause of bad quality here), and we're investigating what to do. https:/&#
62.
by padenot 7y ago
We do exactly this for people who want. A reasonably stable build (including full testing, and benchmarking, which takes multiple hundreds hours, parallelized of course) is available twice a day (0:00 and 12:00 UTC). It self updates (either
63.
by padenot 7y ago
Yes, but mitigations have been in place for some time now.
64.
by padenot 8y ago
It is, however it's not enabled by default for now. It will be in a few releases after we figure about a couple issues with the build system.
65.
by padenot 9y ago
Because the first example that uses holyjit is an implementation [1] of the brainfuck [0] language. [0]: https://en.wikipedia.org/wiki/Brainfuck [1]: https://github.com/nbp/holyjit/blob/m
66.
by padenot 9y ago
They certainly can, I don't know if they do in practice. It always work for me, so I haven't investigated too much.
67.
by padenot 9y ago
Those services are for the initial peer discovery and SDP exchange, which can be done by other means (using any other side-channel). Ongoing work is happening, for example by the webtorrent folks, to remove this constraint.
68.
by padenot 9y ago
WebRTC solves all the issues you're mentioning, and is available in Chrome and Firefox (in some for in Edge, and soon in Safari). Three examples of this, implemented and working: - https://www.sharedrop.io/ - https:&#
69.
by padenot 9y ago
Yes, up to 32768, per spec [0]. It's just that Safari does not implement this part of the spec, which has changed in early 2015 to allow for longer FFTs [1]. [0]: https://webaudio.github.io/web-audio-api/#dom-analy
70.
by padenot 9y ago
> Problem is only Chrome allows tuning FFT precision now. This is plain wrong. Source: I maintain the Web Audio API in Firefox.
71.
by padenot 9y ago
The first one seems like a good job for the Web Audio API.
72.
by padenot 9y ago
Firefox audio developer here. I haven't heard from the folks doing this, and I would have been the person doing the code reviews so I suppose it's left untouched. Edit: looking at the code, it will work just fine, and that means I
73.
by padenot 10y ago
1. No, it's the one thing that has to be on the main thread per spec. 2. It's true for all browsers. ScriptProcessor runs on the main thread and can be glitchier in Firefox (but depending on the use case it can be the opposite). S
74.
by padenot 10y ago
An `AudioContext` (which is the object that lets you do non-trivial audio in the browser) does most of its work on a special, high priority thread, off an audio callback. Having `AudioContext` in a worker does not get you a lot. It's p
75.
by padenot 11y ago
Texture upload to an onboard GPU are faster, iirc.
76.
by padenot 11y ago
We are also doing a spec so that it works in all browsers: https://mediasession.spec.whatwg.org/
77.
by padenot 11y ago
The mayor or Paris and her council are thinking of doing more of days like this one, and to extend the perimeter to include the entirety of Paris. https://twitter.com/Anne_Hidalgo/status/648850877189627904 - very
78.
by padenot 11y ago
We've since switched to another system, bugzilla was apparently a bit hard to use for non-technical people, and the new tool has better workflow management features.
79.
by padenot 11y ago
Probaby MSE.
80.
by padenot 11y ago
This is Mozilla jargon. Anything that is tracked in Bugzilla is a "bug". I've opened bug in Bugzilla to change the chair at my desk, for example (I work at Mozilla).
81.
by padenot 11y ago
You want to make ASAN builds (simply build with clang or gcc > 4.8 with -fsanitize=address on the command line). Then you can break in a debugger, and do some tricks, explained in this page: https://code.google.com/p&#x2F
82.
by padenot 11y ago
Yeah we're fixing this as we speak (I work on Web Audio API at Mozilla), it should work fine in Nightly in a couple weeks, worst case.
83.
by padenot 12y ago
(Firefox Web audio developer here) It's because, we've not optimised our implementation _at all_ (I'm exaggerating a bit but you get the idea). That said now that Firefox's implementation is in good shape in terms of spe
84.
by padenot 12y ago
Yep, we have plans to improve the noise and echo cancellation. It kind of works at the moment, but should be much better. Also the quality is not uniform across the platform, which is another thing we want to fix.
85.
by padenot 12y ago
That's because it uses WebGL and not Canvas2D.
86.
Let’s Encrypt: One More Step on the Road to TLS Everywhere(andreasgal.com)
2 points by padenot 12y ago|0 comments
87.
by padenot 12y ago
Basically, anything. Have a look at http://www.whatcanidoformozilla.org to have a glimpse on what you can do for the project.
88.
by padenot 12y ago
Multithreading in js has been available for a while using Web Workers [1]. They are available in most major browser (including recent IE). [1]: https://developer.mozilla.org/en/docs/Web/Guide/Performance&
89.
by padenot 12y ago
You can use {call,cache}grind for that, but sometimes it's a bit unpractical if the software is big. An approach I sometimes use is to throw a generic profiler at the program, make the program do something that is not fast enough (and
90.
by padenot 12y ago
So, this is known, and tracked in our bug tracker [1]. In the meantime, you can ask your users to use the drop-down in the doorhanger (the little panel that come down), they can whitelist your site this way (it says: "always share with

More ›