Anti-tab-proliferation proposal

[ilzolende]

• If it's a good regularly-updating website, subscribe to it on Dreamwidth, unless
  • it lacks RSS
  • it's the county newspaper or my dad's blog or something.
• If it's a good image, save the image file with a meaningful filename.
• If it's a good text blog post, save the raw HTML or the text or something.
• If it's not good, why am I holding onto this tab? I should probably close it.

This is not yet a complete ruleset.

Comments

[brin_bellway]

One year later, I return with an update:

A while back I pulled Digger into my local to-be-read collection by instructing wget to just copy the entirety of diggercomic.com. (Much like archiving a Dreamwidth blog, though without the login cookies.) Initial tests of the local copy suggest it worked fairly well (took a bit of--ahem--digging to find the first-strip page in it, but once you find it it loads even in airplane mode and the "next" button works as it should), and the copy takes up surprisingly little space: 167 MB uncompressed, 79 MB compressed.

Which webcomics were you thinking of? Would this work on any of those?

[contrarianarchon]

Huh, digger is one of the comics I had noticed lowkey as being setup to be *hard* to do that kind of thing to. (to be fair I *still* have no actual skill at non-manual backup collection, but that if that works that's several layers of potentially quite helpful; if you have tutorials that you know are helpful to save me the time googling help when I get around to it, or at least to make me feel obligated to read them, that would be helpful!).

Speaking of updates to this conversation: I forgot about this, tried switching to Firefox because everyone said it was memory-lite (and I kinda wanted to be less google-ecosystem-bound), discovered that not only is it not, but it has fewer and less effective native memory-management tools. I am now foolishly suspended in a state of using both Firefox and Chrome in an extremely foolhardy manner, with several hundred tabs split over two browsers. (Also Edge on the side as a container for Facebook; this should be fixed soon by an extension that Tulip recommended for the purpose, but I need to actually try and *do* that first)

[brin_bellway]

>>if you have tutorials that you know are helpful to save me the time googling help when I get around to it, or at least to make me feel obligated to read them, that would be helpful!<<

In my previous comment I mentioned my guide to using wget on Dreamwidth, much of which (the non-cookie parts) applies in this case as well. Also, here is the official wget manual.

---

>>tried switching to Firefox because everyone said it was memory-lite (and I kinda wanted to be less google-ecosystem-bound)<<

Same. (same action, during same time period, for same reasons)

---

>>not only is it not [memory-lite]<<

In my own experience, the secret to making Firefox memory-lite is to never, *ever* leave a Tumblr dashboard tab open for extended periods of time. (Webpage-view Tumblr blogs seem to be generally fine.) It looks like the memory-leak problems I was having with Firefox were all the blue hellsite's fault, which...well, it certainly seems in-character.

---

>>it has fewer and less effective native memory-management tools<<

Yeah, the lack of ability to crash tabs at will is unfortunate, all the more so for someone with that many of them. Apparently there are extensions for that, though I haven't tried them myself.

---

>>Also Edge on the side as a container for Facebook; this should be fixed soon by an extension that Tulip recommended for the purpose<<

I don't do Facebook per se, but I do use account containers on occasion and they are definitely handy.