Search
App crashing
I've noticed with the last 2-3 versions of the app (currently 0.0.69, nice); the app crashes 2/3rds of the time when returning to it from being in the background.
Open the app, switch to another app, switch back a couple min later and it closes then reopens as if you'd just started it for the first time today (losing whatever post you had open).
Curious if others are experiencing this?
Android 14, One UI 6.1
Are gifs broken?
Since the last release, I find that gifs won't play in Jerboa anymore. For example, this comment just appears as a static image for me, even when I click on it. Do you see the same behavior?
Edit: solved by user merde alors:
>did you enable "auto play GIFs" in settings>look&feel ?
Then close and reopen the app and that should fix it.
What should be Lemmy's default way of displaying votes?
cross-posted from: https://lemmy.ml/post/14068273
> We're adding the ability to customize this in the upcoming release, but I'm wondering what people think would be a good default.
>
> The 4 pieces of showable/hideable info are: Upvotes, Downvotes, Score, and Upvote %.
>
> In Jerboa, I had a temporary default (until the next lemmy release), of Score + Upvote %
, but people seem to dislike this a lot.
>
> I'll check back on this in a week to see the result.
"Create" FAB bug
![](https://lemmy.ml/pictrs/image/b93d9544-2c8f-48cc-91bd-3b95d3b68d05.jpeg?format=webp&thumbnail=128)
![](https://lemmy.ml/pictrs/image/b93d9544-2c8f-48cc-91bd-3b95d3b68d05.jpeg?format=webp)
I updated Jerboa from 0.0.60 (or 0.0.59 I don't remember) to 0.0.61 (all are F-droid versions) and I noticed this issue: the "create post" ("plus") floating action button hides under the navigation panel. Cleaning the cache and disabling-enabling the panel didn't help. The button is still clickable but it doesn't look right. When the panel is disabled it looks fine if course. I'm on Android 13 btw
When i am trying to log in on my reddthat account using jerboa this error shows. I have'nt had this problem a week ago and reddthat is running the latest version.
![](https://lemmy.today/pictrs/image/b3adab35-fd6f-4a15-af4f-a9ed055e67da.jpeg?format=webp&thumbnail=128)
![](https://lemmy.today/pictrs/image/b3adab35-fd6f-4a15-af4f-a9ed055e67da.jpeg?format=webp)
Other apps and the UI seem to be working . I have edited out the username and password for privacy reasons. Also i am running version 60 but i was running it the previous week too.
EDIT : Uploaded the wrong .jpeg and now have replaced it i don't know if the change has been federated for everyone .
Changed behavior of already read posts?
Hi, I'm using Jerboa in List mode and I recently noticed that posts are marked as read simply by scrolling by. I feel that might be a reasonable change for Card mode, but an entry in a List should not count as read unless it was opened. Or am I doing something wrong?
An error occurs when trying to add a photo to a post
I wanted to post screenshots of my riced KDE setup on Unixporn so I copied them to my phone using a USB cable. And now when I'm trying to add them to a post, it seems to always show the same error (Client request(POST https://lemmy.ml/pictrs/image) invalid: 403 . Text "<..."). The app has all the required permissions granted and I'm not banned from the community. What can it be then?
Default sort for comments
I am no programmer and am not sure if I am allowed to post this here, so delete if you want.
My suggestion: Like the default sort for posts we need a default sort for comments. There should be a dropdown menu like there already is for default sort posts.
Bugs I've encountered
Every time I try to use the text link to URL ()[] and go to hit the "ok" button, the entire windows goes away. The work around is to hit the keyboard minimise to uncover the buttons.
Press anywhere but the keyboard and ya loose everything you type.
Another bug is when you try to paste anything in the body it pastes it at the beginning of the body regardless if where in the text you have highlighted.
Sometimes an instance will load but in unable to view comments (can't remember what it said) you need to clear the app cache to fix the issue
This is about it, otherwise this is my fav Lemmy app around. Keep up the good work.
Ps before you ask this is the only app I've encountered these issues with
Bug Report
This post doesn't show up in the feed of the community to which it was posted when seen via Jerboa and cannot be opened in the app by any other means. For more details and comparison to other apps, please see this post.
Can you make it so we can chose what browser links open to, or create an internal browser option?
I don't like using Chrome anymore, but any link I open goes to Chrome. Way more importantly, any YouTube video opens to the YouTube app, which is a huge problem imo. I end up not viewing 90% of the videos posted on lemmy, because I don't want my YouTube feed to be screwed up.
Even innocuous content is a problem for me. Like, I may be interested in seeing a satisfying wood working video one time, but I don't want my feed thrown off.
As it stands, I pretty much only watch videos on this platform if there's a piped link accompanying them. My 3rd party app for reddit had the option of an internal browser, which I always used.
I love Jerboa, think it has the best UI, and recommend it all over lemmy. But I feel like it's lacking important features, without an internal video player, and less importantly an intenral browser for non-video links.
Even the implementation of a setting that would allow me to open links to Firefox instead of Chrome or YouTube would solve my problem.
Anyway, just a thought.
Edit: So I'm dumb and changing default settings in my phone solved that problem. I would still like to see an internal browser and video player tho.
Cannot write posts from Jerboa
Since the last update, I cannot write or respond anymore with one of my accounts in Jerboa. The same account works as expected with Voyager and the web UI.
With the present account, I can post without problem (and I wrote this in Jerboa). I don't believe that I modified the configuration in any way.
I get the following messages in the other account:
- This account is not yet in a ready state
- This account (name of the account) is b... [cannot see more displayed]
The problem is not limited to any specific lemmy instance (same issue on feddit.de and lemmy.world).
Any idea what is going on here?
Timed Mute Community/User
Sometimes, it may be good for one's mental health to "take a break" from a community or user. It would be nice to be able to temporarily block posts from a user or community that one may otherwise enjoy in a 1h/6h/1d/1w or possibly arbitrary time period.
homing upon tapping the app icon is truly disruptive!
After the most recent update, the view always return to the top of local homepage.
This is very disruptive, since some users would press home when they want to use another app, and would tap the icon on the homepage to go resume what they were doing.
I actually tried to write this post earlier, but something came up that requires me to context switch. When I was done with that, I tapped Jerboa icon on my homepage (muscle memory). To my surprise, the post I was writing disappeared, replaced by the local homepage. I don't even browse local that often...
Links will not open properly
Whenever I try to click on any post link, it opens up whatever my most recent Chrome tab was. Clicking any post link essentially just works as a shortcut to open Chrome. This just started happening to me this morning.
¿Is there a convenient way to preview the actual URL behind a hyperlink before visiting it?
Markup let's you label a link which is really nice for readability but can also be used to trick people into opening a different site from what they are shown. For example the link below suggests it takes you to a Mastodon instance but if you blindly tap it it will take you somewhere else:
https://mastodon.social/explore
Is there a quick and convenient way to check the actual URL behind a link? I know that it's possible to show a post as plain markup but in longer posts with potentially multiple links it's cumbersome to correlate what is what.
Ideally long tapping a link should show you the actual URL or alternatively you always get a small confirmation pop up with a simple tap (that's how it worked on RIF for instance).
Just sanity checking if I'm missing anything, else I might submit a feature request.
Edit: looks like this was added in a recent update. Get the newest version and it will let you long press a link to get an options menu.
Spaced words get clumped together when pressing backspace to erase words
Video demonstration: https://old.reddit.com/r/u_cy_narrator/comments/166y9re/this_space_bug_in_jerboa/
When I am typing and press the backspace, the words get clumped together that shouldnt have been.
Version: 0.0.44
[Sorry that I had to use Reddit to upload video about Jerbora]
I had to downvote you to get the "total" (heart) to show up. You can see in the comment below yours that if there are only all up- or downvotes, it just shows that.
I have managed to reproduce this on Android 8. It seems to be android 8 specific. This is a problem with our toolkit. You seem to the first to experience this because I can't find anything on this yet. The only thing you can do is to downgrade to Jerboa 0.0.66
Error
[java.lang.NoSuchMethodError: No virtual method setAmbientShadowColor(I)Z in class Landroid/view/RenderNode; or its super classes (declaration of 'android.view.RenderNode' appears in /system/framework/framework.jar:classes2.dex) at androidx.compose.ui.graphics.layer.GraphicsLayerV23.setAmbientShadowColor-8_81llA(GraphicsLayerV23.android.kt:212) at androidx.compose.ui.graphics.layer.GraphicsLayer.setAmbientShadowColor-8_81llA(AndroidGraphicsLayer.android.kt:807) at androidx.compose.ui.platform.GraphicsLayerOwnerLayer.updateLayerProperties(GraphicsLayerOwnerLayer.android.kt:119) at androidx.compose.ui.node.NodeCoordinator.updateLayerParameters(NodeCoordinator.kt:545) at androidx.compose.ui.node.NodeCoordinator.updateLayerParameters$default(NodeCoordinator.kt:524))]( java.lang.NoSuchMethodError: No virtual method setAmbientShadowColor(I)Z in class Landroid/view/RenderNode; or its super classes (declaration of 'android.view.RenderNode' appears in /system/framework/framework.jar:classes2.dex) at androidx.compose.ui.graphics.layer.GraphicsLayerV23.setAmbientShadowColor-8_81llA(GraphicsLayerV23.android.kt:212) at androidx.compose.ui.graphics.layer.GraphicsLayer.setAmbientShadowColor-8_81llA(AndroidGraphicsLayer.android.kt:807) at androidx.compose.ui.platform.GraphicsLayerOwnerLayer.updateLayerProperties(GraphicsLayerOwnerLayer.android.kt:119) at androidx.compose.ui.node.NodeCoordinator.updateLayerParameters(NodeCoordinator.kt:545) at androidx.compose.ui.node.NodeCoordinator.updateLayerParameters$default(NodeCoordinator.kt:524) at androidx.compose.ui.node.NodeCoordinator.updateLayerBlock(NodeCoordinator.kt:503) at androidx.compose.ui.node.NodeCoordinator.updateLayerBlock$default(NodeCoordinator.kt:480) at androidx.compose.ui.node.NodeCoordinator.placeSelf-MLgxB_4(NodeCoordinator.kt:384) at androidx.compose.ui.node.NodeCoordinator.placeAt-f8xVGno(NodeCoordinator.kt:332) at androidx.compose.ui.node.InnerNodeCoordinator.placeAt-f8xVGno(InnerNodeCoordinator.kt:168) at androidx.compose.ui.layout.Placeable.access$placeAt-f8xVGno(Placeable.kt:35) at androidx.compose.ui.layout.Placeable$PlacementScope.placeWithLayer(Placeable.kt:646) at androidx.compose.ui.layout.Placeable$PlacementScope.placeWithLayer$default(Placeable.kt:327) at androidx.compose.ui.graphics.BlockGraphicsLayerModifier$measure$1.invoke(GraphicsLayerModifier.kt:580) at androidx.compose.ui.graphics.BlockGraphicsLayerModifier$measure$1.invoke(GraphicsLayerModifier.kt:579) at androidx.compose.ui.node.LookaheadCapablePlaceable$layout$1.placeChildren(LookaheadDelegate.kt:223) at androidx.compose.ui.node.LayoutModifierNodeCoordinator.onAfterPlaceAt(LayoutModifierNodeCoordinator.kt:270) at androidx.compose.ui.node.LayoutModifierNodeCoordinator.placeAt-f8xVGno(LayoutModifierNodeCoordinator.kt:247) at androidx.compose.ui.layout.Placeable.access$placeAt-f8xVGno(Placeable.kt:35) at androidx.compose.ui.layout.Placeable$PlacementScope.place-70tqf50(Placeable.kt:621) at androidx.compose.ui.node.LayoutNodeLayoutDelegate$MeasurePassDelegate$placeOuterCoordinatorBlock$1.invoke(LayoutNodeLayoutDelegate.kt:561) at androidx.compose.ui.node.LayoutNodeLayoutDelegate$MeasurePassDelegate$placeOuterCoordinatorBlock$1.invoke(LayoutNodeLayoutDelegate.kt:548) at androidx.compose.runtime.snapshots.Snapshot$Companion.observe(Snapshot.kt:503) at androidx.compose.runtime.snapshots.SnapshotStateObserver$ObservedScopeMap.observe(SnapshotStateObserver.kt:502) at androidx.compose.runtime.snapshots.SnapshotStateObserver.observeReads(SnapshotStateObserver.kt:258) at androidx.compose.ui.node.OwnerSnapshotObserver.observeReads$ui_release(OwnerSnapshotObserver.kt:133) at androidx.compose.ui.node.OwnerSnapshotObserver.observeLayoutModifierSnapshotReads$ui_release(OwnerSnapshotObserver.kt:98) at androidx.compose.ui.node.LayoutNodeLayoutDelegate$MeasurePassDelegate.placeOuterCoordinator-MLgxB_4(LayoutNodeLayoutDelegate.kt:867) at androidx.compose.ui.node.LayoutNodeLayoutDelegate$MeasurePassDelegate.placeSelf-MLgxB_4(LayoutNodeLayoutDelegate.kt:835) at androidx.compose.ui.node.LayoutNodeLayoutDelegate$MeasurePassDelegate.placeAt-f8xVGno(LayoutNodeLayoutDelegate.kt:761) at androidx.compose.ui.layout.Placeable.access$placeAt-f8xVGno(Placeable.kt:35) at androidx.compose.ui.layout.Placeable$PlacementScope.place-70tqf50(Placeable.kt:621) at androidx.compose.ui.layout.Placeable$PlacementScope.place-70tqf50$default(Placeable.kt:259) at androidx.compose.foundation.layout.BoxKt.placeInBox(Box.kt:223) at androidx.compose.foundation.layout.BoxKt.access$placeInBox(Box.kt:1) at androidx.compose.foundation.layout.BoxMeasurePolicy$measure$5.invoke(Box.kt:203))
Put [Fixed] in the title, this might help other people
Gifs never worked inline for me. They used to work when clicking on them however.
Does this work for you at all?
Edit: Actually this doesn't work for me either now even after clicking into it. Yes GIFs are broken.
Version 0.0.67
I like being able to see upvotes and dowvotes separately as it is done now.
Arstechnica has them separately but also shows the sum which could be an option. For example, 90 (93 / -3)
but with green and red color.
Having a show/hide sum in settings could help please more people but it's extra work for developers.
Did the app autoupdate recently to 0.0.67? If it did, some massive changes/improvements were made in said update, which also affect way votes are displayed.
https://github.com/LemmyNet/jerboa/releases/tag/0.0.67
When your instance admin updates to the latest Lemmy software version, you will be able to hide votes again and have more control over what you may wish to hide or show: upvotes, downvotes, score etc
Title
Aha, thanks! I guess that concludes this thread, as I don't really expect to get a dev chiming in explaining why.
It's not my preferred way of handling it but I don't have the energy to make a fuss. I guess if I click a link that needs to be http, I'll copy it to a browser, and if I post one I'll remind others to do the same. Probably won't come up often enough to care about.
At least you've satisfied my curiosity as to what was going on 😀
Edit: I was repeatedly told while trying to post this comment that the request timeout had expired. When the error stopped appearing, I had posted 4 copies of this message. I have deleted them but I apologize if they still spam your inbox as [deleted] or something.
For example, http://xkcdsw.com is an archive of fan-edited comics, while https://xkcdsw.com is some kind of crypto site.
That's not how URLs work. If that's the behavior you're experiencing, you likely have been the victim of malware/a virus.
The first part of the URL is the scheme, which indicates the protocol that the browser must use to request the resource (a protocol is a set method for exchanging or transferring data around a computer network). Usually for websites the protocol is HTTPS or HTTP (its unsecured version). Addressing web pages requires one of these two, but browsers also know how to handle other schemes such as mailto: (to open a mail client), so don't be surprised if you see other protocols.
Can you access https://catbox.moe/faq.php ? There's a connectivity issues section with different explanations depending where you're connecting from.
The next lemmy release has this PR, which will make how you display votes fully configurable. I based this temporary default off of 3 other lemmy apps, which use the Score + Upvote Ratio method.
My recommendation: Revert your app version to alpha v60 for the partial change that looks closest to the latest. See below:
Screenshot
The options are implemented in Jerboa between showing/hiding scores, upvote percentage and upvote/downvote ratio. You can build your own where you set your default option to what you want. Strangely, it was decided by @[email protected] that it would only show when 90% or below, I disagree it should show as long as is it's less than 100%.
I think it has to do with coordinating some back-end lemmy change to make it a lemmy user account setting but Jerboa nor Lemmy.ca have this implemented yet so there's no in-app way of adjusting it currently. It's too bad.
Refer to Jerboa issues/PRs 1378, 1400, 1402. Lemmy PR 4449/4450 adds this to back end but this was 5 days ago, so it's definitely not functional for anyone on the latest minor release version. Imo it should have defaulted to the old behaviour.
Looks like this for me:
So yes, smth does seem to be missing.
I really really hate this change.
Is there 20k people on the fence, or just one person that disagrees... You can't tell anymore.
Support for this in core Lemmy has been discussed many times. There's an open issue for it that's been gathering dust for a while. Some apps already implement this on the client side I think, not jerboa though.
https://reddthat.com/nodeinfo/2.0.json
Reddthat instance doesn't have the correct version set in their nodeinfo. It is empty, this is important for federation (and for Jerboa to know which API implementation that it needs to use). Now I don't know if this is a Lemmy problem or just a problem with just that instance. But Jerboa behaves as expected
How it should be
@[email protected] posted this previously:
In 61 a migration is borked, this caused some appsettings to be switched around. So previsously if you had custom tabs enabled, this would enable the prevent screenshots setting.
Now I fixed this, so this means those who changed them will see them swap again. And those who haven't upgrade yet won't notice anything. There should be release tomorrow which address all the bugs introduced in this update. Sorry for the inconvenience!