Same, since I updated my instance to 0.18 Jerboa doesn’t work and instantly crashes.

Upvoting this post from Connect for Lemmy. Actually I think I still prefer Jerboa. Unfortunately it has stopped working since I updated my instance to 0.18 so this will have to do for now.

Oh I wasn’t aware of this. Very tempting. Now I lowkey wish they miss the deadline on one of the six accounts I requested the data for, so I can do some European style trolling.

Couldn’t the protocol be updated to be more compliant with the right to be forgotten? Something like, when a user deletes a comment it gets deleted from the DB of every federated instance. Sure enough, admins might have made backups and that would theoretically go against the GDPR but still… you can only apply these laws to a certain extent. It’s the same as you posting a picture on Facebook, me downloading it and you deleting it afterwards. Even if you were to make a GDPR request to Meta you still couldn’t get the picture on my PC. But that’s not Meta’s fault, they can’t do much about that.

I STRONGLY ADVISE you against doing the following, but for educational purposes, just rename the file .husky/pre-commit to anything else. I called mine _pre-commit and slapped a README next to it documenting what I did. This will turn off the husky pre commit job, which is what runs prettier.

Not sure if it’s the same issue you are having, in my case prettier failed to run and that didn’t allow me to commit at all.

The pain of working on the lemmy frontend. I “fixed” this by turning off prettier.