On any of the donation threads where it came up and he replied to it, the most he ever did was some half hearted corporate PR “apology” (ironic)
On any of the donation threads where it came up and he replied to it, the most he ever did was some half hearted corporate PR “apology” (ironic)
Problem is, piefed in run on a different code so you can’t just convert the lemmy database into piefed.
With a Lemmy fork, the transition would be seamless.
Sure, but you can just make a script that migrates it.
Right now, there isn’t any problems with the code, so there is no reason or incentive to fork it.
They’re working on that.
I read about that. I honestly would have switched to piefed myself if I hadn’t gotten too used to the lemmy-ui.
It’s not technically impossible to fork and port lemmy-ui to piefed (the APIs are similar. Hell, you might not even need to modify the code.)
I don’t mind not having lemmy-ui if i can keep using all the other lemmy clients, personally :D
True, when people say the apis are similar, do you mean you could use a lemmy client with it, or that it would be easy to adapt a lemmy client for it?
[AFAIK] The only thing right now, that’s stopping me from using say photon with piefed; is that most clients use the /api/v3 endpoint, but piefed only has /api/alpha. I bugged rimu about try to add a mock /api/v3 endpoint to see how far most lemmy clients would go with an unmodified instance; he’s yet to try that though.
But beyond that trivial point, yes; it should be very easy to adapt a lemmy client. Andrew already did so, while knowing nothing about dart; jwr1 already ported interstellar; and AP is planning to port tesseract/dubvee to piefed.