Andrew

This is all quite old drama, and the issue itself is fixed now, but at one point someone kicked off about how if you uploaded a picture to Lemmy, there was no easy way to delete it (you could delete your post, but the image would still be there at whatever URL was created for it, and it wasn’t even that easy for admins to find and remove it) - so I’m guessing that it stems from that.

Oh yeah, sorry. I didn’t mention that the API isn’t available on production sites like piefed.social. I’ve been messing around with a build of Thunder on my dev instance, and - among other things - the app doesn’t uses the same V3 endpoint that Lemmy does, so it’d always need to be a different version than the one that’s currently available for Lemmy.

No, it’s not geared up for that. There’s a platform called sublinks where the intention is to be initially compatible enough with Lemmy that it can be a drop-in replacement, but they haven’t released anything yet.

It’s not so much that we expect the developers of Lemmy apps to retool. The hope is that, if we can provide a sensible, well-documented API, then it will appeal to front-end developers looking for a project. Also, if there are any devs of Lemmy mobile apps who are unhappy with Lemmy’s API for any reason, then getting involved with PieFed’s whilst it’s still in development, offers them a chance to shape one to their desires.

Speaking of Thunder though - I’ve been able to compile it for desktop, and get it working with PieFed’s API in the state it’s in now. I’ve no experience with Flutter / Dart or front-end development, so it suggests that - for open source Lemmy apps, at least - it doesn’t need to be the original author who ports it, and that the actual details a particular API are only a relatively small part of creating a good mobile app.

Sadly, Anakin’s mum had already been claimed by Watto, and Padme didn’t know about unclaimsies.

(for anyone confused, this is a reference to Skeleton Crew).