cross-posted from: https://lemmy.ml/post/143981

Mod statement: https://np.reddit.com/r/PrivacyGuides/comments/rxf02a/theanonymousjoker_false_privacy_prophet/hs1dxux?context=3

https://i.imgur.com/LahmNkO.jpg

dng99/dngray has branded a citation-less slander post as facts. These are the “community standards” of r/PrivacyGuides. Always remember this.

u/trai_dep, the record stands corrected once again

Moreover, my theory about GrapheneOS community using sockpuppets is true, as confirmed by…

https://np.reddit.com/r/fdroid/comments/rxtc14/came_across_this_thoughts/hs1o6no?context=3

https://i.imgur.com/JX6uTpx.jpg

Tommy_Tran = B0risGrishenko (OP of slander post). Thanks for confirming my GrapheneOS community sockpuppet theory.

      • @TheAnonymouseJoker@lemmy.mlOPM
        link
        fedilink
        -12 years ago

        Nice wordplay there. The only FUD I can see is that post with zero citations about my comments or posts, and the moderators of that community promoting it as facts, ignoring that there are zero citations made.

        Hard evidence requires solid citations, not made up stories.

        Interestingly, you want to “speak up” yet ignore the fact that that OP never cited the comments or posts I wrote to disprove my claims. This was also evident upon my simple confrontation about their argument they earlier had (regarding AOSP’s VPN killswitch feature), while purposely incorrectly citing events on a timeline to look correct. Moreover, later they exposed themselves as using an alt account, and trolled me on Matrix chat.

        Speaking up is not a matter of practicing freedom of speech. It is also a matter of using it responsibly to stand for righteousness.

          • @TheAnonymouseJoker@lemmy.mlOPM
            link
            fedilink
            -22 years ago

            Both the screenshots are completely factual. The Google one is non-debatable. Also, the “sandboxed play services” thing was something I did more than a year ago, and taught people with the 3.0 guide already. Those “high privileges” mean nothing compared to changing package permissions via AppOpsX via ADB commands. There goes the “highly privileged” thing down the drain.

            The reality of “sandboxed play services” is that GrapheneOS just wanted to do marketing because everybody is moving away to CalyxOS for retained app functionality over what end up as a useless security ROM practically. People were fed up of their apps not working, and people were fed up of the unhelpful, toxic community. Stay angry.

            I love how the comment literally above it was the final explanation by me, and the one you linked was a total weasel copout. A purposeful misquoting of Marcel (NetGuard dev) was done before the VPN killswitch feature came to AOSP by that B0ris/Tommy.

            Also, nice promotion to moderator position after my harassment… are those the "community standards)?

              • @TheAnonymouseJoker@lemmy.mlOPM
                link
                fedilink
                -3
                edit-2
                2 years ago

                Prove what? I have an entire section in my guide “CRITICAL FOR CLIPBOARD, LOCATION AND OTHER APP FUNCTION BLOCKING”. I have had it since 3.0 guide for more than a year now.

                The proof for people flocking away from GrapheneOS to CalyxOS is found everywhere as posts on r/PrivacyGuides and r/privacytoolsio (now freezed) and people in Techlore rooms that use CalyxOS. Everybody knows many apps cannot work as intended without Play Services or microG. And thus GrapheneOS now has “sandboxed play services” which basically took ZERO time to develop. Permission management of packages does not involve rocket science.

                dngray's mod comment screenshot

                https://i.imgur.com/LahmNkO.jpg

                Allowing slander hoax = “community standards”. B0ris/Tommy after making that slander post was made moderator, interestingly. Almost as if this was the reward.

                Go troll someone else. I do not tolerate trolling and baiting.

                Edit: AppOpsX works offline and does not need updates. The AppOps mechanism has been in Android/AOSP since ICS/Kitkat days as a hidden developer feature.