Bitmessage/PyBitmessage-2025-02-25
Archived
2
0
Fork 0
Code Issues 167 Pull Requests 54 Actions Packages Projects Releases 5 Wiki Activity

Message count limit #695

New Issue
Open
opened 2014-07-28 10:35:12 +02:00 by neko259 · 4 comments
neko259 commented 2014-07-28 10:35:12 +02:00 (Migrated from github.com)
Copy Link

Please add the limit to a maximum number of inbox messages. There are too many of them and removing very very very old ones is slow if doing it manually.

Please add the limit to a maximum number of inbox messages. There are too many of them and removing very very very old ones is slow if doing it manually.
ghost commented 2014-07-30 14:38:00 +02:00 (Migrated from github.com)
Copy Link

Added to TODO list. An alternative might be to have messages expire from the inbox after a specified amount of time.

Added to TODO list. An alternative might be to have messages expire from the inbox after a specified amount of time.
bmng-dev commented 2014-07-31 08:42:25 +02:00 (Migrated from github.com)
Copy Link

Email had a similar problem too. Users who reached the storage limit complained they couldn't get new messages and insisted the messages they kept were important. If messages are deleted without the users knowledge they complain about losing important messages. If users have 'unlimited' storage they complain about performance issues or not being able to find messages. Users are the ultimate decision maker in which messages are important/unimportant to them, so it falls to users to have an adequate workflow that archives important messages and deletes unimportant ones.

Certainly the delete mechanism needs improvement but with a workflow that regularly goes through your inbox identifying important and unimportant messages and archving/deleting them as appropriate users shouldn't have so many messages that deletion causes significant delay. Just in case people don't know, you can right-click on a message in the inbox and there is a 'Save message as...' option useful for archiving.

Email had a similar problem too. Users who reached the storage limit complained they couldn't get new messages and insisted the messages they kept were important. If messages are deleted without the users knowledge they complain about losing important messages. If users have 'unlimited' storage they complain about performance issues or not being able to find messages. Users are the ultimate decision maker in which messages are important/unimportant to them, so it falls to users to have an adequate workflow that archives important messages and deletes unimportant ones. Certainly the delete mechanism needs improvement but with a workflow that regularly goes through your inbox identifying important and unimportant messages and archving/deleting them as appropriate users shouldn't have so many messages that deletion causes significant delay. Just in case people don't know, you can right-click on a message in the inbox and there is a 'Save message as...' option useful for archiving.
ghost commented 2014-07-31 08:47:50 +02:00 (Migrated from github.com)
Copy Link

So I think this should be off by default, and maybe configurable by address. You might not care that chan messages expire after some time but always want to keep messages for other addresses.

So I think this should be off by default, and maybe configurable by address. You might not care that chan messages expire after some time but always want to keep messages for other addresses.
neko259 commented 2014-07-31 08:59:56 +02:00 (Migrated from github.com)
Copy Link

@bmng-dev My email client has a setting to delete the old messages and (optionally) keep "starred" ones. I think for now just deleting messages would work fine (off by default for those who want to keep their important messages) and then add "add to favorites" option.

@bmng-dev My email client has a setting to delete the old messages and (optionally) keep "starred" ones. I think for now just deleting messages would work fine (off by default for those who want to keep their important messages) and then add "add to favorites" option.
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working as it's supposed to
build
Related to building or build system
dependencies
Pull requests that update a dependency file
developers
The issue is relevant mainly for developers rather than users
documentation
duplicate
enhancement
New feature
formatting
Code or UI text formatting
invalid
legal
mobile
Frontend for mobile devices (kivy)
obsolete
packaging
performance
protocol
Protocol change
question
refactoring
regression
Some issue, fixed in the past, appears again
security
test
translation
usability
wontfix
No Label
enhancement
Milestone
No items
No Milestone v0.8.0
Projects
Clear projects
No project
Assignees
Clear assignees
PeterSurda
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Bitmessage/PyBitmessage-2025-02-25#695
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?