For context, you can consider current Lemmy pre V1 and the upcoming update V1.
Lemmy has some big updates coming soon. Initially, when I wrote Blorp, it made sense to keep things simple and coupled to Lemmy since Lemmy is what I’m personally the most interested in. However, supporting current Lemmy versions and future Lemmy versions is going to require me to decouple Blorp from a specific version of the Lemmy API anyway.
A bunch of people have asked about PieFed support, and I’m realizing the groundwork I’m going to need to lay to support Lemmy v1 will likely make PieFed support much easier. I haven’t looked into MBin, but I imagine it may be similar.
I’m not really sure what the point of this is, other than a routine update post and bouncing ideas off you all. Likely, Lemmy will always be my top priority, but my plan is to update Blorp so it allows you to write adapters to plug into different but similar projects like Lemmy, PieFed, etc.
I think there’s still value in offering some support for PieFed and Mbin, especially if apps are currently few in number or nonexistent for those services. Even if other apps come along that offer fuller feature support, there might still be a place for Blorp to offer limited support for the different platforms by allowing people to switch accounts. It seems to me like a lot of Lemmy apps let people sign-in to multiple accounts so they can quickly switch from one to another. Blorp could similarly offer that but more usefully let users easily switch from a Lemmy account to a PieFed account to an Mbin account. And if that proves popular perhaps later you could add support for more features unique to each platform.