Considering creating a second codeberg account to hide my embarrassment when putting in a feature request to GoToSocial and the masto-frontend they forked for.... support for the weather.

I was looking at someone's neocities page and I love that their little feed has the weather and their little sprites. I'd love to be able to look back on my timeline and see if there's any correlation between the kinds of posts I do, and what the weather was like. I know it's really silly, and it would be like... the lowest importance feature request, but it could be fun.

Maybe climate nerds find this data interesting as well. I'm sure there's like... one other fedi user interested in the weather of their follows/followers. It can't just be me 

#gotosocial

Lost Letters

Updated this #gotosocial instance to 0.21.2

I’ve been having weird media bugs that prevent me from viewing any videos you post on my phone.

Seems that the first reasonable step in troubleshooting would be to get up to date.

Today on NovaLandia: "From GoToSocial and Back to Mastodon"

It's been a *wild* ride since I shutdown my Mastodon instance here on mkultra.monster. From spending time on Bluesky, and being disappointed by their financial and political decisions, to joining nume...

https://mkultra.monster/fediverse/2026/03/31/gts-to-mastodon/

#socialmedia #mastodon #gotosocial

From GoToSocial and Back to Mastodon | cmdr-nova@internet:~$

It's been a wild ride since I shutdown my Mastodon instance here on mkultra.monster. From spending time on Bluesky, and being disappointed by their...

cmdr-nova@internet:~$
Guten Morgen! ☕️
Ich hatte da letztens so einen Gedanken: Wie geil wäre es bitte, wenn wir in den Schulen nicht nur über Social-Media-Verbote diskutieren, sondern das Problem einfach selbst lösen?

Stell dir vor, man setzt mit Schülern ein eigenes Projekt auf: Eine eigene GoToSocial-Instanz oder einen Matrix-Server für die Kommunikation und den Austausch. Anstatt die Kids an Meta und Co. zu verlieren, zeigen wir ihnen, wie man die Technik dahinter einfach selbst hostet.

Das Ergebnis: Volle Souveränität über die eigenen Daten, aber mit demselben Feeling wie bei Instagram oder WhatsApp. Medienkompetenz nicht nur als Theorie, sondern zum Anfassen.
Was hältst du von der Idee, Schüler zu ihren eigenen Providern zu machen? 👇

#Fediverse #Mastodon #GoToSocial #Matrix #SelfHosted #Medienkompetenz #DigitaleSouveränität #Schule #OpenSource

@cholling If you want to attach images you should take #GoToSocial because #WriteFreely has no image space – u have to host your images somewhere else.

[1] https://writefreely.org/docs/main/writer/writing

Writing Posts — WriteFreely Documentation

I'm considering setting up a self-hosted, single-user instance for long-form writing. At the moment I'm thinking of using either #gotosocial or #writefreeley but I'm open to other suggestions. Does anyone have experience with these who could offer pros and cons?

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.

So a couple of things.

@[email protected] just brought up a new instance because the hosting provider he is using had some issues with the hypervisor that his instance was running on. Also I think I may have taken down his new #gotosocial instance with a boost of his message. I'm sorry buddy 😥

I have been running #snac over the last month and a bit (and it also powered a few of my previous instances). The nice thing about snac is that it doesn't use a database of any kind. Everything is stored as files on the filesystem and there's heavy use of hard links to make things work. The benefits of this? No risk of database corruption. And, here's the big one, backups are done by creating a tarball of the instance's running directory. No fuss, no muss.

I agree that monthly backups aren't good enough, I do a hybrid four hour + weekly backup. I do it using mod + date. Here's a sample. I run the script every four hours and it creates a tarball based on a mod of the week number -- I have it set at four to keep a total of four weeks and then rotate. This tarball gets backed up off the VPS every four hours.

The VPS hosting provider that I use also offers seven image backup slots to be used daily, weekly or monthly. I have it set for weekly.

Oh, and lastly, while I am not running a backup instance (too much work), this account is my secondary account if anything were to happen to my instance: @[email protected]

#fediverse #snacadmin #sysadmin

@evan This looks really useful to me as I've been trying to move my primary account on a big server to this single-user instance running #gotosocial. The only sticking point until now is that I rely on hashtags to find new content and my server, although fairly well federated (5k other servers), just doesn't see nearly any hashtag activity.

However, I can't find the followback account from my server. Nothing is returned by search in either the Phanpy or Elk interfaces. Nor can I find any of the hashtags accounts. Do you think this an issue with gotosocial, or my server specifically?

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 :-/