Today, two test instances will be created where we will be looking for bugs for some time, and then the changes will be rolled out to kbin.social and hopefully other instances as well :)
I want to accept as many pull requests as possible, currently, there are still 50 open ones. I'm also following your posts and adding new things to the to-do list.
Appreciate all your work and I am enjoying kbin but please make sure you are not burning yourself out. I have seen it too many times, especially in open source projects that become super popular all of a sudden. Take care of your mental health and work at a pace that you still enjoy. You don't ow us anything.
There's quite a few of us now helping out with tickets. Great to see lots of people coming together to make the site better. Good to get lots of bugs squashed :)
Love it! But that is or can be part of the "problem". Suddenly it's not "I am working on the software I like" anymore but "managing merge requests all day". Not saying that's what's happening here tho. It can be a problem.
@mr47 This issue is browser engine specific rather than device specific, and (annoyingly) falls within valid interpretation of the web manifest standards so it's not really a bug for the browser engines either. The fix is also within the standards, so that's good.
Which issue? Don't see it in the links and I'm not seeing anything I can think of that sounds like that (I'm using the PWA on Android, but using Firefox so maybe that's why)
I'm really looking forward to https://codeberg.org/Kbin/kbin-core/pulls/167 . Maybe I'm just old or something, but the indent is quite slight sometimes and hard for me to see what belongs at which level at certain levels of nesting.
I wish I could contribute, but I've hardly touched anything UI-related in a decade, and likewise haven't worked with newer PHP at all.
I'm super super keen on that one. It's actually the reason I got kbin running locally, so I could implement a quick toggle open/close for deeply nested comments.
Been following that thread and hope it gets out soon, it's something I severely miss from Reddit mobile.
That would be greatly appreciated by us over at /m/kbinStyles so that it’s possible to see that everything still works before the new version goes live.
Obviously not exactly high priority, but I thought it was worth asking anyway.
Some of the userscripts could, longer-term, be converted into server-side Web UI features; I think that that'd make them available to a wider audience, since they become available to all browsers without user effort then. However, for any that don't, I also imagine that it'd also be possible to set up some sort of automated regression testing using Selenium or something like that that warns if it looks like they aren't working in a new version. That'd take load off human userscript maintainers if the userscripts are going to be around for the long haul, and it'd give a heads-up earlier, potentially as soon as the breaking commit goes into git.
This thread gave me a thought that we need a good place to discuss new features and bugs of existing features. I know we have kbinMeta but that is more like discussion of the overall site and the “meta” of things.
Anyways, @kbinfeaturerequests is the place I made for us to discuss feature ideas, pull requests in the pipelines, and pretty much anything in that realm.
Thank you for all your continued hard work, Ernest! I can't imagine the amount of work you have put in as a server admin, as a developer, as front line support, etc.
For those people reading, if you have the means you can buy Ernest a coffee to thank and support him and his efforts.
@ernest just want to thank you for all of the hard work you've done and are doing. Kbin is something really special and you've been going above and beyond with it.
Yep, this one has been brought up a few times and it looks like it's under discussion (the idea of it being at the end is to encourage everyone to read first etc)
While that's a good philosophy overall, a thread like this is a perfect example of why we should have one at the top also, you just want to post a quick comment saying thanks for the work and move on, having to scroll heaps far especially on mobile is rough
Jumping on this to mention two things:
Firstly, thanks to all that are helping develop this. Once I got our instance up and running i was impressed with the whole thing. Potentially related: I have more gray hairs now. Let's just say I'm glad to see that work is being done to simplify the docker setup and improve the admin documentation.
Secondly, one behaviour I've noticed is when searching for a new magazine/community, one of the instance admins is listed as owner and moderator and is automatically subscribed to this new (to our instance) magazine/community, and the created date is listed as when we first searched for it.
Is this a bug (known or otherwise) or expected behaviour? Just seems a bit odd...
Somewhat off topic but does kbin currently have a working API? Every instance I've attempted an API call on just errors out. Same thing when running a local test instance.
Would also likely be a good idea to distribute an OpenAPI spec so people can automatically generate API clients in the future.
Thanks for making such a great platform by the way. Genuinely impressed what a solo dev is able to build with activitypub.
Cheers for the ongoing support mate. I've been pretty keen on contributing and getting some of the UI/UX polished up, keen to see these all hit prod so everyone can benefit ❤️
Love to make the experience on mobile good enough that if you want you won't even need a third party app.
You are writing from your instance, so it's @[email protected]. In the future, there will probably be some sort of suggestion when mentioning people, similar to Mastodon.
Love it! I'm desperately just waiting for the ability to hide posts, that's causing the most disconnect from what I'm used to over on reddit. Would also love the option to save posts, but I'm sure all that is an eventuality
I'm especially looking forward to the bug which causes notifications not to be sent when you receive replies to your comments being fixed. This one is a huge drag on conversation.
As for features, very much looking forward to being able to collapse comments.