As others have said, its an issue with older versions of Lemmy (as in, the websites running it, not your client). Once your admins update the website/instance you're using, it'll be fixed.