Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

1

+1 this is spot on the heart of the matter. There is so much safety by default people implement these days that in the worst case scenarios you still aren't risking true user mistakes: imagine the email client fails to delete, now local state is bad, and they try delete email 4 which is misaligned with the server, the vast majority of back-end devs will have a safety catch there to ensure you only delete what the user absolutely wants to and so this misalignment will not cause erroneous deletions (it may fail in error but it will not delete).

Jimmy Hoffa
– Jimmy Hoffa

2013-01-31 18:09:56 +00:00
Commented Jan 31, 2013 at 18:09
@JimmyHoffa you would use a unique email id in the delete request. It would be really bad to send delete requests based on the arbitrary display order of the emails in your inbox.

Buttle Butkus
– Buttle Butkus

2014-11-05 06:27:26 +00:00
Commented Nov 5, 2014 at 6:27

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »