#instanceadmin — Public Fediverse posts

"ho'omalu is an account assessment service for Mastodon. It evaluates new registrations using multiple independent signals, calculates a weighted risk score, and produces a moderator-friendly traffic light verdict"

https://codeberg.org/nesges/ho-omalu

#Mastodon #ServerAdmin #InstanceAdmin #AntiSpam

"ho'omalu is an account assessment service for Mastodon. It evaluates new registrations using multiple independent signals, calculates a weighted risk score, and produces a moderator-friendly traffic light verdict"

https://codeberg.org/nesges/ho-omalu

#Mastodon #ServerAdmin #InstanceAdmin #AntiSpam

✅ Successful gotosocial-0.22.0 (new stable major release) build and package available here https://pepperm.int.eu.org/pkgsrc/packages/All
From now on, this GTS version is stable: further upgrades will only be available from pkgsrc repository and GTS Codeberg repository (no need for me building -rc packages anymore, that's a good thing).

✅ Submitted a package update to pkgsrc-WIP for v0.22.0, with help of wiz it should be good.
One may use pkgin or NetBSD pkg_add tools to upgrade GoToSocial from now on.
Careful about releases notes and configuration or database breaking changes.

Build platform: NetBSD 10.1 amd64 / pkgsrc trunk
Compilation and linker flags aligned with GTS binary release on Codeberg

#pkgsrc #pkgsrc-wip #gotosocial #netbsd #instanceadmin

✅ Successful gotosocial-0.22.0 (new stable major release) build and package available here https://pepperm.int.eu.org/pkgsrc/packages/All
From now on, this GTS version is stable: further upgrades will only be available from pkgsrc repository and GTS Codeberg repository (no need for me building -rc packages anymore, that's a good thing).

✅ Submitted a package update to pkgsrc-WIP for v0.22.0, with help of wiz it should be good.
One may use pkgin or NetBSD pkg_add tools to upgrade GoToSocial from now on.
Careful about releases notes and configuration or database breaking changes.

Build platform: NetBSD 10.1 amd64 / pkgsrc trunk
Compilation and linker flags aligned with GTS binary release on Codeberg

#pkgsrc #pkgsrc-wip #gotosocial #netbsd #instanceadmin

✅ Successful gotosocial-0.21.3 (current stable) build and package available here http://pepperm.int.eu.org/pkgsrc/packages/All/

✅ Submitted a package update to pkgsrc-WIP for v0.21.3, with help of wiz it should be good

Build platform: NetBSD 10.1 amd64 / pkgsrc trunk
Compilation and linker flags aligned with GTS binary release on Codeberg

#pkgsrc #pkgsrc-wip #gotosocial #netbsd #instanceadmin

✅ Successful gotosocial-0.21.3 (current stable) build and package available here http://pepperm.int.eu.org/pkgsrc/packages/All/

✅ Submitted a package update to pkgsrc-WIP for v0.21.3, with help of wiz it should be good

Build platform: NetBSD 10.1 amd64 / pkgsrc trunk
Compilation and linker flags aligned with GTS binary release on Codeberg

#pkgsrc #pkgsrc-wip #gotosocial #netbsd #instanceadmin

@gotosocial @netbsd ✅ Successful gotosocial-0.22.0-rc3 build and package available here https://pepperm.int.eu.org/pkgsrc/packages/All/

Build platform: NetBSD 10.1 amd64 / pkgsrc trunk
Compilation and linker flags aligned with GTS binary release on Codeberg

Will submit a package update to pkgsrc-WIP when GTS reaches 0.22.0-GA 😊

#pkgsrc #gotosocial #netbsd #instanceadmin

Mastodon security team sent me a message saying that my account has been reported and will be deleted by my server admin unless I follow some steps.

Yeah about that...

#InstanceAdmin #mastodonsecurityteam #johnmastodon

Mastodon security team sent me a message saying that my account has been reported and will be deleted by my server admin unless I follow some steps.

Yeah about that...

#InstanceAdmin #mastodonsecurityteam #johnmastodon

#InstanceAnnouncement Coordinated Potential Bot Network Suspended

We have detected and suspended 5 coordinated bot accounts today.

Indicators of Compromise:

• Content consists of semantically incoherent English text generated by LLM — no direct harm observed, but likely used for account seasoning and filter evasion
• All 5 accounts registered between 2026-03-18 17:52 and 2026-03-19 23:50
• Profiles contain a single English sentence + emoji, or several meaningless English phrases
• All connection IPs belong to Cloudflare proxy ranges
• Registrant domains include disposable email services and high-risk domains

Actions Taken:
Accounts suspended (all IPs verified as Cloudflare IPs — no user privacy has been compromised):
@iwutyp 162.159.XXX.XX
@PhyllisReynolds 172.70.XXX.XXX
@ezob 104.23.XXX.XX
@uhux_xudym 104.23.XXX.XX
@Ethel_Robinson 172.68.XXX.XXX

Email domains blocked:
tmail.lt, maxseeding.vn, dqsbf.blema.io.vn, sphinx.launders.money, kimora.space

Notes:
Registration had previously been set to open in order to simplify the sign-up process. We are now enabling "Require approval" + "Require a reason to join".
If you spot accounts with similar characteristics, or matching email domains/IPs, please report them.
This instance does not welcome malicious or unmoderated bots.

#mastodon #fediverse #antispam #spam #instanceadmin #moderation

#InstanceAnnouncement Coordinated Potential Bot Network Suspended

We have detected and suspended 5 coordinated bot accounts today.

Indicators of Compromise:

• Content consists of semantically incoherent English text generated by LLM — no direct harm observed, but likely used for account seasoning and filter evasion
• All 5 accounts registered between 2026-03-18 17:52 and 2026-03-19 23:50
• Profiles contain a single English sentence + emoji, or several meaningless English phrases
• All connection IPs belong to Cloudflare proxy ranges
• Registrant domains include disposable email services and high-risk domains

Actions Taken:
Accounts suspended (all IPs verified as Cloudflare IPs — no user privacy has been compromised):
@iwutyp 162.159.XXX.XX
@PhyllisReynolds 172.70.XXX.XXX
@ezob 104.23.XXX.XX
@uhux_xudym 104.23.XXX.XX
@Ethel_Robinson 172.68.XXX.XXX

Email domains blocked:
tmail.lt, maxseeding.vn, dqsbf.blema.io.vn, sphinx.launders.money, kimora.space

Notes:
Registration had previously been set to open in order to simplify the sign-up process. We are now enabling "Require approval" + "Require a reason to join".
If you spot accounts with similar characteristics, or matching email domains/IPs, please report them.
This instance does not welcome malicious or unmoderated bots.

#mastodon #fediverse #antispam #spam #instanceadmin #moderation

Mastodon 4.5.6 update deployed

:alex_grin:

#instanceAdmin

Mastodon 4.5.6 update deployed

:alex_grin:

#instanceAdmin

Mastodon v4.5.5 update deployed

#instanceAdmin

Mastodon v4.5.5 update deployed

#instanceAdmin

To improve timezone coverage @k8vsy has been promoted to moderator.

#instanceAdmin

To improve timezone coverage @k8vsy has been promoted to moderator.

#instanceAdmin

@RaysofRed
This instance has been on the #GardenFence blocklist for a long time.

If you're an #instanceAdmin, you should look into it.

@RaysofRed
This instance has been on the #GardenFence blocklist for a long time.

If you're an #instanceAdmin, you should look into it.

Sorry, should have posted an announcement before taking the server down for longer than planned.

However!

christopher@mastodon:~$ cat /etc/debian_version
13.0

#instanceAdmin

Sorry, should have posted an announcement before taking the server down for longer than planned.

However!

christopher@mastodon:~$ cat /etc/debian_version
13.0

#instanceAdmin

I've just paid the invoice to renew the mastodon.radio VPS for another year :alex_partying:

We have enough cash on hand to keep running at current costs for 4 more years (2030) :alex_scream:

If you want to support the instance financially I'd suggest helping out @nocturne who made our awesome Alex emoji - either by commissioning your own emoji or just a direct donation :alex_pleading:

#instanceAdmin

I've just paid the invoice to renew the mastodon.radio VPS for another year :alex_partying:

We have enough cash on hand to keep running at current costs for 4 more years (2030) :alex_scream:

If you want to support the instance financially I'd suggest helping out @nocturne who made our awesome Alex emoji - either by commissioning your own emoji or just a direct donation :alex_pleading:

#instanceAdmin

I've enabled "Fetch all replies"

In theory this should mean you see all / most / more of the replies to posts from other servers - even if the replies wouldn't usually have arrived at our server.

https://docs.joinmastodon.org/admin/config/#fetch-all-replies

#instanceAdmin

I've enabled "Fetch all replies"

In theory this should mean you see all / most / more of the replies to posts from other servers - even if the replies wouldn't usually have arrived at our server.

https://docs.joinmastodon.org/admin/config/#fetch-all-replies

#instanceAdmin

Done!

Updated to v4.4.1 of the mastodon server software.

https://github.com/mastodon/mastodon/releases/tag/v4.4.0
https://github.com/mastodon/mastodon/releases/tag/v4.4.1

#instanceAdmin

Edit: done.
We now have 24G ram and 6 CPU cores.
This should keep everything ticking along nicely rather than pegging the CPU all the time.

Mastodon.Radio server will be rebooting "soon" to upgrade the vps.

#instanceAdmin

Mastodon.Radio server will be rebooting "soon" to upgrade the vps.

#instanceAdmin

Mastodon.radio updated to v4.3.9 of the server software.

https://github.com/mastodon/mastodon/releases/tag/v4.3.9

#instanceAdmin

Mastodon.radio updated to v4.3.9 of the server software.

https://github.com/mastodon/mastodon/releases/tag/v4.3.9

#instanceAdmin

Heads up #Sharkey #admins when #upgrading...
If you have a lot of #data in your #instance #database, running pnpm run migrate might fail because one or more of the ALTER TABLE... statements might actually timeout on your #PostgreSQL server!

To fix this, attach yourself to your sharkey database and enter the following...

ALTER DATABASE sharkey SET statement_timeout = '10min'; 
ALTER ROLE sharkey SET statement_timeout = '10min';

We're back!

Sorry for the downtime, the overnight backup used the last spare space and the old backup files weren't being deleted and @M0YNG was asleep :alex_asleep:

You can check if it's us or you https://status.fediverse.radio

#instanceAdmin

We're back!

Sorry for the downtime, the overnight backup used the last spare space and the old backup files weren't being deleted and @M0YNG was asleep :alex_asleep:

You can check if it's us or you https://status.fediverse.radio

#instanceAdmin

Mastodon.Radio updated to v4.3.8

https://github.com/mastodon/mastodon/releases/tag/v4.3.8

#instanceAdmin

EDIT:
Danke an alle & die dank dem #Fediverse, für die Vernetzung und schnelle Reaktion! Wahnsinn! Das Problem war wohl eventuell Lokal. Dank @[email protected] der mich auf die Simple idee gebracht hat, das Bild neu hochzuladen (um es quasi zu erneut zu Pushen), löste das Problem. Zumindest das Profilbild Problem ^^ :D
Für das Icon wird jetzt einfach nen Emoji genutzt. :D



Ich brauche mal etwas Hilfe: Ich betreibe eine eigene Mastodon-Instanz (bzw. Sharkey), aber irgendwas mache ich wohl falsch. Mein Profilbild und das Verifizierungs-Icon neben meinem Namen werden nur lokal angezeigt – auf anderen Instanzen scheint es nicht synchronisiert zu werden.

Woran könnte das liegen?

#Mastodon #Sharkey #Fediverse #Selfhosting #InstanceAdmin #TechSupport #Linux #Docker #Hetzner #FediAdmin #ActivityPub #Profilbild

🔧 Gerne boosten!

Ich brauche mal etwas Hilfe: Ich betreibe eine eigene Mastodon-Instanz (bzw. Sharkey), aber irgendwas mache ich wohl falsch. Mein Profilbild und das Verifizierungs-Icon neben meinem Namen werden nur lokal angezeigt – auf anderen Instanzen scheint es nicht synchronisiert zu werden.

Woran könnte das liegen?

#Mastodon #Sharkey #Fediverse #Selfhosting #InstanceAdmin #TechSupport #Linux #Docker #Hetzner #FediAdmin #ActivityPub #Profilbild

Hi everyone at BSD Cafe,
I’d like to start by thanking everyone for being part of this community - your presence and support truly mean a lot!
This message will appear across all my BSD Cafe social accounts, as I’d like to make sure it reaches everyone. Apologies for the duplication, but I genuinely believe it’s important.

Lately, there have been some discussions and questions surrounding content moderation on our instance, and I wanted to take a moment to offer some clarity and reaffirm the spirit of our community.

As you know, BSD Cafe was founded as a space primarily focused on technology, with a special place for *BSD and open source. More importantly, though, I want it to be a positive, welcoming, and constructive place for everyone. Our community guidelines, especially principles like "Promote Positivity" and "Be Kind", are central to this vision.
I've seen questions arise, sometimes involving accusations of political censorship from different perspectives, regarding why certain posts might be moderated. I want to be very clear on this: My moderation approach focuses primarily on the tone and manner of communication, not the specific topic itself.
I don't intervene simply because a post discusses politics, a particular tech company, or any potentially divisive subject. I do step in when a post, regardless of the topic or the viewpoint being expressed, adopts a tone that is:
* Provocative or intentionally confrontational.
* Aggressive or disrespectful towards other users or groups.
* Overly negative without constructive intent.
* Contrary to our core principles of kindness and mutual respect.
This standard applies equally to everyone and every "side". If someone were to post something like "Users of X software are idiots", I would address that just as readily as any other topic presented in a hostile way, even if I personally dislike software X.
The goal isn't to "censor" opinions, but to preserve an environment where discussions, even critical ones, can happen civilly and respectfully, without descending into flame wars or personal attacks. We aim to be a space that is pro-constructive dialogue and pro-positivity, not anti-anyone.
BSD Cafe is our shared digital home. Let's continue working together to keep it a pleasant and rewarding place where we can share ideas, learn, and connect over our shared passions (tech and beyond!), feeling comfortable and respected.

Thank you sincerely for your understanding and for everything you contribute to making BSD Cafe a special community!
Let's keep building this positive space together.

#BSDCafe #Community #Moderation #Fediverse #InstanceAdmin #CommunityGuidelines #TechCommunity #Positivity #BeKind

Hi everyone at BSD Cafe,
I’d like to start by thanking everyone for being part of this community - your presence and support truly mean a lot!
This message will appear across all my BSD Cafe social accounts, as I’d like to make sure it reaches everyone. Apologies for the duplication, but I genuinely believe it’s important.

Lately, there have been some discussions and questions surrounding content moderation on our instance, and I wanted to take a moment to offer some clarity and reaffirm the spirit of our community.

As you know, BSD Cafe was founded as a space primarily focused on technology, with a special place for *BSD and open source. More importantly, though, I want it to be a positive, welcoming, and constructive place for everyone. Our community guidelines, especially principles like "Promote Positivity" and "Be Kind", are central to this vision.
I've seen questions arise, sometimes involving accusations of political censorship from different perspectives, regarding why certain posts might be moderated. I want to be very clear on this: My moderation approach focuses primarily on the tone and manner of communication, not the specific topic itself.
I don't intervene simply because a post discusses politics, a particular tech company, or any potentially divisive subject. I do step in when a post, regardless of the topic or the viewpoint being expressed, adopts a tone that is:
* Provocative or intentionally confrontational.
* Aggressive or disrespectful towards other users or groups.
* Overly negative without constructive intent.
* Contrary to our core principles of kindness and mutual respect.
This standard applies equally to everyone and every "side". If someone were to post something like "Users of X software are idiots", I would address that just as readily as any other topic presented in a hostile way, even if I personally dislike software X.
The goal isn't to "censor" opinions, but to preserve an environment where discussions, even critical ones, can happen civilly and respectfully, without descending into flame wars or personal attacks. We aim to be a space that is pro-constructive dialogue and pro-positivity, not anti-anyone.
BSD Cafe is our shared digital home. Let's continue working together to keep it a pleasant and rewarding place where we can share ideas, learn, and connect over our shared passions (tech and beyond!), feeling comfortable and respected.

Thank you sincerely for your understanding and for everything you contribute to making BSD Cafe a special community!
Let's keep building this positive space together.

#BSDCafe #Community #Moderation #Fediverse #InstanceAdmin #CommunityGuidelines #TechCommunity #Positivity #BeKind

Hi everyone at BSD Cafe,
I’d like to start by thanking everyone for being part of this community - your presence and support truly mean a lot!
This message will appear across all my BSD Cafe social accounts, as I’d like to make sure it reaches everyone. Apologies for the duplication, but I genuinely believe it’s important.

Lately, there have been some discussions and questions surrounding content moderation on our instance, and I wanted to take a moment to offer some clarity and reaffirm the spirit of our community.

As you know, BSD Cafe was founded as a space primarily focused on technology, with a special place for *BSD and open source. More importantly, though, I want it to be a positive, welcoming, and constructive place for everyone. Our community guidelines, especially principles like "Promote Positivity" and "Be Kind", are central to this vision.
I've seen questions arise, sometimes involving accusations of political censorship from different perspectives, regarding why certain posts might be moderated. I want to be very clear on this: My moderation approach focuses primarily on the tone and manner of communication, not the specific topic itself.
I don't intervene simply because a post discusses politics, a particular tech company, or any potentially divisive subject. I do step in when a post, regardless of the topic or the viewpoint being expressed, adopts a tone that is:
* Provocative or intentionally confrontational.
* Aggressive or disrespectful towards other users or groups.
* Overly negative without constructive intent.
* Contrary to our core principles of kindness and mutual respect.
This standard applies equally to everyone and every "side". If someone were to post something like "Users of X software are idiots", I would address that just as readily as any other topic presented in a hostile way, even if I personally dislike software X.
The goal isn't to "censor" opinions, but to preserve an environment where discussions, even critical ones, can happen civilly and respectfully, without descending into flame wars or personal attacks. We aim to be a space that is pro-constructive dialogue and pro-positivity, not anti-anyone.
BSD Cafe is our shared digital home. Let's continue working together to keep it a pleasant and rewarding place where we can share ideas, learn, and connect over our shared passions (tech and beyond!), feeling comfortable and respected.

Thank you sincerely for your understanding and for everything you contribute to making BSD Cafe a special community!
Let's keep building this positive space together.

#BSDCafe #Community #Moderation #Fediverse #InstanceAdmin #CommunityGuidelines #TechCommunity #Positivity #BeKind

Hi everyone at BSD Cafe,
I’d like to start by thanking everyone for being part of this community - your presence and support truly mean a lot!
This message will appear across all my BSD Cafe social accounts, as I’d like to make sure it reaches everyone. Apologies for the duplication, but I genuinely believe it’s important.

Lately, there have been some discussions and questions surrounding content moderation on our instance, and I wanted to take a moment to offer some clarity and reaffirm the spirit of our community.

As you know, BSD Cafe was founded as a space primarily focused on technology, with a special place for *BSD and open source. More importantly, though, I want it to be a positive, welcoming, and constructive place for everyone. Our community guidelines, especially principles like "Promote Positivity" and "Be Kind", are central to this vision.
I've seen questions arise, sometimes involving accusations of political censorship from different perspectives, regarding why certain posts might be moderated. I want to be very clear on this: My moderation approach focuses primarily on the tone and manner of communication, not the specific topic itself.
I don't intervene simply because a post discusses politics, a particular tech company, or any potentially divisive subject. I do step in when a post, regardless of the topic or the viewpoint being expressed, adopts a tone that is:
* Provocative or intentionally confrontational.
* Aggressive or disrespectful towards other users or groups.
* Overly negative without constructive intent.
* Contrary to our core principles of kindness and mutual respect.
This standard applies equally to everyone and every "side". If someone were to post something like "Users of X software are idiots", I would address that just as readily as any other topic presented in a hostile way, even if I personally dislike software X.
The goal isn't to "censor" opinions, but to preserve an environment where discussions, even critical ones, can happen civilly and respectfully, without descending into flame wars or personal attacks. We aim to be a space that is pro-constructive dialogue and pro-positivity, not anti-anyone.
BSD Cafe is our shared digital home. Let's continue working together to keep it a pleasant and rewarding place where we can share ideas, learn, and connect over our shared passions (tech and beyond!), feeling comfortable and respected.

Thank you sincerely for your understanding and for everything you contribute to making BSD Cafe a special community!
Let's keep building this positive space together.

#BSDCafe #Community #Moderation #Fediverse #InstanceAdmin #CommunityGuidelines #TechCommunity #Positivity #BeKind

Mastodon.radio has been bumped to v4.3.4 of the server software.

https://github.com/mastodon/mastodon/releases/tag/v4.3.4

#instanceAdmin

Mastodon.radio has been bumped to v4.3.4 of the server software.

https://github.com/mastodon/mastodon/releases/tag/v4.3.4

#instanceAdmin

​:repost_ok:​ let's say i set up a local *key instance or something and i shut down my computer for the night

as i understand it, no one would be able to pull any profiles from the instance and no posts, replies, anything during that time would federate over to it. is this correct? #sysadmin #fediadmin #instanceadmin

Apologies for the downtime.

Server ran out of disk space when doing the daily backups.
(A compressed backup of the database is 14G, and older files are manually cleared. (Or not, in this case!))

#instanceAdmin

#instanceAdmin :alex_partying:

mastodon.radio is now running v4.3.2 of the mastodon server software.

PLEASE do a full refresh if you're using the website/progressive app.

Things might be a little slow for an hour or so as the search account database is re-indexed.

Let @M0YNG know of any issues (I'm just a bot/ghost account for them anyway.)

For a list of changes see:
https://github.com/mastodon/mastodon/releases/tag/v4.3.0

plus https://github.com/mastodon/mastodon/releases/tag/v4.3.1 and https://github.com/mastodon/mastodon/releases/tag/v4.3.2

Reason #791 for deploying a #Sharkey instance over a #Mastodon instance to the #fediverse:

User quotas.

I can set per-user quotas and limits for how much #S3 storage my users consume thereby allowing me to grow and manage my cloud storage costs organically.

#MastoAdmin #FediAdmin #ServerAdmin #InstanceAdmin

Bots on Mastodon.radio

There are a couple already, but with botsin.space shutting down it feels helpful to clarify.

Bots are allowed on Mastodon.radio with the following conditions:
* radio related
* post unlisted/"quiet public"
* account is marked as a bot
* profile description points to your (non-automated) fediverse account
* it follows all of our other rules
* it doesn't use and excessive/disproportionate amount of resources (subject to discussion if it becomes a problem)

#instanceAdmin