Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feature] Trim messages when limit is reached #267

Closed
ghost opened this issue Jun 23, 2015 · 7 comments
Closed

[feature] Trim messages when limit is reached #267

ghost opened this issue Jun 23, 2015 · 7 comments

Comments

@ghost
Copy link

ghost commented Jun 23, 2015

Like it is being done on Android, it would be useful to be able to set a limit after which conversations are automatically trimmed. Not a priority of course

@McLoo
Copy link
Contributor

McLoo commented Jun 26, 2015

The 2000 char on android are quite a lot for a messenger, though TS-B lets you send unlimited(?)/more than 2000 chars. That extra above 2000 is lost on the receivers side as well as on a paired device.
Might be a good idea to notify about that.

@ghost
Copy link
Author

ghost commented Jun 26, 2015

I am talking about a different thing. I'm talking about the trim feature in the settings. The way to delete old messages, you know...
I opened an issue about what you're talking about here: signalapp/Signal-Android#3362

@McLoo
Copy link
Contributor

McLoo commented Jun 26, 2015

lol. sry.

@spipau
Copy link

spipau commented Mar 5, 2019

I just had a SQL Error in my Database and had to reinstall Signal Desktop. I had to delete a database of 10GB! Trimming these old messages would save a lot of disk space for many people.

@kpuljek
Copy link

kpuljek commented Mar 25, 2019

+1, would prefer to trim messages on desktop, without search they're useless anyway

jacobogonzalez pushed a commit to ra-app/desktop that referenced this issue Nov 22, 2019
@EvanHahn-Signal EvanHahn-Signal removed this from the On the roadmap milestone Apr 9, 2021
@stale
Copy link

stale bot commented Sep 23, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Sep 23, 2021
@spipau
Copy link

spipau commented Sep 23, 2021

Some "Activity" so the bot doesn't close this issue as I still think that this is relevant 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

7 participants