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

/kbin meta

2 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
434
/kbin - preview of upcoming changes (kbin.social)
submitted 1 year ago by ernest@kbin.social to c/kbinMeta@kbin.social
83 comments fedilink hide all child comments
 

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
[–] darkevilmac@kbin.social 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.

[–] rideranton@kbin.social 5 points 1 year ago (1 children)
[–] Dantastic@kbin.social 1 points 1 year ago (1 children)

How is an app being developed for kbin without an api?

[–] rideranton@kbin.social 1 points 1 year ago

It basically uses the same methods of submitting content as the website does, reading the entirety of the webpage in the process. It's much less efficient than using an API, but it's possible