jrollans.com is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
We just shipped some new features of our own to mementomori.social! 🎉
New:
- "For you" feed (experimental). Open your home column settings and switch on "Ranked order" to try an algorithmic feed: posts ranked by engagement and by who you interact with, fresh content on every refresh, and you'll rarely see the same post twice. Flip on "Include posts from people you don't follow" to discover new accounts beyond your follows. See someone interesting there? Tap the + on their avatar to follow them.
- PageUp and PageDown scroll the page normally again (thanks @anotherdream for the feedback on this one!)
- The navigation is a bit tidier: Collections and Followed hashtags now live under "More".
The For you feed is fully opt-in. Your home feed stays exactly as it was unless you turn it on. Feedback very welcome!
Fork source and PR drafts available: https://github.com/mementomori-social/mastodon/tree/mementomods-2026-06-07
Full feature list: https://help.mementomori.social/mementomori.social/instance-features
Another feature I decided to steal from the other place. Looks like my hyperactivity set me on fire.
Sorry, @timitii, for putting you on the spot in my dev environment.
In the span of just a week I was left twice with Sidekiq not doing it's job, building up some serious queues and unprocessed events.
I still don't know what caused it, but I suspect that perhaps the DoS bug fixed in Mastodon 4.5.10 was the culprit.
Having now updated to version 4.5.11 it was also the excuse I needed to do some other performance tuning such as optimizing event workers and distributing the load across multiple workers for Sidekiq queues.
Additionally I made some changes to postgres tuning parameters to ensure a more appropriate configuration for the server it was running on; I had not done that before.
All in all, not necessarily downtime but the outcome was pretty much the same anyway.
TL;DR - Some unexpected "downtime" possibly due to a bug in Mastodon, upgraded to 4.5.11, tuned the db, tuned Sidekiq, we're back and kickin' again. I think.
Bill C-34, the new Digital Safety Act / Safe Social Media Act.
If this passes, this will have sweeping repercussions for the Canadian fediverse.
Experimenting with an opt-in ranked home timeline ("For you" feed) for Mastodon, just for myself and in my own fork.
Draft: https://github.com/mementomori-social/mastodon/pull/4
#MastoAdmin #Mastodon #MementoMoriSocial #BuildInPublic #OpenSource
Database cleanup work:
$ psql -c "SELECT pg_size_pretty(pg_database_size('mastodon'))"
pg_size_pretty
----------------
38 GB
(1 row)
$ pg_repack mastodon
INFO: repacking table "public.account_aliases"
....
$ psql -c "SELECT pg_size_pretty(pg_database_size('mastodon'))"
pg_size_pretty
----------------
32 GB
(1 row)
Nice :-) Another successful maintanance ! Also patched up the entire machine and all jails to FreeBSD 15.0-RELEASE-p10 and verified our backups work and are restorable.
GLITCH-SOC Release Watcher » 🤖 🌐
@glitch_soc_release_watcher@mastodon.kodesumber.com
v4.6.0-beta.1
WarningThis is a pre-release! This has not been as widely tested as regular releases, although it is still tested on some servers. If you update to this release, you will not be able to safely downgrade to the existing stable releases. You will,...
https://github.com/glitch-soc/mastodon/releases/tag/v4.6.0-beta.1
Wir sind seit einigen Wochen wieder auf https://joinmastodon.social gelistet, in der Rubrik der regionalen Mastodon-Server. Seitdem ist die Anzahl der Neuanmeldungen von ein bis zwei am Tag auf vier bis fünf gestiegen.
Jedoch sind die meisten Anmeldungen dubios:
- augenscheinlich LLM-generierte deutsche Texte, die dass muss man zugeben, immer authentischer werden, aber (noch) zu aufgesetzt sind.
- Einmal-Mail-Adressen
- IP-Adressen außerhalb Europas
Im Zweifelsfall forden wir nochmal zur kurzen Interaktion auf, bis jetzt kam nie etwas zurück...
We've successfully upgraded our Mastodon server to v4.6.0-beta.1+mementomods-2026-06-07, along with Mastodon Bird UI 4.0.0-beta.1.rc (nightly). Yes, beta, Mastodon has officially crossed from alpha into beta on the road to 4.6.
This update includes today's latest daily build with 119 new commits from upstream since mementomods-2026-05-26.
What's new in Mastodon core - these are the changes Mastodon Team have introduced us in the latest nightly version we are running:
✨️ New features
- Mastodon hit v4.6.0-beta.1, the version we've been chasing through the alpha cycle has crossed into beta, signalling the upstream 4.6 release is getting close
- Collections is in beta! You can now use them on Mementomori.social
- Export Custom Filters, you can finally back up or migrate your filter rules
- A new direct link from Privacy and reach settings to your profile editor saves a click
- Rule acceptance during signup is now a form (better keyboard and assistive tech support)
- Vertical text editing in the alt text editor for languages that write top-to-bottom
- Three new languages in the languages helper: Lazuri, Mingrelian, and Ottoman Turkish
- "Hidden account" message is less misleading when you visit a profile you can't see
- Several internal refactors (BundleColumnError ported to TypeScript, copy-to-clipboard extracted into a hook) that should make future patches smoother
🔧 Fixes & improvements
- Pile of Collections fixes: editor no longer lets you add the same account twice, ValidationError when loading many collections at once is gone, missing null check when importing collections from notifications, and an "about page" error when selecting a non-default Rules language
- Custom filter export had a wrongly-named param
- Profile API documentation link in CHANGELOG corrected
- "Change thumbnail" button no longer shows when it shouldn't
- Server rules and the custom closed-registrations message no longer break
- Custom emoji formatting in usernames inside the `EmptyState` component fixed
- Trending links: author name spacing tightened
- Advanced UI navigation overflow issue fixed
- Signature verification handles invalid keys gracefully
- Container builds no longer fail when the repo name has uppercase characters
- Blocked domains no longer linger in the Elasticsearch InstancesIndex after being unblocked
- Admin Mailer trends mail rendering fixed
- Stylesheet imports are now recursive
♿ Accessibility
- New `PageUp` and `PageDown` hotkeys for list navigation
- Post/feed hotkey navigation made more robust
- Differentiated accessible labels for About links in the footer
📦 Dependency updates
- Vite 8.0.16, Yarn 4.16.0, Sass 1.100.0, Sidekiq 8.1.6, ioredis 5.11.0, ws 8.21.0, axios 1.17.0, react-redux 9.3.0, @reduxjs/toolkit 2.12.0, pg 8.21.0, plus a security update for `@vitest/browser` and many smaller bumps
🐦⬛ Mastodon Bird UI 4.0.0-beta.1.rc (nightly)
This release adds Bird UI styling for the now-live Collections feature:
- Collections nav icon renders again (it was hidden by Bird UI's broad column-link icon-path reset)
- "Follows you" badge in account list items (collections lists, follower lists) uses the same dark pill style as in profiles
- Verified link badge in account list items mirrors the profile field verified style: Bird UI's tick icon and accent link color in place of the green gradient SVG
- All badges in account list items drop the core 4px padding so they sit flush in the row
Plus navigation polish:
- Notifications now sits in the second slot of the side navigation menu, right after Home
- Trends heading no longer renders a stray bottom border
Source code for our Mastodon: https://github.com/mementomori-social/mastodon
Source code for our Mastodon Bird UI: https://github.com/rollecode/mastodon-bird-ui/tree/nightly
As always, if you notice anything unusual or buggy, please reach out to me or any of the admins. Enjoy your time here, and feel free to message me with any questions or thoughts. 
If anything feels off, please let us know!
#MementoMoriSocial #Mastodon #MastoAdmin #BirdUI #MastodonBirdUI #Fediverse
RE: https://burningboard.net/@AlienJay/116682536698437762
Verrückt, ich habe noch nie eine so umfangreiche Diskussion im Fediverse gesehen 😯
Wenn ich es richtig verstanden habe, sind wir zu dem Schluss gekommen, tags.pub nicht zu sperren, und dass jeder Nutzer selbst entscheiden kann, ob er die Instanz blockieren möchte?
It appears colima is unstable for reasons unknown on #newOldiMac. Anyone have any experience running colima on macOS Ventura? Share any tips?
I have just increased its resources for the VM to use 4 of 4 cpus and up to 12GB RAM. Which should be more than enough. We'll see if that stabilizes it, because other than that it has been working well.
Updated my test instance to Mastodon v4.5.11 - perhaps one of the fastest updates so far! Looks like the beta version of 4.6 is out, too.
https://github.com/mastodon/mastodon/releases/tag/v4.6.0-beta.1
Die Instanz https://bayerwald.social läuft jetzt mit Softwareversion v4.6.0-beta.1
https://github.com/mastodon/mastodon/releases/tag/v4.6.0-beta.1
Our MCAT tool, the Mastodon Canada Administration Tool, enables all of our administrators to have deep, audited interactions with our infrastructure.
It was built in-house and is a critical component to keep our instance current.
We are seeing an increased number of account signups on our #Mastodon instance. They are fake and very likely to be a part of the Russian LLM-backed campaign.
The reason for joining tends to be very broad and vague:
I'm looking to join a friendly Mastodon community and participate in discussions.
The email addresses used in these signups are valid (as they are able to verify it), but seem to be automatically generated.
The IP addresses they use either stem from a VPN, Tor exit node or a compromised webhosting thing (we do not log IP addresses - except during the registration, which is deleted once an account is approved or denied).
One positive consequence: this is really helpful to maintain our blocklist
These bots end up being blocked by our pf(4) across the infrastructure.
Heads up: the bot farmers are scraping #mastodon and pretending to be the owners of small artist accounts.
I have confirmed with the owner of the mastodon account that it was not them who applied.
My Mastodon server, cyberplace.social, has received a legal threat in an attempt to have a user's thread deleted. It is styled as a cease and desist.
I have published the email here:
https://github.com/GossiTheDog/Cyberplace/blob/main/LegalThreats/Cease%20and%20Desist%20Order%20-%20Felix%20Juhl
RE: https://socialbc.ca/@chris/116693637298625387
Anyone have any ideas?
I've restored a backup of a mastodon_production database to a new server and I believe this error is coming from when it attempts to connect to the new database.
"Unable to load application: ActiveRecord::UnknownPrimaryKey: Unknown primary key for table accounts in model Account.”
I'm going to try re-restoring the database but this time from the dumpall as opposed to just the mastodon_production db
I was thinking of doing exactly this. Migrating my Mastodon install to Docker.
I run cron jobs to execute CLI commands, how would that work with Docker?
https://mattburke.dev/migrating-native-mastodon-install-to-docker/ from @matt
Ok, I see you could do things like:
```
docker compose exec web bin/tootctl xzy
```
Still it's not super clear to me how to set it up and migrate the existing instance. Feels like several steps for each service, PostgreSQL, redis... I honestly thought it was just setting a composer file and doing `docker-compose up -d`
Hey #mastoadmin folks, the email/username tactics have changed for the troll farms.
- The applications seem to be mostly the most tediously boring CV personal statements possible, including stuff like "respectful conversation" etc.
- Sometimes their request is exactly the same as others you've seen, but with the pre-generated bio string (accidentally?) included. You know, the "Known for ???", "while working in place as occupation", or something about lo-fi.
- Keep an eye out for applications with usernames like firstnamelastname_letter with the email address being approximately that string with the _ replaced by a short alphanumeric string.
- They're putting more effort into getting emails. I had one just now that used atomicmail.io instead of an easier tempmail options like emailondeck or whatever ones are spitting out the .app and .top domains.
- The IPs are not always tagged as tor_proxy but that could just have been luck on their part with the spur(.)us tagging. They're still tagged as a random vpns and proxies though.
These troll farm assholes are also impersonating existing accounts (in this case @federatedmind - I checked with them and their real alts on mastodon instances are on sfba.social, mstdn.social, and mastodon.social). Please be careful and check claims or just reject if the ip/email don't check out.
The farmers also have a new-found hobby of keyword stuffing with phrases you'd expect from corporate/milquetoast liberalism.
(IPs in the screenshot are spur.us-identified proxies, email domains are tempmails)
🇬🇧 Ever wondered how burningboard.net actually runs?
Fully self-hosted in Germany, no trackers, no external logging. Isolated FreeBSD jails, a strict firewall, ZFS and encrypted off-site backups (restore-tested twice a year). Sovereign and transparent. All the details: https://meta.burningboard.net/infrastruktur.html
🇩🇪 Wie läuft burningboard.net eigentlich?
Komplett selbst gehostet, in Deutschland, ohne Tracker und ohne externes Logging. Isolierte FreeBSD-Jails, strikte Firewall, ZFS und verschlüsselte Offsite-Backups (2x im Jahr per Restore getestet). Souverän und transparent. Alle Details: https://meta.burningboard.net/infrastruktur.html
#mastoadmin #freebsd #zfs #gdpr #digitalsovereignty #fediverse
War doch etwas nervig, und außerdem gibt's doch die Relays die eigentlich das selbe machen 🤷♂️
We just released Mastodon 4.5.11 and 4.4.18.
These versions contain several severity security fixes as well as other bugfixes.
Full release notes and update instructions are available on the GitHub releases page.