Yeah, It's true. Since Sunday, I've been noting errors that I'm still working on resolving. It doesn't make it easier that it's the post-holiday period, and due to travels and security measures, it's not the easiest task. I'm working to get everything back to normal as soon as possible.
Thanks for putting in all this work, especially over a period that's traditionally vacation time. Make sure you're striking a good work/life balance, if you can get the site basically functional (as it appears to be now) don't sweat the small stuff. :)
Open source, non-corporate instances should be able to grow, and that growth will be stunted if most people who want to interact with the fediverse are deciding to go to corporate, profit-driven instances.
The issue is, how does defederating not promote leaving for Threads or instances that federate with Threads?
I think it's a good argument against Threads federating at all, but a poor one for defederating from Threads.
If Threads produces 95% of content in the fediverse, and your instance defederates from them, then your instance just doesn't have access to those 95% of content. Threads and its friends will be a lot more attractive then because it has 19x the content of what you have access to on your instance.
I think this will still lead to people leaving for the threads fediverse.
Also, I get the argument for Mastodon, but does /kbin actually have anything at all to fear here? Sure, the user numbers and content would be way higher than the rest of the fediverse. But Threads is a Twitter contender, not Reddit like /kbin and Lemmy. We will only see their content in the microblog tab.
Is the microblog tab actually that important to most people, that the instance could become dependent on Threads for dominating it? I honestly don't see it happen, I feel like this is an imported issue from microblogging platforms that's just repeated here despite being a non-issue for us.
I assume that 99.99% of that 95% from threads will not be missed and the other .01% will be linked by someone from a non-threads instance just like how tiktok and other social media currently gets linked.
Well, for the span tags, I haven't seen other tags being an issue. If you see a code block where the same issue occurs with other tags, tell me so I can update it.
If there is another Reddit exodus, for example, or if we get a surge due to the Threads thing, I feel like many will just turn back due to the UI alone.
I don't know if ernest's views changed since the last exodus, but iirc people joining the platform wasn't really his intention, it just happened. Kbin hasn't even had a proper full release yet, it's still beta software, so I don't think people bouncing off is that big an issue yet.
With the abandonment of Artemis (formerly kmoon), kbin is now only really usable by the mobile site.
That's the case for now, but app development is still happening with other projects:
ernest has mentioned intentions to revive his kbin app project
I understood OP to be talking about mobile specifically. If there is a way to get the userstyles on mobile it's gotta be like 20 steps long. If someone could somehow wrap it all up in an easy package that would be one thing but idk if it's really a viable solution.
I understood OP to be talking about mobile specifically.
And that's why I said Firefox or Kiwi. Both of those are mobile browsers (the latter is chromium) that support extensions, so you can just install your favorite monkey and stylus and add userscripts/userstyles the exact same way as on desktop.
You're welcome. I'm part of the Mbin community (in fact the 'M' stands for Melroy). If you need more help or having issues, feel free to contact me when you need!! I'm also on Matrix.
Melroy, if you don't mind me asking, why did you go away from Kbin to start your own? I see nothing wrong with Kbin, ernest seems to be a great hardworking guy, I feel like we are just spreading the already small community too thin, Kbin is already small compared to Lemmy and now only the development has started picking up it's pace back again, another spinoff of Kbin makes no sense to me personally.
I contributed a lot kbin directly in the past. It has a long history and story. Long story short: Ernest was offline for months without process, and contributors weren't allowed to merge other PRs, except their own. The way of working within the kbin project means that only Ernest will have the last say and every review goes via him. Development halted when he was gone (yes he is now back). Multiple contributors had the same feeling, hence the reason for a fork. Mbin is community focused, it's not driver my a single owner. All contributors have all rights. We work closer together and review each other code. I speak for myself, but I feel that this change of approach empowered all contributors in Mbin and more sense of responsibility. After all the drama at Kbin, Ernest didn't change either. So I'm glad a fork was created. I wish it wasn't needed.
I feel that our visions for the project's development are too different for this to succeed. At this stage, it will definitely be better to work on our own things, /kbin is open source, so there is no issue with that. There are several reasons for this link, link
From my point of view, you were offline because you had personal issues to deal with, and you dealt with that first, and simply resumed the development after that, and I also see no issues with Ernest being the owner because he is the owner and the founder despite the project being open source and sure, contributions had to go through him but that's fine as long as Kbin itself isn't dead, if it was, then asking him to remove that process would be more reasonable to let the rest of the community try to revive the project, but Kbin wasn't dying or so, it was merely paused for a short period of time.
I personally won't be hopping in-between projects like a kangaroo, I am invested and am already on Kbin so far, its good to have alternatives generally, but in this case, I personally see no reason to go for Mbin. I also encourage and hope potential future contributors focus on a set of projects and not spread themselves too thin.
We all have a life outside the internet, so pauses or breaks here and there is natural, this is less visible in big tech companies, more visible in small startups/projects in early stages which was really the case with Kbin, so we should be patient, I will be atleast :)
Blocking someone means, "I want nothing to do with this person," so it makes sense that you'll be unable to see what they do. This should include direct messages, threads, comments, etc. @PugJesus's idea of a setting to hide votes from blocked users is a great idea, as you should be able to fully ignore someone you've blocked.
It also makes sense that someone you've blocked wouldn't be able to do any 1-on-1 interaction with you. If you've blocked somebody because they're spamming or harassing you, it wouldn't be great for them to be able to DM you.
However, preventing them from voting on your posts is something different entirely, as votes don't just concern the creator of the post and the person doing the voting; they also concern everyone who sees the post. Upvoting a comment is a message not just to the creator but also to everyone else that you like that comment, and the same goes for downvoting. Blocking voting is much more farther reaching than blocking DMs, and with votes being visible on the fediverse, it's a great way for trolls to hide people's views on their posts.
But if a troll blocks everyone that down votes them, eventually no one will be left to see their stuff. It is a self solving problem. On the other hand, a troll that you block can interfere with your stuff being shown to others depending on the sorting algorithm.
While that's definitely a notable downside, I think the upsides outweigh it.
For one, being able to see upvotes & downvotes seems to have made a lot of people a bit more thoughtful with handing them out. This obviously isn't the case for everyone — there's still a good bit of downvoting people for disagreeing with the hivemind — but I and others have observed that downvote quality is a lot better here on kbin.social, and I think that vote visibility is a big part of that.
It's also just transparency on kbin.social's part. If votes federate, anyone can set up an instance to view your votes or just go to one that shows them. Someone could literally make a website listing downvotes throughout the fediverse, and there's nothing stopping them. Kbin.social is being transparent about the fact that votes on the fediverse can be accessed by the public, and I have no issue with that.
Kbin.social is being transparent about the fact that votes* on the fediverse can be accessed by the public
This is important. The kind of petty, persevering trolls that @billothekid2 is worried about are exactly the kind of people who'd be likely to look up who downvoted them.
Kbin just makes it clear to us that this info is out there. Anonymous voting isn't possible in federated social media.
These points are not a priority, but relatively easy to achieve. They will gradually appear on the instance in between working on significant things. It's worth following https://kbin.social/m/kbinDevlog
Now I just need to find a convenient way to save this piece of code and copy-paste it whenever I need it 🤔
Honestly, I'd just suggest to add a button for it in the editor after the code one? I think it's a common enough thing to use to warrant it. For every other formatting maybe a little link for a pop up or expandable that shows the remaining formatting rules, similar to how it was on old.reddit.
kbinMeta
Gorące
Magazyn ze zdalnego serwera może być niekompletny. Zobacz więcej na oryginalnej instancji.