meanguy

Thank you for having "developer at artsy.net" in your bio as I would have found this continued questioning odd otherwise.

The gallery cancelled the order claiming both pieces are out of stock. A direct email to the gallery said the pieces were in stock. Typically gallery scam nonsense.

And literally while I was typing this, Amazon called me, totally unprompted.

So there's your verdict. Art galleries still suck, Amazon is still awesome, and it's still virtually impossible to make a significant purchase on the internet in 2013.

Nothing that's Amazon's fault. Amazon purchase history shows order complete, paid via Amazon credit card. Gallery currently refuses to ship either piece.

Verdict: yes, Amazon has successfully brought the magical experience of dealing with art dealers online. Not sure earning their cut is going to be much fun for them, but like Prime I'll happily use it as long as they offer the implausible service.

I've never had a bad experience with Amazon or any of their third parties across hundreds (!) of transactions. Long time collector, I purchased two pieces of art yesterday via the beta. Known gallery, brick-and-mortar. It's already a total debacle.

Late 90s press quoted Bezos as saying he wanted Amazon to sell everything except livestock and gasoline. Compared to art galleries, there's less bullshit and more ethics among the beef and oil companies.

But I pushed the button yesterday specifically knowing Amazon had my back. That says a lot.

Thank you for this. Onc clarification: the "Bieber YouTuBe upload" takedown scenario remained a DMCA issue. The non-commercial = non-felony language was actually made even more explicit under SOPA.

That was actually one of the key points of SOPA -- it extended DMCA-style service provider protection to payment providers and ad networks. As for the "streaming" provision, that was (inartfully) meant to penalize the day 0 crowd, especially for unreleased media. It was not intended to penalize people downloading, watching, or what people who read this site consider "streaming."

The language could and should have been cleaned up then; it all got lost amidst the SOPA screaming. Penalties for "streaming" are covered by the DMCA inside the US. It's how YouTube and UStream can exist. And I think we've seen precisely how many felonies and how much jail time resulted from cover songs and Justin Bieber lip dubs since that law passed 15 years ago.

But right now someone outside the USA can take another party's shady (or well-intentioned stream) of a pay per view, wrap ads from an ad network around it, and accept PayPal in order to see the "unrestricted stream" (scam). And there's no legal framework to deal with it.

That's obvious scammy theft regardless of where you stand on copyright. And all the "good guys" (ad networks, payment providers) remain liable whether they respond to takedown requests or not. SOPA let people take down the ads and PayPal links if they couldn't get the site down. It gave PayPal and Google the same kind of process and liability protection for payments and ads that YouTube already enjoys for video.

This needs to get fixed and techdirt, boingboing and others need to hire someone with minimal legal expertise (optimally Congressional litigation support experience) if they're going to keep hammering this for pageviews and anti-copyright cred.

For starters, it's ntoskrnl.exe. Dig out the original Windows NT stuff from the early 90s and you can infer Dave Cutler and team's original vision. The fact that Microsoft made hundreds of billions of dollars off it, layering all sorts of legacy chaos atop it, obscures the jewel at the core.

There's a third issue here, Tim: a perceived downward trend in the quality of the offerings of O'Reilly Media. My first O'Reilly book taught me sed/awk. Now you print magazines with "How to knit a robot" on the front cover.

I'm all for throwing stuff at the wall and seeing what sticks, but you seem spread awfully thin.

O'Reilly hired a pal to speak at RailsConf based on a popular Web 2.0 site he built. Unfortunately he didn't build it. Also the site was written in C#.

Sigh. Claude Shannon is rolling in his grave.

Click the Xamarin Dev Center link. You'll see Android and iOS but no Linux. They're focusing on mobile client tools.

They never got the full stack running on the server and they punted most of the Windows-specific client stuff from the start.

They landed on a super smart subset and seem to be kicking ass with it. A C# compiler with some odd omissions and cool enhancements + native bindings to iOS and Android equals a damn useful tool. If you're building .NET or even Java backends it's certainly a very sane way to hook into them from Android phones and tablets in the enterprise.

But it's not a cross-platform .NET environment by any stretch and certainly isn't on the path to becoming one.

After losing the support of Novell they refocused (see xamarin.com). They really did an amazing job with what they had, though.

That said, Mono benchmarked about 4x slower on my web apps.

For me, better to use two Windows instances rather than deal with the ongoing Mono compatibility drama across 8 Linux machines.

And here's where I flash pocket aces: I sat in a room with no windows and no computers, across from men with strong chins and short haircuts, reviewing Windows NT source code line by line. On friggin' paper.

Never heard of this guy. Never heard this story. It makes no sense, and I cannot even imagine what "automatically open the processor up to accept commands on start-up" means.

Mr. Curry eventually met with senior NSA/DoD officials, aired what he had -- while a major government lawsuit against Microsoft played out -- and nothing.

Also, Windows NT 4.0 very much did get C2 certification and had E3 (equivalent but not transferable) at the time. Which again doesn't help the story in hindsight.

I mean, seriously... read this nonsense (gcn.com). This stuff doesn't even qualify him for a Wikipedia entry. It's just the story of someone who cracked under the pressure of releasing a version of NT every year for four years straight. He certainly wasn't the only one.

-----

Curry also gave Schaeffer an updated document pulled from Microsoft’s Web site. Under a section of frequently asked questions on security, the site answered the question: “Is Windows NT a secure enough platform for enterprise applications?” by stating that the company recently enhanced the security of NT Server 4.0 through a service pack.

“Windows NT Server was designed from the ground up with a sound, integrated and extensible security model,” the Microsoft Web site said as late as last week. “It has been certified at the C2 level by the U.S. government and the E3 level by the U.K. government.”

Hodson said the passage claiming C2 certification cited by Curry refers to NT 3.5 with Service Pack 3, which is the only version of NT to meet the NSA’s C2 level requirements to date. But because the passage earlier mentions NT 4.0, Hodson said, the meaning could be misconstrued.

I hadn't heard this story before, but time isn't kind to this particular conspiracy. The moment of clarity: Mr. Curry wanted to sue Microsoft but "couldn't find a lawyer willing to take on the case" -- in 1998. EVERYBODY was suing Microsoft in 1998, including multiple governments. If you couldn't find someone to sue them that year, I'm afraid you don't have much credibility.

And this made my head hurt:

"All computer security systems begin with the Intel processor itself," Curry said. "I helped Intel develop their processor, so I know how they work and how vulnerable they can be if left exposed." ... "In fact," he added, "Microsoft NT 4.0 is the least secure of all the NT versions... Processors on Windows NT Version 4.0 are insecure because they have been designed to automatically open the processor up to accept commands on start-up."

Um, you know how Rails binds, right?

Also: MVC2 runs under NET 3.5 which doesn't even have the dynamic keyword. (I don't use dynamic in MVC3 or MVC4 either...)

The "stringly typed" (magic string) stuff was always avoidable. Regardless, see the [CallerMemberName] annotation and others which solves it back to INotifyPropertyChanged.

Now that the backlog of Microsoft tools have shipped, the scaffolding makes a bit more sense. The MVC team released multiple versions (open sourced!) instead of waiting for VS11. Which actually lines up with your core argument.

That's how similar products work. Some contain batteries to remember state. Some are full duplex and request state / update status. Some even work.

Another fun scenario: somebody crashes into a utility pole near your house, the power flickers, all your lights come on, the ceiling fans spin up 100%, and the ashes from your fireplace are distributed all over your house.

Or the lightning strike. Computer works, internet works, can't turn on any lights.

Visit a home automation forum for these and other tales of nerd homes gone bad.