I think it's great that you're interested in this! It may be scary, but it can also be pretty exciting. I would say to start small. There might be a lot of things to consider: establishing rules, the overall vibe of the #magazine, your audience, the type of content you want to see, etc. Pick on one, focus on that for a day or so. If you plan on making new magazine, you'll be free to take your time with this. Growing niche magazines tends to be on the slow side. IMO, that's better for those who are new to this, so they can have time to acclimate to the tools and considerations you'll be presented with. It may also allow you to really reflect on the direction you'd like to take your magazine.
As #niche#communities tend to start slow, people will be hesitant to post content. Unfortunately, when content is rare, people are less inclined to post. This is a problem that reinforces itself, as others are unlikely to post when there is no content. You'll probably need to be "the first on the dance floor", so to speak, if your goal is to grow your magazine. This will likely test your patience, as you will probably be one of, if not the only active posters in your magazine. Picking a magazine name that might see usage in the #fediverse and #mastodon might prove useful for #federating content via the #microblog section. However, if you wish to pick a more unique name, more power to you. Something to consider, is that you may wish to create a sibling magazine that can accept a tag that would federate posts with regularity.
For example, I run @learnjapanese. However, most people will be unlikely to write #learnjapanese on Mastodon. However, I also run @japanese, which federates the #japanese tag from Mastodon instances. You can add additional tags in the magazine settings menu, which allows the federation of posts that contain other hashtags. I've pinned a microblog in both magazines' #microblogging sections to point to each other to increase #discoverability and awareness of related resources. Speaking of discoverability, Ernest recently implemented a #crossposting feature to /kbin that further increases discoverability and accessibility. Posting the same link/image to related magazines will allow users to see other magazines this content is posted to. This appears in the comments section of the thread, directly below the content of the post itself. Ideally, this would generate additional traffic and increase visibility for the smaller, but related magazines. This has been an extremely welcome addition, as someone who is moderating smaller magazines and trying to bring awareness without spamming advertisements.
If you have any further questions, please let me know. I have also subscribed to your magazine. Good luck. :)
Yeah I am aware of slow growth.
My magazine takes lots of its material from a YouTube channel so at least for now their activity would go more or less hand in hand with mine/ours.
I'd be happy to receive even readers! Posting there isn't a necessity for me, for now at least.
The name of the magazine is the same than the YouTube channel's.
I added some tags to the magazine's description and into its settings.
Looking at/testing crossposting at some point.
Just a heads up - since the recent updates, on desktop, clicking on link preview in a comment will make the link and the little icon disappear but no preview loads: https://files.catbox.moe/o41qu7.jpg
Clicking the link itself opens it in a new tab as normal.
I really love it. Thanks to microblogs sections of magazines, I'm now getting plenty of mastodon content and even following some mastodon people despite not having a mastodon account.
Huh, guess it's worth a shot. Hi @ernest, any chance you could waive the month-long not-logged-in requirement for the men magazine? It would appear the owner has lost all patience with Kbin in general and made it clear he isn't coming coming back. I would like to resurrect this community as a progressive non-toxic space for men to engage in healthy discussion without resorting to punching down and insulting others, similar in nature to the old menslib subreddit. With your admin-powered blessing, of course.
No problem. Something to consider though, is that simply moderating the magazine until it's "abandoned" by the owner may end up being the solution. I understand that may not be ideal. While I empathize with your situation, the rules that Ernest establish also exist for a reason. However, I also do not intend to speak on his behalf. I hope things work out for you either way.
I'd be cool with modding it in the meantime, but it doesn't look like anyone (either me or @BaldProphet) has been appointed mod yet to step into that stopgap role.
a-man-from-earth's last post was a week ago, and I don’t wanna keep bugging ernest about this, so I guess I'll sit tight and run out the clock. This is not an emergency by any means, it's just one of the many abandoned communities that need help. Thx for the info and words of encouragement, @daredevil. And good luck with all the cleanup!
I've also applied for moderator. I didn't even realize that community was abandoned, so now I'm wondering how many other communities I'm subscribed to have been abandoned.
An "abandoned" magazine is one where the owner has not logged in for 30 days. You'll probably know when a magazine/community you're subscribed to is "abandoned" when applying for ownership of a magazine is enabled.
An "abandoned" magazine is one where the owner has not logged in for 30 days. You'll probably know when a magazine/community you're subscribed to is "abandoned" when applying for ownership of a magazine is enabled.
The mechanism to delete your account isn't yet working and Ernest needs to manually do a bunch of stuff to make it happen, so it's not so much an "approval" as it is a notification to Ernest that he needs to do something.
Have you blocked anyone? There's a bug that causes certain threads, including your own, to not be visible to you outside your profile. It's caused by you blocking anyone at all iirc. Or maybe it's about blocking domains, I forgot the specifics, but try removing any and all blocks and see if that solved it.
It's fixed in the latest code iirc, but there's not been a stable release yet that incorporates the change.
Additionally, and I have no idea if this is related, I cannot send direct messages to anyone outside of kbin.social
This is correct, direct messages only work on the same instance currently. If I remember the previous discussions about it correctly, this is intentional for some undisclosed (or lost to time?) reason currently. Like, the developer has specifically added code to cause this behavior, I assume because there were worse issues with it.
Thank you, that was it! I have blocked lemmy.ml around the same time, after unblocking it the issue seems to be fixed!
The fact that the blocking wasn't 100% and lemmy.ml still sometimes showed in the feed is also a bit of an issue, but that one didn't break the site in any way, so whatever and hopefully it will work properly in the future.
I think the issue there is probably that the block applies to what's in the (some.domain) next to threads. For non-link threads, it's hidden, but it's the instance the thread was created on. But for threads that link to an article, image, video, or anything else, it's the domain the link points to. So a thread linking to a youtube video will have youtube.com as its domain. And only blocking youtube.com will hide it, not blocking the instance the thread is from.
It think ideally both, the target of the link and the owning instance of the thread, should be accounted for by the block functionality. But I don't think that's currently the case.
Even if lemmy.ml is blocked or even defederated, its communities should remain, just not threads and comments made by lemmy.ml users. But you might still see @lemmy.ml communities show up in your feed if someone from lemmy.world or kbin.social made a thread there.
2 Things there. I was mainly talking about the kbin.social template magazines like tech or opensource but also
The other problem is that reports from kbin are not getting to other instances AFAIK so we must self moderate other instances that appear on here
I do the same for my mastodon instance. I see a user doing something against the rules via another instance their federated profile is limited or suspended from my own instance
Coming from another instance, I really can’t wait for kbin to fix this issue. Every time I see spam, it’s from kbin because of the lack of moderation. I don’t understand why only the instance admin is able to moderate.
Same here. When I started trying to post a few weeks ago it was intermittent. Sometimes it went through, other times I needed to "massage" the post by interacting with it (upvoting, commenting, etc.), sometimes it appeared on the local version of the magazine, sometimes just on my profile. But the past week or so it's been really bad. I gave up trying to fight with it and just made an account on a Lemmy instance to post from.
kbinMeta
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.