This winter really kicked my arse. I had colds and flu three times (April, July, and August). And generally struggled with energy and motivation.
As of today I am taking a week of annual leave, and the only thing I need to do today is be awake and at home during the hour my groceries are scheduled to get delivered. This is a good amount of responsibility to have.
Over the next 9 days I want to do the following 3 things:
1. Take laptop in for repairs
2. Book and have an appointment with osteopath
3. Spend a night at my dad's.
Also do some chores around the house, but not to spend more than 2 hours a day on them.
Also finish The Stone Sky and start on The Shepard's Crown.
Also some Ingressing if the weather is nice.
Also lots of naps.
I should know that everything involving printing is just... perma-stupid. But still.
I've been tweaking both web sites to use <IMG SRCSET> in a few places in an attempt to speed things up a bit by downloading less data. The spec for SRCSET is actually pretty sensible, allowing the browser to download an appropriately-sized image based on the size of its window, the relationship between screen pixels and display pixels, and your hint as to how much of the screen the image will take up..
So let's say you've got a stack of SRCSET images, and the image on your screen is, let's say "five inches" wide, whatever that means, and the vagaries of the world result in the 768px image being used for that. So then you hit print. And now you're going to be printing a "five inch" image on a 300dpi device. Does it use the 1600px image for that?
The hell it does. It scales up the blurry-assed 768px image.
Safari, Mozilla, Chrome and Opera all do this.
This is annoying, because in the DNA store, when you buy a ticket, you are presented with a page with a image of your ticket on it, like so:
One of the common use cases here is "print it out and take it with you". So I've been serving 1600px PNGs, so that they will print well. But it sure would be nice if the people who aren't printing were being served a smaller file.
So I guess my choices are to keep serving large images always, or have prints be blurry. "Hooray."
Maybe there's some nuttery I could do with @print stylesheets in the CSS to override the SRC but that sure sounds fragile.
I mean, hopefully most people are using the Apple Wallet pkpass attachment we send them instead of printing, but still, this is dumb and ought to work.
Incidentally, is there some Android equivalent of pkpass? I'm including the Google-recommended EventReservation microformat in the confirmation email, but I tend to assume that microformats are still just wishful thinking. I haven't seen any documents suggesting that this format actually does anything anywhere. Does it? If it does, what does it look like? (Go buy a DNA ticket and send me a screen shot.)
( spoilers )
It had sold out and then got discontinued (naturally) … and so, even though I love how yummy it smells, I use it very sparingly so I can have it longer.
It’ll be a sad candle day when I finally use up the Italy Espresso candle, but at least I have the Coffee one and Cocoa one to take it’s place now.
As you know, the primary lesson of Scooby-Doo is that ghosts and monsters don't exist, it's always, always a shady real-estate speculator wearing a rubber mask.
Please combine all of these videos of supercuts of the Scooby Gang unmasking, and photoshop Donald Trump's cartoon face onto all of the villains.
I thank you. Future generations thank you. And most of all, those meddling kids thank you.
Just for the record, when this Unfrozen Caveman bitches about the horrors of the world, it is not without recognition of my culpability.
Montulli and Weissman also deserve a portion of the blame, but I was the one who ran with it, so I'm sure they'd be happy to let me fall on that sword.
Date: Thu, 25 Aug 2011 20:01:22 -0700
From: Jamie Zawinski <email@example.com>
Subject: Re: HTML e-mail: is it your fault?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
X-Mailer: Apple Mail (2.1084)
Date: Thu, 25 Aug 2011 14:45:13 -0700
From: Andrew Gray <adsgray@...>
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.5.20 (2009-08-17)
I'm trying to figure out when HTML e-mails were first sent. Do you happen to know if the Netscape Mail and News clients that you worked on were the first MUAs to render HTML?
This question is in the context of struggling to craft an HTML e-mail that looks "good" in every possible stupid mail program that anyone could possibly still be using in the year 2011.
You know, my gut reaction is that the answer to this question is "no", but after some digging, I have yet to find any evidence of a mail reader that can display inline HTML messages (email or USENET) that predates Netscape 2.0!
If you find out for sure, please let me know!
I think there may have been closed systems inside Compuserve and Outlook that supported rich text messages (in formats other than HTML).
The Andrew Message System at CMU and MIT supported WYSIWYG rich messages, including inline images and audio attachments, as early as 1985. Not HTML or MIME, but a predecessor to MIME, as the architect of that was Nathaniel Borenstein who wrote the first MIME RFC.My other project is a time machine of course. First application: preventing HTML e-mail from ever happening.
Yeah, go back to chipping your USENET posts out with a piece of flint, why don't you.
Even if it wasn't the first, Netscape Mail was probably the first mail reader that put the ability to easily *view* HTML messages in front of more than a million users.
I know that Eudora 4 supported display of HTML email, and possibly composition of it, but I'm not sure when that was released.
Qualcomm/Eudora spent a while trying to push text/enriched (RFC 1523, published late 1993 -- not sure when Eudora first supported it) as an alternative to HTML, but that went nowhere. Early versions of Netscape (at least 1.1, I think possibly earlier) supported display of text/enriched, but just about nobody was even aware of that because nobody ever used it.
We also supported display of text/richtext, which was an HTML-like SGML dialect with only a few tags. In 2.0b1 or possibly earlier. I added that just to placate the peanut gallery, not because I expected anyone to actually use it.
I think the only person who really used text/enriched was Brad Templeton through ClariNet, where you could subscribe to USENET newsgroups of the UPI/AP feeds that were formatted with it.
From Mosaic Netscape 0.9 through Netscape Navigator 1.1 (1994), there was a mail composition window which allowed one to attach external URLs. They were attached as MIME multipart/mixed attachments with proper Content-Type and Content-Transfer-Encoding (using quoted-printable to ensure short lines).
You could also "attach" things with "Include Document Text" which would suck them in as plain-text with ">" at the beginning of each line, wrapped at 72 columns.
There was also a USENET news reader and composer built-in. The USENET reader's display of MIME documents was remedial at best. The composition tool only allowed plain-text. Version 0.9 displayed any part of a message between <HTML> and </HTML> as such, even if there was no Content-Type header. That was removed some time before 2.0. Back then, you couldn't actually rely on a Content-Type header propagating through multiple USENET hops -- bnews would strip out any headers it didn't know about!
(Remember that 1.1's big innovation was *tables*. 1.0 didn't have 'em!)
2.0 contained the mail reader, with full MIME support (which was also a news reader, replacing the minimalist one that 1.0 had). So that showed up in 1.22b or so, mid 1995, I guess?
I believe 3.0 was the first version with WYSIWYG HTML composition, early 1996. To accomplish that in 2.0, you had to attach an HTML file. If there was only one attachment, it was sent as the single MIME part.
Forwarded messages were attachments of type message/rfc822 and included full headers, which were hidden upon inline display. Nobody does that any more because now the world sucks.
There was the IETF MHTML working group as early as 1995. I can't find a working archive of the mailing list, but it was run by a fellow named Jacob Palme -- http://people.
dsv. su. se/ ~jpalme/ ietf/ jp-ietf-home. html
Microsoft Outlook Express shipped in 2005 and did not support HTML, but later versions (2006? Maybe 2008?) posted HTML *by default* to both mail and news. This angered many. Outlook Express is also where the blight of top-posting originated, those monsters.
Here, this may be helpful too: http://web.
archive. org/ web/ 19990128073742/ http%3A//www. cis. ohio-state. edu/ hypertext/ faq/ usenet/ mail/ mime-faq/ part2/ faq.html
It would be fantastic if you could update http://en.
wikipedia.with your findings. org/ wiki/ HTML_email
DNA Lounge - 375 Eleventh Street, SF CA 94103 - 415-626-1409
The worst case, given the specified uncertainty, would be that the approaching object is already fractured and weak enough to explode at high altitude. Such an airburst can spread its energy out over a larger area and will be more damaging than a crater-forming impact. The worst-case scenario would be a high altitude airburst releasing about 10.6 Mt of energy. The best estimate would be that the fragment is a slightly less dense 50-meter object. Even a relatively strong object of this size is likely to explode at high altitude; although it is possible some fraction of it could reach the ground and form a crater. This best estimate is almost identical to current understanding of the Tunguska explosion. [...]
Since the uncertainty in impact location is extensive, we also provided a map showing the damage footprint at several locations within the ellipse, which we then we convolved with the footprint (Figure 3). We advised participants that preliminary evacuation plans for an airburst over land should be in a lateral direction into area known already to be at no risk, but that detailed plans should wait until radar data becomes available (about 6 days before impact) [...]
Much of the uncertainty ellipse spans parts of the Gulf of Mexico. An impact within that part of the ellipse would produce a tsunami, and would affect the whole of the coastline from Texas to Florida. According to calculations by Souheil Ezzedine of Lawrence Livermore National Laboratory (LLNL) a tsunami generated by an impact in the easternmost part of the ellipse would have wave heights of 3 to 10 m and would arrive at the coast over a time spanning from 1 to 4.25 hours after the impact. The tsunami would first reach the Louisiana coastline, causing near total destruction to the barrier islands, The wave run-up would extend inland as far as 16 km.
When planetary physicists start role-playing, you end up with the darkest tabletop strategy game ever.
When Joel Thornton at the University of Washington in Seattle and his colleagues looked at records of lightning strikes between 2005 and 2016 from the World Wide Lightning Location Network, they noticed there were significantly more strikes in certain regions of the east Indian Ocean and the South China Sea, compared with the surrounding areas. Unusually, they occurred along two straight lines in the open ocean, which coincided with two of the busiest shipping lanes in the world. Along these paths there were twice as many lightning strikes as in nearby areas.
"We were quite sure the ships had to be involved," says Thornton. But they still had to eliminate other factors that influence storm intensity, such as wind speeds and temperatures.
Once these had been ruled out, the team concluded that aerosols from the ships' engine exhausts were the culprit. Aerosol particles act as seeds, around which water vapour condenses into cloud droplets. In clean air there aren't many seeds, so the cloud drops quickly grow and fall as rain. But when there are a lot of seeds, like over busy shipping routes, a greater number of small cloud drops form. Since these are light, they rise up high into the atmosphere and freeze, creating clouds rich in ice.
It is this that leads to more intense thunderstorms: lightning only occurs if clouds are electrically charged, and this only happens if there are lots of ice crystals. [...]
Although lightning activity is higher over the shipping lanes, the amount of rainfall is no different to nearby regions.
Because that's a totally reasonable thing to do.
It's not like "Hey I would like to display a plain-text version of this angry tag salad" is why multipart/mixed exists in the first place or anything.
My guesses on the thought process here, from least to most likely:
- Eh, everybody just generates their text/plain part by stripping tags anyway, without even the courtesy-reacharound of turning <BR> into \n so why bother?
- I tried that but then 90% of my mail notifications turned into, "Please use an HTML capable mail reader to view this message" because nobody generates text/plain parts but for unknown reasons they feel compelled to include them anyway.
- By the time we are putting that dialog on the screen, we are thirty levels above the last framework that had access to the MIME parts, because that's how software works now, so fuck it, fuck it all, burn it all down.
- Even though I'm on the team that writes a mail reader, I have not read RFC2046.
- Herp derp I eat paste.
Since the Charlottesville attack a month ago, a review of commentary in the six top broadsheet newspapers -- the Wall Street Journal, New York Times, USA Today, LA Times, San Jose Mercury News and Washington Post -- found virtually equal amounts of condemnation of fascists and anti-fascist protesters. [...]
While most "both sides" columns added a qualifier clarifying that there was no moral equivalency between antifa and neo-Nazis, this framing could not help but imply that there was. And a few explicitly argued that, yes, anti-fascism was just as bad as fascism: [...]
The Washington Post and New York Times published markedly more critiques of neo-Nazis than of antifa: the Post by five to two and the Times 13 to five. This was in contrast to the coverage in the Wall Street Journal -- five antifa condemnations and no anti-Nazi ones -- and USA Today, which featured seven anti-antifa pieces and only three opposing white supremacists or calling on Trump to do so. The LA Times and Mercury News were basically split down the middle, with the former publishing six anti-antifa and five anti-Nazi takes, and the latter publishing three against antifa and two against Nazis.
The Wall Street Journal felt compelled to publish five pieces on the resistance to resurgent white supremacy -- without publishing a piece criticizing the resurgence of white supremacy itself.
The Wall Street Journal seemed particularly averse to calling out Trump for soft-pedaling and dog-whistling white supremacists. A recent Guardian expos documented how dozens of writers have left the Journal in response to corporate pressure to "normalize" the Republican president -- an effort evident in the uniformly positive takes on Trump's response to Charlottesville.
Age: 55 (Good G-d, how did that happen?)
Location: Seattle, WA
Describe yourself in five sentences or less: I’m a New York transplant living in Seattle with two cats and way too many books. I am creative and opinionated and still express myself like a native New Yorker, which makes some Seattleites uncomfortable despite my best efforts. I am a theater geek, a movie buff, a lover of tabletop and board games, a reader, a writer and a jeweler.
Top 5 fandoms: I’m a second-wave slash writer (second-wave as in: the first wave was in the early 1970s, the second in the mid-’80s to early ’90’s; everyone else came after) who hasn’t written fanfic in a while, but when I was doing that it was Star Trek, Starsky & Hutch and, more recently, Doctor Who (see my fanfic journal at scarlett_key). I have loved watching and discussing Buffy the Vampire Slayer, The X-Files, Downton Abbey, Game of Thrones, so many more. How do you pick just five?
I mostly post about: My personal life, which also tends to be sprinkled with bits about politics, the science fiction community, movies, theater, books, travel, cats, my family, writing and observations about life in general.
I rarely post about: sports, math, the giant hornbeam tree in front of my condo, jackalopes, and my collection of porcelain hands (yes, really).
My three last posts were about: I occasionally do the Friday Five so this morning’s post was answering last week’s questions, two particularly striking dreams, and discovering the pile of get-well cards I received when I was in the hospital last year.
How often do you post? I currently post about once a week, though I’m aiming for better.
How about commenting? I try to comment on at least half to two-thirds of the posts that I read.