Lemmy shows less content than there is coming from kbin
I've tried a few communities between lemmy and kbin this way.
When i'm logged into lemmy(or not) and view some kbin community it shows me there is either scarce community activity or none at all. While if i visit the original community on kbin it shows a lot more.
The example with the pc gaming community works well. lemmy shows the last new post was 13 days ago. and kbin shows multiple posts made only 3 hours ago.
Another example: Stargate through lemmy shows 0 posts while kbin has low activity but does have posts 3 weeks ago.
Can somebody confirm this? Is this a bug?
You are viewing a single comment
This could be a federation issue with Lemmy.ml and Kbin.social. On Lemmy.world I can see four posts:
https://lemmy.world/c/stargate@kbin.social
I've heard content may not be completely federated unless someone from my instance subscribes to that community or to that instance. Could this be the case here?
In any case i have to always double check because i can't fully trust my own instance to show real community activity.
That is true, at least one person needs to be subscribed. I assumed you were subscribed.
No. I was browsing for communities, seeing how active they were in the process. One website showed the community being official coming from reddit but lemmy showed no content so I was very surprised with these results.
Thatโs the problem then. If you subscribe, then all the posts will appear, but the comments will only appear from the time you subscribed.
Iโm subscribed to my kbin Battletech community from a few of my Lemmy accounts and it still doesnโt work right.
Hi there! Looks like you linked to a Lemmy community using an URL instead of its name, which doesn't work well for people on different instances. Try fixing it like this: !stargate@lemmy.world
Hi there! Your bot isn't taking into account URLs that have an @ symbol in them.
Bot feedback: that wouldnโt work in this case
@rikudou@lemmings.world
Ye bot is broken matey
Yes, I noticed, I'll be fixing that today. Thanks for the report!
Edit: It's been fixed.