MV (Jerboa dev)

Yes but now it must wait for acknowledgement of a request (activity), before sending the next one. If one request takes 333ms means you can do max 3 requests per second. Now big instances like lemmy.world have activity above that so instances too far will perpetual lag behind

Mostly because Lemmy has a hard time keeping up with the federation

https://github.com/LemmyNet/lemmy/issues/4529

That’s already been fixed, and will be part of 0.0.51

Alright we will be dropping this feature until we make a proper swipe to exit

Did you try logging in again with that account?

If it keeps happening after that what instance and what account is it?

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

Can you also test if the problem is still fixed with this build and that the flick to exit works in the ImageViewer

https://github.com/dessalines/jerboa/files/12618555/fix_zooming_jerboa_debug.zip

np

Can you also test if the problem is still fixed with this build and that the flick to exit works in the ImageViewer

https://github.com/dessalines/jerboa/files/12618555/fix_zooming_jerboa_debug.zip

There is no real order of which issues get done. Everyone is welcome to contribute any feature/fix they find important.

I just work on things I find have priority which is mostly bugs first. The next big feature is probably backwards compatible API which is a huge amount of work.

There is a issue for the creation of communities. Already but it doesn’t specify exactly it. Like where do we add this in UI, do we make a fullblown screen or just a popup. Which logic for showing this creation menu. Some instances don’t allow users to make them. etc

The setting makes it so that it open links in private/incognito tabs. So they won’t pollute your browsing history.

This update added support for FireFox. But there seems to be some issues in other browsers. Were you also using Chrome?

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.

It didn’t enable by default in this update. But I think when it did get added it was with default enabled but that was a while ago. I can take look at changing this default.

That issue with firefox is not one caused by Jerboa. So that would need to be reported with FireFox. The only change we did was add support for FireFox.

Also does it work if you disable that setting?

And what about custom tabs?

Settings > Look and Feel > Scroll down

The update you are talking about, is it the latest 0.0.46?

In settings do you have custom tabs or private tabs on? (in Jerboa not chrome)

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

The release on Fdroid does not contain these experimental changes.

Only the above builds

Could you test if you can still reproduce it in these builds?

I have modified some code to isolate the problem.

Release version of 46

Depending on how you installed it might not allow you to install this release version

Note replacing an existing install with this version, will probably delete your app info (it should tell you) use debug version instead if that is not wanted app-release_zoomable.zip

Debug version of 46 app-debug_zoomable.zip