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.

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.

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

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.

Tbh I think the display names as they currently work are dangerous. What would prevent me from setting my display name to @nutomic@lemmy.ml? Most front-ends would not show that I’m actually not you at first glance.

I think that might just be due to different Markdown engines supporting different feature sets. But not having a consistent way to tag spoilers really sucks.

Edit: another thing that’s bugging me about the Markdown engine in Jerboa is that it interprets basically any number as a clickable phone number: 123

Not currently possible because that is not exposed via the Lemmy API, although it would be possible and there’s an open issue about it according to the dev: https://lemmy.ml/comment/439350

I think going to GitHub and voting/commenting on issues we’d like resolved would help the developers prioritize what to tackle first.

Thanks, that’s great to hear!

@[email protected] I know I have no right to ask this as I’m in no position to contribute myself atm, but please make it a long press or add on option to configure the behavior (like Boost). I already find myself fat-fingering the wrong UI action a lot, and this new collapsing behavior doesn’t help.

There actually already is an issue about this: https://github.com/dessalines/jerboa/issues/369 🙂

But just to add, I’ve noticed both of these things too. Actually the Subscribe/Joined button seemed to update almost “immediately” for communities on my local instance, but not for federated communities. The list only ever seemed to update after restarting the app.