EDIT: I believe actually it's because the thread is of type Link. Did you create it as type "Link?" If so, try recreating it as type "Thread."
this post was submitted on 28 Jun 2023
12 points (100.0% liked)
/kbin meta
639 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
I created a new "article" test post (https://kbin.social/m/longboarding/t/108991), and it was immediately federated to Calckey, so it looks like you were right! Thanks for the help!
Do you know if a bug report is already open for that issue?
You're welcome! Sort of. In general, Calckey and others (Mastodon as well) don't handle non-Note-type data very robustly. Those are used a lot with groups and Calckey doesn't really understand groups very well. It's know and it's on the road map, but I don't think this one example is a high priority at the moment (Link-type threads)
Huh. I'm experiencing the same thing. I can pull this post, but not the one you've linked to, from my personal Calckey instance. How odd.
The strange is: I was able to search for and find the current article from Calckey. But it still doesn't work with the other posts I created in magazines that I created (for instance it doesn't work with this one: https://kbin.social/m/longboarding/t/12309).
I don't know why the same action gets different results.
If your Calckey instance has Authorized Fetch/Secure Fetch enabled, this might prevent pulling, but I haven't tested that exact scenario yet.
But what is strange is that it works for some posts, and doesn't work for some others. For instance I could search for and find the current article.
I edited my reply, but I believe it's because the type is a Link, not a Thread. Can you try recreating the thread but as type "Thread?"
view more: next ›