Minds on any website.

Minds runs on a centralized backend (PHP for the legacy stack, Node and Cassandra for the modern services) but publishes its full source under the AGPLv3 license on GitHub. That license matters: AGPL is the strongest copyleft license in common use, and it requires anyone running a modified version of the software as a network service to publish their changes. The result is a platform where the code that ranks your feed, ships your posts, and counts your points is auditable line by line. The public Minds API exposes channel data via /api/v1/channel/:guid, activity streams via /api/v3/newsfeed, comments via /api/v1/comments, and search via /api/v3/search. Public posts and channel metadata are accessible without authentication, the way Mastodon and Bluesky public timelines are. Poper queries these endpoints directly, caches responses on our global CDN edge, and renders posts with the same fidelity as the Minds web client. There is no app review process and no OAuth dance for embedding public content, which makes the widget far easier to set up than Twitter, Facebook, or Instagram embeds that require platform-side approval. The Minds team has historically maintained API stability across major releases, with deprecated endpoints continuing to function for long transition windows. That stability is rare in social platforms and is a direct consequence of the open-source license: breaking the API would break self-hosted instances and forks that the AGPL ecosystem depends on. For a widget developer, that means a Minds embed configured today is unlikely to fail silently next quarter because of a platform-side change, in sharp contrast to Meta and X widgets that have broken multiple times since 2023.

Minds was one of the earliest mainstream social platforms to put creator rewards on a public blockchain. The original MINDS token launched as an ERC-20 contract on Ethereum in 2018, and the platform integrated tipping, boosting, and channel monetization in tokens directly into the user interface. In subsequent years the team experimented with the Polygon-based Pulse rewards mechanism to lower gas costs and broaden the reward eligibility surface. By 2026, most reward activity flows through Pulse, with legacy MINDS remaining redeemable for users who hold the older asset. For embedded feeds, this matters because the API returns reward attribution on a per-post basis: a post that has been tipped or boosted carries an on-chain reference that the widget can render as a verifiable engagement signal. Unlike Twitter likes or Facebook hearts, a Minds reward is tied to a wallet transaction, which gives readers something to verify if they care to. Poper renders both legacy MINDS and current Pulse reward indicators with consistent badge styling, so a creator who has accumulated rewards across the entire platform history shows the full picture on the embed. The token reward layer also has a practical consequence for content quality: posts that earn meaningful reward amounts tend to be the ones a creator considers their best work, because the rewards reflect tipping by other users rather than algorithmic amplification. A reader landing on your site and seeing a top post with a visible Pulse reward badge gets a signal closer to a craft endorsement than to a vanity heart count. For independent essayists, longform investigators, and Web3 builders, that distinction is one of the genuine advantages of choosing a Minds embed over a generic social aggregator. Pulse rewards are accrued in measurable units that the widget can format consistently across embeds, so a creator brand using Minds across multiple sites maintains visual continuity in how their on-chain creator economics surface to readers.

Minds is widely associated with free-speech advocacy and has historically attracted creators after deplatforming events on mainstream networks. The platform publishes a moderation policy that maps explicitly to the First Amendment standard in U.S. law, with documented exceptions for content that is illegal under United States federal law (child sexual abuse material, credible threats of violence, doxxing, copyright infringement). The policy and the moderation queue are described in public posts by the founders and through periodic transparency reports. This positioning is not neutral, and brand owners should evaluate it openly: a Minds embed signals to readers that the host site values minimally moderated public discourse and is willing to surface that ethos on its marketing pages. For libertarian writers, free-speech absolutists, post-deplatforming commentators, and projects building censorship-resistant infrastructure, that signal is a feature. For brands operating in heavily regulated industries (financial services, healthcare, public sector), the policy alignment may not match brand guidelines, and a different feed widget may be a better fit. Poper does not filter or pre-moderate Minds content beyond what the platform itself surfaces in its public API. The widget is a faithful mirror, not a curation layer. The widget exposes a small set of optional filters (NSFW preference, minimum point threshold, hashtag whitelist, hashtag blacklist) so a brand can tune the embed without overriding the underlying platform behavior. These filters operate on the embed surface only and never change what the post author sees on Minds itself. Brand owners who need stronger curation should pair the embed with a manually approved post selection workflow rather than asking the widget to make editorial judgments. The honest framing is that a Minds embed is best for sites whose audiences expect direct, minimally curated discourse, and that audiences expecting heavily moderated brand-safe content streams are better served by a different platform feed.

Beyond the public feed, Minds operates Minds Chat, an end-to-end encrypted direct message system built on the Matrix protocol. Encrypted DMs are not embeddable for obvious privacy reasons, but the existence of the layer matters for how a Minds embed reads on a brand site. Independent journalists and source-protective publishers often pair a public Minds feed embed with a published Minds Chat handle so readers can move the conversation off-platform without trusting an unencrypted DM channel. The combination of a public feed (verifiable engagement, token rewards, AGPL backbone) and an encrypted side channel (matrix-grade protection for source communications) is one of the practical reasons investigative writers and human rights workers use the platform. The widget surfaces only public content, but it can include a configurable footer linking to your Minds Chat handle, your matrix.minds.com identifier, or a contact card, so the embed becomes the entry point to a privacy-focused communication chain rather than a dead end. Matrix-protocol DMs offer a quality of protection that mainstream social DM systems do not match: messages are encrypted client-to-client with keys the platform itself cannot read, and the protocol is interoperable with self-hosted Matrix servers (Synapse, Dendrite) for organizations that want to host their own infrastructure. For human rights groups, NGOs, and investigative newsrooms, that level of source protection is a baseline requirement, and a public Minds embed that links to the encrypted side channel is a far more useful brand surface than a public Twitter or X embed that funnels readers into an unencrypted DM inbox.

Comparing a Minds embed to a Twitter or X embed is useful because the structural differences shape what kind of widget makes sense. Twitter and X charge for API access, gate public read traffic behind authentication, change rate limits without notice, and have removed legacy widget functionality multiple times since 2023. A Twitter widget that worked yesterday can break tomorrow, and the platform's content moderation lives inside an algorithmic recommender that changes constantly. Minds, by contrast, has a stable public API, AGPL-licensed code that anyone can audit, transparent moderation rules tied to U.S. federal law, and a chronological feed by default. For a creator whose audience values the latter set of properties, a Minds embed is a more durable long-term investment than a Twitter embed, even if the absolute audience is smaller. The widget exposes that durability directly: posts in chronological order, points and token rewards as honest engagement signals, no engagement-bait amplification, and no third-party trackers in the embed itself. Combine that with the no-auth public read API and a self-hostable AGPL backbone, and the embed feels native to the kind of independent publishing that Minds was built for.