oni VS Quassel IRC

Now here comes the endboss: Jupyter. For the first time, I feel like I'm missing out on stuff when using vim. I've started a job in datascience, which is actually awesome. However, I work a lot with image data. I also do a lot of analysis on results, meaning I do a lot of fancy plots that hopefully show the weaknesses of our prediction models. I recently wrote an augmentation algorithm where I had to see the output in form of an image after every step to make sure it's correct. This is not a possible workflow in vim right now. I know of many solutions that I already tried, like for example jupyter-vim or the jupyter vim mode. I'd like to work inside my terminal though. I'm not this kind of purist who needs to have a terminal that is compatible with VT100 or whatever people came up with in the 80ies. I also don't care if my terminal in based on an ascii like grid or actually rendered in HTML. I just want (Neo)vim, with the functionality of jupyter (inline plotting) even if this means vim has to be rendered inside an electron app or whatever people use these days for fancy GUIs. Imagine an electron based editor like Oni which not only runs the "real" neovim in the background, but is also able to do inline figures, images, plots and even interactive stuff. It seems to me like I can't be the only one who wants this. So after all this, here's the question: Is there anything you now of that allows for this kind of stuff? Is there any other workflow that I'm not aware of? Or do people just not use those features when working with vim? Pls help a vimmer stay at vim.

Oni or Oni2

SpaceVim - A community-driven vim distribution

While learning Vim, I went through the `vimtutor` many times until I felt really comfortable. After that you can try more advanced stuff (I applied the same pattern with the oni[0] built-in tutorial). Last but not least there are Youtube channels: theprimeagen[1] and Greg Hurell[2] come to my mind. I particularly recommend theprimeagen (he is a Netflix engineer) because he has videos about real-life workflow. And speaking about real life, I was amazed by this video[3] the first time I saw it, it's a very good introduction to macros.

0: https://github.com/onivim/oni

1: https://www.youtube.com/channel/UC8ENHE5xdFSwx71u3fDH5Xw

2: https://www.youtube.com/channel/UCXPHFM88IlFn68OmLwtPmZA/vid...

3: https://youtube.com/watch?v=hraHAZ1-RaM

> But all of the modern services like Teams, Slack and Discord, have seamlessness between client devices as their first priority.

Can't speak for the others, but Teams is really hit-or-miss. Missed notifications, missed messages, out of order messages. Then it appears to be fixed for three months only to happen again. It mostly seems to happen on Android.

In general, you're right, multi-device appeared to have been solved for IM - at least MSN messenger and Skype had it - right around the time when the smart phone came around, but then we had the same problem again in the mobile world, because somehow those messengers couldn't successfully move to phones: WhatsApp and the likes was bound to one device again. They added web access later, but that was more of a hack than true multi-device support.

The big problem the phone messaging apps solved was that their protocols didn't require a persistent connection. Theoretically, all the other protocols, MSN, ICQ, Skype, IRC could have been extended to support this too, but it's always faster to just build something new and be first to market.

If you want to use IRC today and have that modern multi-device experience, IMO the most decent solution is Quassel[1] (and Quasseldroid for Android). It's like a bouncer, but uses a custom protocol between the bouncer (quassel-core) and the GUI (quassel-client), so that it can perfectly sync state across all devices, and with flaky connections on mobile. It obviously required you to run the core on some server so it's accessible from everywhere, so nothing for "normies" as TFA calls them, but to me it's what makes IRC usable in the modern world. I wouldn't want to use irssi in a screen via ssh in termux on my phone.

The next best thing, if you're a Web 2.0 aficionado is probably The Lounge[2].

[1] https://quassel-irc.org/

[2] https://thelounge.chat/

Quassel IRC: A modern, cross-platform, distributed IRC client. Tech Stack: C++, Qt.

You can use a bouncer to do this. ZNC is the most popular. Quasse is a different take on the bouncer, where you have a special client that logs into your Quassel server, and the server logs into IRC. Has certain advantages, like more seamless scrollback and so forth. A variant take on this is irccloud, which is probably the "best" if you just want something turnkey that works with minimal fuss. It has good push notifications, a good web client, and excellent mobile clients

I use purple-discord (libpurple/Pidgin plugin) + BItlBee (IRC chat gateway, libpurple variant) + Quassel (distribued IRC client, like a bouncer) on a home server, and use Quasseldroid to connect on mobile. I would eventually like to simplify this setup.

Personally, I use a self-hosted "Core" (server) of Quassel I compiled from source and host remotely. Attach to the Core "locally" on a ZeroTier LAN network through a persistent physically independent WireGuard/reverse proxy/edge node microserver using various open source apps (preferably compiled from source). On Android I use QuasselDroid and of course compiled from source .

I've been a massive user of IRC since the mid 90s... have written lots of bots, scripts etc plus set up plenty of stuff to deal with being able to disconnect your client without missing out on anything (currently use https://quassel-irc.org/ with the daemon on a VPS). I was even l33t enough to "read bitchx.doc" back in the day...

Quassel - Quassel IRC is a modern, cross-platform, distributed IRC client.

Seems really similar to Quassel (https://github.com/quassel/quassel/), though I don't believe that has a webclient...