don't specify applications for use

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.
This commit is contained in:
Valentin Gagarin 2025-06-11 17:37:01 +02:00
parent 02812f0122
commit 17fe081fa7

View file

@ -74,25 +74,6 @@ Tests will concisely describe the abilities the Fediversity system provides.
These tests can be run on any sufficiently powerful machine with [Nix](https://nixos.org) installed, and reliably validate that the use cases work as intended.
The proposed work is realistically achievable.
## Application support
To demonstrate our functionality, we integrate our work with NGI Zero project [SelfHostBlocks](https://github.com/ibizaman/selfhostblocks), which offers the interfaces for applications to indicate their needs, for our purpose of data portability notably including back-up and restore, and is in the process of [preparing an RFC](https://discourse.nixos.org/t/pre-rfc-decouple-services-using-structured-typing/58257) to get these practices upstreamed to nixpkgs.
At the time of writing, applications it supports include:
- [Arr](https://wiki.servarr.com/)
- [Audiobookshelf](https://www.audiobookshelf.org/)
- [Deluge](https://deluge-torrent.org/)
- [Forgejo](https://forgejo.org/)
- [Grocy](https://grocy.info/)
- [Hledger](https://hledger.org/)
- [Home Assistant](https://www.home-assistant.io/)
- [Jellyfin](https://jellyfin.org/)
- [Nextcloud](https://nextcloud.com/)
- [Vaultwarden](https://github.com/dani-garcia/vaultwarden)
The result of the work should be generic enough to support any NGI packages implementing such interfaces.
## Methodology challenges
One of the challenges we have identified is ensuring the security and privacy of our users' data, even if we will not collect this directly.