I have teletype running on a daily driver ubuntu workstation, and a macbook pro that I use for travel. My intention was to have a sort of "shared todo.txt" config going, where I have one text file, and I need it to be 'live' between multiple hosts. I can reach my daily driver desktop via vpn when traveling, so connectivity shouldnt be a big deal, here's what I've encountered:
-atom.io on ubuntu "just stops". it freezes and a couple times has taken down gnome with it. There's no way to recover from this. I have to kill it, or at worst, reboot, and i lose any unsaved changes - and when this happens, the 'client' (the macbook) complains that the server has not spoken to it in a while and deletes all the local content (this is really bad).
Here are several suggestions on how to better handle periods of inactivity and interrupted networking:
let me specify an versus using a portal uri link. the ip of my desktop will never change, and I'm treating it like "the server" here.
incorporate timestamps in changes, and if the 'server' dies, and comes back again, then it would be amazing for it to notice that 'the client' has a newer copy with changes and will accept the changes from the client
under no circumstance should teletype make atom.io nuke all the local content.
allow the user to specify a file somewhere, like an smb share or dropbox or something similar that acts like a 'state file', so there is more of a github-like experience where no one instance of atom.io is 'the server' and will cause data loss if it goes away
I have teletype running on a daily driver ubuntu workstation, and a macbook pro that I use for travel. My intention was to have a sort of "shared todo.txt" config going, where I have one text file, and I need it to be 'live' between multiple hosts. I can reach my daily driver desktop via vpn when traveling, so connectivity shouldnt be a big deal, here's what I've encountered:
-atom.io on ubuntu "just stops". it freezes and a couple times has taken down gnome with it. There's no way to recover from this. I have to kill it, or at worst, reboot, and i lose any unsaved changes - and when this happens, the 'client' (the macbook) complains that the server has not spoken to it in a while and deletes all the local content (this is really bad).
Here are several suggestions on how to better handle periods of inactivity and interrupted networking: