Dont think you can, in jerboa, for now
this post was submitted on 10 Jun 2023
10 points (100.0% liked)
Jerboa
10298 readers
16 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
- Open source, AGPL License.
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
- bitcoin:
1Hefs7miXS5ff5Ck5xvmjKjXf5242KzRtK - ethereum:
0x400c96c96acbC6E7B3B43B1dc1BB446540a88A01 - monero:
41taVyY6e1xApqKyMVDRVxJ76sPkfZhALLTjRvVKpaAh2pBd4wv9RgYj1tSPrx8wc6iE1uWUfjtQdTmTy2FGMeChGVKPQuV - cardano:
addr1q858t89l2ym6xmrugjs0af9cslfwvnvsh2xxp6x4dcez7pf5tushkp4wl7zxfhm2djp6gq60dk4cmc7seaza5p3slx0sakjutm
Contact
founded 2 years ago
MODERATORS
Really? So how would I interact with that community? A browser with another account on that server?
A web browser, yes, but you should be able to use your sopuli.xyz account just fine. For example, to get to the Jerboa community we're having this discussion in, you would go to the URL https://sopuli.xyz/c/jerboa@lemmy.ml in your web browser. What that does is basically tell sopuli.xyz to show you the community named "jerboa" hosted on the domain (instance) named lemmy.ml. Without the @lemmy.ml, it would look for /c/jerboa on sopuli.xyz, and get a 404 because it isn't hosted there.
If you're signed in to sopuli.xyz on that web browser, you can subscribe to the community from there, and then you would be able to get to it from within Jerboa. My account is with beehaw.org, so if I wanted to do the same, I would go to https://beehaw.org/c/jerboa@lemmy.ml. It's a bit weird, but not that complicated, and it will quickly seem normal once you get used to it.
All that said, one thing I've noticed is if a community from a different instance than the one you're using has 0 posts, it will 404 if you try to go to it from your own instance, and it also won't show up in a search within Jerboa. For example, animanga@lemmy.ml has 0 posts as of this writing, and will 404 if I try to view it from Beehaw or sopuli; it only shows up if I view it directly at lemmy.ml/c/animanga, which doesn't help much since I don't have an account with lemmy.ml.
As a workaround, if you login with your account on the web site you could subscribe to your desired communities and then they'll show up in jerboa.
To view a community on another server from your server, in the search box put "!community@otherserver.com" for example !foss@beehaw.org and after a few seconds it should show up and then you can click on it and subscribe.
Use the search from a browser instead, yes
My solution so far: search on browse.feddit. Copy complete link. Go the web interface of your instance. Go to search and there select search ALL on ALL instances, enter the complete link. Click the found result and subscribe from the sidebar.
I think the proper behavior would be that two instances are federated, a user would be able to see all communities in both.
It's going to be especially hard for users on a small instance to find content if they, or some other person on that instance, has to search for it first.
If I type "!coffeeaddicts" into the search bar, it should show all communities in all instances that are federated with my own that match that query. A person running their own instance would have to search every single community and wait however long for it to populate.
I put "jerboa@lemmy.ml" in the search area, it took a while (a few minutes), but eventually it showed up. I think it takes a while to sync/federate in the background if you're the first person on the instance to subscribe to that community.
view more: next ›