Would it be acceptable in kbin etiquette to add a tag in at least one thread in a magazine I created, and when talking about stuff in other places that touch the same topic, I use the same tag there as well to "promote" the existence of the magazine?
@Damaskox I'd imagine it's alright, as long as you aren't doing so excessively. Other magazines/places might have a rule or disclaimer in the sidebar that will give you a rough idea on how they feel about it. In fact, I'd say that's almost encouraged in addition to being one of the features I appreciate the most about /kbin compared to lemmy or reddit.
@Damaskox The magazine tags work in a way that automatically adds content to it that someone has tagged, for example, on Mastodon. The magazine's name is automatically a tag. I've seen comments on this matter, and I'll be addressing it soon to improve the mechanism and provide a detailed description of its operation in the admin panel. So, for example, all posts tagged #books on the microblog will be included in the magazine "books," but you can add a tag like #novels in the panel if you want those tags to be included as well.
@jared I actually noticed that there was a graphical tab in the magazine settings where the image was added.
It was just in a different place than what I thought.
#kbinMeta Is it possible to submit a thread to a magazine hosted on a different instance? I wanted to post to a lemmy.world community but I can't get it to show up in the magazine selector on the add thread page. Is there syntax I am missing here or is it just not possible?
TL;DR: To create a new post anywhere in the Fediverse, you have to have an account on the host where you want to create it. (As far as I know anyway.)
To participate in comments is slightly different, and in many cases, a comment made on a separate instance (or even platform) will show up on the original instance, provided the admins of each have set up respective federation.
Nonetheless, this can also fail. Consider several people on, say, kbin.social all subscribed to the same Lemmy community on some instance or another.
They'll all see each other's comments as well as the Lemmy users' comments, and be able to interact, but if that Lemmy's admin team decides not to allow external comments to be visible, the kbin folks will be talking to each other and no-one at the Lemmy, even if their comments are in response to, and show up underneath, a Lemmy user's message.
That Lemmy user would be totally clueless unless they knew to access kbin.social and check. And no-one's going to want, or even be able, to do the rounds of all potential Federation sites to see if they have unfederated responses.
What would be nice is if it was possible to log in to one Federation site with credentials for another, or have some non-specific login details that are shared across multiple, but I suspect that's a logistical nightmare waiting to happen.
Since I'm over a thousand characters in at this point, I might as well explain that you're getting this response two weeks late(r) because your post showed up on the kbin.social sidebar for me today for some reason.
@palordrolap Oh hey, thanks for the detailed response! I actually did some exploration and learning since I made the OP, so I can bring some info to this discussion as well in case the post floats by more people!
TL;DR: To create a new post anywhere in the Fediverse, you have to have an account on the host where you want to create it.
Thankfully, this isn't the case. I think Kbin has (or had? haven't tried lately) some UI issues that prevented you from being able to properly find federated communities to submit a post to them. I made an alt account on fedia.io (linked in my profile) and I have been able to post threads on communities in other instances from there.
As far as I know, you are correct about the potential for one-way defederation causing visibility issues in the way you describe. Last I checked that was not really an intended use case for the functionality, i.e. it should normally be a mutual process, but I think that may be an area where the platforms are still experiencing growing pains.
What would be nice is if it was possible to log in to one Federation site with credentials for another, or have some non-specific login details that are shared across multiple, but I suspect that's a logistical nightmare waiting to happen.
Agreed, both that it would be nice and that it will probably never happen. :P I don't claim to know any more technical details than those broad strokes.
So many magazines that were created by default as a result only have 1 moderator: Ernest.
While this is the case, anyone is free to post whatever the hell they want no matter how unrelated or low quality. This is what has prevented me from coming back daily.
@Squidcopter Can you look for a magazine where folks "behave"? Where they create content that actually follows the magazine's theme?
Yeah it can take resources to find one but if could be rewarding enough for ya to establish beginning conditions for you in here!
I have been following @milwaukee and @wisconsin from kbin.social and I noticed that starting around a week ago or so, I can post to the communities but new posts and comments don't make it from midwest.social to kbin.social. Is there a federation issue? Was something recently broken?
@soweli There is certainly some truth to that, but
it gets easeir farily quickly; and
it's worth the effort! Other platforms don't give you the same power and breadth of access across the fediverse.
You'll find you get more interaction from within kbin (and also from Lemmy) if you use 'Threads' rather than 'Posts' (like this). Posts sit in the Microblog and are more aligned to Mastodon way of working - they are harder to see unless people already follow you.
Can we PLEASE make the top bar be customizable already? Or at least filter NSFW by default? It's a really bad look whenever I open this and "jailbait" is at the top of my screen almost every time.
@jcrm Lol - I figured out how to do this accidentally. You may have noticed that Jailbait doesn't appear in the top bar anymore.
It's because I posted this to it (sfw and 18+ by a long shot, but you'll still want eyebleach). Apparently that top bar of communities prioritizes those that have no posts. Take a look - you'll see every suggested community is empty. Posting to one removes it from the selection algorithm.
Pinging @ernest as it looks like the sorting on that top bar algorithm is achieving the opposite of its intended purpose.
Huh…this whole time there were two separate options for it. For some reason I remember the one for “threads” to be at the bottom like the “microblog” one is now. Anyway, thanks for helping me figure this out. Time to turn the confusing thumbnails off again!
My #kbin account seems broken? :\ For the last month+ I can't get any thread I create to show up in its magazine, even when the magazine is a local one. Comments are fine, microblog posts are fine, threads show up in my profile but never the magazine.
Admittedly I don't try very often, but that makes it all the more disheartening when I feel like "yay, I finally have something worth sharing" and, well, no apparently I don't.
@harmonea you may be blocking a domain, which causes a bug detailed here. tl;dr blocking any domain on kbin.social right now hides any non-link entries and comments on them. removing them all fixes it, it's fixed in latest which hopefully the main site gets soon
I've submitted the second to last #kbin#API PR for review! This PR adds thread and thread comment retrieval, creation, deletion, editing, voting, reporting, and moderation functionality to the API! The last PR will be very similar to this one, except for microblogs!
Didn't you have the API 'complete' like 2 months ago?
Yes, but it did not have any tests written to verify that it worked. These PRs have been resolving that issue so that there can be at least some guarantees that the API works when it gets onto kbin.social and others
(Also, please remember to buy @ernest a coffee if you are able, he's been burning the candle at both ends to support kbin.social and deal with personal business)
I hope updates after this big one are gonna come more regularly and that smaller fixes aren't pushed to be included in big updates.
There's a lot of issues which have seemingly been solved a long time ago now but we don't have the fixes because it's all in the big update.
It doesn't feel great to have issues, some of them quite critical, go unfixed for this long and it's probably making people not use kbin as much which is dangerous if we wanna keep this place, especially at this early stage.
I'm of course very appreciative of the work being done and I'm looking forward to the update!
