Explore Projects

Enhance interactive web canvas components for image inpainting, audio streaming, and low-latency token streaming.

Zulip's frontend makes heavy use of Bootstrap 2. In this project, my goal will be to remove it. I will also work on improving the shared components used in the codebase. Along with this, I will work on improving the integrations and fixing other subtle bugs present in the web app

As Zulip plans to refine the settings system using the User Groups based permission model, there is a requirement to update the settings interface for User Group settings to align with the current plan, and the addition of new settings related to user groups is more straightforward. In this project, one of my goals would be to enhance and improve the complete User Group settings overlay so that it looks more like stream settings so that working with settings on user groups becomes smoother. Apart from the above migration, another goal would be to actively contribute towards the migrations of settings systems to the user group-based permission model by actively collaborating on the major issues regarding this. This would require working on a lot of areas description of which is included in relevant issue threads and the proposal. Having contributed majorly towards settings-related areas, I'll also try to contribute to areas like message viewing, markdown, etc., and will try to resolve critical issues related to those.

<p>Most containers currently have a hard-coded default seccomp profile, that is pretty loose and meant to support a wide range of use-cases. The idea of this project is to build a tool that would watch all of the syscalls made within a container, and generate a seccomp profile for this specific container to further harden security. We would want to add a command to the Pod Manager (Podman) tool to basically launch the container and then collect a set of syscalls either through strace, or auditing, or similar tracing technologies.</p>

The Jitsi Meet Log Analyzer project aims to analyze log files created for different components of Jitsi Meet and develop tools that enable interactive search, filtering, scheduling and event processing. Utilizing Grafana Loki for log management and Open Telemetry for sending log data to Grafana Loki, the project aims to improve log analysing and system optimization. With Docker making deployment easier, the project searches, filters and makes logs easier to analyze for each Jitsi Meet component.

This project proposes a short-lived, cryptographically signed QR code on the Rocket.Chat's web client login screen, which authenticated mobile app users can scan to log in to the web client instantly—eliminating the need for manual credential entry. By leveraging ephemeral tokens that refresh every 60 seconds and real-time notifications over WebSocket, the approach safeguards user sessions while streamlining the login experience. Specifically, the solution integrates secure token generation and validation in Node.js, a React-based desktop UI displaying the QR code, and a React Native-based scanner accessible only to authenticated mobile users. This modern, frictionless authentication method enhances both usability and security within the Rocket.Chat ecosystem.

-Project Description The current Botpress Connector allows users to easily connect a bot to a Rocket.Chat instance without any coding necessary. But the current design is limited to a single bot operating on direct channels. This decision was made due to privacy concerns of bots answering with sensitive data. This project aims to improve the functionality and usability without compromising privacy. This project consists of allowing multiple bots to be connected and operating on various use cases (channels, omnichannels and direct). It also aims to improve the UI by correctly rendering rich components (bots with interactive graphical capabilities). By developing these features we can not only focus on extending the Botpress Connector, but also on making these extensions a good foundation for other bot connectors -Deliverables Multiple bots can be configured with the Botpress Connector The Connector can inform which channels the bot is responding to The bot can answer on omnichannel, channels and direct When handling sensitive data, bots will respond with a direct message Rich components correctly render for the agent

<p>This is a full-stack project that aims to fix high priority bugs, extend features, and improve the overall experience in the following domains:</p> <ul> <li>Push notifications and mobile features that require server-side changes</li> <li>Zulip web application on mobile browsers especially Chrome and Safari</li> <li>Inline previews and markdown support in web and mobile applications</li> </ul>

<p>coala as a linting and code fixing tool can be far more useful when its power can be directly leveraged from within the code editor. Since all the major IDE's and code editors are now starting to support the standard Microsoft Language Server protocol it is now possible to expose coala's capabilities via the one said protocol and support a wide range of code editors. This proposal outlines the project where I intend to build one such server loosely based upon the proof of concept implementation built for vs-code. It should see noticeable performance improvements, feature upgrades to support actions such as didChange, didSave etc, customization of bears from within the LSP, support for all languages coala supports and be a fully standards confirming general language server.</p>

The zulip/zulip repository currently tracks thousands of open issues, out of which many are labeled “high priority”; these issues are usually new features or enhancements that should be prioritized. I am proposing a large (360 hours; 12 week) proposal to work on some of these issues related to the following areas that I have experience in from my initial contributions: - Streams - Settings UI - Notification messages I have listed these issues with my brief assessment and implementation plan where possible. When actual work starts, I expect iterative improvements to these plans. Note that I've excluded tests and documentation from my planning below, but those will also need to be added, wherever needed. While working on these, I will also try to find areas where worthwhile performance improvements can be made.

<p>A MPD module is to be developed as a control module inside VLC. It should handle requests from any mpc-client. Implementation of MPC Protocol and features, based on a client-server architecture. Linking the module to the media library to play media files on systems connected to the server.</p>

<p>Enabling Rocket.Chat server administrator to use a NextCloud/ownCloud instance for storage of upload. Integrate NextCloud/ownCloud to Rocket.Chat and within Rocket.Chat client user interface to allow access to the contents of a user’s NextCloud/ownCloud instance.</p>

<p>Rocket.Chat has currently some Javascript clients, including Meteor and React Native. Although some of these clients have their own library to abstract and unify REST and WebSocket calls, the main goal of the project is to implement an SDK that can be used on any Javascript client providing lots of benefits for the community and developers who wants to use the Rocket.Chat API.</p>

Embedded Chat provides enough features to be integrated into various web applications as an in-chat app, but its current UI lacks personalization and configurability. This proposal focuses on enhancing the UI by making components modular, providing pre-built themes, and allowing users to modify the UI using a layout editor. It also aims to improve security via HTTP-only cookie-based authentication and enhance configuration capabilities by making the instance configurable through RC-app.

The lib-jitsi-meet library a core component of the Jitsi ecosystem, facilitates signaling and media negotiation in Jitsi Meet. While some parts of the library have been migrated to TypeScript, a significant portion remains in JavaScript, leading to inconsistencies in type definitions and maintainability challenges and increased risk of runtime issues. This project aims to fully migrate lib-jitsi-meet to TypeScript, enhance the existing typedoc-generated documentation, ensuring a well-typed, and maintainable codebase that enhances both developer productivity and the reliability of the Jitsi Ecosystem

This proposal aims to enhance Rocket.Chat’s administrative capabilities by enabling an optional override system that allows administrators to manage private teams and channels without being members. It includes configurable admin settings, permission override logic, audit logging, and user notifications to balance administrative control with user privacy. Core features include adding/removing users, modifying roles, and managing private team channels directly from the admin panel. Deliverables include backend permission logic updates, admin panel UI components, audit log infrastructure, notification settings, and full technical documentation.

Rocket.Chat relies on Agenda to schedule and run critical background jobs, but administrators have no way to monitor or manage them without directly querying MongoDB. This project will build a dedicated Agenda Jobs Admin Page inside the Rocket.Chat admin panel, giving administrators full visibility and control over background jobs. The implementation will deliver a service layer deriving job status from existing Agenda metadata, six REST API endpoints, and a React admin UI built with Fuselage showing job status, execution history, failure details, and one-click actions to trigger, disable, or enable jobs.

Currently Jitsi uses traditional Picture in Picture in Electron application. Browser meetings support is not yet implemented. This idea proposes to implement Document Picture in Picture for browser meetings for supported browsers and traditional Picture in Picture otherwise. Document Picture in Picture mode allows to embed arbitrary HTML contents. The idea will be to use React's portal to create interactions buttons inside the Document PiP window that will share the redux state change. Interactions such as audio/video toggle, chat window will be added. Apart from that, different layouts such as compact, gallery, speaker will also be available inside the window.

<p>This project is focused to implement a new interface between Rocket.Chat, Omnichannel Livechat widget and Rocket.Chat.js.SDK allowing Agents to get real-time screen-share on customer’s devices.</p> <p>The main goal is to add the core features in Rocket.Chat, Rocket.Chat.Livechat and Rocket.Chat.js.SDK to support any screen sharing provider and to implement a generic screen-sharing manager to allow integration of any screen-sharing providers (by using dependency inversion principle) and to benchmark the server performance in updating sessions and rooms and declaratively loading JS scripts on live chat widget.</p>

This project aims to implement visual regression testing pipeline for Rocket.Chat’s component library, Fuselage, using Loki. The current workflow lacks automated visual checks, making it difficult to detect unintended UI changes. By integrating Loki—a lightweight and self-hosted visual regression tool—with Storybook and GitHub Actions, The result will be a scalable, cost-effective, and developer-friendly solution that increases UI reliability and reduces manual review effort. Deliverables: Loki integration with Storybook for Fuselage Stable snapshot testing environment with consistent rendering CI workflow integration to detect and report visual diffs Visual regression coverage for Rocket.Chat screens

<p>Jitsi Meet is a WebRTC JavaScript application, which provides high quality scalable videoconferencing solution. It uses Jitsi Videobridge as the video relaying server. Currently, developers have embedded many useful functionalities into Jitsi Meet, such as shared document editing, remote presentation, etc. Here, I propose to bring face and speech recognition into Jitsi Meet. First of all, I plan to add "Show your face" prompts for Jitsi Meet. In this case, if a user's face is not well positioned, it will prompt the user to move to the center. Additionally, if time is enough during the summer, I will also add speech-to-text functionality in Jitsi Meet. With the help of speech recognition, there could be a transcript generated automatically for a conference.</p>

People love to listen to music together, for which they would like to start a video conference where they can enjoy music together with their friends and family. A music bot for Jitsi video meetings will serve this purpose. This Music bot will be extremely simple to use, while in a meeting, just copy the meet link to the bot window and start the bot. The bot joins the meeting as a participant and follows the commands. The bot will be controlled by writing simple English commands in the chat box like /play <songName>, /pause, /resume, etc. User can also use their accounts on music streaming apps with the music bot to provide them with high-quality ad-free music if they enjoy a premium subscription on their accounts.

This project aims to improve the chat experience in Jitsi Meet by introducing additional features and user interface enhancements. The goal is to make the chat more versatile, user-friendly, and interactive, thereby improving communication during video conferences. Message Reactions — Users can react to chat messages with emojis, providing quick and expressive feedback. Message Menu — A new kebab menu for each message, offering easy access to various actions. Copy Message — Allows users to quickly copy message content. Private Message — Enables users to start a private conversation directly from a group message (relocated from previous implementation). Edit Message — Will allow users to modify their own messages after sending. Delete Message — Will allow users to retract their messages.