Security is a very important issue if we are talking about live conferencing. As Zoom had several security issues like Room Bombing, insecurity of personal data, and encryption policies, Zoom was about to lose its reputation. Immediate actions are taken by the company to cover these security issues which was out of priority as a requirement for a very fast-growing company during — and because of — COVID-19.

Jitsi has JWT implementation to provide security for web conferencing. Basically, Jitsi rooms can be created and/or joined after a successful JWT validation.

Jitsi with JWT is a very smart and simple solution perspective to add enhanced security to your Jitsi installations. But I must say it is not easy to find accurate documentation on that even on the Jitsi Community portal. Now there are few posts about Jitsi with JWT in Jitsi Community forums. But for sake of simplicity, I made this guide sheet to save the trouble that I had to endure.

Since Ubuntu 20.04 Focal Fossa fairly new compared to the previous Ubuntu LTS Bionic Beaver, there are the same differences when installing Jitsi with JWT support. So I decided to share a separate manual for the installation of Jitsi with JWT authentication support for Ubuntu 20.04 LTS.

I am writing this blog with the understanding that the user has already set up his/her server with a domain name. Any popular cloud service will do. I have used the digital ocean for this purpose.

First ssh to your domain name. In my case it is

Next, copy down the below scripts. These scripts will install lu, her dependencies, and prosody with fixes.

After the installation, the server will shut down and you need to ssh again.

After getting back in the server, run the following scripts

Now you need to be attentive before running these scripts. The 2nd part scripts will install Nginx, jitsi-meet, and jitsi-meet tokens. You can use apache instead of Nginx if you like. After installing jitsi-meet, it will ask for your hostname. You need to mention your domain name which is currently hosted live. You need to have app-id and app-secret for jwt. In my case, I used 5 random letters for app-id and since app-secret has to be strong, Simply run

You also need to make sure to install SSL certification as jitsi-meet uses webrtc features. And we need TLS certification (HTTPS) to run webrtc in our browser and server. You can generate your own certification with the 

Now we need a prosody authentication provider to make use of jwt token. You can read more about it 

Include “conf.d/*.cfg.lua” at the end of the line These would configure prosody.

Under your domain config change authentication to “token” and provide application ID, secret, and optionally token lifetime:

To access the data in lib-jitsi-meet you have to enable the prosody module mod_presence_identity in your config.

Enable room name token verification plugin in your MUC component config section:

Open your meet config in /etc/jitsi/meet/<host>-config.js and enable

 /etc/jitsi/jicofo/sip-communicator.properties

And you are set. Now when you hit your domain and create the room, it will ask for authentication. Once authenticated you will be given the role of a moderator

Once you will be assigned as a moderator, you will have the power of control who you want to enter the room by enabling lobby and can mute the participant or ‘s among other things.

You can also play with your hosted jitsi-server like limiting the number of participants. To achieve this:

Edit your /etc/prosody/conf.avail/meet.example.com.cfg.lua file and add muc_max_occupants as a module_enabled in the conference.meet.example.com "muc" section.

Then, add the options below that. You need both muc_max_occupants and muc_access_whitelist defined.

Guide Sheet for Jitsi Setup With JWT Authentication for Secure Video Conferencing in Ubuntu 20.04 LTS

Recently I was working on one project where I need to show a custom view in my Android application. After some digging, I came across libvlc of VLC and mjpeg library. You can find lots of mjpeg library in Github. But what I want to do in my application is not only show custom view but also to save the frames in jpeg format in some directory. That was easily handled using InputStreams.

I also wanted my application to run in the background, i.e, if the app is in the background, images will still be saved in the file directory. Integrating foreground service do the job.

I Created my own Android Library which can do all these things. You just need to import the dependencies. This library is a wrapper library around the 

https://github.com/perthcpe23/android-mjpeg-view 

which is written in Java. My library is written in Kotlin with additional features.

Able to stream video in an android application.

Requires only Http URL to make connection.

Ability to save video frames in images in the directory Mjpeg.

Can save the image in the background(Foreground service integration).

Add Jitpack to your project build.gradle file

Then add this dependency to your app build.gradle file.

Add 2 buttons for startService and stopService

This is pretty much ou have to do to make use of this library. Remember it is open source and everyone is welcome to contribute to this project.

All samples from the article are available in the library repository.

https://github.com/faizkhan12/mjpeg-view-android-kotlin

Android Mjpeg Video streaming in Kotlin as well as saving images in frames.

Android Library that can stream Mjpeg Video and save video frames in images with ForeGround Service(Kotlin)

This article is written as a continuation of this 

hat teaches you how to bundle your nextjs app with Electron so you can share the .exe file without compromising your code.

A little while ago, I was looking for some direction to package my nextjs application to .exe. The goal was simple: share a fully functional desktop application with my clients without exposing the source code. This process proved particularly challenging due to the dynamic and backend-dependent nature of my application, which extensively utilizes Next.js API routes. I came across the article which I mentioned above that exports the static HTML, CSS, to build an output which Electron renders. But this is only useful when you have a static website or you don’t have a backend route in nextjs.

'''BUT, maybe there’s a solution for those problems. NextJS has a possibility to use custom servers (as described

, on official documentation), but it may be more difficult to integrate with Electron in a good way, and also it will make your app more heavy, since it will truly serve your application (it will run a NodeJS server behind the scenes) on your end-user computer, in addition to enable your users to explore your front-end outside your desktop app (for example, NextJS will run on

and your Electron will render that URL on the

, but it allows your users to open a browser — Chrome, Firefox, Edge etc — and access

I was really intrigued by this approach (also I needed to do it or else I would have to spend the majority of my day explaining to clients the number of environments they need to set up to run the code 😪.).

So basically this guide is helpful for those who are using APP route nextJS and need to have a backend functionality work on Desktop Application.

Before continuing, I’m assuming that you have already setup the nextjs application and have bundled electron application. If not, then follow this 

Begin by creating a server.js file at the root of your project. This server will handle both your API routes and serve your static files. Here's how you can set it up:

The code is pretty self-explanatory. You need to have express js, cors and dotenv installed as a dependency.


require(‘dotenv’).config({ path: path.join(__dirname, ‘.env’) })

 will basically takes the secret that you might have in .env file.


There are 2 routes that I have defined in my server file. Whatever routes you might have defined in your nextjs api route, you need to convert it as your express api route because now we will be running out application using custom express js server.

One more point to be mention is that we will be serving our contents from out folder that was created from 

 and will be using the api routes from express js.

Adjust your Electron setup to interact with this server:

 You might still face problem in facing the value from .env. If you dont have any .env secrets then it’s ok but if you want to fetch those values from .env, you can copy the follwoing code to your package.json .


And you are all set. You dont even need to change your frontend . In order to start your electrom application and leveraging the api capability, just followthese steps:

If you want to bundle your application to let’s say .exe, just follow the usual steps, i.e:


And this is it. This is how I was saved from the frustration of my client and able to share the .exe file across the clients and all of its dynamic functionality.

Integrating Electron with Next.js using a custom server approach not only preserved the dynamic functionalities of my application but also streamlined the deployment process. This method proved invaluable, sparing me the tedious explanations often required when setting up multiple environments for client use. Now, sharing a dynamic, fully functional desktop application with clients is as simple as distributing a .exe file.


Hi, I'm Faiz Khan

Welcome! These days, I'm often found jotting down notes about what I'm learning. If you come across anything and have feedback, corrections, or thoughts, I'd love to hear from you.

Guide Sheet for Jitsi Setup With JWT Authentication for Secure Video Conferencing in Ubuntu 20.04 LTS

Android Library that can stream Mjpeg Video and save video frames in images with ForeGround Service(Kotlin)

Learn how to build a desktop application with Electron and Next.js while also adding API route capabilities.