Bitmessage/PyBitmessage-2024-12-20
Archived
2
0
Fork 0
Code Issues 168 Pull Requests 52 Actions Packages Projects Releases 5 Wiki Activity

Adds original message recieved date in reply. #31

Closed
xqus wants to merge 1 commits from patch-1 into master
pull from: patch-1
merge into: Bitmessage:master
Conversation 2 Commits 1 Files Changed 1 +1 -1
xqus commented 2013-01-27 00:16:18 +01:00 (Migrated from github.com)
Copy Link
No description provided.
Atheros1 commented 2013-01-28 02:36:33 +01:00 (Migrated from github.com)
Copy Link

I've thought about including this before ultimately the reason that I did not was that it reveals the receiver's time zone and that it can't be trusted. The sender of a message cannot be spoofed but the time in a message can be changed. I know that this is true with email as well but I didn't want new Bitmessage users to have to learn to doubt the validity of anything they see in Bitmessage. I would be willing to change my mind but there should at least be an option to disable including the time when you reply. Listing all times in UTC would solve the privacy issue but would be confusing to most people. I can easily add a new checkbox in the settings window on a new 'privacy' tab to enable or disable including the time but for now I think I would prefer to hold-off until it is a more-requested feature and we can decide what time to show.

I've thought about including this before ultimately the reason that I did not was that it reveals the receiver's time zone and that it can't be trusted. The sender of a message cannot be spoofed but the time in a message can be changed. I know that this is true with email as well but I didn't want new Bitmessage users to have to learn to doubt the validity of anything they see in Bitmessage. I would be willing to change my mind but there should at least be an option to disable including the time when you reply. Listing all times in UTC would solve the privacy issue but would be confusing to most people. I can easily add a new checkbox in the settings window on a new 'privacy' tab to enable or disable including the time but for now I think I would prefer to hold-off until it is a more-requested feature and we can decide what time to show.
xqus commented 2013-01-28 19:53:34 +01:00 (Migrated from github.com)
Copy Link

Valid points. :)

Valid points. :)
This repo is archived. You cannot comment on pull requests.
Reviewers
No reviewers
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
bug
build
dependencies
developers
documentation
duplicate
enhancement
formatting
invalid
legal
mobile
obsolete
packaging
performance
protocol
question
refactoring
regression
security
test
translation
usability
wontfix
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Bitmessage/PyBitmessage-2024-12-20#31
No description provided.
Delete Branch "patch-1"

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?