this post was submitted on 23 Jul 2023
15 points (94.1% liked)

Jerboa

10135 readers
2 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 3 years ago
MODERATORS
 

Hi, I am wondering if there is any way to browse a specific instance and view the communities and info about that instance?

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

Oh this one, it needs to be able to search all instances. I almost never want to search a single instance. I don't even know or care which instance I happen to be commenting on right now. Its all seamless with federation

[–] marsara9 2 points 2 years ago (1 children)

Yes but what if you search and find a post that doesn't exist on your home instance? You'd be taken to a 404 page and can't do anything.

But I've got an issue on GitHub for this. And just raised a PR on Lemmy to support the changes I need for this. But a reminder, once you can search all instances you may encounter 404s opening the posts that you find.

[–] [email protected] 1 points 2 years ago (1 children)

I haven't had that problem.

Sometimes I need to reload the page, because it hasn't been indexed or something?

[–] marsara9 1 points 2 years ago

You don't yet because currently I limit the results by the home instance that you select. But once I fix https://github.com/marsara9/lemmy-search/issues/20 I can turn that feature off and return results from anywhere across the fediverse. The problem that happens here is that after that, you can search and it may find an old post that isn't on your instance so you end up getting a 404 Not found error opening that link.