| 开发者 | hippius |
|---|---|
| 更新时间 | 2026年7月9日 16:35 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
wordpress.org/plugins/hippius-media-offloader/.Hippius is a distributed cloud storage platform. Your files are split, encrypted, spread across an independent network of nodes, and verifiable on-chain. It's the simplicity of mainstream cloud — without having to trust a single provider.
Arion is Hippius's own distributed storage engine. It uses Reed-Solomon erasure coding (10 data shards + 20 parity shards = 30 total) and the CRUSH placement algorithm. Your files reconstruct perfectly even if up to 20 nodes fail simultaneously.
Communication between WordPress and Hippius uses HTTPS. Once on Hippius, files are encrypted server-side using NaCl envelope encryption — miners only see encrypted bytes, never your content. For true end-to-end client-side encryption on media, use the Hippius Desktop App in parallel.
Your Access Key ID, Secret Access Key, and API token are stored in WordPress's standard options API, with admin-only access. The Secret Access Key field is masked in the UI and never exposed via JavaScript or to the front-end.
In most cases it improves performance. Hippius serves files through a distributed network of nodes, reducing load on your origin server and freeing up your hosting bandwidth. For global audiences, you can also put a CDN in front of Hippius.
Existing files remain untouched until you actively migrate them. You can bulk-migrate everything, or only enable auto-migration for new uploads and leave the legacy files local.
If you kept local copies during migration, deactivating the plugin restores WordPress's default behavior of serving from wp-content/uploads. There's no automated reverse-migration that downloads files back from Hippius — keep local copies if you want safe reversibility.
The plugin logs each failure with a clear reason. You can retry failed migrations manually from the dashboard.
Yes — images, videos, audio, documents (PDF, DOC, XLS, etc.), archives, and any other WordPress-supported media type. Custom file types can be added through WordPress filters.
The plugin uses one bucket per site. If you need multiple buckets (e.g. for different content types), you can run multiple WordPress sites each pointing at a different bucket.