The max timer is too short. 6 months would be a convenient value - enough time to reference the messages while they might be relevant, but also not floating around forever
I'd like something like 3 months / 13 weeks, but 3, 6 and 12 months seem like good durations.
[1] https://community.signalusers.org/t/longer-timeframe-more-op...
[2] https://github.com/signalapp/Signal-Android/pull/6814#issuec...
That's sad to know. But we need to face the fact that Signal is not a community driven project. It has always been a moxie driven project. So it's not surprising that he would do (or not do) things that the rest of us don't understand or agree with.
Short enough to hopefully nudge people into immediately writing the whole thing off as a terrible idea and then choosing not to enable it.
Apparently dumb shit like this is what Moxie had in mind when he wrote the infamous blog post about why disallowing personal (patched) builds and third party clients gives them the advantage of being able to control the user experience in a way that they wouldn't be able to if people were using an unsanctioned client.
> We’ve also added the ability to set custom timer durations on your conversations, so that some content can be gone in 60 seconds and others can exist for 18 minutes or 4 weeks.
> As far as longer durations are concerned, it's tricky, because backups do not include disappearing messages. That can cause unexpected behavior for a user that set their timer to 18 months.