Thanks for looking into it. I totally understand why you’d want to prioritize Lemmy at the moment.
The API is 99% ready to be enabled on all instances but we haven’t pulled the trigger on that yet.
Recently the developer of Intersteller, an app that does Lemmy, Mbin and PieFed, has been working with us. So yeah it’s doable but you have to really want to, obvs.
I’m considering turning on support but placing a warning on my app that says “not officially supported” or similar. I ran a quick test, and it seems I can almost drop in your API in place of Lemmy. Post names and community counts were broken, but much of the app was working.
What I don’t wanna commit to doing is changing tons of my app to make it Piefed compatible. But I don’t see the harm in letting users connect to a Piefed API.
I’m a PieFed dev.
Thanks for looking into it. I totally understand why you’d want to prioritize Lemmy at the moment.
The API is 99% ready to be enabled on all instances but we haven’t pulled the trigger on that yet.
Recently the developer of Intersteller, an app that does Lemmy, Mbin and PieFed, has been working with us. So yeah it’s doable but you have to really want to, obvs.
I’m considering turning on support but placing a warning on my app that says “not officially supported” or similar. I ran a quick test, and it seems I can almost drop in your API in place of Lemmy. Post names and community counts were broken, but much of the app was working.
What I don’t wanna commit to doing is changing tons of my app to make it Piefed compatible. But I don’t see the harm in letting users connect to a Piefed API.
Here is a build of Blorp with Piefed.
https://pr-62--blorpblorp.netlify.app/