I've submitted the second to last #kbin#API PR for review! This PR adds thread and thread comment retrieval, creation, deletion, editing, voting, reporting, and moderation functionality to the API! The last PR will be very similar to this one, except for microblogs!
Didn't you have the API 'complete' like 2 months ago?
Yes, but it did not have any tests written to verify that it worked. These PRs have been resolving that issue so that there can be at least some guarantees that the API works when it gets onto kbin.social and others
(Also, please remember to buy @ernest a coffee if you are able, he's been burning the candle at both ends to support kbin.social and deal with personal business)
And I thought only the #fediverse can’t keep it’s Like counts and Follower counts and comment threads synchronized across instances.
Earlier today I looked at the “general” Matrix room of the Fediverse Developer Network, and it had just something like 40 people in it. Where did they all go? But all false alarm. Just now, I use the same app to look at the same number, and it’s back at 147, roughly where I thought it was.
Imho none of this is acceptable, never mind technical difficulties.
I wonder if the ActivityPub spec has some allowance for the eliding of the "user" part of a handle. So instead of "@/me@myserver.social" it could just be "@/myserver.social" (without "/").
If not I think that would be a nice add. Maybe just some convention like "If user not present in handle, assume "@/_main@myserver.social".
"ActivityPub 1.0.0 for WordPress has been released allowing WordPress blogs to be followed by others on apps like Mastodon and others in the fediverse and then receive replies back as comments on their own sites."
If the entire rest of the #Fediverse would learn to do what @freakazoid states here, the Fediverse would be in a much better place with a LOT less drama and ignorance.
I hope updates after this big one are gonna come more regularly and that smaller fixes aren't pushed to be included in big updates.
There's a lot of issues which have seemingly been solved a long time ago now but we don't have the fixes because it's all in the big update.
It doesn't feel great to have issues, some of them quite critical, go unfixed for this long and it's probably making people not use kbin as much which is dangerous if we wanna keep this place, especially at this early stage.
I'm of course very appreciative of the work being done and I'm looking forward to the update!
