Delete_current history - dangerous

[scholtalbers]

So...I just screwed up pressing permanently delete on my active history. However, just before, in a different firefox tab I impersonated someone and did not log out but just forgot about it..this resulted in Galaxy deleting his current active history, not the one I was seeing in the active window/tab.

Can this button maybe contain the history id that is visible in the active tab and not call delete_current?

[martenson]

Being id-specific for non-reversible actions sounds very reasonable to me. Ping @carlfeberhard

[dannon]

As far as I know, the plan has always been to remove all notion of "current" history from the API, and require specific identifiers for everything. These non-reversible actions seem like a really, really great early target. +1

[hexylena]

(It sure would be nice if "delete permanently" was only an option once something was deleted. Thus requiring that it first go through the reversible "deleted" state, rather than a one way ticket to /dev/null)