Notices by Steffen K9 ? (steffen@misskey.de), page 6

Jeez! The current spam wave has found me. 😡

@noidea@boerdica.de @Hiker@social.fedcast.ch @heluecht@pirati.ca @zwovierzwo@social.fedinet.de @feb@loma.ml My storage backend is filesystem. ☺️

@Hiker@social.fedcast.ch @zwovierzwo@social.fedinet.de @feb@loma.ml @heluecht@pirati.ca Das ist ungewöhnlich lange. Bei meinem Account lädt /network nach dem Login in weniger als 5 Sekunden. Später lädt die Seiter dann in weniger als 2 Sekunden. Meine DB von libranet.de ist 315 GB groß.

@MsDropbear425@infosec.exchange Thank you for your message. The server is currently suffering from a heavy load on the database. Around 150 accounts and the associated data are currently being deleted from the database. Unfortunately, this leads to situations in which the database cannot process any additional connections.

Gestern am #Cossi gewesen. Vom Winter keine Spur. Blauer Himmel, Sonne, Softeis, Leute sitzen im Sand. 🙂 #Leipzig

Attempt at coexistence 😼🐶

@utopiarte@tupambae.org Sorry, I didn't get any DM.

Concerning the need for moderation on the groups node forum.friendi.ca: If I remember correctly, I took over the hosting and administration of our community node in 2016. In all these years there were only one or two cases where moderation was necessary. The administration is not a big deal, either.

From my point of view the best way to advance and improve community support is having people answering questions and giving hints how to use and run Friendica. We have made much progress in that. Some years ago there were only a few active supporters in our groups/forums. These days I see much more people who are helping others.

@jakob@soc.schuerz.at Das geht nur, wenn du in dem Threads irgendwie interagiert hast. Ansonsten kannst du den ja löschen.

@kahomono@libranet.de I have deleted around 500 very old and dead accounts. The removal of content and accounts from the database is a heavy job. The queue is pretty long at the moment.

@utopiarte@tupambae.org @tobias@friendi.ca That's me. And I'm in control of everything. 😁

@heluecht@pirati.ca Ähem. The post-content table is 55 GB on libranet.de and 45 GB on venera.social. This table is the second largest table in both databases. :-/

@sascha@loma.ml Wenn Settings -> Additional Features -> Post Composition -> Explicit Mentions eingeschaltet ist, kannst du die Erwähnungen manuell ändern.

@libranet@mastodon.social DNS is also responding again.

@smokinjo@friendica.hubup.pro @hypolite@friendica.mrpetovan.com More menu ... under each post. There you find both. The saved folders are accessible in the left side panel.

@fu@libranet.de The default timeout of Apache for running scripts is 5 minutes. That should be more than enough. But there are more timeout settings...

Friendica has an internal network timeout when clients don't respond. I raised that from 30 seconds to one minute now.

PHP has a max_execution_time setting. The default is 30 seconds. I have now raised that to one minute as well.

I have decided how to handle the threads.net domain on misskey.de. I have muted - but not blocked - the domain on server level. This means you won't see any random public content from threads.net in your timelines. Follow requests are still possible. So, you - as user - can decide to follow someone from threads.net to get their individual content.

This is the current state. Let's see how this works. I'll keep an eye on that topic.

@support@libranet.de ♻️

RE: https://misskey.de/notes/9neixa89v8

Threads.net – Not sure how to proceed 🤔

In the last days I have read a lot of statements, opinions, pros and cons about threads.net. But still, I'm not sure how to handle that topic on my nodes libranet.de, venera.social and misskey.de.

Personally, I don't want to be involved in anything related to Meta/Facebook. I'm aware of their history of collecting, analysing and selling meta/user data. From my experience Facebook is often used to spread misinformation - intentionally or out of ignorance. But I don't know anything about threads.net in particular.

When both things would happen on some small, random Fediverse instance I would probably block it. But threads.net is the new elephant in the AP room and until now there's no actual content that would satisfy a domain block. So I'm not sure if I should make that decision now for all users on my servers/nodes.

Possible actions are:
A) enable the domain block for threads.net now
B) let the users decide for themselves to mute/ignore the threads.net domain
C) observe the impact of and actual content from threads.net and decide about the domain block later (giving developers the time to implement possible mitigations)

I'm really not sure what's the best way to handle this. What do you think?

Guten Morgen! 🙂

Wünsche einen schönen ersten Advent. 🎄