RE: ActivityPub Plugin for WordPress: let's assume I would work on a feature that would allow you to follow a complete blog, what would be the best identifier for that account? @feed@example.org? @blog@example.com?
What are your ideas?
As #flatpak has become more popular, I have tried to help make #plugin (s) Flatpak ready.
Interestingly, I keep coming across a general rejection, like "it's not worth the effort", "it's not the future", etc.
I am aware that it has drawbacks. But are you also against it?
Apart from the amount of space it can take up, I have to say that I've never really had any complaints, and I've sort of already accepted it as a kind of convenient, non-system #linux#packagemanager, I guess. #linuxaudio
WordPress now offers official support for ActivityPub - The Verge
The ActivityPub plug-in is now available for all WordPress.com plans, allowing users to communicate with each other across other federated platforms like Mastodon.
Maybe one of you #linuxaudio nerds knows. I'm trying to use the #plugin Instinct by Inertia Audio Systems with Bitwig Studio Flatpak, but Bitwig reports libwebkit2gtk-4.0.so.37: cannot open shared object file: No such file or directory, which makes sense, since the package is present in another version webkit2gtk-4.1 2.42.5-1 on my #manjaro system. I think this dependency is not ideal. But what could I recommend to the developers so that they could deliver the plugin in a "smarter" fashion?
In practice, I have not seen it actually work even once.
I'm able to find my WP user from here in the mastodon.hams.social web UI, and can "Follow". But it doesn't show my headshot AVI - a plain WP logo instead.
Then, after doing said follow, I switch to WP and make a post. Come back here - do I see that post? Hell no.
So I DM from masto to WP. Does that DM show UP anywhere? Nope.
oh dang, in addition to the bugfix, replies to comments made on fedi started being picked up by wordpress ActivityPub and it's like IT'S ALIIIIIIIIIIIIVE :D
Currently it is providing around 5% to my daily consumption, which is not much. It's December and the heatpump is running hard.
The biggest challenge is to prevent export to the grid. The sun is shining when the consumption of the house is the lowest. Currently I am preventing it with some #homeassistant automations, which turn on dehumidifier (which I use for drying clothes) in a laundry room or a boiler.
I would like to create a small #website as a starting point for #plugin developers who want to support #linux as a platform for #musicproduction. I plan to interview existing #linuxaudio#developers like u-he, TAL, AudioThing, Bitwig and others about this. Who of you would like to accompany and/or support me with this? 😊
Dear #linuxmusicians, #linuxaudio heroes! 🤩
Do you think we should offer our time to #plugin#vendor (s) for free to help them port their plugins to #linux?
I've always done so in the past.
I also wonder if we should form some kind of consortium to proactively offer support to vendors.
But from my own experience, and depending on the situation, it can quickly become a lot of work.
What are your thoughts on this?
“Enter the fediverse with ActivityPub, broadcasting your blog to a wider audience! Attract followers, deliver updates, and receive comments from a diverse user base of ActivityPub-compliant platforms.”
Wow, I just learned about the existence of #librewave and Rhapsody, a #crossplatform#kontakt like #sampler available for #linuxaudio! 🤩️ Libre Wave offers a range of libraries for this platform too. I still have to learn more about it but at first glance it looks (and sounds) really interesting and exciting. #plugin
I am still struggling to #debug some #proprietary#audio#plugin (s) using a #flatpak DAW. Is there any way I can see what resources the plugins are trying to access from within the Flatpak #sandbox? Running #bitwig with flatpak run -v com.bitwig.BitwigStudio does not reveal anything and flatpak run --command=sh --devel com.bitwig.BitwigStudio > gdb /app/bin/bitwig-studio (after installing org.freedesktop.Sdk.Debug) only says: (No debugging symbols found in /app/bin/bitwig-studio)