I second all the suggestions except the currently reading/online one: in my experience, seeing "currently reading" statistics just makes dead places feel more dead. It's also not a useful statistic: it doesn't tell you how good a post is, or provide any information about the poster, or even show how popular it is (because you can't really extrapolate about the average engagement from only one datapoint). You can't do anything with the number.
I don't personally have any issues with the website on mobile, I wonder if it could be browser related? I'm also not expecting perfection from something that hasn't been around very long, and never was on reddit so have nothing to compare it to.
I think you have valid points about "dealing" and "learning" and for some, that will be a turnoff. For me, it is an adventure 🙂
Kbin is still in pretty early development. I believe it's technically still in alpha. It'll take a while before we get some QoL updates as there's more imperative things that need to be fixed first.
The API should be coming out soon-ish, which will allow app developers to actually start making Kbin-compatible apps, so we should be seeing some more development in that area shortly.
@BiggestBulb
using kbin mostly on mobile devices, i am time and again surprised that kbin works kinda fine > e.g. kbin deals better with bad internet connections than any other fedi software i have come to know so far > given that kbin is still early beta, this is impressive
i think that we should be patient, and keep reporting bugs :)
Hey, I will get back to this thread and the comments at the beginning of next week. I am able to quickly address some of the issues you mentioned in your post. Changes will undoubtedly be implemented gradually, but for now, the redesign of the ActivityPub module takes higher priority. Once that is completed, the development of the frontend part of the platfrom will truly pick up pace.
Additionally, the suspension of other work was a conscious decision on my part. I believe that the code at this stage needs to be deeply refactored, and that's exactly what I am doing. Solid foundations are the only option for the project to survive and grow in the long term, and to be properly scalable. Adding more blocks to what I have always considered a prototype (which forks do) makes no sense to me.
By default, it's 11MB if I remember correctly. However, during the recent issues with the instance, we could modify this value at the server level. Once Piotr is back, I'll verify and restore the default values.
I share your concerns. I was optimistic at first because kbin looked very promising and the app was evolving pretty fast. Just reaching the point of a functional mobile app would have been enough for me, since we can federate with other communities for more content (before they decided to create their own instance, it was good enough for me).
I am pretty sure the project is on a good track, but in the same time, I think it will probably take 1 or 2 years before we have a good mobile app.
Right now, it is only for iOS. I think there is another one being made for android. (I think ernest has included a link to both of these in one of his daily logs.)
Still, it will probably take some time before everything is polished.
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.
kbinMeta
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.