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?
Es mag sein, dass deine Vorgehensweise für dein Nutzungsszenario ausreichend ist.
Ich möchte und muss mir eine solche Frage vorweg nicht stellen, sondern lieber den universellen Weg wählen. Für mich ist das #Librem5 nur ein weiteres Device mit #GNU/Linux, und es wird wie alle anderen Systeme auch mit der selben Toolchain gesichert. Die großen wie die kleinen, über alle Distros in meinem heterogenen Zoo hinweg.
Mit #restic war das in wenigen Minuten eingerichtet.