a1studmuffin

Yeah, though long tap is already used for toggling the action bar for comments, so you'd end up with a similar issue of using to interact with small links and getting the wrong result sometimes. So probably a user setting to turn the small links on/off entirely would be safest.

I think I'm on Lemmy for the long haul - I like the fediverse decentralisation. The hardest part of Reddit to abandon will be the search results on Google, but perhaps we'll see something similar with Lemmy in a few years if it picks up steam.

Just submitted a PR to fix this, thanks for the suggestion: https://github.com/dessalines/jerboa/pull/549

I did just that, thanks! Everything is so much faster using that instance, wow.

Fairly sure this is fixed, but might not be rolled out yet.

We'll likely add an option soon to turn off small links (like inline user names and community names) so you won't be taken to the user's profile in the first place if you accidentally tap it.

Try a long tap on the comment body. If that doesn't work, try a tap or long tap on the comment header. It's possible there's a few bugs with some of the new comment interactions.

Thanks! Can't believe I missed that. Also, I didn't know we had an aussie Lemmie server, sweet.

This would be lovely. Then once that functionality was working, we could create a Reddit-style front-page for new accounts that subscribed to a bunch of popular hashtags. That would really help to ease onboarding and make instances feel a bit less isolated.

Ah good point - I think we'll need to add that. I'll make a Github issue now so it doesn't get lost.

Edit: https://github.com/dessalines/jerboa/issues/506

If you select View source on the post you should be able to?

I think this will be the server struggling to respond, sending back an error code instead of the requested data in json format. The app should probably display something more user-friendly like "Server error (504)" (or whatever the error code is).

It's odd you're not seeing similar issues on the web version though... maybe it just takes longer to load or there's a timeout somewhere in the app that needs to be adjusted.