Two things, and the second is why the first is simple.
Flamenet Files is gone
Files was folded into the messenger, so this repository is the account service and nothing else. Removed: EnclaveServer and its routes, EnclaveAccess, EnclaveCrypto, the browser client under client/, the Files spec and vectors, the tenant SQL under sql/, the web build and the node CI job, and the Leaf dependency that only ever rendered the file server's pages. The Dockerfile built EnclaveServer and shipped Public/ and Resources/; it now builds the account service alone. 111 files, -15,273 lines.
Nothing was lost. Every table in the production Files database was empty when this was written: no nodes, no blobs, no identities, no tenants. flamenetfiles.com, www.flamenetfiles.com and files.flamenet.io were served by that stack and now answer 404. The compose file, the env and a schema dump are on the box under /srv/prod/backups/files-decom-20260921-211508/, and the two docker volumes were kept rather than pruned.
The delete endpoint
There was no delete endpoint at all, which is why deleting a messenger account left its row here, the handle stayed taken, and the person stayed registered with a service they believed they had left. Found against production on 2026-09-21; the leftover row was removed by hand.
It costs the same proof a sign-in costs, with the same constant-time shape as sessionInner, so an unknown handle costs what a known one costs and this is not an enumeration oracle.
The first version of this MR argued at length about which product a delete should take, and kept the account alive when Flamenet Files still held an identity. With one product that rule can never fire, so AccountRemoval and its five tests are gone, the response no longer reports which of two outcomes happened, and a delete simply removes the account. Nothing had shipped, so there is no wire compatibility to keep.
050_retire_files.sql deletes the files rows and replaces the CHECK constraint rather than dropping it, so a container still being drained cannot write one back. Every account had a files pseudonym and none had a files identity, which is why there is no key material to migrate.
Checks
Suites green.
./scripts/test-account-delete.sh passes against a real Postgres and a running service. It also grew a fix: pg_isready answers before the image has created POSTGRES_DB, which raced the role setup and surfaced much later as a 409 on registration.
The image builds and boots to its DATABASE_URL is required refusal, which is the account service and not a file server.
Note
flamenet/files/auth/v1stays as the authentication context string. It is a wire constant baked into every stored verifier, not a product name, and changing it would lock out every existing account. Said so in ARCHITECTURE.md so nobody tidies it later.
This project is still named flamenet-files on GitLab. Renaming it would break the remote and this MR, so it is left for you.
Two things, and the second is why the first is simple.
### Flamenet Files is gone
Files was folded into the messenger, so this repository is the account service and nothing else. Removed: `EnclaveServer` and its routes, `EnclaveAccess`, `EnclaveCrypto`, the browser client under `client/`, the Files spec and vectors, the tenant SQL under `sql/`, the web build and the node CI job, and the Leaf dependency that only ever rendered the file server's pages. The Dockerfile built `EnclaveServer` and shipped `Public/` and `Resources/`; it now builds the account service alone. 111 files, -15,273 lines.
**Nothing was lost.** Every table in the production Files database was empty when this was written: no nodes, no blobs, no identities, no tenants. flamenetfiles.com, www.flamenetfiles.com and files.flamenet.io were served by that stack and now answer 404. The compose file, the env and a schema dump are on the box under `/srv/prod/backups/files-decom-20260921-211508/`, and the two docker volumes were kept rather than pruned.
### The delete endpoint
There was no delete endpoint at all, which is why deleting a messenger account left its row here, the handle stayed taken, and the person stayed registered with a service they believed they had left. Found against production on 2026-09-21; the leftover row was removed by hand.
It costs the same proof a sign-in costs, with the same constant-time shape as `sessionInner`, so an unknown handle costs what a known one costs and this is not an enumeration oracle.
The first version of this MR argued at length about which product a delete should take, and kept the account alive when Flamenet Files still held an identity. With one product that rule can never fire, so `AccountRemoval` and its five tests are gone, the response no longer reports which of two outcomes happened, and a delete simply removes the account. Nothing had shipped, so there is no wire compatibility to keep.
`050_retire_files.sql` deletes the `files` rows and **replaces** the CHECK constraint rather than dropping it, so a container still being drained cannot write one back. Every account had a `files` pseudonym and none had a `files` identity, which is why there is no key material to migrate.
### Checks
- Suites green.
- `./scripts/test-account-delete.sh` passes against a real Postgres and a running service. It also grew a fix: `pg_isready` answers before the image has created `POSTGRES_DB`, which raced the role setup and surfaced much later as a 409 on registration.
- The image builds and boots to its `DATABASE_URL is required` refusal, which is the account service and not a file server.
### Note
`flamenet/files/auth/v1` **stays** as the authentication context string. It is a wire constant baked into every stored verifier, not a product name, and changing it would lock out every existing account. Said so in ARCHITECTURE.md so nobody tidies it later.
This project is still named flamenet-files on GitLab. Renaming it would break the remote and this MR, so it is left for you.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
changed title from Delete the account here when a client deletes it there to Remove Flamenet Files, and delete accounts outright
<p>changed title from <code class="idiff"><span class="idiff left right deletion">Delete the account here when a client deletes it there</span></code> to <code class="idiff"><span class="idiff left right addition">Remove Flamenet Files, and delete accounts outright</span></code></p>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Two things, and the second is why the first is simple.
Flamenet Files is gone
Files was folded into the messenger, so this repository is the account service and nothing else. Removed:
EnclaveServerand its routes,EnclaveAccess,EnclaveCrypto, the browser client underclient/, the Files spec and vectors, the tenant SQL undersql/, the web build and the node CI job, and the Leaf dependency that only ever rendered the file server's pages. The Dockerfile builtEnclaveServerand shippedPublic/andResources/; it now builds the account service alone. 111 files, -15,273 lines.Nothing was lost. Every table in the production Files database was empty when this was written: no nodes, no blobs, no identities, no tenants. flamenetfiles.com, www.flamenetfiles.com and files.flamenet.io were served by that stack and now answer 404. The compose file, the env and a schema dump are on the box under
/srv/prod/backups/files-decom-20260921-211508/, and the two docker volumes were kept rather than pruned.The delete endpoint
There was no delete endpoint at all, which is why deleting a messenger account left its row here, the handle stayed taken, and the person stayed registered with a service they believed they had left. Found against production on 2026-09-21; the leftover row was removed by hand.
It costs the same proof a sign-in costs, with the same constant-time shape as
sessionInner, so an unknown handle costs what a known one costs and this is not an enumeration oracle.The first version of this MR argued at length about which product a delete should take, and kept the account alive when Flamenet Files still held an identity. With one product that rule can never fire, so
AccountRemovaland its five tests are gone, the response no longer reports which of two outcomes happened, and a delete simply removes the account. Nothing had shipped, so there is no wire compatibility to keep.050_retire_files.sqldeletes thefilesrows and replaces the CHECK constraint rather than dropping it, so a container still being drained cannot write one back. Every account had afilespseudonym and none had afilesidentity, which is why there is no key material to migrate.Checks
./scripts/test-account-delete.shpasses against a real Postgres and a running service. It also grew a fix:pg_isreadyanswers before the image has createdPOSTGRES_DB, which raced the role setup and surfaced much later as a 409 on registration.DATABASE_URL is requiredrefusal, which is the account service and not a file server.Note
flamenet/files/auth/v1stays as the authentication context string. It is a wire constant baked into every stored verifier, not a product name, and changing it would lock out every existing account. Said so in ARCHITECTURE.md so nobody tidies it later.This project is still named flamenet-files on GitLab. Renaming it would break the remote and this MR, so it is left for you.
🤖 Generated with Claude Code
mentioned in merge request flamenet-messenger-android!141
mentioned in merge request flamenet-messenger-ios!217
added 1 commit
7abe9c0a- Remove Flamenet Files, and delete accounts outrightCompare with previous version
mentioned in commit flamenet-messenger-android@377ab65efef7922e5f0f3bd28721702622fdd291
mentioned in commit flamenet-messenger-ios@75fcf183fd54243215443d6817b4961a45930792
changed title from
Delete the account here when a client deletes it theretoRemove Flamenet Files, and delete accounts outrightchanged the description
added 3 commits
main5f6004a1- Merge remote-tracking branch 'origin/main' into fix/deleting-an-account-tells-the-account-serviceCompare with previous version
mentioned in commit
6c4aaf28dd