Accidental autumnal pattern

The little kite shape


fell out of an arch design I was studying, and I thought it was too nice to throw away. Must’ve been something about the falling leaves that made me choose colours like these.

Here’s the SVG, if you care to:


View in Instagram ⇒

Fountain decoration excerpt

Excerpt of mosaic pattern from 16th C CE fountain from Eqypt in the Aga Khan Museum
Excerpt of mosaic pattern from 16th C CE fountain from Egypt in the Aga Khan Museum
Fountain — photo by Sameer Vasta from Flickr. CC BY-NC-SA, 2015.

Clipped repeat:


(Not sure if I got the mosaic quite right. There were some damaged and replaced tiles that look a little out of place.)

maybe I *do* want the Small Web back …

All I wanted to do was read a post on Winston Rowntree‘s Patreon page, yet something was blocked by uBlock Origin. In trying to find what it was, I found the page was pulling in 91 separate resources from 15 different sites:

Do we really need all that crud? It’s a bunch of trackers and fonts and mystery swf and javascript. It might be all responsive web like, but the more fancy you do, and the more of other people’s “TRUST ME” code you pull in, something’s gonna go wrong.

Perhaps a wee lie down is in order

Just the output of a little PostScript program I wrote. Don’t let the little blobby shapes fool you; geometrically, they behave like hexagons. Yes, ½√3 figures a lot in the code.

View in Instagram ⇒

svgo: silently destroying creators’ rights since whenever

svgo is, on the face of it, pretty neat: it takes those huge vector graphic files and squozes them down to something more acceptable. Unfortunately, though, the authors have seen too many files with junk machine-generated <metadata> sections, and decided that it’s all worthless.

Metadata isn’t junk; it’s provenance. Your RDF? Gone. Your diligently researched and carefully crafted Dublin Core entries? Blown away. The licence you agonized over? teh g0ne, man. svgo does this by default. It would be very easy to use this tool to take someone else’s graphic, strip out the ownership information, and claim it as your own. It would be wrong to do that, but the original creator would have to find your rip-off and go to the effort of challenging your use of it. All so much work, all so easily avoided.

You can make svgo do the right thing by calling it this way:

svgo  --disable=removeMetadata -i infile.svg -o outfile.svg

There’s apparently a config option to make this permanent, but the combination of javascript, no docs and YAML brings me out in hives. Given that the metadata section of a complex file is typically a couple of percent of the total, it’s worth keeping. Software passes; but data lives forever, so be kind to it.

work as if you live in the early days of a better nation