@werwolf @Yujiri Good catch! TY for documenting it in detail. The #PrivacyToolsIO & #PrivacyGuides folks have been dodgy as hell from day 1. It was always evident there were deep conflicts of interest, most particularly from the #Signal thread: https://github.com/privacytools/privacytools.io/issues/779 Also see: https://lemmy.ml/post/31433 & https://lemmy.ml/post/30736 & https://lemmy.ml/post/31487

@ascott Jonah Aragon et al. has actually hijacked a “privacytools” discussion from someone who had no #PrivacyToolsIO connection… someone who formed a community to ensure a venue for impartial discussion about #PrivacyTools long before the infighting & existence of #PrivacyGuides: https://activism.openworlds.info/@aktivismoEstasMiaLuo/108079291044212350

@atoponce @joel It turns out PTIO changed their github acct name from #privacytoolsIO to #privacytools so the bug reports were not deleted. That small stupid change broke a shit-ton of links though. This is the new location → https://github.com/privacytools/privacytools.io/issues/

@atoponce @joel W.r.t #PrivacyToolsIO prioritizing money above their principles, I’ll elaborate. When it was pointed out that #PayPal shares customer data with over 600 corporations, the list of which was furnished to #PrivacyTools, not only did they continue accepting #PayPal donations but they neglected to warn their donors about it. That info should not be concealed; it should be transparent.

@atoponce @joel This covers some of the issues with #PrivacyToolsIO → https://lemmy.ml/post/31433 & https://lemmy.ml/post/31487

@joel @atoponce Burung Hantu & Jonah Aragon are both quite incompetent. The fight between them is actually a good thing b/c #PrivacyToolsIO has always pushed misinfo & omissions (they hold back on publishing the pitfalls of the tools they recommend). Their interest is _money_. The conflict of interest & incompetence is evident by the link itself: that article is in #Cloudflare.

@kr1s000 @novaburst@mstdn.social There’s plenty of incompetence all around by all involved with #privacytoolsio. They completely pulled the plug on social.privacytools.io spontaneously without warning. Ppl had no chance to copy their follow list or to tell their followers where their new account will be. It was reckless on both sides. The #Privacytools website has poor advice too. Fuck those incompetent assholes.

Social.privacytools.io instance down?
I assume this is something to do with the ongoing dispute/transition to privacy guides. Goodbye personal account :/ A good reason to run your own instance. #privacytools #privacytoolsio #mastodon

@aruns So what's the new name of #privacytoolsio? What's the new website?

Let's talk about #privacytoolsio.

https://twitter.com/privacytoolsIO/status/1438581801434238984

I want to listen to both parties, but Burung Hantu's actions are not helping.

First they disappear from this open source project for around an year, don't respond to other project members' messages, don't monitor the reddit discussions about the rebrand (which has been happening for months) and when the redirect/rebrand is set up, they come back claiming ownership of the project. Huh?

It seems the matrix homeserver at chat.privacytools.io isn't allowing any accounts. #privacytoolsio Is there any reason why or did they do a public announcememnt saying they are full?

@UmWerker the problem with DDG using MS both for hosting and for searching is that MS can link both sides of DDG traffic together to see who is searching for what. I don't get why there is no loud criticism of this. Sites people naively trust like #privacytoolsio, #prismbreak, #switchingSoftware continue to endorse DDG and neglect to warn users of this.

@ademalsasa #PrivacyToolsIO & #PRISMBreak are terrible sources: https://lemmy.ml/post/31487 The 3rd is #CloudFlare site (obviously it's a bad idea to go to a #privacy abuser for privacy advice)

@SebastianGallehr
@theprivacyfoundation

For me, it's #privacytoolsio

@aktivismoEstasMiaLuo @strypey @mpanhans exactly, plz don't be like #privacytoolsio. Do better. Resist the urge to sell out and refuse donations when there's a conflict of interest.

@mpanhans @strypey Certainly more projects like this are needed. The existing projects (#privacytoolsio, #prismbreak, #swiso) screw it up by recommending alternatives that are counter productive: https://dev.lemmy.ml/post/31487 Avoid their mistakes by gathering input from experts & staying true to the mission.

@exstral #Jami is indeed a good choice. It's one of the few trustworthy endorsements from #privacytoolsio, who you should not trust in general. https://dev.lemmy.ml/post/31433

@darylsun@social.privacytools.io The problem with a huge list is it has several bad apples. E.g.

#Signal (why it's bad: https://github.com/privacytoolsIO/privacytools.io/issues/779)

#DuckDuckGo (why it's bad: https://dev.lemmy.ml/post/31321)

#Keybase (why it's bad: https://dev.lemmy.ml/post/31190)

#Qwant (why it's bad: https://dev.lemmy.ml/post/31645)

#privacytoolsio (why it's bad: https://dev.lemmy.ml/post/31434)

@schestowitz to be fair, #Startpage is still relatively better for #privacy than #duckduckgo (https://dev.lemmy.ml/post/30827), & yet #DDG is foolishly endorsed by #privacytoolsIO

@blacklight447@social.privacytools.io
It's a bit of a #hypocrisy for #privacytoolsIO to subject their donors to a #Cloudflare site.

No warning is given to tell their pro-privacy supporters that their name, address, and sensitive financial data will be shared with a #privacy abuser.

Note as well there are links to #Twitter and #Microsoft #Github (both of which counteract the privacy mission)