[whispersystems] Feature Request - Scheduled Text Messages

[L. Tate]

I just recently switched over to Signal (a little bit before the TextSecure/RedPhone merge) and the previous texting application I used had the feature to schedule a text message. Which upon discovery of this feature, I used it constantly.My use cases were:- Reminders (whether it be to myself or others)- Text someone without interrupting their current activity (sleeping, in a meeting, etc.)- Birthdays/Misc. Events- Much more...My personal examples, include, but are not limited to, a text message to remind myself in a couple of hours a thought that I had or remind me of a due date sent later that night. To send a message to someone at a later date when they aren’t busy, e.g. a meeting, when it won’t disturb them, e.g. sleeping. To send a text to a friend/relative a happy birthday or comment on an event that was coming up in the future, e.g. congratulations of a wedding or wish good luck to a classmate that has an exam.Honestly, the list could go on and I wouldn’t want to bore you with having to read my examples… I also know that a couple of others I have talked to would want/use this feature.
I would love to help out with the implementation/development of this feature.- Thanks, L. Tate

[scienmind]

Hi Tate,

If you decide to contribute some coding for this, you may want to take a
look on this first: #895
<https://github.com/WhisperSystems/Signal-Android/issues/895>

The feature request is for "delayed send" - being able to set a short delay
(few seconds), during which the sending may be canceled by the user.
The main use cases:
- to prevent accidental tap of "send" button
- a chance to review and "undo" intentional sending during the specified
time period

The code changes needed to support "delayed send" are half-way of what is
needed for "scheduled sending", and since #895
<https://github.com/WhisperSystems/Signal-Android/issues/895> is kept in
the bug tracker for a while now, it seem to be treated as a legitimated
request by the original developers. So I think implementing it may be and a
good place to start moving in this direction.

Also, don't start contributing by submitting huge PRs, start small, so that
you'll get in line with project's coding style and habits.
Unless of course you have already contributed to this project before - in
that case, disregard :)