this post was submitted on 27 Jun 2023
19 points (69.4% liked)

Jerboa

10306 readers
9 users here now

Jerboa is a native-android client for Lemmy, built using the native android framework, Jetpack Compose.

Warning: You can submit issues, but between Lemmy and lemmy-ui, I probably won't have too much time to work on them. Learn jetpack compose like I did if you want to help make this app better.

Built With

Features

Installation / Releases

Support / Donate

Jerboa is made by Lemmy's developers, and is free, open-source software, meaning no advertising, monetizing, or venture capital, ever. Your donations directly support full-time development of the project.

Crypto

Contact

founded 2 years ago
MODERATORS
[email protected]
19
Jerboa is not trustable with these bugs, seems like any PR gets merged (self.jerboa)
submitted 1 year ago* (last edited 1 year ago) by catlover to c/[email protected]
25 comments fedilink hide all child comments
 

https://github.com/dessalines/jerboa/issues/891

If you downvote any post in jerboa 0.0.35 you actually upvote it. Seems like anything gets merged? If this goes on like this, there could be a lot of trouble

Edit: Thanks to quick reaction seems like a simple an quick fix. I hope that things will be fine in the future

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 15 points 1 year ago (2 children)

Without a link to the PR you refer to this is a bit of a vague ticket. Did it work in a previous version? And if so, which version?

Also I think your tone is not constructive and you have to keep in mind that this is all open source software being quickly developed to deal with the huge influx of new users. It's good to create github issues for these things, I also agree that it's a silly bug if true but remember the human on the other side, they owe us nothing :-)

[–] catlover 0 points 1 year ago (1 children)

You are right, I should have tested it on an older version of jerboa. I hope that the developers or other users can prove me wrong

[–] ahoy 4 points 1 year ago

git blame shows this bug was introduced in v0.0.35 when they moved from websockets to http.