Skip to main content

Patent Peer Processing

Finally, some good news about technology patents. We have known of the problems with the system for a long time, and now that things are starting to turn around, the burden is on the people to take the power being given them and make a difference and show that this works.

I am calling on everyone who has the slightest time and knowledge to contribute to this new system, because the results affect you just as much as the rest of us. That includes all non-US citizens, because we do live in an global village, and anything anywhere can affect everyone everywhere.

We need to make sure the new system is setup in a way that we can consume and digest the information in the same way we filter, rank, pass, and project information around the blogosphere today. That means ensuring that feeds are setup from the PTO, establishing aggregators, tagging conventions, and working toward trusted patent review bloggers. We can use the same tools we have been employeeing to digest insane am0unts of our own information and apply all of that to locating the best, worst, and silliest of claims by the patenters.

It might be great that any individual can read, review, research, and respond to the patents for the PTO to utilize in their decisions, but there is only so much an individual can do, even when there are many such individuals. When we turn all of us individuals into a group, a community, a patent chomping machine, and we can do something that is actually bettering for the entire world.

Comments

Anonymous said…
So, because the USPTO isn't competent enough to do this itself, or maybe they don't get enough funding to do it properly, they now try to force everybody else to do their work for free?

If they want experts they should pay them, and if that's not financially possible, then that means those patents aren't worth enough to exist in the first place.

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operat...

Announcing Feet, a Python Runner

I've been working on a problem that's bugged me for about as long as I've used Python and I want to announce my stab at a solution, finally! I've been working on the problem of "How do i get this little thing I made to my friend so they can try it out?" Python is great. Python is especially a great language to get started in, when you don't know a lot about software development, and probably don't even know a lot about computers in general. Yes, Python has a lot of options for tackling some of these distribution problems for games and apps. Py2EXE was an early option, PyInstaller is very popular now, and PyOxide is an interesting recent entry. These can be great options, but they didn't fit the kind of use case and experience that made sense to me. I'd never really been about to put my finger on it, until earlier this year: Python needs LÖVE . LÖVE, also known as "Love 2D", is a game engine that makes it super easy to build ...

My Software Job Transition Strategies?

I’ve been spending a good deal of the last two days preparing mentally for starting a whole new challenge as a developer. New things aren’t new to me, but this is different and big enough really call for some Deep Thoughts ™. For one thing, I’ve made a big move from the world of Python web development to totally other Python work and while web development has never been the only thing I do, it has been the only work that paid the bills. That transition isn’t one that bothers me or daunts me, though. Instead, I’m thinking about transitioning to the scope of the work I’m getting into. For a long time, I juggled multiple clients and client projects every day, so no single project usually took up most of my time. Every developer juggles time through the day, but exactly how that works in each company and on each project varies a lot. I was looking for a place that I could really focus in a way that I haven’t for a long time. I think I found that, but now I have to deal with the consequen...