After reading about the many people who self host their own fediverse instance, I wanted to give it a shot as well!

I won't be migrating this account, but you will see a follow request from one of my new accounts, @navi

I'm trying out #Hollo

I'm testing the import into Hollo again and it seems to be working

#Hollo

OK let's recap.
I have a GMKtec nucbox G3, Intel n100, 512gb ssd, 16gb ram.

• mastodon-glitchsoc: no. Not for a small instance. Too heavy.
• Sharkey: no. Not for a small instance. Too heavy, and too ma'y informations on the screen.
• Mitra: no. Could have been good one, but users can write stuff and make it readable only if you pay with XRM (or other crypto shit)
• Iceshrimp: no. The dev is random.
• Hubzilla: why not. But doesn't work properly with my yunohost setup.
• BonFire: why not. But nobody knows it. There is no mobile app so far, but it's planned.
• Akkoma: why not, but it's hell to install.
• Gotosocial: why not. But there is no UI, need to use phanpy, phanpy doesn't have mobile app and needs to be pinned on the screen. Other mobile apps take GTS in charge though. Haven't found anything bad until now.
• Hollo: why not, but when it will be on Yunohost, otherwise I don't want to use a specific service (railway, as apparently it's the fastest way to install it)
• Snac2: why not, probably the simplest to set up, lightweight. But need an nginx to point the domain on the software, and need a reverse proxy. It has a minimalist UI.

#activitypub #mastodon #glitchsoc #SharKey #mitra #iceshrimp #hubzilla #bonfire #akkoma #gotosocial #hollo #snac2

Hey @yunohost j'ai contacté les devs de #hollo #hollosocial et #snac2 (respectivement @hongminhee et @grunfink ) et le dev de snac2 à dit qu'il serait plus que content d'aider à la mise en place de l'app dans yunohost, et pour hollo le dev m'a donné le lien d'une issue GitHub
Je serais moi aussi plus que content de voir ces apps dans le catalogue et apparemment je ne serai pas le seul.
Prospérité sur vous parce que vous faites un boulot exceptionnel ❤️

Edit: est-ce qu'un traducteur serait disponible pour traduire en français les settings de Gotosocial sur l'interface web svp ? :)

#selfhosting #selfhost #autohebergement #yunohost

Today I found

• Stegodon #stegodon
• Hollo #hollo #hollosocial
• snac2 #snac2

A couple days ago, I got a DM from a #Bonfire user. I happily replied and sent a follow request—but the Accept never came back, even though they hadn't enabled manuallyApprovesFollowers. My DM reply probably never arrived either. Classic interop bug.

I checked out the Bonfire source and dug in. Turns out Bonfire hasn't implemented RFC 9421 yet, so it was silently discarding any activity signed with it. That alone would be workable, except for one more issue: Bonfire was responding 200 OK even when signature verification failed, instead of 401 Unauthorized.

This matters because Fedify implements a double-knocking mechanism—if a request signed with RFC 9421 fails, it retries with the older draft cavage signature. But since Bonfire returned 200 OK on the failed first knock, #Fedify had no reason to send a second one.

I filed two issues on the Bonfire #ActivityPub repo—one requesting RFC 9421 support, and one about returning 401 on invalid signatures. For the latter, I also sent a PR, which got merged pretty quickly: bonfire-networks/activity_pub#9.

That said, individual Bonfire instances won't pick up the fix until they actually deploy it. So in the meantime, I patched Hollo and Hackers' Pub to use draft-cavage-http-signatures-12 as the firstKnock, so Bonfire instances can at least understand the first request.

One last thing: Fedify caches whether a given server supports RFC 9421, and the Bonfire servers I'd already talked to were cached as “supports RFC 9421”—because they'd been returning 200 OK. I had to manually clear that cache on both hollo.social and hackers.pub before everything finally worked.

After all that, the mutual follow went through and my DM reply landed. Worth it.

#fedidev #fediverse #Hollo #HackersPub