Conflicting feelings about how and where to federate
As a #Friendica small instance administrator, I am quite conflicted on who or what to follow, because everyone I follow will show up in the global timeline for all users forever.
1) I want to foster a Friendica-first global timeline so that our local users actually have a chance to use all of Friendica's features and so that Mastodon culture (short posts and threads due to character limits, title-less posts) does not completely overtake the local community.
2) I still want to interact with people and topics I am interested in, the vast majority of which happen to be on #Mastodon or other #microblogging software.
Everyone is on Mastodon or its microblogging derivatives. Even right now, after consciously following Friendica profiles first, practically my entire home page is Mastodon users. Almost all interactions I have are with microblogging accounts.
I don't want to have to avoid following interesting people just to avoid poisoning the global timeline with Mastodon accounts because they end up showing up for everyone in global.
Ich will keinem auf die Füße treten, aber es ist schon ein bisschen gruselig, wie viele #Sysadmin Anfängerfragen in #Fediadmin Chats regelmäßig auftauchen.
Lernt doch bitte erst mal die Basics, bevor ihr Dinge ins Internet stellt und ihr die Verantwortung für die Daten von anderen Benutzern übernehmt.
#Mastoadmin
Good news! We are now implementing the @iftas CARIAD 66% block list via IFTAS' FediCheck service.
This blocklist combines:
- The IFTAS *Do Not Interact* list, a list of instances that IFTAS highly recommends not to federate with
- A curated list of further domains that a selection high volume instances have defederated from.
There are 80%, 66% and 51% consensus levels available for the curated list. At this point we are syncing with the 66% consensus level.
At the moment we believe 66% is probably the right starting point, though if there's demonstratable value in reducing to 51% we'd consider doing so.
While the FediCheck service will simplify automated blocking of widely recognised offenders, it does not replace our own autonomous blocks based on what we observe and what is reported to us.
I believe the FediCheck service also allows our instance to automatically temporarily limit instances where we're seeing a spam wave or similar, but I need to look into it.
IFTAS have some really good resources, so some further reading if you're interested:
https://connect.iftas.org/library/iftas-documentation/cariad-policy/
https://connect.iftas.org/library/iftas-documentation/iftas-dni-list/
https://connect.iftas.org/library/iftas-documentation/fedicheck/
#MastoAdmin #FediAdmin #FediCheck #IFTAS #SafetyOnline
also #fediadmin post here
updated my instance to have 65,535 characters, I do not plan on making posts that long, but I like that better then 500 characters.
anyway there we go!
#FediAdmin question: is there a way to add CW to existing replies to my own posts? Something easier than raw SQL to the postgres database:
UPDATE
public.statuses
SET
spoiler_text='whatever'
WHERE
uri='http....'
I've switched the instance from vanilla Mastodon over to glitch-soc.
We now have access to a massive **2048** character limit for posts, more poll options and a few more bits and bobs to hopefully make life on the server a little bit more fun!
I've done some stability testing and monitoring and everything appears to be working absolutely fine, but I'll be continuing to monitor closely over the coming days.
#MastoAdmin #FediAdmin #FediverseDotGames
Wisst ihr ob #pixelfed mit Contabo S3 Speicher kompatibel ist?
Jetzt noch beim Contabo Sale zuschlagen und von
4 core / 8 GB RAM /400 GB SSD auf 6 coresb /16 GB / 600 GB SSD upraden? In letzter Zeit kommt die Kiste an ihr Limit wenn mehrere sidekiq Jobs gleichzeitig laufen.
Has anyone switched from vanilla Mastodon to glitch-soc on the official helm chart? Is it really as easy as swapping it out, populating the new values and rebuilding the assets?
Keen to get some of the features that the vanilla project team seem to be allergic to.
#Mastodon #GlitchSoc #MastoAdmin #FediAdmin
yo, other sharkey admins. got a question
we're finally self-hosting and it's gone pretty well so far. i know yall say nginx works best for it, so thats what we're using, but it's basically the simplest config possible atm. i know there are a lot of tips and things youve all come up with that make things run more smoothly, would anyone care to share some of those?
Here is your regular reminder to donate to your Fediverse instance.. (if you don't run your own).
💙 If you operate a federated instance, have benefitted from our activities, and would like to show your support for IFTAS publicly, we humbly ask you to become a Supporting Instance: https://about.iftas.org/our-sponsors/
Your participation helps us demonstrate strong community backing to our sponsors and stakeholders. Add your server today:
➡️ https://cryptpad.fr/form/#/2/form/view/JfYu0zQZ3T7qbjb0YWF3fi8uw2ixXF9rwnJRvxLiAkI/
#FediAdmin #MastoAdmin #TogetherStronger
https://about.iftas.org/our-sponsors/