of all these beautiful features, gotta say the CSS styling on the mags is my FAAAAVVEEE. i love doing it. i kinda go overboard and need to reel it in, but the ability to personalize your mag is so fun. though, people should have an option to toggle mag styles off, they can be distracting or the best part about the mag lol (ㅅ´ ˘ `)
Thanks for the feedback, I've contributed sorting of the magazines and actually "the other four are under the hot tab" is not the case. They're not in any specific tab, they just sort by number of threads/comments/posts/subscriptions. I've done it this way to be backwards compatible with newest/hot/active tabs that were already there before introduction of sorting by clicking on table headings. Nonetheless, I agree that the Magazines page needs more polishing after recent changes and your suggestions are good.
Hello, does anyone know if it’s possible to moderate a magazine hosted on kbin with a lemmy account? I’ve been taking care of a magazine hosted here for months and the owner is MIA as far as I can tell (I tried messaging them to no avail), but the adoption feature mentioned here doesn’t appear for me from the lemmy side. Given how lemmy and kbin are compatible-yet-different, I’d understand if the moderation features can’t cross over, but for now I just don’t know so here I am =) Thanks for reading!
Thank you for your answer! I suppose I’ll do that, then. So far the magazine has honestly not really needed moderation, but it’s always better to have someone ready before problems happen =')
In this specific case the community owner posted good guidelines before disappearing so we have that at least, but I’d appreciate being able to change the pinned message for example (current one is outdated), and the other community I adopted got a totally random troll post once so I now consider that these can pop absolutely anywhere at any time =')
It is! Thank you very much 🧡 (Limbus Company is a turned-based strategy game with a heavy emphasis on story, and the less gacha-esque gacha to ever exist x’) )
Some ideas for anti-spam measures that might help:
block users who post flood -- e.g. if an account makes 10 posts a minute, it's a spammer
block accounts that end up massively in the negative shortly after they start posting -- e.g. an account at -50 within 15 minutes of making its first post is probably a spammer (exact thresholds may need some tuning). Note that this is different from blocking new accounts that go into the negative since people can register accounts in advance of an attack and wait until later to cause disruption.
block users who post repetitive comments/links excessively -- e.g. if the same link is in 10 comments/posts from the last hour or they've submitted the exact same comment a dozen times, the account is probably a spammer (again, thresholds may need tuning); that won't catch all the bots (one of them added a bunch of random words) but will catch some of them. More clever filtering could catch the other bots.
block new posters who are reported many times by established accounts in good standing -- at least until an admin can check what is going on
I'm not entirely sure any of that would be effective in controlling visibility of spam accounts from other instances. I'm quite sure that up/down voting does not always federate perfectly. Those steps would all be effective in handling malicious accounts on the same instance they're registered with, as long as their malicious posts and comments are also on that same instance; the effectiveness would certainly fall off sharply for content posted at other instances.
I wonder if there needs to be some kind of "governance board," like the NATO or EU of the fediverse, where major instance admins meet and set agreed upon standards of instance behavior.
We don't need to depend on federated downvotes to judge what does or does not belong on kbin. In fact, I think it's probably better if we don't. People are downvoting the bots here. I have yet to see an account with negative rep. on kbin that wasn't a spammer.
Regardless, rate-limiting incoming posts will limit the damage and annoyance to us.
I wonder if there needs to be some kind of "governance board," like the NATO or EU of the fediverse, where major instance admins meet and set agreed upon standards of instance behavior.
I'm not sure that would help with this particular issue -- and there's already a fair amount of bad relations between instances so I don't think a wider fediverse board is likely to succeed even if it could help somehow... I guess instance admins that do agree on general moderation principles could help co-admin each other's instances to cover better for when they're offline (maybe some of them already do?), but we shouldn't have to depend on remote admins being responsive to deal with an issue affecting our instance.
Ernest is dope, figure that's worth repeating, probably the hardest working man in open source social media right now
I really like the UI a lot compared to other fediverse alternatives
I like that I can see both blog posts and threads from one app
Kbin users seem to be more balanced than many lemmy instances which seem to foster groupthink and brigading.
Features seem to be rolled out based on community feedback, I made a post a long time ago about abandoned magazines and was pleasantly surprised to see a method of reclaiming ghost magazines included in a recent update.
I don't know any other social media site that allows you that level of freedom of customization.
Reddit used to have custom CSS, still does if you use the old design via the settings or the old.reddit.com address. Check out /r/steam for a subreddit with heavy custom styling.
Sadly in later redesigns they threw that feature out in favor of a more professional but boring looking uniform design.
Some stuff like spoilers started out on the platform using custom CSS. Spoilers used to be done by styling links pointing to a specific address. The worldnews subreddit uses it to hide paywalled articles.
kbinMeta
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.