@Albertkinng Not sure about your particular client, but through the #mastodon website you can follow #kbin users by searching @kbinname@kbin.social
such as @unofficial_kbin_guide. You can follow magazines the same way @magname@kbin.social
like @kbinMeta.
In #mastodon, you can search for all #kbin users by searching @kbin.social
. And of course if you follow hashtags in #mastodon, #kbin posts that include those hashtags will be pulled in.
Let me know if this work with your client. But great question, I will add it to the FAQ.
This is great.
Thanks!
I’ve not created a magazine but I’ve been curious about how Mods associate microblog posts with the magazine. I’m assuming that’s through the “Tags” tab you describe on the moderation page.
Yep. Any tags associated with a Magazine will pull in those posts that include those tags.
one is the distinction between upvote/boost
Upvotes (Favorites) are like reddit upvotes and boosts are like Twitter’s retweets. So when you favorite something, you are saying, “Hey, Fellow Subscribers, this is interesting.” When you boost something, it is like saying, “Hey Fediverse, check this out!”
how to subscribe to an entire instance
To subscribe to an instance:
https://kbin.social/d/<>
. For example, https://kbin.social/d/lemmy.world
. Either of this methods will land you on the instance’s domain page.Thanks for these questions! I will add them to the Guide.
I just launched https://unofficial-kbin-guide.surge.sh/. Hopefully it helps! If you feel something is missing you can make a request at https://kbin.social/m/unofficial_kbin_guide.
The Devs are hard at work, there is just a lot for them to do. You can see the most recent PRs here. You can raise an issue here for more visibility:
https://codeberg.org/Kbin/kbin-core/issues
@Levsgetso Thank you for your feedback. The page has been updated.
The Unofficial Kbin Guide is now available! https://unofficial-kbin-guide.surge.sh/
Let me know of any feedback, update requests, or corrections.
#kbin #kbinmeta #kbinhelp #kbinguide
@melroy @ernest I do not have a codeberg account. I would have to get that set up and get back to you. As for the best place for the docs to live, I would say that you both are right (cop-out answer, I know). Here’s why:
To be fully searchable, but only bring relevant guide results the docs should be their own package (I really did not see a way off hand to search the codeberg wiki). To engage the users the docs should be easy to navigate, easy to search, and easy to read. As for the wiki, I am not super familiar with codeberg, but the wiki does look limited. I am not sure if Codeberg comes with a “pages” option like github.
However, https://unofficial-kbin-guide.surge.sh/ is built in markdown using mkdocs material. So, the current repo https://codeberg.org/Kbin/kbin-docs could be repurposed to hold these files and set up to deploy on pr merge. Take a look at https://docs.codeberg.org/ and https://codeberg.org/Codeberg/Documentation for example. I would not tie doc updates with code releases so we do not have to wait on code releases to deploy doc updates.
I would advise to serve the published docs outside of codeberg since not all (maybe even most) of kbin users are not necessarily developers. So, I would serve the content somewhere like https://kbin.pub/en/docs or at https://kbin.social/docs. If choosing kbin.pub we will have to make a clear distinction between “user” docs and “developer/server” docs. Also, if using kbin.pub … then the help column on kbin.social (as well as other kbins) must be updated to point to the new docs.
I am happy to help. Let me know your thoughts.