Jerboa @lemmy.ml Dessalines @lemmy.ml 5 mo. ago

Jerboa v0.0.70-alpha Release

github.com Release Jerboa v0.0.70-alpha Release · LemmyNet/jerboa

What's Changed Fix initial page_cursor by @MV-GH in #1553 Removing renovate schedule. by @dessalines in #1555 Update plugin com.android.test to v8.5.0 by @renovate in #1561 Update plugin com.andro...

22 comments

Not going back to Jerboa unless the basic feature of searching contents other than just communities is implemented. I find this fundamental feature sorely lacking in Jerboa while every other app around there have this.

\

https://github.com/LemmyNet/jerboa/issues/27

\

Kind of surprising, because this is pretty basic feature, and has been open for over two years.
Getting "Posts failed loading, retry" button after scrolling to the end of Subscribed feed (does not matter if Scaled, New).
Verified across multiple instances.
E: And the button does nothing, specifically, after clicking it it vanishes and comes back (the loading bar does not appear). No problem in All.
- I see that also, its a bug.
  
  Edit: https://github.com/LemmyNet/jerboa/issues/1596
- k, just did a release with this fixed, thanks to mv-gh for this one.
  
  Was just checking the issue out and seeing MV-GH had a fix ready, awesome work and thanks for the quick release!
- Is there a way to revert to an old version of the app? This issue is annoying enough for me that I'm now temporarily on Voyager. I don't hate it, but I'd rather be on Jerboa.
  
  If you installed through f-droid, you can install older versions.
Update plugin com.android.test to v8.5.0 by @renovate in #1561

Was it properly checked for backdoor injections?
- Is there a reason you're suspicious about that particular dependency, or are you just asking about dependencies in general?
  
  I'm worried about that one specifically. Dependencies in general can be suspicious if they come from untrusted sources but in that case it's suspicious by being related to testing (like the xz thing was) that shouldn't even be in a released app anyways.
- What's the context there? We update dependencies very frequently.
  
  The context is the name of the dependency and its very questionable purpose.
- If you have a security concern you should raise this with Google using a minimal working example to demonstrate yourself.
  
  Do you have a genuine concern and can you provide a working example of the attack surface in a repository that you can share?
- What is the "proper" way?
  
  Check the code for suspicious lines and then check the compiled app for network traffic etc

You've viewed 22 comments.