I'm really excited about the @gotosocial project. The world needs more compiled software that harnesses the true power of CPUs.
I had a look at the #gotosocial roadmap, and it seems very well planned out. I'm not familiar with #golang, but I hope I can help out some time after my thesis! #activitypub#fediverse#selfhosting#selfhosted
Realized that my tinkering with #GoToSocial, #Takahe, #CalcKey and #Snac2, continuing to use #Pixelfed, #Lemmy and #Bookwyrm, and looking for compatibility problems are part of the same impulse that had me trying out every web browser I could find in the early 2000s and deliberately using Firefox and Opera on Linux as my daily drivers instead of IE on Windows.
It's a drop in the ocean, but it's my push for interoperability over #monoculture.
I guess it really is #Ivory "for Mastodon" since it can't retrieve a timeline from an #Akkoma instance. Probably not even worth trying on a #GotoSocial instance, right?
Le sigh. Let's hope people stop writing and testing only against Mastodon instances. Soon.
Started self hosting mastodon with gotosocial at sanchayanmaity.com. gotosocial being very alpha, it will be quite a while before I make that my primary account (probably going to end up being another year or two) but everyone on my follow list will see another follow request. Sorry about that 😅.
While making the decision considered snac2, ktistec and akkoma.
snac2 being in C was my first choice but was not sure about long term viability project wise. Push comes to shove I can always maintain C code base myself.
ktistec done in crystal lang and am fine with building from source. But one extra step. More features complete compared to gotosocial. This and gotosocial are the only viable simple alternatives IMO.
akkoma seemed still complex.
gotosocial implemented in go. Seems about right for self hosting. Get the release binary tar ball, extract, modify domain setting in config, put systemd service in place, add reverse proxy to nginx and done. Oh a database is needed, but just had to add a table to postgres since I already had it running for forgejo. If a db and nginx are already running, there is hardly much required for these two. Well reading for the first time took a while but very easy to get running.
Mastodon is good and all, but self hosting could be a little friendlier for single user instances. Till a Rust implementation comes along if at all, putting my money in gotosocial 🤞.
I have to admit that #Elk (@elk) is a pretty neat #Mastodon client if you're looking for a Twitter-like experience.
Feels very snappy and has all the feature I need. A few glitches with regards to auto-completion of tags and accounts, but I'm confident that the developers will fix those before the first non-alpha release.
Maybe #GoToSocial (@gotosocial) are a good combination for self-hosting. 🤔
I'm curious how people use the #fediverse. Do people have just one account on #Mastadon, #misskey or wherever they post everything from, or do they have an account on a #pixelfed instance for photos, a #bookwyrm instance for book stuff, etc... and just renote as they need across their main ID?
@clanoriana I have a number of accounts but I mostly use this Mastodon account. I have my own #GoToSocial instance but use it minimally until the feature set is sufficient for daily use.
The #fediverse feels very much like its in its infancy and we haven't even seen the killer apps emerge yet.
If an actor provides an outbox URL, but not an inbox URL, it means that it cannot receive Follow activities and it can not push content to the followers. In such cases, the follower's server should switch to periodic polling like RSS.
This will enable statically-built blogs ( #jekyll#hugo etc) to appear in Mastodon network.
So, my curiosity to try all the things that connect to the #fediverse... Currently running #Akkoma and testing it out (not followed anyone to avoid confusion and annoying people. I do follow fellow Akkoma admins @MisterArix and @eviloatmeal). Also running #GoToSocial on a different box, but that one maybe torn down soon. It's great alpha software, I'm super curious to see how it is when they get more features added.
Finally worked out how to get #GotoSocial federating to #Honk with a couple of quick-fix-kludges. I know how to (mostly) properly fix the second (Honk rejecting GtS statuses) but the first (GtS rejecting Honk follows) is a bit trickier.
In the process of debugging that, I had to debug #Toot and fix that to allow it to post statuses to both GtS and#Akkoma. FFHS.
Hopefully the ActivityPub spec will get firmed up now it’s in active use and we can get rid of these stupid nonsense incompatibilities before I go completely insane.
@magnus919 That does look interesting. I just wish somebody would develop a way to migrate from one server type to another on the same domain so we can easily play around with different ActivityPub implementations.
@mmeier FWIW, I’m intending to have #GoToSocial and #Takahe running side by side, not just to learn more about each, but to understand federation dynamics between them from both sides of the equation.
I'm playing around in #takahe 's GitHub repo and checking out the docker-compose.yml (which is not yet meant for production... but is still informative).
I'm really liking how all state is kept in the database. There are no persistent volume claims for Takahe itself. All configuration for Takahe is externalized through inherited environment.
@jbeimler yeah these are exciting times for the #fediverse. I’m setting aside time to play with #goToSocial and #takahe and see if I can give back to either project in terms of operational doc, Docker compose examples, etc.
When someone asks about options for servers or clients I have a habit of tagging recommendations, and when there is not an account for the thing, I have to stop and search for a dev or find a website address to link to etc.