I think this #GoToSocial instance ran on #OpenBSD #arm64 using #ODROID HC4 is doing pretty well while eating (only) 5W.

Alt...

A Grafana stats dashboard showing responsiveness of HTTP responses.

is the best #fediverse #selfhosted solution still #GoToSocial ?

@nw@ioc.exchange

You may want to have a look on #GoToSocial and #snac.

You can also install #Friendica on a shared hosting (classic #LAMP environment). Did this for testing some years ago.

My own project #Mammuthus isn't ready for the stage yet.

@phanpy@hachyderm.io

Once, someone asked what was the weirdest platform you run GtS on. Well...

This message was sent from #GoToSocial running on an #OpenBSD #arm64 board (#ODROID HC4).

But But But !!!! I just realized #Ivory for iOS have been updated on my iPhone and now supports… markdown 🎉

Thanks @ivory@tapbots.social. You’re now my preferred iOS App for using #GoToSocial 😆

Ok, as RPi has limited issue, let's build #GoToSocial for #OpenBSD on the #ODROID HC4... So far, nice things:

• compiling lines seem to scroll faster.
• it doesn't use more than 6W (according to the Shell Plug) while compiling.

EDIT 1 hour later: all GtS stuff are build. Power consumption never went above 6W. Now idling at 5W :)

EDIT 1h15 later: GtS started, created its SQlite database and displayed its Web homepage. This sounds great.

It takes aaaaaaaaaaages to compile #GoToSocial for #OpenBSD on a #Raspberry Pi Zero 2 W... but it's a good stableness benchmark. So far, it has not hanged - now that I use another Ethernet Hat and POE adapter.

EDIT, 3 hours later:

# uname -a
OpenBSD PiZero2W.home.arpa 7.8 GENERIC.MP#6 arm64

# ./gotosocial --version

!! you are using an unsupported build configuration of gotosocial with WebAssembly disabled !!
!! please do not file bug reports regarding media processing with this configuration !!
!! it is also less secure; this does not enforce version checks on ffmpeg / ffprobe versions !!
gotosocial version 0.21.2+git-343fed2

some more yarn spells are required now...

EDIT, 4 hours later:
if something had to fuck with low memory, it had to be Java shit stuff.

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

EDIT, 6 hours later:
Damned! The RPi died while I left it unsupervised :-/

Oh… not sure if that’s #Ivory or #GoToSocial, but it happens that other replies to posts only appear after I actually reply.

I generally read the whole thread to ensure I don’t reply something that was already said. But this "bug" turns you into a "already been said twice boy" :(

@hi ah, I question I just cannot resist!

I have my own instances of #Gotosocial, #snac2, and... #honk, all for my own use.

All running as jails on a FreeBSD box with an 8 core Ryzen 7 and 32GB memory, but those 3 jails, plus a couple of others only really utilise about 4-5GB.