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
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
#gotosocial #instance updated to 0.19.1 #instanceadmin
Mastodon.Radio updated to v4.3.8
EDIT:
Danke an alle & die dank dem #Fediverse, für die Vernetzung und schnelle Reaktion! Wahnsinn! Das Problem war wohl eventuell Lokal. Dank @DerSchulze@elbmatsch.de 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
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
Instance updated to 0.19.0 #gotosocial #gotosocialadmin #instanceadmin
Instance updated to 0.18.3 #gotosocial #gotosocialadmin #instance #instanceadmin
Another DNSBL (antispam dns blocking list) shutdown, too much personal risks vs regulations and laws.
Because gdpr and nis2 backfire at small but useful projects like this.
Sad day, isn't it ?
Heads-up mailserver admins: remove ix.dnsbl.manitu.net from your postfix/spamassasin dnsbl
#antispam #infosec #postfix #spamassassin #mailserver #sysadmin #instanceadmin #gdpr #nis2
Mastodon.radio has been bumped to v4.3.4 of the server software.
: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
Instance updated to v4.3.3 of mastodon server software.
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!))
"It's not supported across the #Fediverse to switch between implementations on the same domain."
Is this condition ever going to change? #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
Media Usage:
Currently 21.6GB is used for media, about 100MB are actual media FoxesInLove posted. Everything else is from it's followers. Your instance will cache the profile and header of each follower.
Database:
134MB for PostgreSQL 13MB for Redis
So you have to consider the follower count as well as the following and the activity of the users.
Dunno if someone is interested in it but if you're thinking about your own instance for you and your friends or for your bot, here are some infos:
FoxesInLove is on this instance, the account has around 10k followers. The other accounts on this instance have no significant counts.
Currently this instance has 4 Sidekiq Processes and 4 for Webstuff. (dunno how much CPU power)
If the bot posts something the instance is half dead for a few minutes.
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)
Since I’ve already suspended 1 domain at the instance level, I decided I’d be publishing each domain that I block or suspend here: https://codeberg.org/Screem-Sec/PublicResources/src/branch/main/Mastodon/Blocklist
I want to be extremely transparent while hosting this instance in the event anyone wants to use the resources I make public or want to assess whether they want to join or not.