clap VS slack-libpurple

For CLAP plugins, hopefully this extension will land at some point, and host and plugin developers will implement support for it. https://github.com/free-audio/clap/pull/311

In the previous release, which came out a few days before this one, I got the GUI to run in Bitwig on Windows. It unfortunately doesn't yet work on macOS. I also implemented a new patch format which has better support for compatibility transformations and the clap state extension. Patches created with previous versions are automatically converted when opened.

If you need inspiration from a well designed C plugin API, look at CLAP.

I'm proud to announce the latest major yabridge release. I spent the last couple months working on support for bridging CLAP plugins. With yabridge 5.0 you can now use Windows CLAP plugins in native Linux CLAP hosts with full functionality. CLAP is a collaborative effort by a group of plugin and host developers of all backgrounds to create a permissively licensed extensible plugin standard that is simple while also catering to the needs of plugin developers, host developers, and musicians alike. When bridged under yabridge, these plugins are likely to have lower bridging overhead than their VST2 and VST3 counterparts while also being more responsive and offering better support for instrument plugins and parameter modulation.

Maybe make a CLAP version?

GitHub

Eion Robb has done an incredible amount of work in this space. His GitHub page[1] has tons of plugins, and I particularly appreciate the work he has done on the Matrix plugin to make it available to Windows users.

Lest you think this is less than cool because you don't use Pidgin, bitlbee[2] is a great tool to get slack (and others!) into your IRC client. I haven't run it myself, but I know that it heavily relies on purple[3] for its magic. I can tell it gets a lot of use, perusing the issues on the slack purple plugin[4] for example.

1: https://github.com/EionRobb?tab=repositories

2: https://www.bitlbee.org/main.php/news.r.html

3: https://wiki.bitlbee.org/

4: https://github.com/dylex/slack-libpurple/issues?q=is%3Aissue...

Unpopular opinion number one: James is not that bad. At least it can do video calls properly which is not something I would say of Slack.

Unpopular opinion number two: pidgi was better and I don't why we all decided as an industry to go to these ridiculously heavy memory hog electron based clients. I use Slack from Pidgin to this day: https://github.com/dylex/slack-libpurple

Another alternative is combining bitlbee with slack-libpurple and using an emacs IRC client, such as the built-in ERC. I used this back when I wanted both Discord and Slack available in the same emacs.

It's not IRC, but there exists a working libpurple plugin that you just auth as with your normal user account:

https://github.com/dylex/slack-libpurple

I just use it with Pidgin, but there are curses clients too (I'm aware of bitlbee, there are probably others) if you prefer the IRC-style experience.