saghul

I haven't used MicroPython in a long time, but it seems to include hmac: https://github.com/micropython/micropython-lib/tree/master/h... right?

> AV1 decoding support through libdav1d

Nice to see progress in the AV1 front!

RN on Android also uses JSC, so no JIT. And, and per the video (https://www.youtube.com/watch?v=zEjqDWqeDdg&feature=youtu.be...) there is no JIT on Hermes either.

As a Fastmail customer and standards enthusiast (been to a couple of IETFs myself) this makes me extremely happy. Kudos for following the standards path in this world of walled gardens.

My mom worked in the neonatology ICU for years, and while every once in a while there was a tragedy which made her very upset, not many bad (and unexpected) things happen these says. It's a very rewarding job, as you help start a life.

Alas this can only be said about the first world. In less developed parts of our world this would be the complete opposite I imagine.

I wonder if this also means ChakraCore would be abandoned. I haven't played with it directly, put it seems to be a very capable JS runtime, which has no home outside of Edge. Well, there is node-chakracore, but I wonder why Microsoft would interested in keeping that effort.

Unless... they replace V8 in their Chromium build with Chakra. They already have a V8 API shim, so I guess that would be within reach.

All Jitsi projects will remain Open Source.

All seems to indicate we'll continue the same path.

It sure is feasible, but it would have to come from the community. If you are interested in trying to move it forward, please join our community: https://community.jitsi.org/ and start a discussion!

Interesting to see this here now :-)

I'm part of the Jitsi team, and made the transition from Atlassian to 8x8. I'm happy to answer questions if any, to the best of my ability / capacity.

Hi there, Jitsi dev here: note that the Jitsi desktop client (the one which supports SIP) is no longer actively developed, it transitioned to being community maintained.

We have been focusing our efforts on Jitsi Meet for past few years: https://jitsi.org/jitsi-meet/

> One valuable property of C that the author didn't hit, C code is easily translatable into assembler in your head. He kind of misses this point with the virtual machine discussion. Yes C code becomes different types of assembly by platform, but you can look at C and have a clear idea of what the assembly will look like.

I've seen this many times, I'll be honest: I can write C, but for the life of me I don't have the slightest clue how the assembly code will look like.

We merged this guide into http://docs.libuv.org/en/v1.x/guide.html which got some updates to match API changes.

I merged it into the official docs, thanks a lot for all your work nsm! <3

This is insanely cool, great project and use of WebRTC!

I see Docker / your container tech of choice as a solution to this. Your server can still run whatever distro, and a specific app can run a different one.

This can be annoying from the sysadmin perspective, since there are now multiple operating systems to take care of, but at the same time, the developer may not be able to produce builds for all distros their users would like.

Ubuntu is a fine choice IMHO, given the above. But yeah, some debs / ppa would be nice.

Jitsi Meet is web (and Electron) and mobile. The (older) Jitsi desktop client is not part of the Meet family per se, it's a multiprotocol IM client.

Thanks for the kind words!

> Can I use jitsi and record audio, separate tracks for each party?

Nope, we don't have that capability, sorry.

FWIW, the app does not depend on any Google Play services, so you could grab the apk from any of those mirrors and manually install it, and if you really want to, you could build it yourself, instructions are here: https://github.com/jitsi/jitsi-meet/blob/master/android/READ...

1) Add our repo, apt-get install jitsi-meet and you're done! We have 0 proprietary bits.

2) That feature requires that you deploy a service of your own to facilitate this. At this time, meet.jit.si provides this for free for 2 minutes, but if you deploy the service to your own infra you'll need to deploy jigasi and configure a VoIP provider yourself.

Cheers!

I assume you talk about the Jitsi desktop client. TBH I don't know. I cannot find it on the UI either, sorry!

Something you can do is use Jitsi Meet (the WebRTC client) and have the monitored device permanently connected to a meeting room (protected by a password if you are using our public infra) and join the call whenever you want to see the other side.

Thanks for sharing! Some of us on the Jitsi team can answer some questions, if any. Ask away!

Lovely blog post. Well written, thorough and clear. Getting people involved in a large project is not an easy feat, and I think this may open the eyes of people not knowing were to start.

Well done!

Very nice article, thanks for sharing! It reminded me of this one, written by my coworker Tyler: https://medium.com/smells-like-team-spirit/teamwork-and-ment...

Technically correct, but Node tends to err on the safe side, specially when dependencies are bumped, as is the case. In this release both libuv and npm were updated.

The problem is with CPU intensive tasks. Being as expressive as Python is, it would be nice if CPU intensive algorithms could be written in it, without blocking all other Python threads while the algorithm runs. For example.

I'm not the author, but I don't think anyone here pretended that it's a "professional grade product". From the actual README: "Workq is in alpha status and not yet stable."

Agreed. I use https://readthedocs.org to take care of building and hosting documentation, and it's really handy.

I live in Amsterdam and indeed I see them all the time. They are all white, however vs many other Teslas people have so I see no problem there.

Moreover, in many countries taxis have a specific colour, and I personally never liked white for my own car because it would look like a taxi :-)

Thanks everyone for sharing your experiences! I used to joke this kind of spam no longer existed, now I know.

As Murphy's law would have had it, got my first spam SMS after posting this. THEY ARE WATCHING US.