@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
❌ Software Removal | Signal · Issue #779 · privacytools/privacytools.io

Problem with Signal Signal has copious privacy issues making it unfit for privacytools.io endorsement. Users are forced to supply a phone number to Signal (https://github.com/privacytoolsIO/privacy...

GitHub
@Yujiri @werwolf It did not seem to matter how much dirt they were presented on some of their endorsements. Regarding the Github repo change, they did a renaming from pt.io to ptIO. This broke a lot links to bug threads that were heavily circulated & quite embarrassing (Signal & Keybase threads in particular). At first I thought they destroyed all the content, but it was just a renaming.
@werwolf @Yujiri I burnt out on feeding dirt to the PTIO project that they were not acting on, perhaps due to backroom deals. So I gave up on them.. fed dirt on their endorsements to other projects. In any case, it’s interesting that you spotted data destruction at the same time as the github renaming. That could even be the underpinning reason for the renaming (if not to break embarrassing links)