3 ms·
Technically interesting, but why would I use this over one of the many full page screenshot or "Print to PDF" browser extensions? That is what I use when I want
by eastendguy 6y ago
Technically interesting, but why would I use this over one of the many full page screenshot or "Print to PDF" browser extensions? That is what I use when I want to archive something.
- heinrichhartman 6y agoWhich browser and extension are you using? I tried a few, but could not get good results with any of them. print to pdf, output always looked terrible. Full page screenshot took ages to scroll throught the page hijacking my viewport. Those captures should happen in the background.
- eastendguy 6y agoFor manual capture I use https://chrome.google.com/webstore/detail/full-page-screen-capture/fdpohaocaechififmbbbbbknoalclacl https://chrome.google.com/webstore/detail/full-page-screen-c... and Chrome "Print to PDF". Layout issues are not important for my use case. For scheduled captures I automated this workflow with kantu: https://chrome.google.com/webstore/detail/uivision-rpa/gcbalfbdmfieckjlnblleoemohcganoc https://chrome.google.com/webstore/detail/uivision-rpa/gcbal... > Those captures should happen in the background. Yes, it would be nice if the Chrome extension api would allow full page screen captures to happen instanstly. Currently all extensions need to scroll up/down.
- gildas 6y ago> Currently all extensions need to scroll up/down. SingleFile does not. It can save lazy loaded contents without scrolling.
- jcahill 6y agoWeb archivists are coming at the problem with different requirements, related to fidelity and the systematic mirroring of address structure along with payload content and control information. By the sound of it, you likely wouldn't want to substantially change your personal filing system to have your page captures conform with those requirements.