Ask Malaysians about anything!
You mean community from another instance right? It's a bit wonky right now, but you can directly go to that community by typing in the link, like for example "monyet.cc/c/gaming@beehaw.org" for the Gaming community at Beehaw
But if you wanna browse community, you can use this community browser to look for it.
Hope it help!
Ahh great. Thanks for the info. I just need a way to sub my communities.
Ohh, right, even if you directly linking to that community, it takes a few try for them to connect.
To add to crabby's response, the trick is to put the full URL into the search bar, and then when it says no results found, just chill for a minute and a link will come up! I mean literally up to a minute btw, though it's often faster. Guide here, right at the bottom.
Lemmy is still very janky but they're working at a crazy pace right now. We're hoping to update monyet.cc to 0.18.1 this week, there's a ton of bugfixes and new features coming!
if 0.18.1 is still at release candidate stage by the end of this week, will you still upgrade or will you wait for it to be properly released?
lots of instances have already upgraded to one of the release candidates. so, if you've already set aside some time for doing the upgrade, perhaps you could consider going ahead with it.
even though all the 0.18.1 milestones have been reached, something else cropped up.
my impression is that the developers want to revert that change and get 0.18.1 released, but quite a number of instance admins (who have already used the release candidates with that change included) are against it, so discussions will continue, and 0.18.1 may be delayed until a conclusion that satisfies most parties is reached.
Thanks for the info!! I can't commit for the team on the spot, but we'll give this very serious thought if there's nothing by EOW. Upgrading to a well-tested RC seems like a solid idea - good risk vs reward. Bit annoying that there's no lemmy-ansible RC though; we've been trying to stick to the vanilla upgrade path so far as we've been constrained on dev capacity. (But this might change soon, stay tuned...)
if in the end, the upgrade to lemmy 0.18.1 doesn't happen this week, perhaps you could consider upgrading pict-rs from 0.3 to 0.4 (here is the migration guide).
at least with that done, you'll have one component upgraded, so you don't end up with a very big upgrade to do all at once (I mentioned in another thread that they changed the nginx config too).
edited to add: lemmy 0.17.4 was already using an embedded pict-rs 0.4, so I take that to mean there are no api incompatibilities (at least for the apis lemmy uses) between pict-rs 0.3 and 0.4, and it's just that the lemmy-ansible maintainer decided to coincidentally upgrade lemmy 0.18.0 and pict-rs 0.4 together.