0x54ask is a <b>todo.txt</b> manager. It supports context (@W at work, @H at home...) and tags (+linux, +bank, +tero). 0x54ask forks SimpleTask Cloudless. It provides passive perks: data safety, automerge, filesystem protection - and it never connects Internet, at all. <b>Todo.txt manager: context and tags</b> <b>Context</b>: You write down a task. If it was the only thing, what would be the next action? Drill a hole for picture? If the wall is in your home, you've got to do it there. Thus, @H (at home). <b>Tags</b>: I'll be working on +linuxeu project for the next 5 hours. Show me all tasks I can bill on that. Thus, filter by +linuxeu. <b>Plain text</b>: Todo.txt is - surprise - plain text. You can edit it with vim, emacs, micro or nano. Todo.txt and calendar.txt use the same +plustags and @Contexts. Fully offline, or synchronize how you like. <b>0x54ask passive perks</b> What does the 0x54ask fork bring to the table? Data safety, better sync, smaller attack surface, modern interfaces. These benefits work passively. You don't have to do anything to use them. <ul> <li><b>Keeps your data safe</b>. It automatically detects if todo.txt has been modified by other programs (such as text editor or syncthing). Modifications appear as soon as 0x54ask sees them. Changes are stored as soon as they are made. Current state of file is checked again.</li> <li><b>Automatic merge</b>. If a conflict is detected, 0x54ask can often automatically merge the changes. This is possible, because todo.txt is a line based format, and many changes appear in different lines. Main approach to auto merge is generic and works, no matter which program made the changes. There is additional support for automatic resolution of Syncthing conflicts. Special support is needed, because these sync conflicts can happen while 0x54ask is not running.</li> <li><b>Filesystem protection</b>: You can pick the directory where todo.txt is. This will be the only directory available for the app. This restric