kbin.run meta
Hi everyone, [kbin.run](https://kbin.run/) is approaching its 1 year anniversary (June 11, 2023) and I figured it'd be a good time to provide a quick summary of the infrastructure changes and expenses incurred over the past year. I've had to migrate servers 3 times to settle on a suitable hardware configuration, datacenter, and price point that works well for running kbin/Mbin. Mbin has made significant performance improvements over /kbin, so the latest server is suitable... for now. Of course, I will upgrade again should it become necessary with additional site traffic, resource utilization, etc. Total expenses: $612.86 USD Total donations: $111.48 USD **Operating deficit: $501.38 USD** Thank you to everyone who has donated to help offset the cost of running the instance, it is much appreciated! If you want to also help me out, please visit the [FAQ](https://kbin.run/faq) page for ways how! Happy cake day to everyone and here's to another great year in the Fediverse and Mbin development!
Hi everyone, I saw a conversation on a certain magazine about the wording of [kbin.run](https://kbin.run/)'s [terms of service](https://kbin.run/terms). I'm not going to reply there because its unproductive and irrelevant to the conversation being discussed. I do; however, encourage everyone to (re)review the [privacy policy](https://kbin.run/privacy-policy) and [terms of service](https://kbin.run/terms) of the instance. A reminder that this is a US based instance and I will enforce compliance with **all** established US laws and comply with **all** law enforcement requests, subpoenas, etc. I am not a lawyer and I'm not going to pay a lawyer to write an all encompassing fediverse friendly TOS, although if that's something people want, please donate to the site so I can afford to hire one. I'd like to think this is one of the most transparency friendly instances out there between all the information I provide in the [about](https://kbin.run/about), [FAQ](https://kbin.run/faq), [privacy policy](https://kbin.run/privacy-policy), [terms of service](https://kbin.run/terms), etc. With regards to the specific concern about the "third party" wording in Section 11. of the [terms of service](https://kbin.run/terms)... **outside of the realization that any federated instance subscribed to any user or magazine on this site is by definition a third party**... there are also automated measures in place to log and report users that post or share material flagged as child sexual abuse material (CSAM) detected with hashes provided by the [NCMEC](https://report.cybertip.org/). This is a **ZERO** tolerance area and I have already reported several instances that either don't care about this or have no moderation in place to handle it. Thank you for your understanding and I welcome a healthy discussion if desired; otherwise, please submit a user account delete request and I will remove your account from the site.
I posted a similar "feeler" [thread](https://kbin.run/m/kbinrun/t/14456/META-How-s-my-driving) last year and I'm curious how the more recent/active userbase is feeling about [kbin.run](https://kbin.run/). Things you like/dislike/wish I could do better/etc? I welcome healthy criticism, so feel free to let me know your thoughts. As always, the [FAQ](https://kbin.run/faq) page has the latest instance information if anyone is ever curious about the behind the scenes operation.
I tried to subscribe to 18+ magazine from outside of kbin.run instance, but they wont load. Local search for 18+ magazines shows 0 results. Does this mean that kbin.run has a policy against such content, or is this some sort of an oversight?
I subscribe to !incremental_games@incremental.social. Checking incremental.social tells me there are new posts, which kbin.run does not see. I private messaged the mods and did not get a response. Asking here partially to ask this kbin instance's admin about the federation issues, and to figure out what to do about federation issues in the future.
Ready for another Mbin feature!? Direct messages (aka DMs) now federate between Mbin instances and to/from Lemmy! Checkout the details at https://github.com/MbinOrg/mbin/pull/830 and, as always, please report back if you find any issues. The message view has also been revamped, but we're continuing to optimize button positions, text locations, etc... so some of that stuff may still change, just fyi. @BentiGorlich@gehirneimer.de is again the dev of honor introducing these long awaited features to make Mbin competitive and play nice with the other platforms in the Fediverse.
[kbin.run](https://kbin.run/) is testing out the next feature to be added to Mbin -> [FEDERATED PINS](https://github.com/MbinOrg/mbin/pull/831)! Let us know if you find any issues. Also, when a moderator pins/unpins a thread the action will now appear in the instance's modlog, e.g., https://kbin.run/modlog. Another awesome addition by @BentiGorlich@gehirneimer.de
Is there a way to transfer the ownership of a magazine over to a different account? I have moved to this account from my old Mbin account (also on kbin.run) so that I could update my handle since I am in the process of changing my name and no longer wanted my handle to contain my old name. From my old account I was able to add my new one as a moderator easily, however as a normal moderator I do not have access to the magazine panel like I did on my old account. And I haven't seen any settings options to either elevate my permissions or transfer magazine ownership over entirely to my new account. Am I missing something, or is it just not possible to transfer a magazine? Any help would be appreciated.
Test it out and let us know if you find any issues; you add channels the same way as adding any other magazine/community. How is this possible!? [kbin.run](https://kbin.run/) is running the PR branch from https://github.com/MbinOrg/mbin/pull/782 Major props to @BentiGorlich@gehirneimer.de for adding this long awaited feature to Mbin!
I was testing kbin.run and noticed a different layout to kbin though when I had a look at fedia.io I noticed they use the same format as kbin.social. Is the different design due to kbin.run and fedia.io being different versions of mbin or is it a setting the instance admins set up? I put a picture in the post to show what I mean.
I just moved from kbin.social, but I can't find / subscribe to these magazines: - @ LifeHacks@kbin.social - @ lifeprotips@lemmy.ml - @ thunderbird@lemmy.world Any help appreciated!