👓 Monday, October 2, 2017 | Scripting News

Read Monday, October 2, 2017 (Scripting News)
Journalism people say Google is bad at journalism. I must be missing it but why don't they fix it and get Google out of their business. They don't feel they're responsible for anything, not even what they do. Of course Google sucks at journalism. What Google does the best is keep a huge network of computers running against unbelievable attacks from everywhere. The bad guys must always be trying to knock them down. Yet their servers are reliable and run fast. That's what they do best. Everything else is so-so.

Reply to Colin Walker on the idea of a required reading page

Replied to I've been thinking some more about the idea of a required reading page. by Colin Walker (Social Thoughts)
Could the things held here be placed on an About page? Possibly - it depends what they are. If they are links to your own posts then almost certainly. External links? Maybe, maybe not. So, why have a required page and what does it give the reader?
In classical studies in the Renaissance the number of texts which were popular and considered expected/required reading for a “learned” person were a relatively set number and generally completely consumable and completely known by those with an education. Thus a writer could make a reference to the old testament or to Cato and the vast majority of the audience would get that reference (without footnotes or explicit references) having read these same texts.

Sadly the depth and breadth of available literature has exploded since Gutenberg making it nearly impossible for anyone in a modern audience to have read and know what the author may presume them to know. As an example, in Shakespeare’s day many of his side references would be known by even the uneducated, while most modern students have to rely on Cliff’s Notes or annotated editions to understand those cultural references. The modern day equivalent is that most avid fans of the Simpsons television show are also generally well educated on popular film since the 1940s, otherwise they’re missing 90% of the jokes.

Things become much more stilted within the blogging arena, particularly when a writer may cover a dozen areas or more in which they may have significant experience, but which will likely be completely unknown to some of their regular readers, much less new readers who aren’t specialists in these fields themselves. This may turn away readers at worst, but will destroy the conversation at best. (Though I will admit it doesn’t seem deter some of the lookie-loos from taking at shot at interacting on the lowest levels at Terry Tao’s blog.)

In some sense, in knowing their audience, writers have to have some grasp of what they do or don’t know, otherwise it becomes difficult to communicate those progressively more expanding thoughts. Having hyperlinks certainly helps within a piece, much the way academics footnote journal articles, but it can be just as painful for the writer to constantly be referring back to the same handful of articles constantly. In this sense, having a recommended/required reading section may be useful, particularly if it were ubiquitous, but I suspect that the casual drive-by reader may not notice or care very much. However, for that rare <5% it may be just the primer they’re looking for to better understand you and what you’re writing about.

One of the most difficult things to do in a new job or when entering a new field is to become aware of the understood culture and history of the company or the field itself. One must learn the jargon and history to contextualize the overarching conversation. Jumping into Dave Winer’s blog without knowing his background and history is certainly a more painful thing than starting to read someone whose blog is less than a year old and could thus be consumed in a short time versus thousands upon thousands of posts since the literal start of blogging on the internet. It’s somewhat reminiscent of David Shanske’s problem of distilling down a bio for an h-card from the rest of his site and his resume. What do you want someone you’ve just met to know about you to more quickly put you into a broader context, especially when you want them to get to know you better?

I think we’re all in the same boat as David in figuring out the painful path of distilling all this down in a sensible and straightforward manner. I’m curious to see what you come up with and how it evolves over time.

👓 Required reading | Colin Devroe

Read Required reading by Colin Devroe (cdevroe.com)
The first time I linked to Colin Walker, which was only about 4 months ago, it was because he was fiddling with his blog, trying to come up with the right way to display his content for him and his audience. It is a topic that has fascinated me for 20 years and to see someone else thinking about it out loud is great.

🎧 The Weekly Index, extending the Bullet Journal (audio) | Colin Devroe

Listened to The Weekly Index, extending the Bullet Journal (audio) by Colin Devroe from cdevroe.com
Eliza and I have extended the Bullet Journal to include a Weekly Index – a two-page spread showing the entire week in one snapshot. It has been working for us for several months.

Recorded October 1, 2017.

👓 🎧 Mobile blogging goals (audio) | Colin Devroe

Listened to Mobile blogging goals (audio) by Colin Devroe from cdevroe.com

Recorded September 10, 2017

Starting with this audio bit I’m making a few changes.

I’m ditching the episode numbers. My audio bits are not a podcast, they aren’t really episodes, and keeping track of the numbers is just more work. I will, however, denote in the title that this is an audio post.

I’m also switching to the audio format that comes directly out of Voice Memos on the iPhone rather than doing the work of converting the file to MP3. If you have any issues listening to this audio file please let me know.

Enjoy the listen!

🎧 This Week in Google 423 I Can’t Hear You Over the Internet | TWiT.TV

Listened to This Week in Google 423 I Can't Hear You Over the Internet by Mathew Ingram, Ron Richards, Jason Howell from TWiT.tv

Google has a whole lotta leaks. Pixel 2 XL! Google Home Mini! Google Pixelbook! Coral Daydream VR headsets! Google might buy HTC's phone division any second now. Chrome will block autoplay videos in January. Google Tez makes payments with sound in India. Apparently everyone is letting users target ads using racist phrases. And we celebrate 20 years of Google.

  • Ron's pick: Sonarr app
  • Jason's Pick: Instal custom Oreo themes with Substratum and Andromeda

🎧 This Week in Google 424 The Echo Chamber | TWiT.TV

Listened to This Week in Google 424 The Echo Chamber by Stacey Higginbotham, Jason Howell, Matt Cutts from TWiT.tv
Google is 19 years old. Its present to us? Cool Google Doodles. Its present to itself? 2,000 HTC Engineers. Google and Levi's make a smart jacket. Google might make a better-sounding Home. Amazon is definitely making approximately 724 new Echo devices, including a smaller Echo, Zigbee-enabled Echo Plus, Echo Spot, Echo Buttons, and more. Just don't try playing YouTube videos on your Echo Show. Twitter tests 280 character limits.

https://youtu.be/rQlurQAIMq4

👓 Books from 1923 to 1941 Now Liberated! | Archive.org

Read Books from 1923 to 1941 Now Liberated! (Internet Archive Blogs)
The Internet Archive is now leveraging a little known, and perhaps never used, provision of US copyright law, Section 108h, which allows libraries to scan and make available materials published 1923 to 1941 if they are not being actively sold. Elizabeth Townsend Gard, a copyright scholar at Tulane University calls this “Library Public Domain.” She and her students helped bring the first scanned books of this era available online in a collection named for the author of the bill making this necessary: The Sonny Bono Memorial Collection. Thousands more books will be added in the near future as we automate. We hope this will encourage libraries that have been reticent to scan beyond 1923 to start mass scanning their books and other works, at least up to 1942.