{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigomh2jfxmbbnsauh5hsh2loy2r3yhslp6i3phsssmu2wtjhgj3ei",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mkaqdrhs24b2"
  },
  "path": "/t/what-are-your-thoughts-on-signals-policy-for-edited-messages/37347?page=2#post_23",
  "publishedAt": "2026-04-24T13:44:06.000Z",
  "site": "https://discuss.privacyguides.net",
  "tags": [
    "this topic from 2024"
  ],
  "textContent": "PurpleDime:\n\n> That’s a fair argument. But **when Proton Mail, and other email services allow you to unsend an email within minutes or seconds after you clicked send, aren’t they protecting you against yourself?**\n\nI think the problem here is that it is much easier for a non “real time messaging” service, otherwise known as email in this case, to implement a system in which the client is prevented from viewing the edit history.\n\nI do suppose this differentiation is a little less clear given that IMAP is, more or less, _constantly_ syncing with the email server, where as traditional POP email only synced with (and fetched from) the server at the active demand of the user.\n\nWith regard to assuming edit history is visible:\n\nPurpleDime:\n\n> I don’t think most people make that assumption when the message is unread. That’s the point.\n\nI do think Signal could potentially give a clearer warning _(in app perhaps)_ that edit history is visible, but I do not see this reason alone as justification enough to remove the ability to see edit history from messages that have “yet to be read”.\n\nI also think that, as others have said in this thread, defining when a message is actually unread vs just not viewed in app would add enough complexity that the simpler approach to removing edit history for these messages would be to do so universally, and personally I see to much value in edit history for that to be worth it.\n\nI will say that I do not _personally_ send particularly long/complex messages over signal, and many of my communications on there are with people who understand my writing style and process, so perhaps I just don’t fit the scenario of having to hide my edits on Signal.\n\nWhen I do need to write to less personally acquainted individuals, or in a more formal setting I often draft my intended writing at least once before sending in the hopes of avoiding edits after the fact.\n\n**Side Notes:**\n\nScheduled message sending feels like a separate issue, though I 100% rely on such features myself.\n\nPurpleDime:\n\n> If I had scheduled my emails to be sent at 9 am, which was not possible, my boss would have never gotten that negative impression of me.\n\nThe edit history on this forum has been hidden for some time now because of this topic from 2024\n\nPurpleDime:\n\n> _TrustyRocinante:\n>\n>> I edit my comments on this forum often because I’m impatient\n>\n> I hear you. But this post is not about PG. I am not advocating for PG to hide edits. I am specifically talking about Signal, in the context where the message was unread by the recipient",
  "title": "What are your thoughts on Signal's policy for edited messages?"
}