I suggest the 5 second wait to delete method to be revised

It can be dangerous.

Today I lost all my contacts.

I had the new Jolla phone and the old one laying before me on the desktop to transfer contacts from the old phone to the new one. I selected all contacts and was ready to transfer. Then I had some bluetooth issue and searched the net for help - during which I accidentally touched the phone with the selected items - apparently right on the trash bin. I didn’t see the timer running, because I didn’t notice the touch. When I looked at the phone, I only saw the message n contacts deleted. :grimacing:

1 Like

Apart from double-confirm on high-stakes stuff, what do you actually mean should change?

1 Like

I would feel safe if I had a way to enable double confirmation for all deletes. It should be optional but possible. Touch delete, then swipe or something like that.

3 Likes

Hi,
something similiar happened to me when Jolla decided to change from the continuous remorse bar to one that just ticks 5 times. While both giving 5 seconds to react, the former just draws more attention that something’s happening (maybe related to our brain being much more alerted to moving things).
Fortunately, there exists a patch “Smoothly running remorse counter”. For me that’s enough, maybe for you too.

1 Like

Hi! And thanks for your idea. Can you explain the difference? I’ve been using sailfish since the start, but can’t remember. It probably wouldn’t have helped though, because I wasn’t looking.

It wouldn’t help if you look at an entire different direction. But (at least fo me) it just helps to draw attention if looking at something else nearby, thus registering it in peripheal view.

1 Like

You do have a backup, do you?

1 Like

I wish there were configuration option to change from remorse timer to a popup where one has to drag a slider to confirm a destructive action.

At least once I have lost data due to remorse timer starting accidentally without me knowing that I’ve activated something (action activated similar to accidental “pocket call”)

Also, I’ve “panicked” during that short remorse timer period, sometimes just failing to disable, sometimes accidentally swiped the timer away (which made the destructive action happen instead of canceling it)

I.e. IMO the UX of the remorse timer is bad. Some think differently. But if there were way to replace it with something…

3 Likes

Haha, I knew someone would say that. I own a cup with an inscription saying no backup no pity. But I have no current backup. :smiley:

2 Likes

Heise? See the devops aspect: Fail fast, fail hard, do never try this again. Sorry for your loss.

2 Likes

Yep, Heise. I didn’t lose too much, but I was sweating nevertheless.

Devops you say? I’d love to backup my phone via ansible.

Probably possible with rsync combo. This post might help in some partial ways too.

I don’t know how to trigger manual backup to tar on SD from settings in CLI or any other way automatically. Not asking for cloud option. I would appreciate if anyone know?

1 Like

I just tried it. This works from the terminal directly on the phone at least:

busctl call --user org.sailfishos.backup “/sailfishbackup” org.sailfishos.backup backupToFile s /home/defaultuser/manual-backups/backup.tar

The manual-backups directory was created and a big backup.tar in it.

It also has a progress method. You can look up the sailfish backup capabilities with this command:

busctl --user introspect org.sailfishos.backup "/sailfishbackup"

4 Likes

Thanks. That was fast!

3 Likes

I agree with you, that only the remorse timer to cancel the action is not the best solution. I once suggested a different approach: delete immediately but provide the remores timer to UNDO the action. That way, you could also enable an UNDO action that can be triggered after the remorse timer timed out, e.g. by adding a top-menu item “Undo” afterwards.

1 Like

I actually find double confirmations quite annoying. It reminds me of Windoze behaviour … Delete … Click yes … Popup: do you really want to delete? … If I wouldn’t want to, I’d not hit that button!

If I really deleted something erroneously, I could recover it from the bin, under Linux as well.

So, I’d definitely prefer a simple routine to recover files from the bin instead of a double confirmation for deletion - or, at least, a possibility to disable the double confirmation.

To me, the 5 seconds remorse timer seems to be more than enough to reverse my decision.

1 Like

I think an option to enable double confirmation would be the best for everyone.

I also thought about undo, but bin and undo approaches introduce a lot of complexity compared to optional double confirmation.

2 Likes

Agree, I also prefer ‘opt-in’ to ‘opt-out’, actually. :+1:

2 Likes

My guess is that it should be feasable to write a patch that would allow the timer to be either 5seconds, 10 seconds or 20 seconds.
It may not be exactly what you want.

Some apps, like Fernschreiber, use a 10 seconds timer for important things such as deleting a chat.