Roadmap

👋 Hello, this is a tentative roadmap for the Permanent Seeder.

👉 This document is expected to be updated over time and hence reflect the latest changes/ideas.

Chronologically ordered items when possible. Most of the items looks to express an idea instead of a specific implementation. The latter should be discussed on issues/repos accordingly.

Roadmap List:

• Offer a bridge between regular web (http://) and hyper (hyper://) protocols.

  • ie: easy download via http of something added via hyper. Shareable Permanent Seeder download links.

• Offer a general use client app that can enable users to easily interact with their Permanent Seeder instances.

  • Explore the possibilities of working together with other seeders in the space, looking to standardize some common operations in favour of interoperability.

• Improve reliability.

• Make Permanent Seeder instances lighter (regarding memory resources).

  • Decouple internal components

• Research about keys limit mechanisms (based on quotas)

• Explore load balance (based on previous keys quotas research) between Permanent Seeder instances.

• The road to a Permanent Seeder Service

  • with more work on reliability, decoupling internal components and keys quotas we have the starting pieces to start working on a Permanent Seeder as a Service.
  • Add auth layer
  • Reverse current external update mechanism. Expose a REST-like API of stored resources.
  • Deploy and test ideally with a geographically distributed set of Permanent Seeders.
  • Stats improvements.
    • dashboard improvements per user/company