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

/kbin meta

110 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 2 years 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!

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [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.