You can use Kimbia to run a series of tasks like linting, testing, building, and deploying your application.

Zana aims to be like Mason.nvim, but with the goal of supporting not only Neovim, but rather any other editor.

Zana is swahili for "tools" or "tooling".

A minimal package manager for Neovim (and other editors) which uses the Zana Registry to install and manage packages.

By its spiritual predecessor Kulala.nvim, bringing .http files support to a nice GUI app.

Why?

You should own your data (.http files in your vcs). You shouldn't have to worry about logins or accounts. It should be mostly compatible with Kulala.nvim, Rest.nvim, VsCode RestClient, IntelliJ and Visual Studio.

You can see the current WIP here: https://bsky.app/profile/mistweaverco.com/post/3lhfmepcw322s

The website will ask you "do you like emojis?" once. If you answer with yes, you see emojis, if you answer no, all emojis will be hidden from you from that point on.

I never heard of Parsec, have to look it up, but Bananas should be also real low latency, because it's a direct connection.

That is totally possible if you just want to join a driver/host.

If you want to take over and become the driver that would not be possible or with some real limitations (not being able to give access to your keyboard/mouse and also not having the ability to show the cursors of the participants)

That's exactly how I use them. I'll probably add a selector for "with Emojis | Plain text" on the website. So we can make everyone happy.

Does remote control and drawing really work on all platforms? I remember screen hero and Linux support was always an after thought and did never work well with all features.

Yes, that's right. But tbh, getting Mediastream in Electron can be done by a 5y old.

If you're using a recent Electron. Nearly everything (Discord, Slack, you name it) does not. This is all from memory, but I believe Wayland was "fixed" in Electron 19, but with a showstopper bug that was never backported. Many Electron apps are on 18 to this day.

Yes, I was just triggered by the "just" somehow :( it is not the hard part that I was trying to solve. The hard part is the UX/UI and the WebRTC part itself.

I believe you interpreted it exactly the opposite of what I wanted. I put "just" in quotes precisely to make the point that that there's a lot more to your application than getting the screencast buffer.

I remember Jitsi being awesome, but as far as I can remember, you need to have a Jitsi server running, right? I wanted it to be as independent as possible of servers or orgs, so that when I get rolled over by a bus and stop paying for services, it still continues to work for everyone.