jwr1

u/jwr1@kbin.social
28 posts · 33 comments

Recent posts

Recent comments

So if my kbin account is in kbin.social, I am not able to login in the app at all?

That's correct, for now at least. It's not a limitation of the app, but that the API has not been enabled (by the kbin.social admin) on this server yet. At the moment, kbin.earth might be the only server that has working login functionality, but you could try some of the other API enabled kbin servers, it'll pop up an error if they don't work. See my related comment here.

Are you planning on throwing a copy of your app in Google Play?

Yes, probably once it's more mature. I looked into the process already but was thrown off by the fact that Google wants my government ID (I'm a privacy advocate), but I'll probably end up doing it eventually. Also, if the project gets enough financing, I might put it on the Apple store as well.

Unfortunately, not yet. Only once the api is enabled for kbin.social (you can check by seeing if the API docs page loads) will it work. At the moment, the only api enabled instances I know of include karab.in, kbin.run, kbin.melroy.org, and kbin.earth. While working on the app, I found a kbin bug that causes logins to fail, so unless they've updated already, it's possible kbin.earth is the only instance you can actually log in on.

The individual magazine's page has not been implemented yet; I might try to work on that tomorrow. Unfortunately, kbin.social does not support the API yet (that's why karab.in was the default).

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?