@tux Running a pretty reasonable stack now ...
FreeBSD 15.0-RELEASE-p5
Mastodon 4.5.8
PostgreSQL 18.3
Valkey 9.0.1
Opensearch (fork of Elastic) 3.2.0
28,4 GB PostgreSQL Database size
162 GB Media Files
4,88 GB Search Index size
@tux Running a pretty reasonable stack now ...
FreeBSD 15.0-RELEASE-p5
Mastodon 4.5.8
PostgreSQL 18.3
Valkey 9.0.1
Opensearch (fork of Elastic) 3.2.0
28,4 GB PostgreSQL Database size
162 GB Media Files
4,88 GB Search Index size
Did quite some maintenance on burningboard.net Mastodon instance today ..
Updated servers and jails to FreeBSD 15.0-RELEASE-p5
1.
proxy_cache_path (S3 media cache) was already on a ZFS dataset with autosnapshot disabled .. But proxy_temp_path and client_body_temp_path (both nginx temp folders) weren't. Leading to extremely bloated daily ZFS snapshots for the Nginx jail. Changed those and cleaned old snapshots -> 31GB reclaimed space
2.
Cleaned up Database Snapshots and did a pg_repack on prod to reclaim deleted database pages -> 3GB reclaimed space
3.
Fixed issue with backend path over gif tunnel to Elasticsearch (6in6). Turned out to be a MSS issue (clamp-mss to 1140 on the tunnel iface solved it!)
4.
Fixed IPv6 routing issue for Prometheus Monitoring after reboot (rc.d static_routes != ipv6_static_routes)
All in all, our instance is in very good shape again :-)
#mastodon #mastoadmin #socialmedia #fediverse #freebsd #unix @tux
Just finished optimizing and checking things after being away from this machine in particular for a while. Our server stack could theoretically handle 5k more registered users and about 1500-2000 monthly active users before we'd need to start thinking about scaling up.
Right now, we have 889 users and around 410 monthly active ones and we're running at roughly 25-30% capacity. Plenty of space to grow.
We're federating with nearly 42000 other servers, which is actually the heaviest part of running an instance, not the local users. Every boost, reply, and follow across the fediverse adds work for our servers.
It was never my intention to grow this server this much or even have this many users, but now we have regular people, authors, political parties, organizations, YouTubers, and more. I'm still amazed about this. Yet I'm keeping a low profile because, even though we have our own admin team, at the end of the day this is still my hobby project organized by me and my wife.
That said, I've done my best to keep things as flexible as possible, and our finances are stable. I'm really glad my "hobby project" has brought so much joy to so many people.
If you know someone looking for a Mastodon home, we've got room 🏠
@bert_hubert op “onzinnig” modereren we niet op mastodon.nl maar wel heel streng op onze huisregels.
Merk je daar iets van? Ik hoop van niet eigenlijk, want dan doen we het pas echt goed. Met dank aan @support waar de echte helden achter zitten.
RE: https://neuromatch.social/@jonny/116344579209407001
#FediBlock @tuban_muzuru (and their other account @tuban_muzuru), see below:
Anyone know a reason to not find accounts that use a signup IP that is a known Tor exit node as a signal of being a bot?
I'm looking at IPs by doing: Query: <reversed-ip>.dnsel.torproject.org → resolves to 127.0.0.2 if it's a Tor exit.
Fediverse admins,
You can get a headstart on moderating your server by using ready-made server blocklists. There are many different lists to choose from, pick the one that suits your server's needs the best.
There's a guide for admins about using ready-made server blocklists on Mastodon here:
➡️ https://fedi.tips/importing-ready-made-server-blocklists-on-mastodon
There's a good roundup of many different blocklists by @oli at:
➡️ https://writer.oliphant.social/oliphant/the-oliphant-social-blocklist
Mastodon pode incluir alerta de marca registrada no instalador
Em breve quem for instalar um novo servidor Mastodon e o endereço da instância incluir "mastodon" ou "mstdn" poderá ver um alerta de marca registrada ao executar mastodon:setup.
A mensagem diz "o nome Mastodon é uma marca registrada e o uso dele é restrito", seguido por um link para saber mais sobre esta política.
A atualização ainda não foi aprovada e não faz parte do código, mas isso pode mudar nos próximos dias.