Kbin magazine threads do not federate until interacted with. #875

Update: it did get to fedia but doesn't appear to have federated to any Lemmy instance.

update 2: I just checked some of my magazines hosted on fedia over on kbin and the only posts which appear to have federated are from my fedia account.

As you mentioned in the thread in kbinMeta, fedia was down for ~30 min when you were trying this.

To take a look at one of the more active magazines on fedia...

https://fedia.io/m/FloatingIsFun/newest
https://kbin.social/m/floatingisfun@fedia.io/newest
https://lemmy.world/c/floatingisfun@fedia.io?dataType=Post&page=1&sort=New

they're sorta matching up, of course the latest is missing, perhaps that happened during the downtime, lemmy world is missing one I notice

I do want to mention rabbitea.rs is running an older version of lemmy, there were a lot of changes to federation since 0.17, it may be worth talking with your admin about updates. Especially since, at least according to fedidb, registrations are disabled which I thought there was a bug with turning off signups and federation, though the issue on it seems to be about private instances which may be different than sign ups closed, I just remember lemmy world trying to turn off signs ups pre-0.18 and issues coming up

Edit: Oh I said latest was missing from that magazine but it just popped up on kbin and lemmy.world 1 hour later. Perhaps fedia has some queue issues, but it does seem to be working, albeit slowly.

I could understand that being a problem for getting updates, but this particular post originated from there, got to kbin.social and didn't make it any further. I'll ask about updates anyway, of course.
The other post I was alluding to was in ukdtt@fedia.io - it's the licence updates one originating from feddit.uk. I can't see this on rabbitea.rs or lemmings.world (I only subbed from there recently but before today, currently there are no posts at all showing, whereas I'd expect at least that one). lemmings.world is on 0.18 so I think that means the version is unlikely to be the cause.

For the ukdtt one I've been trying to go over the process involved when one instance posts to remote magazine, how the update gets to other remote instances.

https://fedia.io/m/fedia/t/143235/Nothing-posted-from-outside-Fedia-federates-out#entry-comment-750681

The flow described by this person seems to indicate someone posting on feddit.uk to ukdtt@fedia.io, feddit.uk is responsible for sending it to rabbitea.rs/c/ukdtt@fedia.io, rather than fedia itself. That makes it seem like it's completely lemmy -> lemmy and fedia (kbin) is not involved at all.

Of course, that's only if this is accurate, not saying it isn't but I certainly am not familiar with activitypub enough to know for sure. Or perhaps there is another issue, like feddit.uk being made aware of the subscribers of the destination magazine.

I did check earlier and both feddit.uk and rabbitea.rs are aware of each other and not blocking either one. The other odd thing is even if I go to rabbitea.rs and try to pull in the original url https://feddit.uk/post/771973, it doesn't appear to work; but I'm not super familiar with lemmy so not sure if that's allowed like how it works in mastodon/kbin

I searched for that URL and it pulled it in, so that bit is working at least. I think you need to be logged in to do remote lookup.

I've just experimented with this some more, having posted an article which didn't even reach the hosting instance.

From instance A, article posted gets to M. It doesn't appear to get any further UNLESS that article is subsequently commented on by a user of instance M edit: or interacted with any other way, even upvotes are fine. I also tested from instance B without commenting and the same thing happened.

A in this case is rabbitea.rs, B is feddit.uk and M is where the magazine is hosted on fedia.io (the magazine is ukcomedy@fedia.io if you want to see the test articles before I delete them)

Also of note is that I accidentally posted from the wrong account, deleted the article but it's still visible on fedia.io, so deletions don't appear to be federating.

I've been trying to figure out what the expected behavior is with regard to content propagating. I think I understand the concept of subscribing on a given server, then future content should be available. I am pretty sure stuff is getting missed even with this in place prior to posts/comments being made.

Sometimes you can get a specific post, either it shows up by itself or because you ask for it, but the comments don't show up. Or only some of the comments show up. Sometimes you can get them by searching the URL but sometimes you can't. If you can get it, it doesn't fetch the rest of the thread's comments, only the particular one you ask for. Mostly this is happening with smaller communities so experimentation is difficult because the pool of posts/comments is limited.

Do kbins have a list of instances they are supposed to be federated with? The lemmy sites have this in the footer so at least you can know if there is a block in the way. If I grok properly, I would have check:

• federation/block status

• software version (at time of posting and/or at time of retrieval?)

• downtime during or subsequent to posting

of the following:

• the home instance of the community in which the item ought to appear

• the home instance of the person who made the post/comment

  • maybe: home instances of subsidiary items, like a reply

• the instance I am looking at

to determine if there is actually an error. Need a spreadsheet lol

It appears comments might have the same issue. A mastodon user commented on an article but this wasn't visible from Lemmy until I prodded it by upvoting.

I joked about a spreadsheet. But really we need a form where you can input details and say whether it "should" or "could" be visible.