this post was submitted on 25 Jun 2023
498 points (100.0% liked)

/kbin meta

639 readers
1 users here now

Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign

founded 1 year ago
 

Hi there, in the upcoming kbin releases, I will be describing the changes along with author tags, but for now, you can check out what's happening here: https://codeberg.org/Kbin/kbin-core/activity, as well as my personal feed: https://ernest.dev

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.

Have a nice day!

top 50 comments
sorted by: hot top controversial new old
[–] [email protected] 106 points 1 year ago (1 children)

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.

Have a great Sunday!

[–] [email protected] 49 points 1 year ago (1 children)

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 :)

[–] [email protected] 19 points 1 year ago (2 children)

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.

[–] [email protected] 12 points 1 year ago (1 children)

@Mnmalst Yeah, I am well aware of what you're talking about, and I am trying to maintain a balance. I knew that it could look like this at a certain stage, but I didn't expect it to happen so quickly ;) I assumed I would have a bit more time to prepare and acquire knowledge. Now I have to improvise. I make mistakes, but I try to fix them and always keep an eye on the big picture. That's all I can do. Working with pull requests is great, I enjoy learning new things from others, and it's also fun to discover bugs together. At least for now. ;-) But I always emphasize that my priorities are my milestones, which keep me afloat, so I care about organizing our collaboration as quickly and effectively as possible. However, we also need to get to know each other a little better.

load more comments (1 replies)
[–] [email protected] 10 points 1 year ago

I think it's important to not have a single person having to deal with those. But admittedly it's hard to get to that point. I've only significantly done established, commercial software dev, where you can just trust your coworkers. Random people on the internet are harder to trust. Anyone can play nice for a couple of days for a chance to slip in something malicious.

The project is not only rather new (so any contributors are gonna be new), but it's also hosted on an unfamiliar site (which is to say, it's not GitHub), so most people don't have an account with history either.

[–] [email protected] 51 points 1 year ago (5 children)

Nice!

The PWA rotation issue is really annoying, happy to see this will be fixed. :)

[–] [email protected] 7 points 1 year ago

Definitely a big annoyance point for me!

[–] [email protected] 5 points 1 year ago (3 children)

Is this about the PWA rotating when auto rotation is set to off? Sounds like a bug on the device, as it's not happening to me.

[–] [email protected] 4 points 1 year ago (7 children)

That might be android only, I'm not sure. I remember seeing a pull request about it having to do with something in the PWA manifest.

[–] [email protected] 3 points 1 year ago

I'm on Android 13 with Firefox, and haven't noticed the issue. Tried specifically to disable the autorotation, rotate the phone while kbin was running - and nothing (it does rotate when autorotation is on). I installed the PWA about a week ago.

load more comments (6 replies)
[–] [email protected] 3 points 1 year ago (1 children)

@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.

[–] [email protected] 3 points 1 year ago

I see. I guess Firefox works correctly.

load more comments (1 replies)
[–] [email protected] 2 points 1 year ago

Oh thank god, I thought it was a "feature" and here to stay.

load more comments (2 replies)
[–] [email protected] 36 points 1 year ago (3 children)

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.

[–] [email protected] 8 points 1 year ago

This script does collapsible comments with nesting. It's fantastic.

[–] [email protected] 7 points 1 year ago (1 children)

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.

load more comments (1 replies)
[–] [email protected] 4 points 1 year ago

Yes! Collapsible comments is my most painful missing feature.

[–] [email protected] 12 points 1 year ago* (last edited 1 year ago) (2 children)

Will the test instances be publicly available?

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.

[–] [email protected] 18 points 1 year ago (3 children)

Sure thing, I will manually approve accounts from time to time. These scripts are mind blowing ;)

https://lab2.kbin.pub/
https://lab3.kbin.pub/

[–] [email protected] 3 points 1 year ago

Was lab1 destroyed by a zombie outbreak?

load more comments (2 replies)
[–] [email protected] 5 points 1 year ago* (last edited 1 year ago)

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.

[–] [email protected] 11 points 1 year ago

Thanks for all the work you're doing!

[–] [email protected] 10 points 1 year ago (7 children)

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.

load more comments (7 replies)
[–] [email protected] 9 points 1 year ago

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.

[–] [email protected] 9 points 1 year ago

@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.

[–] [email protected] 9 points 1 year ago

@ernest Hi, this open issue might be worthwhile looking into/raising priority on.

https://codeberg.org/Kbin/kbin-core/issues/398

[–] [email protected] 8 points 1 year ago (5 children)

Please don't make me scroll the whole thread with comments just to reach the comment input. Super discouraging

[–] [email protected] 5 points 1 year ago

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

[–] [email protected] 5 points 1 year ago

+1 this needs to be fixed

load more comments (3 replies)
[–] [email protected] 7 points 1 year ago

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...

[–] [email protected] 6 points 1 year ago (1 children)

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.

[–] [email protected] 6 points 1 year ago (2 children)

@ernest

sounds nice but what about better moderation tools

[–] [email protected] 35 points 1 year ago

Some fixes are awaiting review, while the rest is still on my local branch. On Monday morning, the changes will be pushed to testing.

[–] [email protected] 9 points 1 year ago (1 children)

@dekkzz76 @ernest Most things going in atm are from community members who are "scratching their itch"

Mod tools will/are happening but there will always be way more or these sorts of things.

[–] [email protected] 4 points 1 year ago (2 children)

@pieceofthepie @ernest

mod tools are core part of the kbin experience, so it should be important for the core devs,

[–] [email protected] 35 points 1 year ago

I assure you that's the case. These are simply tasks that require a bit more time and attention to work on ;)

[–] [email protected] 13 points 1 year ago

@dekkzz76 @ernest I mean, maybe a bit dismissive of all the work being done, but sure.

Work on core experiences is absolutely happening, but also take time.

[–] [email protected] 5 points 1 year ago (1 children)

Thanks for the great work on this @ernest, and every contributor who's dove in and made a PR.

[–] [email protected] 25 points 1 year ago* (last edited 1 year ago) (1 children)

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.

[–] [email protected] 3 points 1 year ago

That'll be slick!

[–] [email protected] 5 points 1 year ago

Cool stuff, thanks all for the hard work it's appreciated!

[–] [email protected] 5 points 1 year ago

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.

[–] [email protected] 4 points 1 year ago

This is some good work! Excited to see all the improvements once they are implemented here!

load more comments
view more: next ›