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.
Anyone who knows #react or some other front end type stuff want to help me with a small project? Looking to created a frontend for #gotosocial (#golang powered #mastodon like service). Just something super basic.
Just curious, according to the #gotosocial page while it does not provide it's own web client, one can use any mastodon client with it: https://joinmastodon.org/apps
To understand them better, I will not stop with just reading and documenting, but might write a app (server, client, bot) to solidify my understanding.
There are different approaches to developing apps for #fediverse
• a typical mastodon app implements both front-end and back-end
• #gotosocial type of apps implement only backend api (along with cli all in #Golang )
• apps like @sengi_app are only at the front-end
• @brianmmdev is implementing a fediverse app via #serverless model
As mastodon picks up steam, we will see different types of apps
I've tried avoiding talking about #Tumblr directly (though there was far less reason to do so, before recently).
Making any project a foil to another existing work will always define it in terms of that other work and, I think, comes off as a waste of everyone else's time.
But I've been seeing a lot of excitement around Tumblr adding #ActivityPub and it has me…Concerned™.
Not due to the size of an instance this would add to the network (though it's a fair concern) nor due to possibly making
corporation (though that /is/ relevant) but we've started developing federated software that we, collectively, can own with no binding need for corporate reliance and…we're already discussing trading that away?
Like, – unless #Tumblr open-sources, /first/ (and I mean #AGPL or equivalent; not even just #GPL), and I'm able to run it on my own server – going to #Tumblr or recommending people to them is just losing the ownership you would otherwise have with a #PeerTube, #GoToSocial, or #BookWyrm.
Thus far the easiest #activitypub service I’ve installed has been #gotosocial, followed by #mastodon, and I wasn’t actually able to get #pleroma (or any forks) to build properly. I’m really rooting for the @gotosocial team and am looking forward to seeing how it progresses.
Tried #gotosocial as the backend instance. It's behaving a little funny and it wasn't any easier to install than I thought it would be from the original #mastodon implementation. So I'm ganna start trying out all of these different ones to see which one I like the best.
@dudenas not dismissing pleroma and gotoSocial etc at all. :) I am very glad these options exist. When I chose to self host in 2020, pleroma was still very new and most of the current alternatives didn't exist yet. Today I am not sure if I might have made a different choice.
but the smaller user base can be a draw back. this post is about options, not dismissing any of them :)
Gotosocial is considered alpha, Pleroma seems to be mature, and quite feature-rich.
Neither of them has properly developed account migration, which is a deal breaker for me. In other words, if you create an account on Gotosocial or Pleroma instance, you might get to stay there, or leave your followers.
@joshuaCrewe It works as good as any other standalone frontend that talks to Mastodon-like APIs, like #Pinafore for example. You can try it out at https://fe.soapbox.pub . It's just that #gotosocial is still missing some endpoints for bookmarks, tags or muting which can cause minor issues (it's still alpha).
What software do people recommend I host if I want to make my own fediverse activity pub server? I was thinking to host pleroma but I would like to get other peoples recommendations.
Aha, nice. I'd personally say there's value to getting more diversity in the kind of apps that are hosted, and then indeed #Pleroma is an option. But also you can consider forks of #Mastodon, such as #Hometown with local-only posting or #Ecko.
If you want to go modern, innovative but still a tad experimental, then #GoToSocial may be a very interesting choice. Bit more experimental still you get to #Bonfire.