this is an implementation detail since the project scope is adjusted to
provide a framework. also too early to talk about that here, there's
a section in the architecture document for sample applications.
who ever owns the budget needs to decide on the target audience for
communication. very likely the current technical scope will be primarily
interesting for developers (somewhat familiar, ideally proficient with
Nix), i.e. integrators that would use Fediversity as a library for their
hosting product. the UI demo would merely show the principle, but from
the current state of affairs it's unlikely we'll be able to "sell" it as
a turn-key solution to non-experts.
given:
- surging interest in digital autonomy more generally
- dependence on the open-source community to build upon the project's
innovations long-term
i propose amending the project so as to:
- demote fediverse from project goals to sample services, deferring
service selection to stakeholder needs
- emphasize service quality over quantity
- more explicitly mention self-hosting options, while mentioning the
procolix use-case as a sample use-case to facilitate for project
sustainability
i expect these changes benefit:
- the EC, for better addressing today's concerns
- the implementing team, as focus on quality seems a better way to
ensure project success and impact
- end-users, by better taking into account actual demand
- the open-source community, which has more use for a sustainable
project offering high-quality examples to expand on and learn from
