264
My kitty
(programming.dev)
That's already been fixed, and will be part of 0.0.51
The full sentence is This account (%s) is being verified
It's verifying that everything is correct, acc not banned, JWT works, instance alive, ...
It only shows that, if you are attempting something that causes it to be verified while already verifiying that account.
Nbd, should ve resolved itself in a few seconds
Jerboa is just showing you the error it got from your instance. I can look into the source code for Lemmy but that won't be for a while.
"community ban" is not something that is coded into Jerboa as far as I know.
What "embed links"'? Those in markdown? or all links opening externally? Either of way I can't reproduce this. We did make some minor changes regarding opening links externally so that Firefox private tabs are supported. What browser do you use, what settings do you have for custom and private tabs. What version of jerboa. Android/phone info. Basically more info = better
That feature doesn't exist yet.
But there are some considerations to be made in implementing this.
Like the images that shouldn't load, do we hide them, do show a black shade or placeholder. If so which placeholder because i doubt that you want to see Jerboa icons everywhere instead. If we hide them there there is no difference between postviewmode largecard shortcard so do we keep showing both? Someplaces it's probably better to hide them like the avatar.
This will most likely be part of a much bigger "data saving" feature where you can enable loading images(previews/comments/avatars/banners) on WiFi only/all/never.
And it be pretty cool if you could granular select which images you do and don't want to load. But there is no UI for that yet. So that will have to be designed too.
We cannot solve that issue on our end. It is a problem with the toolkit that we use, see https://issuetracker.google.com/issues/294102838
You can disable text corrections if you want a work around
https://github.com/dessalines/jerboa/issues/194#issuecomment-1635789189
Their approach requires no additional work as it's fully automated. That's the biggest reason.
I wrote the routes manually which took some time. And it still needs quite some work for the summaries and descriptions
It is caused by a bug introduced in lemmy 18.3
https://github.com/dessalines/jerboa/issues/1109
I have a fix for it already
That's a lemmy bug, not Jerboa. I reported the bug already. We don't get a choice as frontend on what gets returned once that option is set.
That list gets generated based on the lemmy instances tracked by fediverse.observer site that have a monthly active user amount greater than 50.
view more: next ›
testAccount
joined 1 year ago
The swipe gesture feature uses a new experimental component. As far as I am aware we can't configure the sensitivity. We have decided to have it off by default. We also fixed the swipe direction not being aligned with the description.