Four short links: 8 August 2014

Four short links: 8 August 2014

Synchronization, Security Pi, YouTube Stardom, and Javascript Logging

  1. Everything You Wanted to Know About Synchronization But Were Too Afraid to Ask (PDF) — This paper presents the most exhaustive study of synchronization to date. We span multiple layers, from hardware cache-coherence protocols up to high-level concurrent software. We do so on different types of architectures, from single-socket — uniform and non- uniform — to multi-socket — directory and broadcast-based many-cores. We draw a set of observations that, roughly speaking, imply that scalability of synchronization is mainly a property of the hardware.
  2. Raspberry Pi as Low-Cost Security Camera (Instructables) — $120 HD motion-sensing web-viewable security camera.
  3. Inside YouTube’s Fame Factory (FastCompany) — great article about the tipping point where peer-to-peer fame becomes stage-managed corporate fame, as Vidcon grows. See also Variety: If YouTube stars are swallowed by Hollywood, they are in danger of becoming less authentic versions of themselves, and teenagers will be able to pick up on that,” Sehdev says. “That could take away the one thing that makes YouTube stars so appealing.”
  4. Sherlog.js (Github) — Javascript error and event tracker application. Honestly, I have no idea if this is any good but the name is golden. I’m such a sucker.
Four short links: 21 May 2013

Four short links: 21 May 2013

Videogame Hyperinflation, Thumbdrive Computing, Distributed Consensus, and Organism Simulation

  1. Hyperinflation in Diablo 3 — interesting discussion about how video games regulate currency availability, and how Diablo 3 appears to have messed up. several weeks after the game’s debut a source claimed that there were at least 1,000 bots active 24/7 in the Diablo 3 game world, allegedly “harvesting” (producing) 4 million virtual gold per hour. Most of the gold generated by the ruthlessly productive, rapidly adapting bots found its way to third party vendors in a black market which undercut the prices in the sanctioned, in-game auction houses.
  2. Dell Project Ophelia (PC World) — $100 USB-stick-sized Android computer.
  3. Call Me Maybe (Kyle Kingsbury) — a series on network partitions. We’re going to learn about distributed consensus, discuss the CAP theorem’s implications, and demonstrate how different databases behave under partition.
  4. OpenWorm (The Atlantic) — simulating the c. elegans nematode worm in software. OpenWorm isn’t like these other initiatives; it’s a scrappy, open-source project that began with a tweet and that’s coordinated on Google Hangouts by scientists spread from San Diego to Russia. If it succeeds, it will have created a first in executable biology: a simulated animal using the principles of life to exist on a computer.
Comments: 2
Four Short Links: 7 May 2013

Four Short Links: 7 May 2013

Raspberry Pi MITM, Industrial Robot SDK, Cheap Mill, and Open Source State Replication in Go

  1. Raspberry Pi Wireless Attack ToolkitA collection of pre-configured or automatically-configured tools that automate and ease the process of creating robust Man-in-the-middle attacks. The toolkit allows your to easily select between several attack modes and is specifically designed to be easily extendable with custom payloads, tools, and attacks. The cornerstone of this project is the ability to inject Browser Exploitation Framework Hooks into a web browser without any warnings, alarms, or alerts to the user. We accomplish this objective mainly through wireless attacks, but also have a limpet mine mode with ettercap and a few other tricks.
  2. Industrial Robot with SDK For Researchers (IEEE Spectrum) — $22,000 industrial robot with 7 degrees-of-freedom arms, integrated cameras, sonar, and torque sensors on every joint. [...] The Baxter research version is still running a core software system that is proprietary, not open. But on top of that the company built the SDK layer, based on ROS (Robot Operation System), and this layer is open source. In addition, there are also some libraries of low level tasks (such as joint control and positioning) that Rethink made open.
  3. OtherMill (Kickstarter) — An easy to use, affordable, computer controlled mill. Take all your DIY projects further with custom circuits and precision machining. (via Mike Loukides)
  4. go-raft (GitHub) — open source implementation of the Raft distributed consensus protocol, in Go. (via Ian Davis)
Comment: 1
Four short links: 24 April 2013

Four short links: 24 April 2013

Solar Numbers, Process Managers, BitTorrent Sync, and Motherfrickin' Snakes in Your Motherfrickin' Browser

  1. Solar Energy: This is What a Disruptive Technology Looks Like (Brian McConnell) — In 1977, solar cells cost upwards of $70 per Watt of capacity. In 2013, that cost has dropped to $0.74 per Watt, a 100:1 improvement (source: The Economist). On average, solar power improves 14% per year in terms of energy production per dollar invested.
  2. Process Managers — overview of the tools that keep your software running.
  3. Bittorrent Sync — Dropbox-like features, BitTorrent under the hood.
  4. Brython — Python interpreter written in Javascript, suitable for embedding in webpages. (via Nelson Minar)
Four short links: 27 February 2013

Four short links: 27 February 2013

Open Source Cancer Informatics, NPR Framework, Littery Junk, BitTorrent Sync

  1. Open Source Cancer Informatics Software (NCIP) — we have tackled the main recommendation that came out of our June meeting with open-source thought leaders: Keep it simple. Make barriers to entry as low as possible, and reuse available resources. Specifically, we have adopted a software license that is approved by the Open Source Initiative (OSI) and have begun to migrate the code developed under the cancer Biomedical Informatics Grid® (caBIG®) Program to a public repository. Our goal in taking these steps is to remove as many barriers as possible to community participation in the continuing development of these assets. Awesome! (via John Scott)
  2. NPR’s Framework for Easy Apps — their three architectural maxims: Servers are for chumps; If it doesn’t work on mobile, it doesn’t work; and Build for use. Refactor for reuse..
  3. Random Junk in People’s Labs (Reddit) — reminded me of the contents of my “tmp” and “Downloads” and “Documents” directories: unstructured historical crap with no expiration and no current use. (Caution: swearing in the title of the Reddit post) (via Mihalyi Csikszentmihalyi)
  4. Sync — BitTorrent’s alpha-level tech to “automatically sync files between computers via secure, distributed technology.” Not only is it “slick for alpha” (as one friend described), it’s bloody useful: I know at least one multimillion-dollar project built on their own homegrown implementation of this same idea. (via Jason Ryan)
Comment: 1
Four short links: 21 December 2010

Four short links: 21 December 2010

Big Companyitis, Spyware Apps, Maturing Cloud, and Mobile Sync

  1. Cash Cow Disease — quite harsh on Google and Microsoft for “ingesting not investing” in promising startups, then disconnecting them from market signals. Like pixie dust, potential future advertising revenues can be sprinkled on any revenue-negative scheme to make it look brilliant. (via Dan Martell)
  2. Your Apps Are Watching You (Wall Street Journal) — the iPhone apps transmitted more data than the apps on phones using Google Inc.’s Android operating system [...] Both the Android and iPhone versions of Pandora, a popular music app, sent age, gender, location and phone identifiers to various ad networks. iPhone and Android versions of a game called Paper Toss—players try to throw paper wads into a trash can—each sent the phone’s ID number to at least five ad companies. Grindr, an iPhone app for meeting gay men, sent gender, location and phone ID to three ad companies. [...] Among all apps tested, the most widely shared detail was the unique ID number assigned to every phone. It is effectively a “supercookie,” [...] on iPhones, this number is the “UDID,” or Unique Device Identifier. Android IDs go by other names. These IDs are set by phone makers, carriers or makers of the operating system, and typically can’t be blocked or deleted. “The great thing about mobile is you can’t clear a UDID like you can a cookie,” says Meghan O’Holleran of Traffic Marketplace, an Internet ad network that is expanding into mobile apps. “That’s how we track everything.”
  3. On Undo’s Undue Importance (Paul Kedrosky) — The mainstream has money and risks, and so it cares immensely. It wants products and services where big failures aren’t catastrophic, and where small failures, the sorts of thing that “undo” fixes, can be rolled back. Undo matters, in other words, because its appearance almost always signals that a market has gone from fringe to mainstream, with profits set to follow. (via Tim O’Reilly on Twitter)
  4. libimobiledevice — open source library that talks the protocols to support iPhone®, iPod Touch®, iPad® and Apple TV® devices without jailbreaking or proprietary libraries.
Comments Off
Four short links: 21 January 2010 Four short links: 21 January 2010

Four short links: 21 January 2010

Wireless Hacks, Real Time Web, 3D Christmas, Mac Sync

  1. DD-WRT — replacement firmware for cheap wireless router boxes that add new functionality like wireless bridging and quality-of-service controls (so Skype doesn’t break up while you’re web-browsing). Not a new thing, but worth remembering that it exists.
  2. Brain Dump of Real Time Web and WebSocket — long primer on the different technology for real-time web apps. Conclusion is that there’s no silver bullet yet, so more development work is needed. (via TomC on Delicious)
  3. Data Decs — 3d-printing Christmas decorations based on social network data. My favourite is the blackletter 404. (via foe on Delicious)
  4. ZSync — open source syncing application that makes it easy for app writers to connect desktop apps and iPhone apps. (via Dave Wiskus)
Comment: 1
Four short links: 15 September 2009 Four short links: 15 September 2009

Four short links: 15 September 2009

Delegation, Journalism, Dating Numbers, Learn Git

  1. Why You Shouldn’t Do It All Yourself — this resonated with where I am in a few projects. One of the hardest things to learn in management is how not to do it all yourself. People often call this a problem with “delegation”. But the problem isn’t with telling others what to do. The problem is learning how not to do it all yourself. (via br3nda)
  2. The Story Behind The Story (The Atlantic) — I would describe their approach as post-journalistic. It sees democracy, by definition, as perpetual political battle. The blogger’s role is to help his side. Distortions and inaccuracies, lapses of judgment, the absence of context, all of these things matter only a little, because they are committed by both sides, and tend to come out a wash. Nobody is actually right about anything, no matter how certain they pretend to be. The truth is something that emerges from the cauldron of debate. No, not the truth: victory, because winning is way more important than being right. Power is the highest achievement. There is nothing new about this. But we never used to mistake it for journalism. Today it is rapidly replacing journalism, leading us toward a world where all information is spun, and where all “news” is unapologetically propaganda.
  3. OkTrends — analytics from a dating site show what works in email. We analyzed over 500,000 first contacts on our dating site, OkCupid. Our program looked at keywords and phrases, how they affected reply rates, and what trends were statistically significant. The result: a set of rules for what you should and shouldn’t say when introducing yourself online. (read their note on how they protected privacy before freaking out)
  4. Learn GitHubHere we have tried to compile the best online learning Git resource available. There are a number of articles and screencasts, written and arranged to try to make learning Git as quick and easy as possible.
Comment: 1
Four Short Links: 28 August 2009

Four Short Links: 28 August 2009

The Future, Python Metrics, Distributed Version Control, and Stylish R

  1. What The Future’s All About (Webstock Words) — Bruce Sterling on the future. We’re not going to get a future Cloud World as somehow opposed to a future Augmented Reality World. It can’t happen. The ideas can be clearly distinguished, but ideas about technology, labels for technology, predictions and suppositions about technology, they don’t map onto actual real-world technology. Human culture doesn’t work like a logical argument.
  2. PyMetrics — code analysis software that produces metrics for your code. (via the excellent 10 Ways To Let People Know You’re a Bad Python Programmer by Noah Gift)
  3. Prophet and SD 0.7 Are Now AvailableProphet is a lightweight schemaless database designed for peer to peer replication and disconnected operation. Prophet keeps a full copy of your data and (history) on your laptop, desktop or server. Prophet syncs when you want it to, so you can use Prophet-backed applications whether or not you have network. SD (Simple Defects) is a peer-to-peer issue tracking system built on top of Prophet. In addition to being a full-fledged distributed bug tracker, SD can also bidirectionally sync with your RT, Hiveminder, Trac, GitHub or Google Code issue tracker.
  4. Google’s R Style GuideR is a high-level programming language used primarily for statistical computing and graphics. The goal of the R Programming Style Guide is to make our R code easier to read, share, and verify. The rules below were designed in collaboration with the entire R user community at Google. (via Bo Cowgill’s blog)
Comments: 3
Four Short Links: 24 August 2009

Four Short Links: 24 August 2009

Distributed Version Control Systems, Ideas Tracking, OO Survey Results, New Barcodes

  1. Making Sense of Revision Control Systems (ACM Queue) — good introduction to the subject from Bryan O’Sullivan, author of Mercurial: The Definitive Guide (aka Distributed Revision Control with Mercurial) that covers Subversion, Mercurial, and git. Under the distributed view of revision control, every commit is potentially a branch of its own. If Bob and Alice start from the exact same view of history, and each one makes a commit, they have already created a tiny anonymous fork in the history of the project. Neither will know about this until one pulls the other’s changes in, at which point they will have to merge with them. These tiny branches and merges are so frequent with Mercurial and Git that users of these tools look at branching and merging in a very different way from Subversion users. The parallel and branchy nature of a project’s development is clearly visible in its history, making it obvious who made which changes when, and exactly which other changes theirs were based upon.
  2. Ideas Are AwesomeIdeas Are Awesome is a web culture aggregator tracking emerging marketing, design, and technology memes. We are currently tracking: simplify, empower, give, inspire, connect, adapt. (via cheeky_geeky on Twitter)
  3. OO Concepts Survey ResultThere were 3785 people who completed the survey. These charts show the proportion who gave the different possible responses for each question. If you’re an OO programmer, use this to determine how aberrant your practices are (hint: most people are neither zealous nor consistent).
  4. Bokodea new camera based interaction solution where an ordinary camera can detect small optical tags from a relatively large distance. Current optical tags, such as barcodes, must be read within a short range and the codes occupy valuable physical space on products. We present a new low-cost optical design so that the tags can be shrunk to 3mm visible diameter, and unmodified ordinary cameras several meters away can be set up to decode the identity plus the relative distance and angle. The design exploits the bokeh effect of ordinary cameras lenses, which maps rays exiting from an out of focus scene point into a disk like blur on the camera sensor. (via waxy)
Comment: 1