@FediTips Fun fact: that first link has incorrect information on it. I know because the server I am not does not block Threads but is listed as being part of Fedipact. Who knows what other inaccuracies are on that list? I know my server’s admin has tried to get this corrected, to utterly no avail.
@tokyo_0 I think Hanlon’s Razor most likely applies, so I won’t make any judgements as to motive, but the lesson here is in the importance of posting accurate information online. When you’re making a list of people or entities associated with a sensitive issue, accuracy is going to be paramount. Anything less invites speculation.
@adam Yes, it does. And if someone is going to speculate, it's their responsibility to make sure you're speculating about the right thing.
Glad @FediPact could shed some light on the mixup. It might be good for the vaganism.social site to make a little clearer that it isn't the official fedipact website. Maybe there's an issue with updates reaching it from the official list — sounds like it might be good to iron that out if there is and if there's a simple solution.
@adam Yes, it does. And if you're going to speculate, it's your responsibility to make sure you're speculating about the right thing.
Glad @FediPact could shed some light on the mixup. It might be good for the vaganism.social site to make a little clearer that it isn't the official fedipact website. Maybe there's an issue with updates reaching it from the official list -- sounds like it might be good to iron that out if there is and if there's a simple solution.
@tokyo_0@FediPact@nm I’d propose that a list of instances based on the position of instance admins should always link to a post by the instance admin that verifies the position. This whole thing started when the original FediPact list (the pink page) included our instance based on a false submission. Then the veganism.social list seemingly pulled in that info without any further verification. Lots of blind trust here. Linking to receipts would solve all of this.