Not sure if this is a known bug, but any time I'm signed in and try to enter the "all content" view (on any page) i get the "We are working on resolving the issues" error.
If I sign out of kbin it works fine, so it seems related to the fact that I'm signed in as me.
Sorry for reporting bugs here - I realize it's a bit lazy and not ideal!
Personally, I’ve been getting a lot of ‘too many requests’ errors when I try to upvote and then boost a post or thread too quickly after one another. I’m on iOS, using Safari.
Ah, there's one more thing I forgot. I would like adding a new post/thread to be done asynchronously to reduce client-side time, but this might extend to next week because even though I have the foundation prepared, I want to thoroughly test it.
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.
This little guy. I won't take a current photo because even though it's quite snowy in Poland, he won't avoid any puddle or mud, so he temporarily changed color :p
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.
There are some tools there that I use for the development of the AP module. Among them is Yunohost, which allows for quickly creating test instances of many federated applications with just a few mouse clicks. It's a good choice for someone looking to embark on a self-hosting adventure.
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 :)
kbin.social
Najnowsze