mlhetland
commented
1 year ago For me, the problem here is that the storage demands just keep increasing over time, which also slows down the app. Just opening an image takes several seconds.
Disappearing messages could help, if the time frame could be set to much longer (such as a year, maybe, or even more), because some message history is useful. But since this is only about my local storage, I’d rather not enforce the policy on a receiver.
So … whether the cap is on time, or the number of messages, I’d like (1) for it to be possible to have a large cutoff (represent actual storage capacities), and (2) only affect me.
It seems the comment above here claims it’s possible to do a deletion based on the number of messages, but as far as I can see, that’s not true.
Also: For me this doesn’t even have to be automatic. If I could manually clear up space by deleting old messages, that would be fine. Like, just add some option when deleting chat history to not delete all of it – but only the older parts (based on time or number).
I don’t know if this really is the place for a discussion about this, but I couldn’t find any better place, at the moment. And given that this has been an open request for about a decade, which is supported on Android … it would be really great if some solution could be found for iOS as well.
following on from https://github.com/signalapp/Signal-iOS/issues/254
I've recommended this issue be closed on the upstream as it's a feature request. I also recommended the feature request be closed as one of the options proposed in the title has been shipped (namely removal of messages based on a time).
At this point I stand by the recommendation the feature request be closed (if you ship one of the options given in an issue title then hey that's pretty close and issues shouldn't be open for ever) but agree it's reasonable to open up another feature request with the proposed feature which has not shipped, namely "automatic removal of messages based on a time".