I'm not sure if this is a good suggestion, are you able to delete it via moderation as you're the magazine owner? Someone mentioned having issues deleting their own posts but still could via moderation recently, but I'm not actually sure what that difference means as I haven't moderated any magazines myself.
Ok, so trying to post THIS op I got that same error, refreshed and tried again and again the error but on my profile it showed as posted twice but somehow I had no problem deleting THAT duplicate so why can't I delete those on my own magazine? Strange
So when a community isn't in kbin yet you can search @[community name]@[instance] to create it. I was asking if a similar thing is possible with threads.
Yea that works for single posts, use the fediverse icon on the remote server for the proper url to search.
You don't get the reply's but you can search like that on a single reply too.
This month, the largest update is planned. It's taking a long time because part of the team is returning from vacation, hence the delays. I hope that the update will resolve some of the most pressing issues. I'm also trying to remove spam systematically, but currently, the code is my priority. After implementing the new version, I will seriously address the community.
If there's anything urgent, currently contacting through the form is the quickest option. Cheers!
Hmm, so far that is only showing the microblog posts that are tethered to the magazines I sub, but I also don't really follow many people yet so maybe they have just been drowned out.
Interesting, I've heard people say the same before. I do always sort by newest myself, but I sub to a bunch of magazines and also, say, three mastodon accounts, and that page is basically just solely the mastodon posts, very rarely do I see microblog posts in lemmy/kbin. I guess a filter of magazines vs users would be useful
Edit: Also, is the default view all time for you? I could see that causing a problem as well if it's hot / all time. I mainly have three bookmarks: /hot/12h, /sub/newest/24h, /sub/microblog/newest/1d. Getting all results for all of time by default seemed a bit weird to me, especially for microblog posts
The default view appears to be hot, but changing to new does not do much (is there an actual difference between sorting new/x and new/y? Specifying a time frame for new sorting seems kinda pointless).
I think the issue here is probably that I'm subbed to a magazine that has set up a fairly common hashtag (#opensource) for its microblog, so it naturally pulls in a lot.
Definitely, you're right that new timeframe doesn't matter, I meant to type hot all time xD I would expect that to potentially grab like whatever was boosted most in the past but then again the algorithm does tend to show newer things even under hot.
Yea the tag system might need a bit of work. It works great for some magazines, but for others not so much. For example m/help is supposed to be a magazine for kbin help but it pulls in everything under #help which can be anything in the fediverse. I did see someone suggest a way for a magazine to remove it defaulting to using the tag of its name, which doesn't seem like a bad idea to me
In hindsight I remember why I filter newest to a timespan, so wanted to make note of it. Right now: https://fedia.io/m/kbinMeta@kbin.social/microblog/newest 500s for me but https://fedia.io/m/kbinMeta@kbin.social/microblog/newest/1w is able to load. so cutting off some of the older posts helps me run into less 500 issues, and I generally don't care too much about old posts unless I'm searching for something. that might be a fedia specific thing though, not sure how 500s are on other instances
Hi there, I'm currently working on solving the problem. There will be significant changes this month. I know it's taking longer than I initially announced, but this will be a really solid release. The contributors have made an incredible work and I didn't want to miss anything. https://kbin.social/m/kbinMeta/t/381108/Lots-of-new-spam#entry-comment-2209332
It's partly specific to the kbin software, and partly specific to kbin.social. The biggest problem is that the software doesn't currently support having more than one administrator account per instance.
The flagship instance, kbin.social, is administered by ernest, who is also the lead developer of the project. Working on the software seems to keep him plenty busy, to the point where he's not able to keep up with administrator tasks.
Since kbin.social was (I assume) not used by very many people before the reddit migration, almost all the older magazines are owned by ernest, and have no other moderators set. There's also a large number of magazines that were created during the migration, but have since been abandoned by their owners. Reassigning these is a task that currently only ernest can do.
And of course as the most populated instance, kbin.social is a more desirable target for spammers, compared to the other kbin instances.
kbinMeta
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.