awdsns

joined 1 year ago
[–] [email protected] 1 points 1 year ago (1 children)

Then ask your instance admin to update to 0.18.4. I don't see this bug using the same Jerboa version on my home instance, which has already updated.

[–] [email protected] 1 points 1 year ago

Yes, when you open the homepage of your instance in a browser and scroll to the bottom, it should say something like "BE: 0.18.4".

If it says that and you still get this bug, it's a new one.

[–] [email protected] 1 points 1 year ago (5 children)

Which Jerboa and Instance backend versions are you seeing this with? There was an issue in the backend that could produce this behavior but should be fixed in 0.18.4: https://github.com/LemmyNet/lemmy/pull/3823

[–] [email protected] 4 points 1 year ago* (last edited 1 year ago)

Which front end would show both names? On (mobile and desktop) web and in Jerboa I only see the display name if it's set. And the only limitation seems to be that a leading @ is not allowed.

[–] [email protected] 25 points 1 year ago* (last edited 1 year ago) (3 children)

Tbh I think the display names as they currently work are dangerous. What would prevent me from setting my display name to [email protected]? Most front-ends would not show that I'm actually not you at first glance.

Edit: Misread the question as being about display names. Full unicode support for usernames would be even more dangerous, basically opening the door to unicode homograph spoofing on that level too.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

I was thinking of something like that too, but probably never would've gotten around to implement it myself, so thanks! Could you put your script on Github or something maybe?

Also it would be great if it could copy at least top-level comments by OP, because that's often used for linking to a source.