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

That’s a good idea! I understand the sentiment of leaving a final “fuck you” to Reddit, but at the same time the thought of losing the treasure trove of accumulated knowledge stored there pains me.

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.

That’s how I interpret the post pinned to their front page asking users to go somewhere else: https://lemmy.ml/post/1147770

I don’t think lemmy.ml is accepting new users currently. Choose another instance (server) from the recommended ones at https://join-lemmy.org/instances

It doesn’t really matter much which one, you will still be able to interact with communities across different instances.

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.

I have the impression that the federation thing as a whole still has some issues. Like I checked some of my submissions on different instances and it would sometimes show different comment counts, but the comment which would explain the difference was nowhere to be seen. So it wouldn’t surprise me if vote (non-)propagation also doesn’t always work as intended.

I read that they just ignore incoming downvotes, so on Beehaw you’d never see them, only locally on the instance where you voted.

Thanks, that’s great to hear!

@a1studmuffin@lemmy.ml 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.

https://play.google.com/store/apps/details?id=com.jerboa