Perma messages #1456
Labels
No Label
bug
build
dependencies
developers
documentation
duplicate
enhancement
formatting
invalid
legal
mobile
obsolete
packaging
performance
protocol
question
refactoring
regression
security
test
translation
usability
wontfix
No Milestone
No project
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Bitmessage/PyBitmessage-2024-12-20#1456
Loading…
Reference in New Issue
Block a user
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?
There should be an option to make a mesage permanent, the corresponding object would be automatically re-created with a new expiration and PoW after the old one expires. This is helpful in particular for chans, so that you can see the message no matter when you join.
If I understood correctly this is possible only for own or anonymous message. You cannot just take message, replace embedded time, do PoW and advertise new object, because data to sign includes embedded time.
Yes, also for chan participants (if sent from chan address). Although that may create signaling problems as to who is supposed to do the PoW.
By anonymous I meant exactly the messages sent from chan address. As for PoW, I guess it should be done by one, who removes the message from inventory (and is fully synced in that time).
More questions are about the receiving parties...
Perhaps at the beginning it should only be supported for yor own and not chan addresses, hiding it in the UI accordingly. It could be enabled later once the questions are resolved.
The indicator could be in an extended encoding variable. There also needs to be method to indicate a reference to the old object for UI handling (to understand these are duplicates) but I'm not sure at the moment how to do that securely.