this post was submitted on 11 Jun 2023
16 points (86.4% liked)

Memes

45612 readers
622 users here now

Rules:

  1. Be civil and nice.
  2. Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] Terevos@lemmy.ml 1 points 1 year ago (1 children)
[–] Barbarian@sh.itjust.works 10 points 1 year ago (3 children)

No. It works. You can subscribe to any Kbin magazine on Lemmy just like it was a Lemmy community

[–] mrmanager@lemmy.today 3 points 1 year ago (1 children)

It doesn't work for me actually.

[–] thegiddystitcher@beehaw.org 1 points 1 year ago

I believe Kbin isn't federating properly at the moment because everything is on fire over there due to growth. But once that's sorted out, then you'll be able to do this.

[–] SuitedUpDev@feddit.nl 3 points 1 year ago (1 children)

I just tried it on my instance, not getting any results however, I believe it probably has something to do with the server capacity (on either ends).

[–] Barbarian@sh.itjust.works 2 points 1 year ago (1 children)

Just tried it myself on my instance. Seems to be an issue with certain magazines. Did a search for the full URL of https://kbin.social/m/gaming with all settings on "All" and it worked. https://kbin.social/m/tech did not though. Not sure why.

[–] SuitedUpDev@feddit.nl 3 points 1 year ago (1 children)

Probably growing pains. The federation is obviously happening between those servers but the exchange of data only happens if you actually if a user subscribes. But probably Kbin has some servers issues.

I've been seeing server errors at Kbin, every time I tried to look it at.

[–] thegiddystitcher@beehaw.org 2 points 1 year ago (1 children)

Yep they're on fire, husband was on there but has temporarily moved back to Lemmy since Kbin isn't federating. They'll sort it aaaaht I'm sure.

[–] SuitedUpDev@feddit.nl 1 points 1 year ago (1 children)

Yeah, it's just a matter of time. I saw the same thing happen during the initial wave of the Twitter migration.

All instances were smoking... Notifications took 10 minutes to arrive, messages sometimes even hours 😂

[–] thegiddystitcher@beehaw.org 1 points 1 year ago (1 children)
[–] SuitedUpDev@feddit.nl 1 points 1 year ago

Definitely! 🍿

[–] Terevos@lemmy.ml 1 points 1 year ago

It appears to work for some communities, but not others. I'm guessing it's not syncing properly