dialecticcake, 1 year ago Based on this source the issue has been fixed but the instance owners need to update to the latest version of Lemmy (v 0.18) which has the fix.
Based on this source the issue has been fixed but the instance owners need to update to the latest version of Lemmy (v 0.18) which has the fix.