The link in the notifications would always lead to the first page of a comment thread. If the linked comment was not on the first page of the thread, you'd have to look for it manually.
Arghhh... Sorry, I replied with a longer message from my phone at that time - at least that's how it seemed to me. Now I've noticed that the response didn't send. In short, there must be an application account on the specific instance due to limits, but catch me on Matrix - we'll discuss it in detail.
Not sure if this is a known bug, but any time I'm signed in and try to enter the "all content" view (on any page) i get the "We are working on resolving the issues" error.
If I sign out of kbin it works fine, so it seems related to the fact that I'm signed in as me.
Sorry for reporting bugs here - I realize it's a bit lazy and not ideal!
There are some tools there that I use for the development of the AP module. Among them is Yunohost, which allows for quickly creating test instances of many federated applications with just a few mouse clicks. It's a good choice for someone looking to embark on a self-hosting adventure.
Sure thing, I've noted that some accounts are stuck in the queue for deletion. This typically applies to older accounts. I'm currently working on it, and everything should be functioning properly soon. Your request is in the queue. Sorry for that.
Hey @ernest, not sure if you saw my question here (https://kbin.social/m/kbinMeta/p/3482999) or not, but I was wondering what the recommended way to authenticate a user with the kbin API that allows federated use. From what I understand, the way it's currently set up is that developers have to register an oauth client with a kbin server in order to authenticate users from an external client. Does that mean every kbin server we want an external client to connect to has to register with oauth?
kbinDevlog
Gorące
Magazyn ze zdalnego serwera może być niekompletny. Zobacz więcej na oryginalnej instancji.