Replying to all the random individuals that seem to think that I’m “endorsing” one of the Fediverse products over any other, and seem to be making a big deal over #akkoma vs #mastodon etc.
That’s not the case. I’m actually a horrible MIS person, and I would never want to maintain my own server. I’m a programmer for chrissake!
The same way you should fear me if I hold a soldering iron, you should be very very nervous if I were to do any server management.
So all credit (or blame) for the choice of Fediverse platform goes to @monsieuricon, who maintains kernel.org and just made it really easy for me to try this out.
… and on a similar note: not only am I not much of a MIS person, I’m also not much of a social networking person.
I foresee a lot of disappointment in the future of any followers of this account 🔮.
I’ve been away from the #Fediverse for a while and it seems like new platforms are popping up. My third-party Mastodon client don’t always fetch all the posts from instances like snowdin.town and #akkoma, and it seems like people are having lots of fun there too. I’d like to learn more about them. Please reply with resources!
I'm pretty sure that the #Fediverse is one of the first social networks I've been on that didn't ever ask me to betray any of the people in my address book.
Well, that's it. My #akkoma instance social.fellr.net is no more. It couldn't even delete my old account properly without getting a timeout on the database. Man, I really don't like the way it's designed. I know it's better for the #fediverse if not every instance is #mastodon, but at the moment there is nothing better in terms of reliability. Again, #gotosocial is very promising, but needs a bit more features. They're coming though! #fediadmin#meta
Bafflingly, the MastoAPI doesn’t allow you to specify created_at when posting a status. Which makes historical importing a bit tricky (and presumably is one of the reasons why you can’t migrate your statuses when you migrate your account…)
Update: I am not enjoying patching #Akkoma to allow backdated posts because a) It's Elixir and therefore largely incomprehensible, b) almost zero commentary to help you follow the code, and c) uber-abstraction down to tiny functions which means you have to have 20 files open to track down one action.
Tempted to move the damn bots to #GotoSocial just because that code is at least in a language I use (but still largely comment-free and over-abstracted.)
In contrast, adding the ability to backdate posts to #Honk took me about 15 minutes.
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.
Finally up and running with an Akkoma instance now. Will play around with this for a week or two but chances are this will become my primary account in the end.
If you haven't been following along I've been frustrated with Mastodon consuming too much server capacity, and have wanted to try something more suited for a single-user instance.
My research led me here, and by truly pushing the boundaries of my server skills I managed to set up my own #Akkoma instance.
It's not pretty (not much Fediverse software seems to be), but it gives me a lot more control in a much more streamlined install. I will likely design my own theme for it as well.
The more I use different #fediverse apps, the more I feel that we are on the edge of a different future, in the early stages of something that we haven't seen before.
In the last few months, I've used #Mastodon, #Misskey, #Calckey, #Funkwhale, #lemmy, #Peertube, #Bookwyrm and #Pixelfed. Soon, I'm going to try an install of #kbin. In the not too distant future, we will see #GreatApe bringing more options for video chat to the Fediverse. There are countless more platforms that I haven't had a chance to try.
The network formed by the interconnections between those apps is the Fediverse; a Federated Universe. Federated, because everything out there is connected with everything else, in one giant network. What I am truly beginning to appreciate is just how real that vision is, and just how disruptive to our future it's going to be. More than a truism, these the fediverse platforms really will allow us to see and interact with nearly anything else out there.
The platform we use no longer determines the information we can access; it doesn't build walls around us. Instead, what out choice of platform determines, is how we interact with information, rather than determining what information we are able interact with in the first place. The walls in the walled garden haven't so much been torn down, as simply never built.
I can write a blog post, and someone on Mastodon can reply to it. I can make a group post on lemmy, and someone from Calckey can reply to it. I can see an awesome photo on Pixelfed, bring it in to #Akkoma and boost it for everyone else to see. And then anyone who sees it can interact with it.
The cross platform interactions are still imperfect. Standards are still being developed, code is still being written and features are still being defined, but the future is right here, we are on the cusp of something new and amazing.
Of course, this is all old news to someone who has been part of the fediverse for years now, but it feels different now. The momentum is here, we are seeing a shift and I think once we cross that precipice, once we have normalised the cross channel interactions we are starting to develop, it's going to be very hard to go back.
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.
@tmp je relance ta question, vu la peu de réponses et qu'elle date ça serait intéressant d'avoir des réponses plus récentes 🙂
Et j'élargirai à #Pleroma et #Akkoma#Calckey.
En particulier, quelles fonctionnalités sont exclusives¹ à Pleroma, Akkoma, #Misskey, Mastodon/#GlitchSoc (et leur éventuels dérivés ?) ?
Quelqu'un a fait un comparatif ?
¹ soit complètement (ex:formater un message) et non compatibles, soit compatible en lecture (ex: tel logiciel peut voir, mais pas faire la même chose).
L'objectif est d'avoir de la manière la plus synthétique possible une comparaison assez complète des différents logiciels, prioritairement côté utilisation.
Dégager leurs spécificités, leurs avantages, inconvénients…
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.
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.
I think the issue with #pleroma was just not really understanding the resources needed to build vs run, so it might be worth revisiting that or #akkoma maybe, to experiment.
The weirdness of course being that you can’t really swap out backends easily since the federation basically locks other instances to this particular instance running -this particular software- which still confounds me.