I think most of us who moved here from Reddit are enjoying our time here on kbin.social. We've left a lot of the riff-raff behind us and made new friends with intelligent, thoughtful members of kbin, Lemmy, Mastodon, etc..
But we need to spread out.
Not only have we stressed the server with thousands of immigrating users, but we were being watched by darker forces, namely Meta and Instagram.
A quick search of the net will show that we were not the first mass-migration. The first migration was last year when people from 'the bird site' (rhymes with jitter) fled Elon Musk's new regime. Most of those people moved to Mastodon.
We largely moved to kbin. Kbin.social to be more exact.
I'm a member of both Mastodon and kbin, and a couple of posts shocked me. The first one about Meta I have found again:
https://mastodon.social/@gnarkotics/110568580882355105
The second one about Instagram I have failed to locate, but the gist was that Instagram had reached out to one of the larger Fediverse servers and asked the person who runs to have a meeting 'off the record'. That person turned them down and told other members of the Fediverse what happened. The general consensus is that this was going to be a monetary offer to allow Instagram to further colonize the Fediverse by purchasing one of the larger servers.
And therein lies the problem: if the majority of users gravitate to a few large servers, then that leaves those larger servers vulnerable to exploitation.
I, as a recent immigrant, did not understand this. I thought that, intuitively, we should all gather in one place and grow the server. It's the exact opposite. We need to spread out to smaller instances. This didn't really register with me until I spoke with this person.
https://fedi.getimiskon.xyz/objects/77a0f3cd-6f31-42f7-a3ea-29af8b25c0b3
Remember too that having an account on a smaller instance still allows us to see everything on kbin.social. For example, look at this:
We are looking at a mixture of posts from Lemmy and kbin.
Moving to a smaller instance does not limit your interactions. What damages the fediverse is people trying to recreate all of Reddit on one instance.
TLDR: If you like it here, the best thing you can do for the fediverse right now is to set up on one of the less populous instances.
I invite correction and clarifications.
EDIT: Adding further sources below.
Meta/Facebook is inviting Fediverse admins under NDA for “meetings” (mstdn.social)
https://news.ycombinator.com/item?id=36384207
Facebook, Inc. is planning to join the Fediverse. How do we make it lose as much money as possible?
https://www.loomio.com/d/QoH98Gg6/facebook-inc-is-planning-to-join-the-fediverse-how-do-we-make-it-lose-as-much-money-as-possible
Beware Of Meta Offering Gifts To Mastodon
https://medium.com/nextwithtech/beware-of-meta-offering-gifts-to-mastodon-6adb317e039d
Meta vs Mastodon: Battle for the Future of Decentralized Social Media
https://marketingnewscanada.com/news/meta-vs-mastodon-battle-for-the-future-of-decentralized-social-media
Legal-Copyright discussion from Mastodon yesterday
ttps://mas.to/@franktaber/110602489997086618
And a cartoon to boot
I may move on to a private or semi privately run instance in the future but I'm definitely a fan of kbin over Lemmy and the current state of self hosting kbin is a mess. When things have gotten better on that front I will look at moving on and expanding the fediverse.
Yeah, that's one of the things kinda holding me back for now as well.
Edit: I fnally gave it a shot. It turned out to be pretty easy. I just followed the admin guide on kbin's codeberg at https://codeberg.org/Kbin/kbin-core/wiki#admin-guide and scrolled down to the "Install with Docker" section.
Did this on an M1 Mac that already had Docker Desktop set up, so basically I skipped the first four subsections as not relevant and went straight down to the "Clone repo" subsection. (After cloning the repo, there is a section on getting docker-ce set up for Linux/GNU that I skipped).
I simply did "docker compose build" and didn't explicitly need to build fresh images. Then I ran "docker compose up" and the system was up.
Going to https://kbin.localhost .. told me that I forgot to build my npm or yarn assets. Whoops!
Since I didn't want to mess around with yarn on the host system (though that probably would have worked if I tried) I just found the kbin-php container id by checking the list from "docker ps" and then used "docker exec -it [kbin-php-container-id] /bin/sh" to log in with a shell. Then I ran "apk add yarn" followed by "yarn install" and "yarn build"
After that everything worked.
Somehow I missed seeing the configuration section, and so I created an admin user by registering a new user through the UI, and then running "docker exec -it [postgres-contanier-id] psql -U kbin kbin" to connect direcly to the database. Using psql I executed "update "user" set roles="['ROLE_ADMIN']", is_verified=true where id = 1;" then logged out and logged back in get recognized as an admin.
Finally I went ahead and created the random magazine through the UI.
Something is still off. The UI works fine and anything locally is good, but I can not seem to subscribe to magazines on other instances or even search for them from my own kbin.local - they just comes up empty. Not sure why this is happening but I'll update as soon as I learn more!
This is kbin.social, not kbin. You can set up an account on kbin.cafe, kbin.place, and a lot of others and still be able to post and comment here.