After years of programming I have to say the most influential book for me by far is "The Design of Everyday Things" by Donald Norman. In the end, you're designing a tool for someone... whether it's a end user or an api. The days of control-alt-delete are over... or at least they should be. Thinking about the user interface (whether it's mechanical, gui, api,or sdk) should not be something the programmer slaps on after the functionality is completed.
Comex basically just diff'd what was fixed in the latest OSX patches against what was in the last iOS patch. Then read up on this patch that hasn't made it to iOS yet. FYI, this won't work if you have 4.1 beta or higher installed supposedly (cuz Apple already had the patch bundled up ready to go when they release the next build)...
The real credit goes to Charlie Miller who found this problem in the first place.
The funny thing I found was that Charlie Miller was given credit by Apple in the patch note.. "Credit to Charlie Miller working with TippingPoint's Zero Day Initiative for reporting this issue." but then Charlie tweets about p[articular exploit.. "Very beautiful work,"... "Scary how it totally defeats Apple's security architecture."
It might be as simple as your message isn't getting to the right person.
You said you have emailed and complained. Does that mean you clicked on the webmaster link and wrote a couple of sentences? Emailed/complained to the author? That's not going to go anywhere...
I suggest you write a letter with company letterhead (preferably from your lawyer's firm) that asks them to stop. Mail it to their head lawyer if you can find him.. or to the "Legal Department" if you can't. Send it by certified mail, courier, or some other method where someone over there has to sign for it. That way you have a trail.. lawyers will know you're serious then.. otherwise you're just some crack pot. And when you're serious... they're going to have to be serious. No lawyer is going to throw something like that in the garbage... a webmaster or even the author... on the other hand with an email... delete.
Shrimp with fluoxetine (Prozac) go towards the light and get caught easier by fisherman?
Prozac makes me feel good... so.. eating shrimp with Prozac is like eating... chocolate.. makes me feel good...
Yumm... bumper crop of chocolate shrimp...
I bet the sea birds eating the shrimp have high levels of Prozac too... humm.. chocolate seagulls....
It's an Omnivision sensor using a TSMC process.
OVT is the only company doing production back side illumination as far as I know.
BSI isn't the end all be all of sensor tech... really not that big a development for anything besides cellphones either. Loss from wiring drops very quickly percentage wise as the pixel gets bigger so decent sized pixels (astronomy, security, SLR, etc etc) aren't that affected. It's when the pixels get stupidly small that you have to worry about stuff like this. The cost and problems associated with BSI definitely make it not worth while for bigger pixels.
Other companies have their own solutions as well... Aptina for instance uses a microlens light pipe technology that collects and funnels the light between the wiring to solve the same problem. It's kind of like using a magnifying glass to focus all the light into a fiber optic cable.. running the cable through all the wiring and then dumping all the light onto the actual sensor diode.
Actually, the DNS-321 is slightly cheaper. It doesn't have a bittorrent client built in so if you need that then you should get the 323 for the client and then expand with 321s. I found a comparison between the 2 online..
http://www.smallnetbuilder.com/content/view/30520/79/
There's no DCHP on the 321 either but chances are you have a wireless router or a real router handling that stuff. No support for printers either but again.. you need that just get 1 323 and then fill out your closet with 321s.
Turns out the 321 is faster if you go over 64 MB.. which you'll probably be doing a lot if you're doing movies. I have 2 321s with 2TB drives for a total of 8TB of movies. The solution is damned cheap in my opinion.. costing only about $50 on top of the drives (the 321 is less then $100 if you hit the rebates (tigerdirect.com) for 2 drives).
The only problem I've had is a screwy permission problem that creeps up every once in a while... I can't copy onto or off of the drive because of permission problems for some files. I think it has something to do with how the DNS-321 handles the file metadata from OSX. Seems to work fine with PCs though I haven't pushed it like I have with OSX.
Slashdot Mirror
After years of programming I have to say the most influential book for me by far is "The Design of Everyday Things" by Donald Norman. In the end, you're designing a tool for someone... whether it's a end user or an api. The days of control-alt-delete are over... or at least they should be. Thinking about the user interface (whether it's mechanical, gui, api,or sdk) should not be something the programmer slaps on after the functionality is completed.
http://support.apple.com/kb/HT4131
Comex basically just diff'd what was fixed in the latest OSX patches against what was in the last iOS patch. Then read up on this patch that hasn't made it to iOS yet. FYI, this won't work if you have 4.1 beta or higher installed supposedly (cuz Apple already had the patch bundled up ready to go when they release the next build)...
The real credit goes to Charlie Miller who found this problem in the first place.
http://www.appleinsider.com/articles/10/08/03/browser_based_ios_jailbreak_utilizes_scary_pdf_security_hole.html
The funny thing I found was that Charlie Miller was given credit by Apple in the patch note.. "Credit to Charlie Miller working with TippingPoint's Zero Day Initiative for reporting this issue." but then Charlie tweets about p[articular exploit.. "Very beautiful work,"... "Scary how it totally defeats Apple's security architecture."
It might be as simple as your message isn't getting to the right person. You said you have emailed and complained. Does that mean you clicked on the webmaster link and wrote a couple of sentences? Emailed/complained to the author? That's not going to go anywhere... I suggest you write a letter with company letterhead (preferably from your lawyer's firm) that asks them to stop. Mail it to their head lawyer if you can find him.. or to the "Legal Department" if you can't. Send it by certified mail, courier, or some other method where someone over there has to sign for it. That way you have a trail.. lawyers will know you're serious then.. otherwise you're just some crack pot. And when you're serious... they're going to have to be serious. No lawyer is going to throw something like that in the garbage... a webmaster or even the author... on the other hand with an email... delete.
Shrimp with fluoxetine (Prozac) go towards the light and get caught easier by fisherman? Prozac makes me feel good... so.. eating shrimp with Prozac is like eating... chocolate.. makes me feel good... Yumm... bumper crop of chocolate shrimp... I bet the sea birds eating the shrimp have high levels of Prozac too... humm.. chocolate seagulls....
Cius Fail Though seriously.. the big ass speakers would be nice for a teleconference application.
It's an Omnivision sensor using a TSMC process. OVT is the only company doing production back side illumination as far as I know. BSI isn't the end all be all of sensor tech... really not that big a development for anything besides cellphones either. Loss from wiring drops very quickly percentage wise as the pixel gets bigger so decent sized pixels (astronomy, security, SLR, etc etc) aren't that affected. It's when the pixels get stupidly small that you have to worry about stuff like this. The cost and problems associated with BSI definitely make it not worth while for bigger pixels. Other companies have their own solutions as well... Aptina for instance uses a microlens light pipe technology that collects and funnels the light between the wiring to solve the same problem. It's kind of like using a magnifying glass to focus all the light into a fiber optic cable .. running the cable through all the wiring and then dumping all the light onto the actual sensor diode.
Actually, the DNS-321 is slightly cheaper. It doesn't have a bittorrent client built in so if you need that then you should get the 323 for the client and then expand with 321s. I found a comparison between the 2 online.. http://www.smallnetbuilder.com/content/view/30520/79/ There's no DCHP on the 321 either but chances are you have a wireless router or a real router handling that stuff. No support for printers either but again.. you need that just get 1 323 and then fill out your closet with 321s. Turns out the 321 is faster if you go over 64 MB.. which you'll probably be doing a lot if you're doing movies. I have 2 321s with 2TB drives for a total of 8TB of movies. The solution is damned cheap in my opinion.. costing only about $50 on top of the drives (the 321 is less then $100 if you hit the rebates (tigerdirect.com) for 2 drives). The only problem I've had is a screwy permission problem that creeps up every once in a while... I can't copy onto or off of the drive because of permission problems for some files. I think it has something to do with how the DNS-321 handles the file metadata from OSX. Seems to work fine with PCs though I haven't pushed it like I have with OSX.
I love you ... I just don't like the things you do... or what you say...
Translation:
I love f*cking you...
Lies!! All lies!! I have the new ipone right here... http://www.youtube.com/watch?v=yNy79_3PXCE