wmie2 VS Quassel IRC

Having a GUI WMI browser tool helps a lot, for example: https://github.com/vinaypamnani/wmie2/releases

Performance counters are an excellent solution for this. They are easy to quite easy to use and very light on the load. To add to this answer: - Fire up performance monitor on Windows, there you will be able to see all available counters, most will have a brief description - There is also the option to use WMI, however it is a lot more tedious, but it offers even more data. I used this program to see classes I could use: https://github.com/vinaypamnani/wmie2. And here are all CIM classes listed: https://learn.microsoft.com/en-us/windows/win32/wmisdk/cimclas Both worked flawlessly on Windows 10.

WMI Explorer -https://github.com/vinaypamnani/wmie2/releases

Sounds like your CI is machine based rather than user based, so take a look in the ROOT\ccm\Policy\Machine\ActualConfig namespace. Look for the CCM_CIAssignment class, then look for CCM_DCMCIAssignment instances. Those should be all the CI's for that device (someone please correct me if I'm wrong). The assignment name will give you the name of the CB (not the CI) and the collection it's deployed to separated by an underscore. You can use the GUI of WMI Explorer if it's easier for you. Just make sure to run it as admin.

WMI Explorer is a very nice tool to have around. It'll help you see queries and what type of stuff are available. https://github.com/vinaypamnani/wmie2

WMI Explorer - Provides the ability to browse and view WMI namespaces/classes/instances/properties in a single pane of view.

If you want to do some basic debugging, load up the catalog in the SCUP tool and see what the WQL says. Then use WMI Explorer on one of your live system to see what it says.

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