Thanks for flagging this confusion. It's helpful to hear how this is perceived. Short answer: The spreadsheet is, indeed, embedded in a broader context. (And has a pointer to that context in the "Notes" tab.) Slightly longer explanation in my main comment on this thread.
That's an interesting suggestion, thanks. Certainly worth looking into. In the meantime, you can consider the newsletter's landing page to be a canonical URL of sorts — it will always link to the structured archive: https://tinyletter.com/data-is-plural
Hi, author/creator here. Very neat to see this on HN, thanks. The spreadsheet is a byproduct of the weekly newsletter I publish: https://tinyletter.com/data-is-plural
The spreadsheet simply contains the text and links from each newsletter edition ... but in a tabular format. (One advantage to the newsletter over the spreadsheet: the links make a bit more sense, since they're associated with specific anchor text.) The "non-structured" archive of previous newsletters can be found here: https://tinyletter.com/data-is-plural/archive
I've been using VisiData for about nine months now, and have found it to be tremendously useful. These days, it's typically the first first tool I reach for when examining/exploring a new dataset.
Hi, Greg! Library author here. I'd be happy to add a configurable UserAgent. Perhaps the default would be a generic "waybackpack" but could be configurable to add contact info for the user. Does that sound about right? Prefer a different approach?
And, yep, the library is intentionally designed only to request one snapshot at a time.
Agreed. The archive uses the first line of the newsletter as the summary. I've been using the same tagline as the first line. But, for future newsletters, I think I'll make the first line more descriptive. E.g., for the most recent: "Maternity leave, art collections, firearm dealers, New Guinea languages, and aircraft-wildlife strikes." Would that be an improvement?
Another thanks for flagging, mark-r. I've updated spectra to address this issue more explicitly. Per colormath[0], colors are allowed to go out of gamut. Colors now have `mycolor.rgb` and `mycolor.rgb_clamped` properties; `mycolor.hexcode` uses the clamped values. Are there other ways you'd like to see the out-of-gamut issue addressed? Open to suggestions.
> And what is the parameter to brighten/darken/saturate/desaturate?
The parameter for brighten/darken is a positive/negative linear adjustment to the L(ightness) value of the color's Lab representation. (Spectra converts the color to Lab, makes the change, and then converts back to the original color space.)
Likewise, the parameter for saturate/desaturate is a positive/negative linear adjustment to the c(hroma) value of the color's Lch representation.