There’s a lot of drama in that Issue, and then, at the very end:

Thanks for sharing your concerns here. We have been progressing use of our SDK in more use cases for our clients. However, our goal is to make sure that the SDK is used in a way that maintains GPL compatibility.

the SDK and the client are two separate programs
code for each program is in separate repositories
the fact that the two programs communicate using standard protocols does not mean they are one program for purposes of GPLv3

Being able to build the app as you are trying to do here is an issue we plan to resolve and is merely a bug.

To my mind, the ideal would be that if you, as the person who wants to share some ‘open-source’ news, chose one community that you think is ‘best’ (based on what instance it’s on, if the mods are real people and are active, participation levels, whatever you think really). And we, as subscribers, would do the same. This way, the ‘good’ communities would thrive, and the ‘bad’ ones would wither away. What happens at the minute, is that there’s 8 communities for open source, and there’ll always will be, because they aren’t in competition with one another.

(this is mostly just a general point about cross-posting behaviour, it’s not meant as a dig at you personally).

Just a temporary thing with Lemmy I think - PeerTube (like Lemmy and Mastodon) are already part of the fediverse. You used to be able to successfully subscribe to PeerTube channels from Lemmy (when it was on 0.18), and likely will be able to in future (it’s just a Lemmy bug that needs a fix).

It’s federated like Lemmy, so each platform has ‘local videos’ and an ‘all videos’ section. E.g. https://fedi.video/videos/local and https://fedi.video/videos/overview

Of course, since it’s federated, it means other platforms like PieFed, MBIN and Mastodon can access the same stuff, so you don’t need to register anywhere if you’re on one of them.

No API exists yet for PieFed, unfortunately (it’ll need to have one at some point, though)

It seems to be quite a lot for the server it’s hosted on though (which is not the snappiest). There are, of course, still areas in the world where - for one reason or another - people still are effectively on dial-up speed-wise.

Buster should turn their attention to the size of the images uploaded to servers like this: 1.1M is arguably overkill for this one.

Looks interesting - I imagine there’s lot of uses for this. I currently use ngrok to tunnel from 443 to a local server, which is good way to test fediverse apps, but I wouldn’t be able to use bore for that (because it only assigns random public ports above 1024, and doesn’t deal with the SSL end of things)

Not much for beets. My config.yaml is just:

library: ~/.config/beets/musiclibrary2.db

import:
    move: yes

terminal_encoding: utf8

plugins: fetchart embedart

(so fetchart and embedart are the only plugins)

(from then on, a Navidrome server hosts the music, and I tend to use a Windows app called ‘Feishin’ to play it)