At least one mistake in there though, since you can definitely block instances in Kbin too. It's not the most obvious though.
Also:
A single health check call a minute by a single app is nothing compared to real world usage
Yeah, it definitely is not a drop in for Lemmy's API, so if Sync were to support my API for kbin it would be an additional layer for them to add.
I've been working on the API, and it is pretty much feature complete (barring feedback) and should be entering review very soon.
Fedia is just another kbin instance, not really a fork. It is tracking the development branch a bit closer than kbin.social, but it's still the same repo
Lemmy stores who upvoted what but does not make it easily available to everyone like kbin does - you can set up a Lemmy instance to grab upvoted and read them from the DB if you are so inclined, or you could just look at kbin to see the same info
Looking in ImageRepository.php it doesn't appear that images have their extra data stripped. Also testing it on my dev instance showed that GPS data remained in the image. Should be an easy fix since all image uploads are processed through that repository.
Edit: In fact there's already an issue open for it - https://codeberg.org/Kbin/kbin-core/issues/374
kbin users:
Look at what they need to mimic a fraction of our power
/s
YouTube Revanced is a replacement for the Vanced app that is less likely to get taken down since it doesn't distribute YouTube assets
Only on kbin, on lemmy that doesn't exist (yet)
Not yet - the API is still being reviewed for integration into the main kbin codebase. artemis.camp is using the prerelease code to test the app. If another kbin instance decides to use the prerelease code I believe it might be able to be used on that instance as well, but I'm not 100% on if that's been implemented by Artemis