Ah yes, the Bobby Tables approach.

Huh, interesting. I guess now I know where BeOS / Haiku got its inspiration for how their windows look.

Maybe I’m bitter, and I know a lot of people wouldn’t agree with this, but honestly? I think the non-corporate part of the Fediverse should just assume malice from the get go and preemptively defederate from whatever Meta put out. That way nothing’s changed - Meta would essentially have a private / proprietary / isolated network, as far as users are concerned (much like Facebook already is), and even if the Fediverse will see less growth in the short term because of that, there will be no confusion on where everybody stands.

I don’t know about Jerboa, but this happens on the web too, and it’s usually on more fringe / less popular communities. There’s a workaround that works for me, I mostly heard about it from someone else here on Lemmy. It’s not great user experience, but it works.

• Go to the search function;
• Type in the name of the community, hit enter;
• Select “Commnities” on the search type dropdown (yes, you have to do it after submitting the search as per the previous steps, seems like another UI bug);
• If after doing the above the community is not found, then here enters the magic sauce:
  • Change the search terms so the community is fully qualified / keyed as !communityname@instance.server, all in lowercase. So, for example, if you’re looking for the “kreisvegs” community on feddit.de, type !kreisvegs@feddit.de on the search field;
  • Submit. It still won’t be found. Give it a few seconds, change back the search terms to only the community name (without the instace and “!” at the start). Submit. It should now show up.

You may have to repeat step 4 onwards a couple times, sometimes.

My uneducated guess as to what’s happening: the federated communities listing is probably cached on the instance, and by default it’ll only look for communities cached on your instance. My guess is that federated communities only gets into the instance cache when members of the current instance have searched / subscribed to that community. Typing the fully qualified community name on the search field (which is the tip I got from someone else) apparently forces the search function to actually contact the external instance to look for the community, instead of looking in the cache, but that can take some time, hence why you should wait a few seconds on the 6th step. That guess could also explain the problem also happening on Jerboa, since the problem would be server-side.

I agree. It’s just people being lazy and resistant to change. The irony is that it was exactly those “big techs” that bred this kind of behavior on them, now they turn around to criticize those big techs, but have no spine to do what actually takes to change that, so they keep on taking the abuse.

I think what he’s getting at here is people asking him about building an alternative platform to Reddit - much like Lemmy, Kbin, Tildes, etc. are - as opposed to an app for an existing alternative platform. I’ve seen poeple buzzing about that on some of those threads about Apollo on Reddit. Those people are so in denial that I couldn’t conjure to effort to point how ridiculous that idea is. Some people did, and were quickly shut down with the usual complaints (fediverse is confusing / does’t work, etc.)

Maybe not a crazy breaktrough in computing power, but I wonder how much of a performance boost that much cache can bring.