- Deep Learning Bibliography — an annotated bibliography of recent publications (2014-) related to Deep Learning.
- Inside the Go Playground — on safely offering a REPL over the web to strangers.
- Wolfram Tweet-a-Program — clever marketing trick, and reminiscent of Perl Golf-style “how much can you fit into how little” contests.
- Memory Management Reference — almost all you ever wanted to know about memory management.
ENTRIES TAGGED "Twitter"
Everyone wants an alternative to email, but do we really need one?
Editor’s note: this post originally appeared on Medium; it is republished here with permission.
Conventional workplace wisdom declares email a daily scourge. We receive too much of it. We spend too much time replying to it. We concoct elaborate strategies to cope with it and avoid incurring a debt that downward-spirals to email bankruptcy.
We bow down at the altar of Inbox Zero, the methodology that dictates we take prompt, concrete action to dispatch with every single message we receive. Reply to it. Or file it. Or delete it. We turn the drudgery of processing the flood of correspondence into a game. Inbox Zero, FTW! Achievement unlocked … till the next time we hit refresh. Because emails are like gray hairs: for every one we send packing, five more will soon arrive in its place. Any client-side strategy we take to conquer our inboxes is thus limited by the fact that it’s palliative, not ameliorative. Perpetuating Inbox Zero means living in a constant state of vigilance, aggressively and swiftly responding to every incoming message. It means becoming an email answering machine!
One speaker at Fluent 2013 whose talk was particularly well received was Todd Kloots of Twitter who spoke about HTML5’s pushState API and demonstrated how it was used in Twitter’s Web-based interface.
Some key parts of Todd’s talk include:
- The opportunity Twitter saw in pushState [at 01:45]
- What you had to do with dynamic URLs before pushState [at 02:46]
- A summary of the pushState API [at 06:10]
- Gotchas and browser support [at 07:58]
- How pushState sped up navigation on Twitter.com without re-architecting [at 12:15]
- What Twitter had to do server-side to make progressive enhancement work [at 19:11]
- Final thoughts [at 31:37]
- Q&A [at 32:15]
iOS Pentesting, Twitter's Infrastructure, JS Data Sync, and Chromium as C Runtime
- idb (Github) — a tool to simplify some common tasks for iOS pentesting and research: screenshots, logs, plists/databases/caches, app binary decryption/download, etc. (via ShmooCon)
- Twitter Infrastructure — an interview with Raffi Krikorian, VP of Platform Engineering. Details on SOA, deployment schedule, rollouts, and culture. (via Nelson Minar)
- Chromium is the New C Runtime — using Chrome’s open source core as the standard stack of networking, crash report, testing, logging, strings, encryption, concurrency, etc. libraries for C programming.
Twitter isn't quite beyond jumping the shark, but it has taken a big step backward.
While I’ve been skeptical of Twitter’s direction ever since they decided they no longer cared about the developer ecosystem they created, I have to admit that I was impressed by the speed at which they rolled back an unfortunate change to their “blocking” feature. Yesterday afternoon, Twitter announced that when you block a user, that user would not be unsubscribed to your tweets. And sometime last night, they reversed that change.
I admit, I was surprised by the immediate outraged response to the change, which was immediately visible on my Twitter feed. I don’t block many people on Twitter — mostly spammers, and I don’t think spammers are interested in reading my tweets, anyway. So, my first reaction was that it wasn’t a big deal. But as I read the comments, I realized that it was a big deal: people complaining of online harassment, trolls driving away their followers, and more.
So yes, this was a big deal. And I’m very glad that Twitter has set things right. In the past years, Twitter has seemed to me to be jumping the shark in small steps, rather than a single big leap. If you think about it, this is how it always happens. You don’t suddenly wake up and find you’ve become the evil empire; it’s a death of a thousand cuts. Read more…
Finding ways to make media interact with the physical world
Reporters, editors and designers are looking for new ways to interact with readers and with the physical world–drawing data in through sensors and expressing it through new immersive formats.
In this episode of the Radar podcast, recorded at News Foo Camp in Phoenix on November 10, Jenn and I talk with three people who are working on new modes of interaction:
- Mark Trammell, of Sonos, previously of Obama HQ and Twitter
- Rebekah Monson, of the University of Miami
- Robert Hernandez, of the University of Southern California’s Annenberg School
Along the way:
- SensorSub, a project Rebekah is working on that uses data-gathering submarines to measure water quality
- Robert’s students are working on augmented-reality projects at the Los Angeles Central Library–building story-time experiences for children and interpreting the library’s famous murals
- How a lengthier sign-up process brought more people onto Twitter
- Mark’s efforts to understand user interaction on physical hardware
- Wise Kaplan and Cranky Kaplan, the fictional Twitter alter-egos of former New York Observer editor Peter Kaplan, who passed away shortly after we recorded this episode. In the same vein: Mayor Emanuel, Twitter satire from Dan Sinker that was subsequently anthologized.
- Snow Fall
For more on the intersection of software and the physical world, be sure to check out Solid, O’Reilly’s new conference program about the collision of real and virtual.