Andy Baio digs into the reuse of certain content by AllThingsD for their Voices section:

Ultimately, if authors are happy, there’s no problem. But it seems like there’s a divide between two types of writers online: unaffiliated independent bloggers running their own sites and bloggers employed by larger online magazines.

Also, be sure to read the related response from Anil Dash about how the Associated Press plans to handle a similar reuse of content:

If the Associated Press made its argument on the basis of credibility and reputation, transparency and accountability, as the web-native publishers have, it would be far easier to defend their desire to share in the business model developed by the aggregators.

Fast text replacement with canvas and VML – no Flash or images required.

Oooh. Must experiment with this soon. (via @hicksdesign)

I’m linking to this because I’ve been stung by the problem too. The issue is with new MacBooks and MacBook Pros with the button-less trackpad. These trackpads have no dead zone like the old trackpads did. So until I get accustomed to using them, I often end up resting my right thumb on the lower portion of the trackpad where the physical button used to be. Because of this, once I go to move the cursor with the trackpad, I inadvertently perform a two-finger gesture, which Apple now recognizes on these new trackpads. Photoshop interprets these as either zoom or rotate actions, which is rarely what I want to happen. This plugin disables those actions in Photoshop, until Adobe engineers figure a graceful way to interpret (or otherwise ignore) two-finger gestures.

“…it’s finally time to take IE6 behind the shed and shoot it.”

I love this in-depth look at implementing grids for liquid layouts. Ethan goes into detail just how it all fits together, and the magic formula needed to make it all work. Now if we could just have the ability to easily scale images inside a liquid layout (without resorting to clipping background images), we’d be golden (pun intended).

Eric Meyer elaborates on why we need a better layout mechanism for web content (whether it be via CSS or not). We know we shouldn’t use tables for layout. Floats are a hack, positioning is flawed, and display:table-cell is no better than using a table itself. But Eric explains here why table behavior works moderately well for layout:

… this is why the old “only use tables for layout” argument keeps coming up over and over: strip away the overheated rhetoric and obvious link-baiting, and you find the core of a real need. Because as powerful as CSS can be, table cells do certain things very easily that CSS makes very, very hard. Cells stretch vertically, keeping equal heights as a matter of their intrinsic nature. They stay out of each others’ way, while still being allowed to sit next to each other and use any sizing dimensions. They tie their layout to their parent elements, and vice versa.