TruAnon Identity vs UFP Identity

You have profiles. This lets members bring their own confidence of identity to them, and choose how others see and share it. It amplifies a profile. When identity carries weight, members do more of whatever they came to do — and do it more safely. It is voluntary. Members use it because the platform makes it worth using. What shows is theirs to set, and theirs to withdraw at any time, everywhere at once. Confidence of identity is built from a public history that cannot be assembled on demand. Where it is visible, a fraudster gains nothing and carries more risk, and moves on to a less trusted platform. The community sorts itself, without rules or moderation. It is automatic and continuous. Members keep it current by being who they are. The site stores nothing that identifies anyone — a rank, a score, an image address. Everything else is read live when viewed and never written down. Where badges appear Beside member names on comments and post bylines — classic and block themes On the member’s profile (the author page): badge, title, and granted details On UsersWP member profiles and in the members directory — no code Anywhere else via the [truanon] shortcode, the [truanon_card] profile card, or the Badge block [truanon_settings] places the member panel on any front-end page for membership sites What it costs your server Badges render from cached rank and score; no page waits on an API. Styling is self-contained — no Bootstrap, no icon fonts — and every color is a CSS custom property (--truanon-*) a theme can override. Using it with a membership plugin Community plugins render their own profile pages and member directories. WordPress core never fires its author or comment hooks there, so TruAnon reaches them either natively (UsersWP) or with a one-line snippet (everything else). UsersWP — nothing to add. The badge places itself on member profiles and in the members directory (there as a compact rank-colored check, rendered from cache with no per-member API call). On their own profile the owner also sees a Verify / Manage bar that opens their identity panel (anchor + privacy switches). It is on as soon as you enter your key; the setting on the TruAnon admin screen turns the member control off if you’d rather place it yourself. If you ran an earlier version with a [truanon_verification] profile snippet, remove it after updating so the badge isn’t drawn twice. Other plugins (BuddyPress, Ultimate Member, bbPress) — one snippet. Pick the piece you want with a shortcode — [truanon] (pill), [truanon size="inline"] (just the check, no API call), or [truanon_card] (full card); each accepts user="login-or-id" — and place it from your plugin’s profile hook. For BuddyPress, in your theme’s functions.php or a code-snippets plugin: add_action( 'bp_before_member_header_meta', function () { echo do_shortcode( '[truanon_card user="' . bp_displayed_user_id() . '"]' ); } ); Then give those members a place to manage their identity, since they never open wp-admin: put [truanon_settings] on a front-end page (or profile tab). It shows the visitor their own badge and a Verify / Manage button with every privacy switch. (On UsersWP this is the inline switch above, so the shortcode is optional there.) Upgrading from 1.x / 2.x? The old [truanon_verification userid=".." username=".."] shortcode still works. It now renders the current design — an inline check in a members list, the full card on a profile — so existing placement snippets keep working with no edits. Pass size="inline", size="large", or size="card" to force one specific piece. For developers and AI assistants Placement is automatic on stock WordPress (comment authors, post bylines, author archives) and on UsersWP (member profiles and the members directory). On any platform without native support — BuddyPress, Ultimate Member, bbPress, a custom theme — place it explicitly with the surface below. How fetching works (the model): a badge paints from a small per-user cache — rank, score, color — so no page ever waits on the API. TruAnon is called live only when the full badge/card is shown and the member’s identity switch is on; never for a list/inline check, and never for a member who has not turned it on. Each successful call refreshes the cache; the list checkmark reads that cache and never calls out. The call is not gated on a stored “anchored” flag — whether a member is anchored is what the call returns, and it is recorded as a result, never required as a precondition. Shortcodes: [truanon user="login-or-id" size="large|inline"] — the badge. inline is a small check with no API call, for lists. [truanon_card user="login-or-id"] — the profile card: badge and the details the member has granted, read live. [truanon_settings] — the member’s own Verify / Manage control with privacy switches, for front-end membership sites. [truanon_verification userid=".." username=".."] — legacy 1.x / 2.x alias; context-aware. Template tag (PHP): truanon_badge( $user = 0, $size = 'large' ) — $user is a user ID, login, or WP_User; $size is large or inline. Block: “TruAnon Badge” (truanon/badge), attributes user and size. Filters: truanon_userswp_render_badge ( bool, int $user_id ), truanon_inline_manage ( bool ), truanon_inline_link ( string $url, int $user_id ), truanon_absent_text ( string, int $user_id ). To integrate a profile plugin without native support: hook that plugin’s action after the profile name or header and echo truanon_badge( $id ) or do_shortcode( '[truanon_card user="' . $id . '"]' ) on the single profile. In a member directory or loop, use the inline size so each row renders from cache with no per-member API call. Members who never open wp-admin get their own controls from a [truanon_settings] mount on a front-end page.

UFP Identity is the only dynamic security platform created for e-commerce sites, design agencies and developers that simplifies login authentication. If there is a token, we support it. UFP Identity supports a wide variety of secure tokens enabling faster, more streamlined access to your websites all the while protecting user accounts from being compromised and preventing spam enrollments to your website. Our challenge UFP Identity set out to solve a huge technical challenge: To protect (I mean really, really make private!) online user’s personal info, make the process to access any number of websites at once really easy, and stop bad guys from hacking your stuff. Our technology platform includes: Strongest level of password authentication and encryption! Spam protection preventing unwanted user account creation Account-compromise protection Threat level adjustment to heighten login protection for your users Seamless token integration (password, Yubico, OTP, various OATH tokens, one-time codes to phone/email/irc) Quicker logins for your users. By the way we’re building a mobile app for that. Universal password support for websites that use UFP Identity. This means login credentials can work on multiple websites. Real-time monitoring of every login ensures your users are your users Reporting tool for website administrators details every login transaction and outcome (coming soon!) Multiple tokens to single account Multiple accounts to single account Certificate Signing Request The Certificate Signing Request requires a private/public key pair and the private key is encrypted with a secret key. In order to create a good secret key the plugin attempts to get good random data from /dev/urandom. If this fails, the plugin makes an attempt to securely retrieve random data from https://www.random.org Enrolling users Activating this plugin by installing the certificate will upload information about your users to our servers. We only enroll the username, email and hashed password over a private SSL connection using 2048 bit keys. We will never use any information about your users for any purpose other than authentication and verification. We will never use the email for any purpose other than resetting credentials or authentication. We will never sell or give up any of the information about your users. Telemetry We send telemetry data to our servers over an SSL connection with 2048 bit keys. This telemetry data only contains data that we would otherwise get with a successful install of the UFP Identity plugin. The telemetry can be turned off by adding an option ‘identity_telemetry_enabled’ => ‘no’. Location Information We make a call to http://freegeoip.net/json/ to get location information for the Certificate Signing Request. This is to help pre-populate the required fields and minimize the amount of work you need to do. We only do this once, upon install.