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?
Dez 31 13:52:03 j4 restic[11274]: scan finished in 27.881s: 275870 files, 6.237 TiBDas ist der dickste Brocken in meinem Zoo und ein Vollbackup dieses Systems mit #Bacula brauchte zuletzt ca. 6 Tage (aber nur 2x im Jahr). Bin sehr gespannt, wie lange #restic benötigt - wenn der Vergleich auch unzulässig ist, weil ungleich leistungsfähigere #Hardware beim Ziel.
Und natürlich, ob der Diskspace am Ende ausreicht. Vermutlich werde ich das erst am Donnerstag erfahren.