I agree with @Drewski, defederation should be the last choice. Kbin does have an option where you can block whole domains, so if you'd prefer that, go here and click the block button: kbin.social/d/fanaticus.social
I was using the flutter_markdown package to render markdown. Fortunately, the text style can be changed, so once I get around to it, I'll fix the color issue.
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?
Also, I'm not sure if this is intentional or not, but I've noticed posts don't seem to show up in feeds until they have at least one favorite. This post, for instance, wasn't in https://kbin.social/c/kbin initially, but once I upvoted it, it showed up. Maybe it doesn't qualify as "hot" if it has zero votes.
No, kbin.cafe is not run by the same person that runs kbin.social; here's a post by the owner of kbin.cafe and @ernest is the owner of kbin.social and the main developer of kbin. As you mentioned, kbin works similar to an email service, so different kbins (and lemmys and mastodons) can communicate with each other.