DTube feed widget for any website.

DTube was launched in August 2017 by Adrien Marie as a decentralized video platform built on top of the Steem blockchain, with video files stored on the InterPlanetary File System (IPFS) instead of a centralized server. The pitch was simple: YouTube without YouTube. Creators would publish through a censorship-resistant stack, viewers would upvote with Steem-based tokens, and the platform itself would never have unilateral takedown power. In March 2020 the Steem community forked away from Steem (which had been acquired by Justin Sun) into the new Hive blockchain, and DTube migrated with the rest of the Steem-native ecosystem. Today every DTube post is a JSON document committed to the Hive blockchain by an author who controls their own posting key, every video file is pinned by IPFS content hash so anyone running a public IPFS gateway can serve playback, and every upvote a viewer casts triggers the normal Hive reward curve that pays out in DTC tokens (DTube's own coin) and HIVE tokens to the creator's wallet. There has also been technical evolution under the hood. DTube experimented with its own Avalon blockchain for higher-throughput metadata but the public-facing stack you reach today is overwhelmingly Hive plus IPFS, which is what the widget targets. Reading the chain reliably means querying multiple hived JSON-RPC endpoints (Hive Watcher, anyx.io, api.hive.blog, deathwing.me) with automatic failover, walking history back through legacy STEEM blocks for creators whose accounts predate the fork, and following both the dtube tag and any community tags the author posts under. Poper does all of this server-side and caches results at the global CDN edge so visitors to your site never hit the Hive RPC layer or an IPFS gateway directly.

Unlike YouTube where every video lives at a stable youtu.be URL, every DTube video lives at an IPFS content hash like QmXxxx... that does not exist on any single server. Anyone running an IPFS node can pin the hash and serve the file, which is the whole point of the censorship-resistance story, but it also means your widget needs a strategy for which IPFS gateway to fetch playback from. The DTube apps default to player.d.tube (DTube's own gateway) which is fast when it is up and slow or unreachable when it is not. Public alternatives include ipfs.io (the Protocol Labs gateway), cf-ipfs.com (Cloudflare's gateway, deprecated for some content but still useful), and an increasing number of community-run gateways. A naive embed that hard-codes one gateway will silently break for some viewers depending on geography, ISP-level peering, and which gateway has the file in its hot cache. Poper handles this with a tiered gateway strategy: try DTube's own gateway first (highest hit rate for active DTube content), fall back to ipfs.io after a short timeout, and finally fall back to cf-ipfs.com or a community gateway if both stall. The fallback chain happens transparently inside the iframe, so your viewer sees a play button instead of a spinning loader. Worth knowing: DTube videos pinned by enough peers (the popular ones) load as fast as anything on the open web. DTube videos that have lost peer pinning (rare older content from inactive creators) may never load no matter what gateway you try, because IPFS is not a guaranteed-storage layer the way a centralized CDN is. The widget surfaces a clean degraded state when this happens rather than rendering a broken thumbnail or an infinite spinner.

The single biggest reason DTube creators care about which embed they ship is reward preservation. On YouTube an embedded video pays the channel through ad revenue regardless of where the play happens. On DTube the model is completely different: every upvote a viewer casts within a 7-day window of the post triggers a payout split between the creator (typically 50%), curators who upvoted early (typically 50%), and a small platform fee. Payouts settle in DTC tokens (DTube's native coin, distributed via inflationary chain rewards) and HIVE tokens (the Hive blockchain's main coin, distributed by the Hive reward pool). If your embed strips the upvote button, fakes the upvote button, or routes upvotes through your own Hive account instead of the original creator's post permlink, you have just broken the entire reward economy for that creator. Most third-party DTube embeds either ignore this completely (rendering a static thumbnail with a play button that links to d.tube) or try to clone the upvote UI in a way that does not actually post to chain. Poper takes the principled path: embedded videos play through DTube's official iframe, which renders the official upvote button, which posts upvote operations directly to Hive under the viewer's own account permissions. The creator gets every DTC and HIVE token earned. The viewer keeps custody of their own keys. Poper never sees a private key and never proxies an on-chain operation. Reward preservation is the whole reason a crypto-native creator would consider embedding at all. The widget's job is to make the embed beautiful and fast without touching the chain semantics underneath.

Embedding videos and ranking videos are two completely different things. A DTube IPFS iframe by itself is invisible to Google's video index because Google cannot crawl what is inside an iframe and almost never executes the JavaScript needed to resolve an IPFS hash to a playable URL. To be eligible for the video carousel that appears at the top of many search results pages, and to get the rich video thumbnail next to your organic listing, your page needs Schema.org VideoObject structured data for each video. The required fields are name, description, thumbnailUrl, uploadDate (ISO 8601), and duration (also ISO 8601). Strongly recommended fields include contentUrl, embedUrl, and interactionStatistic for engagement counts. Centralized platforms like YouTube hand you a standard iframe that emits none of this, but at least there is a public Data API that third-party widgets can read to fill the gap. Decentralized platforms like DTube have neither: there is no equivalent of the YouTube Data API and there is no equivalent of YouTube's hosted thumbnail service. Poper auto-injects a complete VideoObject JSON-LD block for every DTube video in the feed, populated from the Hive blockchain post metadata (title, description, tags, creation timestamp) plus IPFS-resolved thumbnail URLs and computed duration where available. The result is that a page with the Poper DTube widget embedded ships richer structured data than the d.tube watch page itself, because d.tube does not emit VideoObject for embedded videos either. Validate after embedding by pasting your page URL into Google's Rich Results Test. This is the single highest-leverage SEO move available to any blockchain video creator on the open web in 2026: your DTube content becomes discoverable in conventional search alongside YouTube content, while still living on a censorship-resistant stack.

The most common reason a serious creator publishes to DTube in 2026 is that YouTube's algorithmic enforcement loop has either demonetized their channel, age-gated their content, or removed individual videos for reasons the creator believes are arbitrary. DTube and the broader Hive ecosystem do not have this enforcement loop because there is no central operator with the technical authority to remove a chain-committed post or unpin an IPFS file that other peers are still serving. That property has made DTube a quiet refuge for political commentators, independent journalists covering geopolitical conflicts, free-speech advocates, drug-policy reformers, harm-reduction educators, and a growing list of creators in adjacent spaces. None of that means the content is automatically more credible, but it does mean the embed model is structurally different. If you run a commentary site, an independent newsroom, a free-speech aggregator, or any publication where the creators you cover have themselves been demonetized or deplatformed elsewhere, the DTube widget is the most aligned embed you can ship. It signals technical seriousness about the censorship-resistance story (you are using the actual blockchain plus IPFS stack, not just claiming to be uncensorable), it preserves the creator's on-chain reward flow (so embedding actively supports the people you are covering rather than just exploiting their work), and it keeps the watch session on your domain instead of bouncing visitors to a separate front-end. Combined with VideoObject JSON-LD, lite-player Lighthouse parity, and multi-creator aggregation, that is a complete embed story for any publication whose editorial position requires more than YouTube can structurally offer. DTube is not a YouTube replacement for everyone. For a specific shape of publication it is precisely the right embed.