Just Curious: How long does it take for a kbin post to reach mastodon?
Just Curious: How long does it take for a kbin post to reach mastodon?
Or a thread to lemmy. Basically, how long does "federation" take?
(I am not sure if I am saying that correcly, but you know what I mean.)
You're viewing part of a thread.
Not sure what's going on with the kbin.social/d/ view of urusai.social, but I was able to find posts (not threads) here:
https://kbin.social/search?q=urusai.social
This led me to @neatchee, who is the instance owner. You might try following them, but I agree, that's an odd bug.
Oddly enough, even users I have already followed do not have their content federated to these magazines at times, even though I have checked their history and seen them use the tags I've assigned to the magazines. I could simply be doing something wrong, but I'm not sure what it is.
Yeah, posting to Kbin from Mastodon instances is a challenge. Kbin filters and tries to assign incoming hashtags to existing magazine hashtags.
If a post contains a hashtag that is taken by another magazine, that magazine usually gets the content instead of yours. Your magazine's hashtag has to appear first in the text. Your Japanese forum is probably catching all of the #japanese posts before they get to LearnJapanese.
Second, it's random which of your magazine hashtags will pull content and from who. The order of the hashtags doesn't appear to affect this.
The only way to ensure a post gets from Mastdon to Kbin or Lemmy is to put
@yourmagazine@kbin.socialin the post tag. This will make sure it shows up on Lemmy, and will get your post to the Kbin Microblog of the magazine 90% of the time. If you want to be extra sure, do it like this:@yourmagazinename@kbin.social #yourmagazinename (then any following hashtags)Hopefully the update will clean this up a bit.
@Arotrios @readbeanicecream @daredevil fwiw I can confirm that URUSAI! does not have any restrictions on kbin.social. And I'm able to load your kbin profiles from our Mastodon instance without issue.
I'd need to look into how the /d/ implementation in kbin works to know more.
But if you toss me the URL of a mastodon instance that DOES show up there without issue I might be able to learn something :)
@neatchee @daredevil I think perhaps someone has to post a link hosted on your instance for it to appear. For instance this works:
https://kbin.social/d/mastodon.social
but smaller instances like this:
https://kbin.social/d/pagan.plus
...don't seem to, generating a 404 because no one has created a link or thread back to a pagan.plus post (although their users post over to kbin often). Possibly posting link (in the url field of Add a Link on Kbin) to an urusai.social hosted post will do the trick.
@Arotrios @readbeanicecream @daredevil this sounds very plausible. Unexpected, but it would make sense that kbin's /d/ path is showing you the directory of content from your server's local cache and not querying the target server.
Which kinda makes sense, honestly: since that feature is trying to list everything kbin knows about from the target server, populating it for the first time would definitely cause a significant load on that instance
@daredevil @neatchee - Looks like the linked post is what did the trick. I posted here to the Fediverse community to let them know about your instance (it's pointed at your pinned intro post).
As such, this link is now working for daredevil:
https://kbin.social/d/urusai.social
And will allow subscriptions.
Fantastic, this has been very enlightening. I appreciate your time and effort.
@Arotrios @readbeanicecream @daredevil and it answers my question: it is not the full server firehose, just the posts already known to the kbin server
@Arotrios @readbeanicecream @daredevil now I'm really curious how it works when you subscribe to a server. Is it pulling in that server's public and local feeds? Or is it only showing you posts from users on that server that your instance already knows about
I'll keep an eye on our instance of urusai.social and let you know in the future
Only that it knows about to start, but I think that once it gets subscriptions to the domain, it starts pulling more automatically. I could be wrong, however - I'm not sure which activities aside from posting are federated.EDIT: I was wrong - the domain only grabs Threads, so Mastodon posts will likely not show up this way. They may get indexed if they're sent to a kbin magazine using the
@magazinename@kbin.socialformat
This led me to @neatchee, who is the instance owner. You might try following them, but I agree, that's an odd bug.
Thanks, it's worth a shot.
If a post contains a hashtag that is taken by another magazine, that magazine usually gets the content instead of yours. Your magazine's hashtag has to appear first in the text. Your Japanese forum is probably catching all of the #japanese posts before they get to LearnJapanese.
So it seems as if @japanese gets priority of the #japanese hashtag due to it being the name of their magazine? Or possibly that they had the hashtag first? I hope multiple magazines are able to federate the same hashtag eventually. @Acala, the admin of @japanese has been inactive for the past few weeks. That's rather unfortunate, as the magazine has no published threads in addition to an inactive moderator.
Second, it's random which of your magazine hashtags will pull content and from who.
That's unfortunate, but helps to clear things up.
The only way to ensure a post gets from Mastdon to Kbin or Lemmy is to put
@yourmagazine@kbin.socialin the post tag. This will make sure it shows up on Lemmy, and will get your post to the Kbin Microblog of the magazine 90% of the time. If you want to be extra sure, do it like this:
@yourmagazinename@kbin.social #yourmagazinename (then any following hashtags)This has been very informative, thank you. I'm probably not gonna bug #mastodon users to add this to their posts, but if I ever decide to use mastodon myself I'll keep this in mind.
Hopefully the update will clean this up a bit.
Agreed, kbin as a platform is the most interesting for me, and I hope to see things turn out well.