@joel @atoponce Now it looks like Burung Hantu has deleted the #PTIO bug tracker. That’s quite revolting because it was rich with information. Those bug reports were a good way to see the harms & pitfalls of the tools that #PrivacyTools endorses. It also hilighted PTIO’s blatant disregard for accuracy and integrity.

@celia @klaatu @dsfgs Projects that exist for the purpose of privacy and #MACFANG avoidance (e.g. #PTIO, #PRISMbreak) have chosen #Github and #Gitlab.com for their own projects, and this I find most revolting: https://lemmy.ml/post/35452

@ademalsasa more dirt on #PTIO: https://lemmy.ml/post/31433

@panina I abandoned #Wire because it got blocked in China and my VPN service became so unreliable it was effectively useless. But when #PTIO delisted them for setting up a US shell company to receive money from venture capitalists, and I saw them deprioritize work on federation, that was the final nail. Using Riot now and pretty happy with it. It bothers me that New Vector are hoovering up venture capital, but at least Matrix is a federated system with a documented protocol.
@rugk @sir

@njoseph It's so foolish for Lissy93 to blindly copy #PrivacyTools endorsements, because now she is contaminated by the recklessness & poor judgement of #PTIO. See https://dev.lemmy.ml/post/31434

As a specific example, there's a fascinating discussion going on in the #PrivacyTools.io GH issues about to what degree #PTIO ought to engage with the #DataFarms. I've dealt with the same strategic questions many times in other projects like #CC and the #NZ #PirateParty. We want to model best practice (use #FreeCode, federated systems etc) but there's no point preaching to the choir. The people we need to reach are the ones most engaged with the existing, centralized systems. (2/2)
@bob @alexl