Buongiorno a tutte e a tutti.
Questo account (netico@nebbia.fail) verrà presto chiuso.
Chi si è divertito a leggere i miei post fino ad ora, potrà continuare a farlo seguendo il mio nuovo account (netico@fediverse.midala.net).
Mi sono trasferito su un'istanza non basata su #Mastodon (in polemica con le decisioni prese dal team che ne guida lo sviluppo). Il mio nuovo accesso al fediverso si fonda su #GoToSocial, un software che tenta un approccio minimalista, più nelle mie corde.
Now that #GoToSocial 0.13.0 is out, we are preparing to take a break :)
If you've been following us for a while, you'll know that every year over the holidays we like to make our github repository and matrix channels read only for a while. This lets us step back from support work for a few weeks, and focus on things other than GoToSocial (seeing friends and family, playing video games, reading, cuddling our pets), in order to recharge our mental and emotional batteries and come into the new year feeling fresh and excited again.
This year, we'll take our holiday from (and including) the 19th of December, up to (and including) the 2nd of January. During this time:
the three GtS matrix channels will be read only
the github repo will be read only for non-members of the org (though you may still see us pushing commits and whatnot)
we will be less active on this account
So, if you spot any issues with v0.13.0, please file them before the 19th, or save them until after the 2nd.
I installed #GoToSocial for friends and me, and I like it. However, I would like to keep the instance closed for now, while our circle and some friends are getting used to it.
❓ Is there a way to disable federation in GoToSocial and set the default post visibility/privacy to public?
I looked for it and couldn't find instructions for admins easily on those matters. In general I do support GoToSocial's default settings, but in my case other settings would be more suitable.
Is the ballooning server storage requirements for Mastodon (e.g. for small single-user or family instances) a side-effect of being a good ActivityPub client itself, or just a Mastodon thing?
E.g. if I wanted a just-as-federated server but running, say, GoToSocial instead, would I need just as much disk space?
The Feditext iOS client for Mastodon, GotoSocial, Firefish, etc. now has its own account on fedi.software! Please follow us here for official Feditext updates and announcements.
The other day I was messing around with the lightweight alternative to Mastodon called #GoToSocial (currently in Alpha).
Anyway I registered a silly little domain name (https://bits.lag.tf) and have now been running it for a while in production on a tiny Alpine #Linux container on my home server.
I thought I'd put it out there if anyone is interested in a test account DM me your email and desired username or fill out this form and I'll set you up.
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
Here's a strange question, maybe for my @admin -- setting aside the need to upgrade to #mastodon 4.1.4 -- I've been looking at #gotosocial and I'm unable to search anyone on any instance. However, from another #mastodon instance (happens to be 4.1.4) I AM able to search & follow accounts on #gotosocial instances.
So I guess the question is, is kolektiva.social blocking gotosocial instances, or are they all blocking kolektiva.social, or is mastodon 4.1.3 not compatible, or ... why would this behavior arise?
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.
The alpha version of @gotosocial now has support for allowlists.
Allowlists automatically prevent federation with all other servers, except those that the admin has added to their allowlist. (Traditional blocklists work the other way round, allowing all federation unless a server is blocked.)
Allowlists bring more safety but also reduce reach, and that's why it's up to each admin to decide whether to use them.
This week I boosted posts from #GoToSocial and #Akkoma instances and followed someone on a #Funkwhale instance all from my #Mastodon instance, as if they were all Mastodon posts and accounts.
Every morning, an instance administrator wakes up knowing they need to keep the infrastructure running smoothly for their users, ensuring a good and free social experience.
Every morning, a Fediverse user wakes up knowing they will find many people eager to socialize and interact, who strive to keep the Internet a place for the free exchange of ideas and opinions, away from the dynamics of closed protocols and Big Tech monetization.
It doesn't matter if you are a server administrator or a Fediverse user, thank you for being here and for contributing every day with your efforts to keep the Internet a free place.
#GoToSocial memory usage looking good now (the important line is the orange one - heap size); looks like @kim has fixed the increased memory usage we were seeing on main recently.
To help you understand the graph: the high yellow line is memory allocated to GoToSocial by the operating system, the blue and red lines are idle/released bytes respectively, and the orange line is actual memory currently in use.
That's on a config with 60MiB of cache space configured, with hydrated caches, so account for 60MiB of cache usage, and about 40MiB for everything else (running the web server, constantly responding to requests, processing incoming data, media, etc etc).
almost finished the self-serve email change mechanism for #GoToSocial, a nice simple form on the settings page with a little info thing to remind you if you already have an email change requested/pending