You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to build a 'read-it-later' flow similar to Pocket/Wallabag, but instead saving every article of interest as HTML to a folder on a remote server (the folder is then synced by Syncthing then I read them on various devices using KOReader). I think SingleFile could work great for this as I already do the same thing with Zotero Connector which relies on SingleFile.
But in particular, I want to be able to 'save' tabs to this remote folder from many devices including Android, Windows, Mac, Linux. I recently saw this FR and think that using WebDAV destination (or Samba, if that could be easily added) on all these devices might work best, and hopefully might even work on Android via e.g. Kiwi Browser that runs Chrome extensions.
But as I thought more about it, I realized why not have the remote server just run SingleFile directly and produce the HTML there, instead of sending the completed file across the internet? The disadvantages are if you annotate or strip the page prior to saving it which would not be possible on a remote server. But just sending the URL of a page I want to save sounds more lightweight and useful in many scenarios regardless.
I was wondering if this sounds interesting or if there are problems with this workflow (and if there's any easy way to set it up today)? Maybe WebDAV will work best regardless, I'm just concerned about if the connection to the server fails if sending a lot of data wirelessly over 3G/LTE and I unknowingly lose and forget about the page I'm trying to save. I'm also open to other solutions that allow a webpage to reliably be saved to the remote folder, eventually.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm trying to build a 'read-it-later' flow similar to Pocket/Wallabag, but instead saving every article of interest as HTML to a folder on a remote server (the folder is then synced by Syncthing then I read them on various devices using KOReader). I think SingleFile could work great for this as I already do the same thing with Zotero Connector which relies on SingleFile.
But in particular, I want to be able to 'save' tabs to this remote folder from many devices including Android, Windows, Mac, Linux. I recently saw this FR and think that using WebDAV destination (or Samba, if that could be easily added) on all these devices might work best, and hopefully might even work on Android via e.g. Kiwi Browser that runs Chrome extensions.
But as I thought more about it, I realized why not have the remote server just run SingleFile directly and produce the HTML there, instead of sending the completed file across the internet? The disadvantages are if you annotate or strip the page prior to saving it which would not be possible on a remote server. But just sending the URL of a page I want to save sounds more lightweight and useful in many scenarios regardless.
I was wondering if this sounds interesting or if there are problems with this workflow (and if there's any easy way to set it up today)? Maybe WebDAV will work best regardless, I'm just concerned about if the connection to the server fails if sending a lot of data wirelessly over 3G/LTE and I unknowingly lose and forget about the page I'm trying to save. I'm also open to other solutions that allow a webpage to reliably be saved to the remote folder, eventually.
Beta Was this translation helpful? Give feedback.
All reactions