5 ms·

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 aro

by Rd6n6 5y ago

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

pwdisswordfish8 5y ago
> The max timer is too short 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.
dddw 5y ago
I agree, some conversations like spouse you'll like to look back and forth a little. I've sent in a issue omg GH about a year ago, will look it up.
Vinnl 5y ago
I suppose that's why: > 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.
- mrpotato 5y ago
  I thought the same as you until I checked how it worked in the app. Maximum is 4 weeks, there is no higher option.
  - Vinnl 5y ago
    Shame! Thanks for verifying though.
benhurmarcel 5y ago
I agree, I don't use it for most conversations because 1 month is too short. I'd go for 6 months or even 1 year.
Symbiote 5y ago
The discussion for a longer timeframe is here [1]. It seems Moxie doesn't want this [2], and it's disappointing that he doesn't provide any explanation or justification. 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-options-for-disappearing-messages/2744/83 https://community.signalusers.org/t/longer-timeframe-more-op... [2] https://github.com/signalapp/Signal-Android/pull/6814#issuecomment-327033465 https://github.com/signalapp/Signal-Android/pull/6814#issuec...
- AnonHP 5y ago
  > It seems Moxie doesn't want this [2], and it's disappointing that he doesn't provide any explanation or justification. 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.
pavon 5y ago
Agreed. Also surprised to see how short the suggested times on pull-down list are. Many of them might make sense to set on a specific conversation, but are insanely short as a default for all conversations. I don't have my phone on me 24/7, and thus would never even see messages from a sender who used more than half of those options.
wolverine876 5y ago
From Signal in July 2020: > 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. https://github.com/signalapp/Signal-Android/issues/9855 https://github.com/signalapp/Signal-Android/issues/9855

by Rd6n6 5y ago

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

pwdisswordfish8 5y ago

> The max timer is too short 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.

dddw 5y ago

I agree, some conversations like spouse you'll like to look back and forth a little. I've sent in a issue omg GH about a year ago, will look it up.

Vinnl 5y ago

I suppose that's why: > 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.

mrpotato 5y ago
I thought the same as you until I checked how it worked in the app. Maximum is 4 weeks, there is no higher option.
- Vinnl 5y ago
  Shame! Thanks for verifying though.

benhurmarcel 5y ago

I agree, I don't use it for most conversations because 1 month is too short. I'd go for 6 months or even 1 year.

Symbiote 5y ago

The discussion for a longer timeframe is here [1]. It seems Moxie doesn't want this [2], and it's disappointing that he doesn't provide any explanation or justification. 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-options-for-disappearing-messages/2744/83 https://community.signalusers.org/t/longer-timeframe-more-op... [2] https://github.com/signalapp/Signal-Android/pull/6814#issuecomment-327033465 https://github.com/signalapp/Signal-Android/pull/6814#issuec...

AnonHP 5y ago
> It seems Moxie doesn't want this [2], and it's disappointing that he doesn't provide any explanation or justification. 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.

pavon 5y ago

Agreed. Also surprised to see how short the suggested times on pull-down list are. Many of them might make sense to set on a specific conversation, but are insanely short as a default for all conversations. I don't have my phone on me 24/7, and thus would never even see messages from a sender who used more than half of those options.

wolverine876 5y ago

From Signal in July 2020: > 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. https://github.com/signalapp/Signal-Android/issues/9855 https://github.com/signalapp/Signal-Android/issues/9855