We're not talking about destroying the work of the people who were Told™. We're talking about destroying (the only copy of) the work of authors whose publishers (unwittingly, in many cases) used the wrong paper.https://twitter.com/brianmfitch/status/971770091665752064 …
-
-
Replying to @Rich_Harris
Authors may not be reachable. Oh, and this stupid fucking ventilation system ***doesn't even*** protect the books better. Some douchebag engineers just happen to think it looks cool. Authors will be forgiven for telling the engineers to fuck right off, and not damage the books.
1 reply 0 retweets 2 likes -
Replying to @AdamRackis
right! it's the height of entitlement and childishness. Which makes sense — I can't think of anything more immature and less constructive thanhttps://github.com/staltz/prevent-smoosh …
1 reply 0 retweets 10 likes -
Replying to @Rich_Harris @AdamRackis
It deeply concerns me that many dev advocates, who I would think would view themselves as shepherds of the open & compatible web, are advocating for this change and ripping on people who believe in preserving the books.
2 replies 0 retweets 2 likes -
Replying to @danbucholtz @Rich_Harris
Oh man my respect for the "developer advocate" position's been free falling in past years. They always seem to work for major corporations who profit from search engines, and their advice seems to ALWAYS be narrowly focused on maximizing their profits from said search engines.
2 replies 0 retweets 3 likes -
-
Replying to @danbucholtz @AdamRackis
yeah, perhaps we need to start having 'user advocates' who can push back
1 reply 0 retweets 4 likes -
Replying to @Rich_Harris @AdamRackis
I nominate you
My three go-to voices of reason are you, @tomdale, and@wycats. All of you are three of the finest, most diplomatic representatives of the ideals of the web.1 reply 0 retweets 1 like -
Replying to @danbucholtz @AdamRackis and
ha, thank you! (and back at you) — some distinguished company to find yourself in
1 reply 0 retweets 2 likes
Likewise!
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.