You know why I write long single posts instead of multiple posts of a thread containing 500 character posts each that are replies to each other?
Because people don’t actually read threads. Instead, they read one post in the thread, make a reply – completely oblivious to the context of the thread.
This is why my #Akkomane server has a 5,000 character limit default. I make good use of those characters too.
Sure, sometimes people occasionally complain because my posts are long. However, the amount of bad replies I receive have gone down significantly.
For that reason, I sure love more characters. I’m using 669 of them on this very post! It’s fantastic!
Any guides for how to deploy a selfhosted #akkomane? I deploy applications using docker, but I'm not quite sure how that would work between two applications.
#Threads gets a lot of blowback for making federation opt-in on their service.
But from an admin perspective, thank God they’re doing that because if 120 million accounts suddenly joined the #Fediverse, this could kill many servers.
Meta might have the resources send messages from that many accounts, but many Fediverse servers don’t have the resources to receive all of them.
This is why resource efficiency is such an important concern for the Fediverse at large. Hence why I’m interested in building a community of #Akkomane enthusiasts.
To give you a general idea at how well akkomane.social scales, it’s currently running on 1vCPU with 2GB of RAM. With these resources, it’s able to host 25 users – and things are humming along quite smoothly.
In contrast, the minimum RAM I’d use for a Mastodon server is 4GB. And that’s only if I posted a few times a day and had an account with less than 100 followers.
So really, if you’re concerned about managing scale, then #Akkomane is a pretty good option for you.
The reason I’m excited about #Akkomane has less to do with whiz bang features, and more to do with scalability of the service.
With typical #Fediverse services, it takes a lot of resources to run them. And the more your server federates with others and redistributes messages, the more of a toll it takes on CPU and RAM.
More than one Fediverse server has closed because server admins simply didn’t have enough money or resources to keep them operating.
But Akkoma is great for low spec servers. This is why so many single-user servers use Akkoma. Unfortunately, the default UI/UX isn’t so user friendly.
However, I’ve discovered that an alternative front-end, Mangane, offers a UI/UX that is both familiar to most people, and offers lots of bells and whistles – such as quote posts, post scheduling, Markdown, etc.
Akkomane offers the best of both worlds: server stability and a friendly UI/UX.
ANNOUNCEMENT: The world’s first general purpose #Akkomane server is here!
With great excitement, akkomane.social is open for registrations!
Akkomane is an alternative to #Mastodon and #Threads that provides incredible stability with a beautiful and futuristic Twitter-like front-end for the #Fediverse.
I have launched akkomane.social to demonstrate this software’s unique capabilities.
Currently, I’m capping memberships to 20 people (not bots). While membership preference is given to those who’d like to build and maintain an Akkomane server, everyone is welcome to apply! More membership slots will be available in the coming weeks.