#mastodadmin — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #mastodadmin, aggregated by home.social.
-
hi #MastoAdmins,
Is there any way to limit the size of files you receive from other instances?
My #Mastodon server often receives huge files -- 100s of MBs in size (videos). I'd rather block them. My Media Usage can get out of hand very quickly.
I can see anything in the docs.
I also run a #GoToSocial instance, and I can limit what I receive. It just means the user has to click a link to open the file on the remote instance. Seems a great solution.
Thanks
#MastodAdmin #serveradmins -
hi #MastoAdmins,
Is there any way to limit the size of files you receive from other instances?
My #Mastodon server often receives huge files -- 100s of MBs in size (videos). I'd rather block them. My Media Usage can get out of hand very quickly.
I can see anything in the docs.
I also run a #GoToSocial instance, and I can limit what I receive. It just means the user has to click a link to open the file on the remote instance. Seems a great solution.
Thanks
#MastodAdmin #serveradmins -
Good news, everyone!
packmates.org was updated to the latest available mastodon version: v4.5.9
-
Good news, everyone!
packmates.org was updated to the latest available mastodon version: v4.5.9
-
Services considering defederating mastodon.cloud
Be aware that account holders are attempting to move their account, and this can take considerable time to complete, several days, especially for members with large follower counts.
Others may still be on 30-day cooldown after having moved there recently.
Please consider Limiting the service while members attempting to move complete that action.
Suspending a service severs all relationships and is unrecoverable.
-
Services considering defederating mastodon.cloud
Be aware that account holders are attempting to move their account, and this can take considerable time to complete, several days, especially for members with large follower counts.
Others may still be on 30-day cooldown after having moved there recently.
Please consider Limiting the service while members attempting to move complete that action.
Suspending a service severs all relationships and is unrecoverable.
-
Hold up! There's a new Mayor in town. 🎩
Let me introduce the new mascot to oslo.town, skillfully crafted by Oslo-based illustrator @Linda_h 🧡
#mastodon #mastodadmin #illustration #oslo #oslotown #bigcatsofmastodon #mascot
-
Hold up! There's a new Mayor in town. 🎩
Let me introduce the new mascot to oslo.town, skillfully crafted by Oslo-based illustrator @Linda_h 🧡
#mastodon #mastodadmin #illustration #oslo #oslotown #bigcatsofmastodon #mascot
-
Er is weer een nieuwe donateur bijgekomen. Dank voor je donatie @IcyPalm!
Wil je ook doneren aan toot.re? Check dan https://opencollective.com/tootre
-
Er is weer een nieuwe donateur bijgekomen. Dank voor je donatie @IcyPalm!
Wil je ook doneren aan toot.re? Check dan https://opencollective.com/tootre
-
Er zijn de afgelopen dagen drie nieuwe donateurs bijgekomen. Hiermee komen de maandelijkse kosten op €22 uit.
Dank daarvoor @Denninger @IngoEveraard @ibAdam 🙏
Wil je ook doneren aan toot.re? Check dan https://opencollective.com/tootre
-
Er zijn de afgelopen dagen drie nieuwe donateurs bijgekomen. Hiermee komen de maandelijkse kosten op €22 uit.
Dank daarvoor @Denninger @IngoEveraard @ibAdam 🙏
Wil je ook doneren aan toot.re? Check dan https://opencollective.com/tootre
-
We waren even een paar seconden uit de lucht voor een update naar Mastodon 4.4.8.
Heb je iets gemerkt? 😉
-
We waren even een paar seconden uit de lucht voor een update naar Mastodon 4.4.8.
Heb je iets gemerkt? 😉
-
RE: https://burningboard.net/@Larvitz/115378987076272282
Schön, dass @Larvitz die Updates immer so schnell einspielt 👍
Ich durfte die neue Fetching-Funktion eben schon live erleben – echt cool!
-
RE: https://burningboard.net/@Larvitz/115378987076272282
Schön, dass @Larvitz die Updates immer so schnell einspielt 👍
Ich durfte die neue Fetching-Funktion eben schon live erleben – echt cool!
-
Hallo,
hier gibt es gleich ein Update auf v.4.5.0-beta.1 von Mastodon. Wir sind kurz weg und kommen ggf. gleich wieder.
Danach bitte Quoten das die Leitungen glühen.
https://github.com/mastodon/mastodon/releases/tag/v4.5.0-beta.1
-
It’s awful again — tons of Russian propaganda spam under the hashtag #ammonia
-
It’s awful again — tons of Russian propaganda spam under the hashtag #ammonia
-
https://bayerwald.social läuft jetzt mit Softwareversion v4.3.7
-
About oligarchy-free social media:
What could the #fediverse or #mastodon do to become more popular?
Multi-tenancy.
For a long time I have thought that a huge adoption barrier is most fedi server software's focus on single-tenancy.
Right now in order to run an instance you need to be able to have server admin skills. You also need to run a server or rent one in the first-place.
This alone makes using a single-user instance much more difficult as it is a reasonable option only for those with the sufficient tech skills.
Why is that important?
Because it means that it's very difficult for regular users to customize their fedi experience to their liking. Instead users have to often hop around instances to find one which suits them and are still often impacted by sometimes arbitrary or very different takes on moderation or how to run an instance.
Yes, managed instance hosting is a thing, but the lack of a multi-tenant architecture means it won't scale well and can't be offered for free. There's no reason why the mastodon process on my server wouldn't be be able to handle 50 different domains and represent them as 50 different instances to the network while having the same or nearly the same server load.
If Mastodon had a multi-tenant setup I could allow every user who so wants to sign up with their own domain name and just worry about acting as a hosting, instead of having to struggle to create a one-size-fits-all set of instance rules, blocklists, etc.
There would still be general rules regarding content I'm certainly not willing to host, but onboarding users would be much easier if there wasn't the constant threat than any of my user's actions could land the whole instance on a fediblocklist.
In the end, I've read about many people who have tried Mastodon / Fediverse or who want to try it, complain precisely about how important and difficult it seems to choose the right instance in the first place. Many who do join without second thoughts, end up having to migrate their account and losing all content in the process. Others don't even get to the point of signing up or, if they do, they use a large instance such as mastodon.social as a safer option, which of course leads to centralization and beats the purpose of federated social media.
As a decentralized social network our goal should be to facilitate as many single-user instances as possible and that is only feasible if the tech requirements are drastically lowered to something like: "bring your own domain or buy it through us, we handle the rest".
-
About oligarchy-free social media:
What could the #fediverse or #mastodon do to become more popular?
Multi-tenancy.
For a long time I have thought that a huge adoption barrier is most fedi server software's focus on single-tenancy.
Right now in order to run an instance you need to be able to have server admin skills. You also need to run a server or rent one in the first-place.
This alone makes using a single-user instance much more difficult as it is a reasonable option only for those with the sufficient tech skills.
Why is that important?
Because it means that it's very difficult for regular users to customize their fedi experience to their liking. Instead users have to often hop around instances to find one which suits them and are still often impacted by sometimes arbitrary or very different takes on moderation or how to run an instance.
Yes, managed instance hosting is a thing, but the lack of a multi-tenant architecture means it won't scale well and can't be offered for free. There's no reason why the mastodon process on my server wouldn't be be able to handle 50 different domains and represent them as 50 different instances to the network while having the same or nearly the same server load.
If Mastodon had a multi-tenant setup I could allow every user who so wants to sign up with their own domain name and just worry about acting as a hosting, instead of having to struggle to create a one-size-fits-all set of instance rules, blocklists, etc.
There would still be general rules regarding content I'm certainly not willing to host, but onboarding users would be much easier if there wasn't the constant threat than any of my user's actions could land the whole instance on a fediblocklist.
In the end, I've read about many people who have tried Mastodon / Fediverse or who want to try it, complain precisely about how important and difficult it seems to choose the right instance in the first place. Many who do join without second thoughts, end up having to migrate their account and losing all content in the process. Others don't even get to the point of signing up or, if they do, they use a large instance such as mastodon.social as a safer option, which of course leads to centralization and beats the purpose of federated social media.
As a decentralized social network our goal should be to facilitate as many single-user instances as possible and that is only feasible if the tech requirements are drastically lowered to something like: "bring your own domain or buy it through us, we handle the rest".
-
Und die nächste #Spamwelle ist unterwegs, diesmal bestehen die Posts nur aus einem blauen QR-Code, der auf einen Kurzlink zeigt (yip.su). Wenn Ihr sowas seht, dann meldet es.
Ich habe auch schon wieder Domains eingeschränkt, von denen mehrere Spam-Accounts kamen:
- ac.akirin.xyz
- usasa.ky -
Und die nächste #Spamwelle ist unterwegs, diesmal bestehen die Posts nur aus einem blauen QR-Code, der auf einen Kurzlink zeigt (yip.su). Wenn Ihr sowas seht, dann meldet es.
Ich habe auch schon wieder Domains eingeschränkt, von denen mehrere Spam-Accounts kamen:
- ac.akirin.xyz
- usasa.ky -
And we're back on v4.2.13
Any strong opinions on trying the release candidate for v4.3 vs. waiting for a real release?
-
They informed us that they need a downtime for up to 1h. So we will be down soon. #mastodadmin
-
They informed us that they need a downtime for up to 1h. So we will be down soon. #mastodadmin
-
Die Instanz https://bayerwald.social läuft jetzt mit der Softwareversion v4.2.12
https://github.com/mastodon/mastodon/releases/tag/v4.2.12
#mastodadmin #mastodon #update -
wow, @TechCrunch linked to one of our Fedi posts live-reporting on the Fediverse spam attack...
thanks guys :p
-
wow, @TechCrunch linked to one of our Fedi posts live-reporting on the Fediverse spam attack...
thanks guys :p
-
And we've updated chaos.social to mastodon v4.2.7 #mastodadmin
-
And we've updated chaos.social to mastodon v4.2.7 #mastodadmin
-
elizur.mehas been compromised. #fediblock #fediadmin #fedadmins #mastodadmin #misskeyadmin #cybersecurity #spam -
elizur.mehas been compromised. #fediblock #fediadmin #fedadmins #mastodadmin #misskeyadmin #cybersecurity #spam -
RE: Kuroneko incident
#fediadmins are advised to temporarily disable sign-ups for now, or implement some anti-spam measure to limit signups to not get spammed.
Currently they are targeting #misskey and #mastodon, but other #activitypub servers may soon be targeted.
More details will be posted soon. Stay tuned. #fediblock #fediadmin #fedadmins #mastodadmin #misskeyadmin #cybersecurity #spam -
RE: Kuroneko incident
#fediadmins are advised to temporarily disable sign-ups for now, or implement some anti-spam measure to limit signups to not get spammed.
Currently they are targeting #misskey and #mastodon, but other #activitypub servers may soon be targeted.
More details will be posted soon. Stay tuned. #fediblock #fediadmin #fedadmins #mastodadmin #misskeyadmin #cybersecurity #spam -
i'm testing my backups prior to a migration. After restoring a `pg_dumpall` on a fresh system (`psql -f pg.dump postgres`) i get this error:
/home/mastodon/live/vendor/bundle/ruby/3.2.0/gems/activerecord-7.0.8/lib/active_record/reflection.rb:317:in `primary_key': Unknown primary key for table accounts in model Account. (ActiveRecord::UnknownPrimaryKey)
What could I be doing wrong? am I restoring incorrectly? when I grep the dump file it contains all the ADD CONSTRAINT ... PRIMARY KEY lines.
-
@[email protected] Anyway, the pattern seems that they are using the same string on every post. So I rather recommend you filter out their Discord invite over that string. #fediblock #fediadmin #fedadmins #mastodadmin #misskeyadmin
-
@[email protected] Anyway, the pattern seems that they are using the same string on every post. So I rather recommend you filter out their Discord invite over that string. #fediblock #fediadmin #fedadmins #mastodadmin #misskeyadmin
-
@[email protected] Don't. That's literally "Konnichiwa"
Literally just Hello in Japanese.
find a better string to filter from lmfao #fediblock #fediadmin #fedadmins #mastodadmin #misskeyadmin -
@[email protected] Don't. That's literally "Konnichiwa"
Literally just Hello in Japanese.
find a better string to filter from lmfao #fediblock #fediadmin #fedadmins #mastodadmin #misskeyadmin -
Affected instances AFAIK:
- cunnyborea.top
- m.mxin.moe
- social.cutefunny.net
(honestly some of these instances could get their own #fediblock entry by themselves, but now's not the time) #fediblock #fediadmin #fedadmins #mastodadmin #misskeyadmin -
Affected instances AFAIK:
- cunnyborea.top
- m.mxin.moe
- social.cutefunny.net
(honestly some of these instances could get their own #fediblock entry by themselves, but now's not the time) #fediblock #fediadmin #fedadmins #mastodadmin #misskeyadmin -
There's currently an incident involving some kind of Japanese skids who call themselves the "Kuroneko" organization.
They seem to be attempting to commit DDoS attacks on Misskey servers, constantly creating new accounts on compromised instances and spamming advertisements for their hacking services.
Admins who are federating with these compromised servers, while they might not get compromised themselves, may be affected by the sheer amount of traffic volume from their spam.
Admins are advised to #fediblock or temporarily stop sending requests to affected servers for now, if they don't want to get secondhand DoS'd
IMO I never expected them to be Japanese out of all things, kinda funny. They also host VOICEROID and VOICEVOX TTS bots on their Discord apparently. Kinda a weird flex I guess.
But yeah, probably just a bunch of skids.
#fediblock #fediadmin #fedadmins #mastodadmin #misskeyadmin -
There's currently an incident involving some kind of Japanese skids who call themselves the "Kuroneko" organization.
They seem to be attempting to commit DDoS attacks on Misskey servers, constantly creating new accounts on compromised instances and spamming advertisements for their hacking services.
Admins who are federating with these compromised servers, while they might not get compromised themselves, may be affected by the sheer amount of traffic volume from their spam.
Admins are advised to #fediblock or temporarily stop sending requests to affected servers for now, if they don't want to get secondhand DoS'd
IMO I never expected them to be Japanese out of all things, kinda funny. They also host VOICEROID and VOICEVOX TTS bots on their Discord apparently. Kinda a weird flex I guess.
But yeah, probably just a bunch of skids.
#fediblock #fediadmin #fedadmins #mastodadmin #misskeyadmin -
Ahhh, who’d be a Mastodon admin, eh? I’ve lost count of the countless late nights and weekends and frantic hours I’ve spent keeping two instances running and all of their users happy, and have definitely got far more grey hair as a result of it.
And quite often I get grief from people for trying to do my job.
And you know what? I wouldn’t change it for anything 😜
-
Ahhh, who’d be a Mastodon admin, eh? I’ve lost count of the countless late nights and weekends and frantic hours I’ve spent keeping two instances running and all of their users happy, and have definitely got far more grey hair as a result of it.
And quite often I get grief from people for trying to do my job.
And you know what? I wouldn’t change it for anything 😜
-
#Backblaze B2 is a pretty cheap cloud storage alternative to Amazon's S3.
I've been using it to backup my personal Dropbox archive, currently storing 289.5 GB in it for $1.7 per month (not sure if the file versioning counts in that reported size).
You can also serve those files from behind #Cloudflare, which I'll probably start doing for my #Mastodon storage needs:
https://www.backblaze.com/blog/free-image-hosting-with-cloudflare-transform-rules-and-backblaze-b2/
I'd add a Cache-Control header, though, as it doesn't serve one.
-
#Backblaze B2 is a pretty cheap cloud storage alternative to Amazon's S3.
I've been using it to backup my personal Dropbox archive, currently storing 289.5 GB in it for $1.7 per month (not sure if the file versioning counts in that reported size).
You can also serve those files from behind #Cloudflare, which I'll probably start doing for my #Mastodon storage needs:
https://www.backblaze.com/blog/free-image-hosting-with-cloudflare-transform-rules-and-backblaze-b2/
I'd add a Cache-Control header, though, as it doesn't serve one.
-
See the screenshot for the relevant bit. This instruction will remove whatever Cache-Control you try adding (don't know why, this is the first time I'm using it like this):
try_files $uri @-proxy
Basicall, any #mastodadmin has to manually check caching headers to avoid surprises coming from Nginx + Docker interactions, and then try and fix that config via trial and error 🙂