Replies

Thursday, August 6th, 2020

Replying to a tweet from @hdv

It’s the classic metacrap problem: invisible metadata rots.

https://people.well.com/user/doctorow/metacrap.htm

It’s one of the reasons why microformats always favoured marking up existing, visible (user-facing) data.

Replying to a tweet from @yatil

This is an interesting development though:

https://blog.chromium.org/2020/07/using-chrome-to-generate-more.html

HTML -> accessible PDF as an archival workflow?

Wednesday, August 5th, 2020

Replying to a tweet from @jina

No rush! You can take as long as you like.

(As you know, I am no stranger to playing the long game. 🙂)

Replying to a tweet from @ThainBBdL

Whoops! Thanks for spotting that—should be fixed now.

Replying to a tweet from @linushoremans

Nice! (and thank you!)

Replying to a tweet from @meyerweb

When I was a kid, I thought the word “character” started with a “chuh” sound (’cause, y’know that is how it’s spelled).

I also pronounced the “b” in the “subtle” …which wasn’t.

Reading a lot just leads to embarrassment.

Replying to a tweet from @robweychert

Smooth!

(like butter)

Monday, August 3rd, 2020

Replying to a tweet from @harrybr

Yes.

I refuse on principle to use an ISP that does any traffic shaping.

Sunday, August 2nd, 2020

Replying to a tweet from @aerotwist

Seeing as Safari shows all the computed properties correctly, I’m guessing it was something that was introduced after the Webkit/Blink fork?

But weirdly, Firefox is showing the same behaviour as Chrome.

Replying to a tweet from @simevidas

But all off the border- properties are specified in long hand. Neither Firefox nor Chrome shows their computed values in dev tools.

Friday, July 31st, 2020

Replying to a tweet from @briansuda

I think that was dConstruct 2015.

Thursday, July 30th, 2020

Replying to a tweet from @SaraSoueidan

Eid Mubarak, Sara!

Wednesday, July 29th, 2020

Replying to a post on adactio.com

There’s also the ongoing pitch drop experiments:

https://en.wikipedia.org/wiki/Pitchdropexperiment

Replying to a tweet from @mrbarnabyb

Replying to a tweet from @torahwilcox

I just stumbled across this recording from a band I sometimes played with in Germany in the 90s doing a cover of Eisbär (I’m on bouzouki):

https://soundcloud.com/user-52736705/lunar-ride-eisbar-grauzone-cover-live-zmf-1999

Tuesday, July 28th, 2020

Replying to a tweet from @slightlylate

I concur that impact is more important than motive.

That’s why I was surprised that you ascribed motive in your blog post (a motive that contradicts Apple’s stated motive).

Replying to a tweet from @slightlylate

I’m trying to make of it what you will, but you won’t tell me. 🙂

They claim one motive (privacy). You claim another (not wishing to expand the web platform).

Which one is true and which one is false?

Replying to a tweet from @slightlylate

Nowhere in published policy documents do Apple or Mozilla say that they do not wish to expand the web platform.

You wrote a blog post stating that Apple and Mozilla do not wish to expand the web platform.

Replying to a tweet from @slightlylate

So you’re not accusing them of lying?

You claim that they do not wish to expand the web platform.

What they have written published in policy documents is that they have privacy concerns.

Is what they are saying true?

Replying to a tweet from @slightlylate

You should be a politician.

It’s a “yes” or “no” question.

Are they lying?