Post AYVDwbNHXUIeaNiQbI by duncan1n1@ieji.de
(DIR) More posts by duncan1n1@ieji.de
(DIR) Post #AXmYA9wQKqZrDsp6bA by SolSoCoG@ieji.de
2023-07-17T10:11:01Z
0 likes, 0 repeats
I've just blocked all Meta IPs so threads.net (blocked) traffic wouldn't even hit or impact us at all. Also went ahead and signed the #FediPact because why not 🙃
(DIR) Post #AXmZoj4RFEOXiCTnRQ by martijn@ieji.de
2023-07-17T10:29:34Z
0 likes, 0 repeats
@SolSoCoG I'm not personally against it. A lot of people are 'happy' in that ecosystem and this opens doors to communicate with them. Massive extra traffic aside, I think from a social aspect federating with them is a good thing.I used to be very active on Facebook groups as a mental health activist, because that's where everyone is and looks for support.
(DIR) Post #AXmcAmZ18aB4pDQZkm by SolSoCoG@ieji.de
2023-07-17T10:55:58Z
0 likes, 0 repeats
@martijn looking at how invasive Meta is, and I know what I'm talking about, I was analysing and categorizing data for them at one point via a third party contractor, this is really horrifying and the last spot you want to look for support at. But yeah it is where you have the highest chance of get support in social media. And thats what h as to change so a big chunk of instances declines federating with them and getting any benefit from us. They are still ruled by pure greed.
(DIR) Post #AXmcZvHtq5od7aPQ12 by martijn@ieji.de
2023-07-17T11:00:31Z
0 likes, 0 repeats
@SolSoCoG yeah I understand. I did similar work once for a fruit themed computer/phone company in Cupertino. But that aside, just considering the social aspect. I found a good spot on Lemmy, so I hope at some point that people can find that
(DIR) Post #AYVDwbNHXUIeaNiQbI by duncan1n1@ieji.de
2023-08-07T23:26:26Z
0 likes, 0 repeats
@SolSoCoG I'm not a fan of the instance-level block on Threads.From the privacy point of view, blocking the instance does not improve the privacy of users on this site, because anyone, including Meta, can setup a new instance and gain access to all publicly available information on our instance.The only thing the block does is to stop people on the two instances interacting with each other, and that should be a choice of the user themselves, not the instance administrator.