A support page, a contact page, and an address people can find #197

2026-09-11T12:48:10Z

paulhitt commented

2026-09-11 12:48:10 +00:00

(Migrated from gitlab.com)

The site could already be written to, and said so: /safety lists abuse, security, privacy and legal, and is linked from the footer. What was missing was the ordinary case. Somebody whose app will not sign in is not being harassed and should not have to read a page about harassment to find where to write - and there was no support address at all, in the site or in either app.

/support covers what actually goes wrong (sign-in against the wrong relay, the Android full-screen-intent permission, battery savers closing the connection), what to put in the email, and two things worth being blunt about: nobody here will ask for your passphrase, and nobody here can read your messages, so "what did my message say" is unanswerable however much we would rather it were.

/contact lists every address with what each is for, how long we take, and that a week of silence means send it again rather than that you were ignored.

Separate footer links on purpose. "Getting help" is somebody being hurt by a person; "App help" is the app being broken. One needs answering today, and a single Support link would bury the urgent one in the routine one.

Mailboxes: support@ and contact@ did not exist. They are now aliases onto the account that already receives abuse/security/privacy/legal/postmaster. Delivery proven by sending to each and watching it land in the mailbox - not by reading a 250 at RCPT, which is exactly what support@ was already returning for an address that went nowhere.

Relay suite: 698 tests in 63 suites, plus the XCTest suites, all passing.

Co-Authored-By: Claude Opus 5 noreply@anthropic.com

The site could already be written to, and said so: `/safety` lists abuse, security, privacy and legal, and is linked from the footer. What was missing was the ordinary case. Somebody whose app will not sign in is not being harassed and should not have to read a page about harassment to find where to write - and there was no support address at all, in the site or in either app. `/support` covers what actually goes wrong (sign-in against the wrong relay, the Android full-screen-intent permission, battery savers closing the connection), what to put in the email, and two things worth being blunt about: nobody here will ask for your passphrase, and nobody here can read your messages, so "what did my message say" is unanswerable however much we would rather it were. `/contact` lists every address with what each is for, how long we take, and that a week of silence means send it again rather than that you were ignored. **Separate footer links on purpose.** "Getting help" is somebody being hurt by a person; "App help" is the app being broken. One needs answering today, and a single Support link would bury the urgent one in the routine one. **Mailboxes:** `support@` and `contact@` did not exist. They are now aliases onto the account that already receives abuse/security/privacy/legal/postmaster. Delivery proven by sending to each and watching it land in the mailbox - not by reading a 250 at RCPT, which is exactly what `support@` was already returning for an address that went nowhere. Relay suite: **698 tests in 63 suites**, plus the XCTest suites, all passing. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

paulhitt commented

2026-09-11 13:16:58 +00:00

(Migrated from gitlab.com)

mentioned in commit 7a2a8260e7

mentioned in commit 7a2a8260e743ab414d99f7bcb5a4483dbea143d6

paulhitt (Migrated from gitlab.com) merged commit 7a2a8260e7 into main

2026-09-11 13:16:58 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: extant2000/flamenet-relay#197