← Back to all sparks
P

PeerTube

MEETINGS
Velocity3.8

Decentralized federated video hosting and live streaming platform.

PeerTube makes moderation federated: instances can now subscribe to each other's blocklists

federated moderationblocklist subscriptionssecurity hardeninginstance admin toolingplugin api
Current state
The 8.3.0 candidate opens a new line and is by far the largest release in this window. Instances can subscribe to remote blocklists and watched-word lists that periodically re-sync, automatically muting accounts and servers and re-tagging existing videos and comments in the background, and an instance can publish its own blocklist as a public log for others to consume. A dense security block lands with it — cross-IP account login lockout, per-account rate limits on abuse and comment creation, OTP encryption moved to GCM, SVG sanitisation. The preceding 8.2 train was narrower: download bandwidth throttling and stabilisation.
Where it's heading
The through-line from 8.2 to 8.3 is that PeerTube keeps building for the instance admin rather than the viewer, but the unit of defence has changed. 8.2 handed a single admin local controls — per-instance and per-IP download throttles aimed at scraping botnets. 8.3 makes those defences shareable, so moderation decisions propagate between instances on their own, while new plugin auto-tagger registration lets classification be automated too. The security list reads like a post-audit sweep rather than incremental hardening.
Prediction
Expect 8.3 to spend its remaining candidates on stabilisation as 8.2 did, with the manual migration script and the multi-minute startup migration the main upgrade risks to shake out. Whether subscribed lists get curation or trusted-publisher tooling isn't visible in these entries.

Recent moves

  1. 19d ago

    Instances can subscribe to each other's blocklists and word lists

    ⚡ SPARK

    The largest release in this window, and it changes what running an instance costs: blocklists and watched-word lists become subscribable across servers, syncing on their own and re-tagging existing content when they change. It extends 8.2's admin-defence posture from local throttles to defences that propagate between instances.

    View source ↗
  2. 3mo ago

    PeerTube 8.2.0 release candidate 3

    A candidate that only forward-ports security fixes from 8.1.8 and bug fixes from 8.1.7. It is the stabilisation tail of the 8.2 train rather than new work.

    View source ↗
  3. 3mo ago

    PeerTube 8.2.0 rc2: m4b audio, playlist hotkey, concurrency fixes

    Adds .m4b audio support and a playlist hotkey alongside fixes for concurrent live segment and torrent writes. Small user-facing additions bolted onto the reliability work that defines this release cycle.

    View source ↗
  4. 4mo ago

    Download throttling, an NGINX fix, and a privacy deprecation for the accounts API

    ⚡ SPARK

    The candidate that sets 8.2's agenda: per-instance and per-IP download bandwidth limits, an NGINX I/O fix, Node.js 20 and old-iOS support dropped, and notice that the public accounts endpoint moves behind moderator auth in v9. It is the clearest statement yet that PeerTube is tuning for instances under hostile load.

    View source ↗