this post was submitted on 19 Sep 2023
11 points (100.0% liked)
/kbin meta
4 readers
1 users here now
Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign
founded 1 year ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
@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.
@Arotrios @readbeanicecream @daredevil and it answers my question: it is not the full server firehose, just the posts already known to the kbin server