architecture.md

@@ -290,7 +290,6 @@ Whereas details of the implementation may need to be decided as the technical ch
         - [allow disabling application while retaining data](https://git.fediversity.eu/Fediversity/Fediversity/issues/186)
         - [ProxmoX deployment allows scaling resources assigned to a VM](https://git.fediversity.eu/Fediversity/Fediversity/issues/119)
         - [aid needed user actions on schema update](https://git.fediversity.eu/Fediversity/Fediversity/issues/214)
-        - [completed initial application offering](https://git.fediversity.eu/Fediversity/Fediversity/issues/350)
         - [pooling application instances to shared VMs](https://git.fediversity.eu/Fediversity/Fediversity/issues/322)
         - [allow use of external single sign-on](https://git.fediversity.eu/Fediversity/Fediversity/issues/161)
         - [on migration, allow reconfiguring monolithic vs distributed](https://git.fediversity.eu/Fediversity/Fediversity/issues/341)

fediversity.md

@@ -72,39 +72,17 @@ Tests will concisely describe the abilities the Fediversity system provides.
 these tests can be run on any sufficiently powerful machine with Nix installed, and reliably validate that the use cases work as intended.
 The proposed work is realistically achievable.
 
-
 ## Identified applications
 
-We have identified a number of applications as relevant targets to offer as part of our project, emphasising the value to users' digital autonomy.
-To structure our efforts, we have categorized them into three waves, as follows:
-
-- Low-hanging fruit (courtesy of SelfHostBlocks)
-    - [Forgejo](https://forgejo.org/)
-    - [Nextcloud](https://nextcloud.com/)
-    - [Vaultwarden](https://github.com/dani-garcia/vaultwarden)
-- Host-oriented
-    - [PowerDNS-Admin](https://github.com/PowerDNS-Admin/PowerDNS-Admin)
-    - [Stalwart](https://stalw.art/) email server
-    - [Matrix](https://www.matrix.org/) chat server [Dendrite](https://element-hq.github.io/dendrite/) + web client [Element](https://element.io/)
-- Socials
-    - [Mastodon](https://joinmastodon.org/)
-    - [Pixelfed](https://pixelfed.org/)
-    - [Peertube](https://joinpeertube.org/)
-
-Considerations taking into account in the selection of applications to be implemented include their added value, maturity, security, how well they complement our other applications, support for identity management standards such as OIDC and LDAP, software license, ease of implementation, documentation, strategic relevance in protecting user privacy and autonomy, and the availability of viable alternatives.
-
 As the initial application to be supported, we have selected [Forgejo](https://forgejo.org/), given it:
 
 1. is supported in [SelfHostBlocks](https://github.com/ibizaman/selfhostblocks), facilitating implementation
 1. is part of our own infrastructure, allowing us to bootstrap
 1. given the above, makes our development team self-sufficient for the purpose of its initial user feedback cycle
-1. relevant features are merged upstream (c.f. Vaultwarden, where support for single sign-on is still outstanding)
+1. relevant features are merged upstream
 1. uses a language featuring static typing, offering it a baseline level of robustness
 
-Which other packages we will decide to support will depend further on the packages that will be adressed in the 'subgrant projects' that will be requested in the 'open calls'.
-In finalising our initial selection, both with regard to quality-quantity trade-offs as well as relative priority among the identified applications, we will coordinate with relevant stakeholders as the project matures.
-
-Our consideration to limit the initial list of supported applications is to keep focus on our core innovation, as properly adding support for applications may involve:
+Our consideration to limit the initially supported applications is to keep focus on our core innovation, as properly adding support for applications may involve:
 
 - PoC:
     - compartmentalising state for backups/portability/redundancy