Quassel IRC VS Brackets

> 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...

Link to the wonderful people who discovered how to fix the stupidest live preview error in all of human history: https://github.com/adobe/brackets/issues/11519

Heh, just a month ago Adobe Brackets (another Atom clone) did the same https://github.com/adobe/brackets

Oh, that's a good point about the sunsetting. In Brackets's case, Adobe left it active in the hands of the community.

Live Preview in particular is one of the areas I had some fun working on. I worked out a way to do diff/patch to make it quickly and incrementally update the browser[1]

[1]: https://github.com/adobe/brackets/wiki/Research%3A-HTML-DOM-...

Brackets may be a free and open-source code editor from the owner of Photoshop, Premiere Pro, and other amazing software providers Adobe. it's a primary target for web development and particularly on web designing because it provides plenty of features for web designers like Quick edit, Quick Docs, Live preview, Autosave, JSLint, Preprocessor support, Open source, Extension, themes, and more. Its software is licensed under the MIT license and it's currently run and maintained by Github's open-source developers. Its GitHub repository is https://github.com/adobe/brackets. it was created with help of Electron JS(JavaScript). it's available in 38 languages like HTML, CSS, JavaScript. It supports lots of extensions like Beautify, Autoprefixer, Emmet. Minifier, ToDo, Bracket Gits, Brackets File Icons, Swatcher, and more. it absolutely was initially released on 4 November 2014 around 7 years ago. it's integrated with NODE JS, JavaScript, Adobe PhotoShop, Vizy, and more, and firms like Zenkit, Startlink, MaGIC, WorldGaming, NeoQuant, Core, OpportunityWork, and more are using it for her projects. it's lots of benefits like -

I think you just need to download this : https://github.com/adobe/brackets/releases/download/release-1.14.2/Brackets.Release.1.14.2.msi

I don't think there's a fix for this. This problem has many issue entries on github, and it will eventually get worked on at some point. However you could try this troubleshoot guide.

https://brackets.io/ as well as https://registry.brackets.io/ are already back again. Currently there are still some issues with SSL certification but as soon as these are resolved we should expect to get a working extension manager again. After that, the community will be able to transition to the new branch of Brackets (brackets/brackets-cont) most likely by some kind of patch.