Translate

Thursday, October 11, 2007

Fractal digital watermarking

I was thinking about my DMESE idea earlier today while on the bus, and it occurred to me that the concept would allow Original Equipment Manufactured media, which I'll call OEM media from here on out, to be designed to be hard to forge, as digital media equipment would encrypt copies they make only for OEM's that asked for it, so that a person could, for instance, copy their own videos that they made without the copies being forced to be encrypted.

That would put pressure on illegal copiers to counterfeit the OEM's to fool the equipment--or simply get it convinced that they were not copies of OEM media at all.

So digital watermarking would be necessary on data stored on the OEM disks so that, for instance, your DVD drive knew it was dealing with copyrighted material even if other signs said it was not.

And thinking about digital watermarking as the bus rode on got me to considering a fractal based watermarking scheme in the red color zone, where fractal images would be embedded in the red frequency range in such a way that they would be invisible to the human eye (so no you would not see this red thing on your screen).

I thought fractals because mathematically a fractal image could have an infinite number of components while practically there would be a finite but very large number of fractals embedded in the red zone which, for instance, a DVD drive could detect so it would know it had an OEM disk.

It would be very difficult though for a counterfeiter to remove ALL the fractals, and the presence of fractals in the red zone would indicate an OEM media.

So manufacturers would just make equipment that detected fractals in the red zone, which would tell the equipment it was dealing with an OEM, and then some other detail, like holograms on the disk itself would tell it that it had a valid copy, forcing counterfeiters to counterfeit everything or not fool the machine.

Then there could be a continual battle, like with currency, to keep counterfeiters from succeeding with making passable copies of OEM media, while it would be very hard for them to try to simply erase the digital watermark, as every single OEM could have a different fractal watermarking in the red zone, and equipment would assume any fractal in the red zone meant it had an OEM.

Thoughts I had while musing on the subject on the bus this morning.


James Harris

Sunday, September 30, 2007

People, process and products

Source: NY Times

Ping
The Unsung Heroes Who Move Products Forward

By G. PASCAL ZACHARY
Published: September 30, 2007
The success of Apple, Intel, Google and scores of other technology companies has as much or more to do with their process innovations as the products.


Goes to the old debate about how entertainment figures draw so much attention while modern innovators rarely do as well, and maybe part of it is just visibility.

Like the opinion article linked to above mentions, these are people in the background building products which are what people see.

But it is so much bigger than computers, as who are the innovators figuring out the latest cars or airplanes, or making televisions flat or I wonder, how many people around the world know the key inventors of the television set?

Go way back and who figured out how to make glass? Or my own personal favorite when considering this question, how many people know what person or persons developed the spoon?


James Harris

Friday, August 10, 2007

Class Viewer for C?

I have been thinking for a while about what to do next with the Class Viewer project and I keep thinking that an enterprise version is a logical step and it occurred to me that other languages would be a nice step as well, like for C++.

An enterprise Class Viewer could be a gateway to a software development company's javadocs, offering a nice middle level app between them and users as well as their own developers.

And other languages would bring the ease and functionality of Class Viewer to other domains.

But there has to be a need and a market where I'm not going to do the work without knowing if either exists so I put the idea thinking that a natural funding source for venture capital would be Google as they put their apps out there for free already.

But I'm not going to contact them so I just throw the idea on my blog. Maybe something will happen.


James Harris

Saturday, May 26, 2007

My idea for managed copy

With "managed copy" in the news lately it seems a good time to mention again my idea for allowing end users to make personal copies:

Digital Media: Copy protection

REALLY simple idea which involves having end user's own machine encrypt copies to itself, so that it can read its backup copies made of DVD's but other people cannot--without a key that can be passed by flash drive--and also it burns onto its copies identifying information.

My idea includes allowing users to use a flash drive to pass a key to their other systems or to friends for maximum flexibility, with the knowledge that the copy they pass tells who they are, and also cannot itself be copied.

To me that idea solves all the problems involved with protecting digital media from casual copying, though criminals may of course go that extra mile in trying to make copies for money, there would be an end to the very casual copying where usually law abiding citizens consider it to be like speeding on the highways and would do it as a matter of habit.

Today it is like everybody does it, there is no onus on it, and it is very easy.

With this idea, a friend could get angry with you if you pressed for a copy, since it would contain information about them and possibly leave them open for prosecution, so what kind of friend would you be in pressing for one?

Knowing that yeah, you can give your friend a copy but if that ever gets to the FBI, they have your digital signature all over the thing, which your friend cannot use without a flash drive for them to get the key anyway, and they cannot copy it again themselves, would take most casual copiers out of the equation, leaving only the die-hards.

I am an idea person so I know how hard it is to get attention for even great ideas, so rather than go through the pain and misery of trying to copyright that idea, and market it, I have given it away open source.

It is a free idea. It is free!!!

Does not mean anyone will use it though as hey, I know, no matter what most people think, mostly we have a dumb world. I know because I have had lots of ideas.

Easy solutions are routinely ignored if people do not like the source.

Brilliance is mostly a burden and a source of frustration today, as hey, people really do not like you for coming up with simple solutions, as it makes them feel stupid.


James Harris

Saturday, April 21, 2007

Javadocs, deep linking and quick reference

My Class Viewer project gives two key things with javadocs:

1. A handy way to keep up with all of them using an xml file, which I call packagedirectory.xml, where you can put in public javadocs as well as your own, and then, you can just forget about worrying where they are!

(Note the xml file can be edited easily in a text editor.)

2. Deep linking into javadocs to the method, where if you don't know the exact method you can do searches using a single char or as much of a string as you want with any piece you might think is in the method as I made the search as flexible as I could.

Understanding deep linking is just about seeing it done once, and you can see an example in my previous post, but the gist of it is that you get taken to your method in the javadocs, so no more scrolling down searching!

But these features have been available from my project for over three years now.

Ok, yeah, there was a long period with a minor bug where when a method had multiple arguments the URL would have an extra space in it, so you'd get taken to the top of the javadocs page---which is a gracious failure---but I finally fixed the code.

The problem still remains though with Microsoft's Internet Explorer, last time I checked, which is yet another good reason to get Firefox!

Oh and did I mention that once you put your javadocs location in packagedirectory.xml you need never worry about where your javadocs are again? Yes I did, but that is such a huge feature, and there are other solutions out there like javadoc online but there you do not get deep linking and what about your own projects and your own javadocs?

Why not let the computer keep up with all that detail, which you can do with Class Viewer?


James Harris