Just submitted a PR to fix this, thanks for the suggestion: https://github.com/dessalines/jerboa/pull/549
Just submitted a PR to fix this, thanks for the suggestion: https://github.com/dessalines/jerboa/pull/549
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.
Ah good point - I think we’ll need to add that. I’ll make a Github issue now so it doesn’t get lost.
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.
Yeah after some discussion on GitHub this is the direction the app is headed in, and the next update should have some settings in this regard with Boost-like behaviour as a user option. We can add more options if the community are split on their preferences. The joy of open source!
Yeah BaconReader does the same, I think it makes sense. I’ll try and fix that for the next release.
Now it’s in and I’m using it, I’m wondering if it would be better if tapping a comment would only collapse the children of that comment instead. This might prevent user frustration if they try and click a link in a comment but miss, so the comment closes instead.
My pleasure, I’m glad I could contribute in my own small way to this awesomeness!
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.