Actually, no. If at least one user from your instance has subscribed to a community of another instance, that other instance’s communities show up in your search results (they are federated)… at least that is how it should work 100% of the time, but it doesn’t. In most cases, it doesn’t actually show all of the communities that would show up during a search, meaning the web UI would return a lot more results.
The method you’re using is actually a safe bet: specify the instace’s URL and don’t have to rely on whether that specific instance is federated with my instance, just search for communities there as well. That approach is easier if you actually have a link to the community which you’d like to add and the instance on which it resides. But, if you have no idea on what instance that community might reside, it’s easier to actually seach for it via the web UI, which I hoped would be implemented in an app sooner or later (having relevant results I mean).
Yeah I’m wanting to implement that into liftoff. That’s the main feature I’ve been wanting in apps.
To clarify this app is a resurrection of an abandoned Lemmy app, when this app was active Lemmy was not as popular and we didn’t have massive instances like Lemmy world. Working through this is a fun challenge but it’s also a user experience challenge. What instance are you having issues with?
Well, many, to be honest. I have a few accounts, 2 on sh.itjust.works and 1 on lemmy.fmhy.ml. Some communities appear in results on one instance, others don’t, and vice versa. If you try to open up the community via your instance (my.instance/c/community@another.instance), it just returns a 404 🤷. This happens on both lemmy.fmhy.ml and sh.itjust.works. For example, I can see and join the OpenBSD community from my account on lemmy.fmhy.ml, but not from either of my accounts on sh.itjust.works. I can see other communities on that instance just fine, but that particular community, no.
And this happens with a lot if other communities as well, the OpenBSD one stuck in my mind cuz I really wanted to be in that one with all of my accounts, but I can only be with just 1 account.
Oh, and the pending thing 😒. The pending communities show up in my feeds, yet they’re still marked as pending. Cancel pending, subscribe again, wait a few days… yep, still pending.
It’s buggy, I know, but it’s new and all new things are, so I don’t really mind. I was meaning to make a bug report regarding some of these bugs on Lemmy, just haven’t gotten around to it.
PS: All of the searches regarding the communities were done in the web UI, so it’s not a Jerboa bug, it’s a Lemmy bug.
Actually, no. If at least one user from your instance has subscribed to a community of another instance, that other instance’s communities show up in your search results (they are federated)… at least that is how it should work 100% of the time, but it doesn’t. In most cases, it doesn’t actually show all of the communities that would show up during a search, meaning the web UI would return a lot more results.
The method you’re using is actually a safe bet: specify the instace’s URL and don’t have to rely on whether that specific instance is federated with my instance, just search for communities there as well. That approach is easier if you actually have a link to the community which you’d like to add and the instance on which it resides. But, if you have no idea on what instance that community might reside, it’s easier to actually seach for it via the web UI, which I hoped would be implemented in an app sooner or later (having relevant results I mean).
Yeah I’m wanting to implement that into liftoff. That’s the main feature I’ve been wanting in apps.
To clarify this app is a resurrection of an abandoned Lemmy app, when this app was active Lemmy was not as popular and we didn’t have massive instances like Lemmy world. Working through this is a fun challenge but it’s also a user experience challenge. What instance are you having issues with?
Well, many, to be honest. I have a few accounts, 2 on sh.itjust.works and 1 on lemmy.fmhy.ml. Some communities appear in results on one instance, others don’t, and vice versa. If you try to open up the community via your instance (my.instance/c/community@another.instance), it just returns a 404 🤷. This happens on both lemmy.fmhy.ml and sh.itjust.works. For example, I can see and join the OpenBSD community from my account on lemmy.fmhy.ml, but not from either of my accounts on sh.itjust.works. I can see other communities on that instance just fine, but that particular community, no.
And this happens with a lot if other communities as well, the OpenBSD one stuck in my mind cuz I really wanted to be in that one with all of my accounts, but I can only be with just 1 account.
Oh, and the pending thing 😒. The pending communities show up in my feeds, yet they’re still marked as pending. Cancel pending, subscribe again, wait a few days… yep, still pending.
It’s buggy, I know, but it’s new and all new things are, so I don’t really mind. I was meaning to make a bug report regarding some of these bugs on Lemmy, just haven’t gotten around to it.
PS: All of the searches regarding the communities were done in the web UI, so it’s not a Jerboa bug, it’s a Lemmy bug.