Some people don't know that Obama lied. But it's obvious fact based on the evidence. In another discussion some apparent trolls were complaining about the claim, but I am uninterested in discussing it, but for those who are interested, the basic summary is this:

* The administration said, for weeks, that the video and the unrest around it was a cause of the attack on the embassy in Benghazi.

* They claimed that the evidence led them to say so.

* They have never provided any such evidence. Some of what they claimed happened -- such as protests existing at the embassy in Benghazi -- was false, and there was never any evidence it was true (maybe in the first hours, but not after the first days).

* There was much evidence, even in the first days, that the attack was preplanned, but it was ignored in favor of the nonexistent evidence of spontaneity.

* The documentary evidence shows that, from the beginning, they had evidence that it was preplanned, and the only "evidence" of spontaneity cited was that it happened soon after protests in Cairo.

Draw your own conclusions, but I do not believe that the President would say it was a spontaneous reaction to the video without some evidence of it, and he had none. He said it because he thought it was believable and wanted to win an election, and if it were preplanned then it is a failure of his administration.

If you want more, check out last week's 60 Minutes report by Lara Logan. Most of it has to do with showing that we a. knew the attack was coming and b. didn't take reasonable steps to prevent it.

Installing Debian...

No doubt people who've read my posts realize I'm concerned about the NSA spying issue, especially in light of the global cooperation in sharing information between spy networks run by other countries including Australia, New Zealand, Germany, and the UK. Even here in Canada our CSIS uses information collected on their behalf by the US NSA. It's already being abused, with information being fed to the DEA and from there on to police departments in the US, which has nothing to do with the original goal of "catching terrorists."

As my own ISP, SaskTel, leases servers in Florida, my email is monitored. My Google and Yahoo accounts are also monitored. There is no way for me to communicate any more without being tracked.

I've always expected this day would come, because when the internet protocol was designed, one of the key requirements were headers that identified the sender and receiver of data packets. There was no way around this, and there is still no way to avoid such identification (though it can be obfuscated to some degree by protocols like TOR.)

As computers have gotten more powerful, it was inevitable that humanity would have the capability to monitor all communications and track all users. It was just a question of when would it happen, and I must admit I'm surprised that we've come this far in my lifetime.

Unfortunately, it would seem the corporate-led fascists are the ones who are leading the charge. Governments whose leaders no longer respect the will of the people, nor even listen to the concerns of the people, but instead spin the lies suggested by their corporate masters. The world is all about the money nowadays.

Maybe some day we'll see a resurgance of humanism and a more equitable social order based on socialist ideals ala Star Trek, where people work for perks, not survival, but I don't think we're going to see that in my life time. Perhaps we'll never see it, because the more entrenched the elite owners of the corporate world become in their mastery of individual country's governments, the less likely it is that they can be uprooted and removed from the halls of power.

Still, I haven't given up hope on humanity.

I'm just very worried about where things are going to go in my own lifetime, never mind the lifetimes of my nieces and nephews.

Despite the tracking that is possible, people insist on using pseudonyms and aliases for their web accounts. I think that's fundamentally wrong. If you've got any sense of honour, integrity, and personal responsibility, you should not be afraid of having your comments and articles on the 'net associated with who you really are. In fact, you should be proud of who you are, stand up as an individual, and rant with enthusiasm against the evils of the world.

Sure you'll make mistakes. You'll say embarassing things. You'll shove your foot in your mouth up to the knee from time to time. And those mistakes will not be erased from the 'net.

But so what? Everyone is human. If anyone is in error, it's those who insist on judging people by their past mistakes instead of realizing that people screw up, learn from their mistakes, and grow to be better people because of them. I've certainly never worried about being judged by potential employers or friends on the internet.

After all, if I am anything, it is honest and blunt with my opinions. I am the kind of person I want to be and would want for a friend: trustworthy and blunt. I hate double-talking backstabbers with a passion, and wouldn't want to work for a company that would judge me based on my internet social life instead of my job history and quality of my work.

So rave on, rave on, rave on, I shall.

Peace.

Mark Sobkow

Beta 6 implements the table id generators for the RAM implementation and corrects a defect in the implementation of the RAM deletes.

It also corrects the use of table id generators for all of the supported databases (DB/2 LUW 10.1, MySQL 5.5, SQL Server 2012, PostgreSQL 9.1, Oracle 11gR2, and Sybase ASE 15.7.) Previously the client-side code that is generated for objects which incorporate BLOBs (or TEXT for SQL Server) would not have properly used the table id generators, but instead would have relied on obsolete/incorrect code for schema id generators of the same name.

All of the RAM and database implementations have regression tested using the CFDbTest 2.0 test suite.

Beta 6 and the corresponding test suite are available for download from http://sourceforge.net/projects/msscodefactory/files/.

I finally reached Beta 5 with my pet project. It now supports manufacturing of code for DB/2 LUW 10.1, SQL Server 2012, MySQL 5.5, Oracle 11gR2, Sybase ASE 15.7, and PostgreSQL 9.1.

I've finally achieved what I set out to do 15 years ago -- provide a multi/cross database coding tool that automates the mapping from an abstract business model to the specifics of the database while using all of the available performance tuning options of the database. This is far more challenging and complex than something like EJB3, which just generates dynamic SQL, not stored procedures and prepared statements.

Next up will be using the tool to write an application. I'm thinking of doing something simple and straight forward, like the core of an accounting system with general ledger, accounts, subledgering, and so on. During that development I may well add in the security support I've been planning all these years, but maybe not. Time will tell.

Regardless, I'm just peaking to have finally achieved this long outstanding milestone. :)

http://perens.com/blog/2013/01/16/1/

The PostgreSQL 9.1 implementation has been updated to make use of stored procedures, prepared SQL statements, and every other performance-tuning trick I've learned in 30+ years of database programming. Subsequent betas will be released as additional databases are brought to the same level of integration as this release for PostgreSQL.

The PostgreSQL code should run rings around EJB3 and similar technologies that rely on dynamic SQL.

MySQL 5.5 support is as complete as it will ever be, and basic DB/2 LUW 10.1 support is also provided.

Download MSS Code Factory Beta 1 from SourceForge.

It's hard to believe that it was about 10 months ago I took a sabbatical and went on life-saving work in Africa, Antarctica and the Amazon basin. I was part of a team of 14 from Chiropractors Without Borders .

This find organization travels the world with our drop tables and performs life-saving chiropractic treatments wherever needed. Natural disaster areas, poor areas of the world, you name it. We've even been learning Veterinarian Chiropractic.

I performed my first adjustment on a penguin during the second leg of our mission (Antarctica). Dr. Mike, who specialized in Vet-Chiro, pointed out one particular penguin which wasn't moving. He carried the gentle creature over and examines its spine. "There! Right there!" he said as he positioned my finger on the bird's back. Lo and behold: a subluxation! It was amazing! "How do I treat it? This is a lot smaller than I'm used to", I asked. "Directional Non-Force Technique (DNFT) works best with avians." said Dr. Mike. I positioned my thumbs ever so gently and applied what seemed like the right amount of pressure.

I quite literally felt the subluxation melt away like butter.

We placed the penguin down. It stood still for a moment then waddled away to be with its mate. This truly was one of the happiest moments of my life. Every cell of creature on the planet has Innate Intelligence within. They know how to repair themselves, all that is needed is removal of the subluxation causing nerve communication issues.

As you can see from the MSS Code Factory project site, things are progressing steadily with my pet project. I've just finished spending a couple of weeks reworking the PostgreSQL database IOs to use PreparedStatements wherever possible instead of pure dynamic SQL. At this point, dynamic SQL is only used for cursor-based reads and index queries which reference nullable columns; all other queries and accessors use prepared statements (static SQL.)

I haven't tested the performance of this new layer with PostgreSQL, and don't intend to compare performance of dynamic and static SQL as it would require keeping copies of and debugging both versions of the code. I know from previous experience with DB/2 UDB that using PreparedStatements can result in an 80% overall performance improvement for something like loading a model into a relational database.

Unfortunately most of the performance benefits would be lost when using the code for a web server, because you have to releasePreparedStatements() at the end of each web page served, because there is the possibility that a particular vendor's implementation of PreparedStatements might have data associated with it on the server end of the connection, and the connection has to be released after serving the page.

One of the biggest advantages of switching to static SQL is that parameter binding with PreparedStatements can handle variables up to the maximum size for the type, whereas dynamic SQL is limited by the size of the statement buffer accepted by the database (which used to be a significant limitation with DB/2 UDB 7.2, though I've no doubt that limit has been expanded or eliminated.)

A key point of the use of static SQL is that the only difference between the different databases now is the specific SQL functions used to convert strings to date-time types, so I'm going to be rolling out the support for the commercial databases under GPLv3 after all, rather than trying to leverage them for profit. The differences are just too negligable for me to believe anyone would pay for the privelege of using a commercial database.

I've been working as a programmer since the spring of 1987. I've travelled all over North America, worked in many cities and with some of the biggest names in technology. I've had an absolute blast working with skilled and intelligent people who were not only good at what they did, but became good friends.

But it's time to face the facts: I can no longer work "office hour" jobs due to chronic migraines. Even with complete flexibility to work from home and at odd hours, I was barely able to get in 24-30 hours per week at the last company that was willing or able to work with me on the scheduling issues caused by the migraines.

I've therefore filed for disability here in Saskatchewan, and am in the process of getting approved for the SAID program (Saskatchewan Assured Income for Disability.) I used to pay twice as much in taxes per year in the '90s than I'll be getting under SAID, but at least it'll be subsistance living.

Don't make the same mistake I did of enjoying your income while you have it. Save and invest your money like it's going to be the last dollar you earn, because you never know when you're going to be hit by the proverbial bus and find yourself disabled. It's not fun, it's not a "safety net" as some claim, and it's a very depressing future to face.

But many of you will face that future, whether due to medical issues or accidents.

Good luck.

P.S.

I'm going to try to keep Singularity One Systems, Inc. alive because every once in a while I do find a few hundred bucks worth of offsite programming I can do for someone. With the company, I can "bank" that income, and draw the $200/month I'm allowed to on disability over time, as well as running a few expenses like monitors and part of my internet/phone fees through the company instead of paying it all out of pocket.

Who knows? Maybe some day one of my pet projects will turn into a money maker. I've always said I'd program for a hobby if I weren't programming for pay, and that's where life is headed: hobby programming to keep myself from being bored silly in "retirement."

Peace.

My Ubuntu 10.04.1 partition developed a serious case of USB problems after this morning's kernel update. When I rebooted to try to reset the USB devices, the partition table nuked itself.

So I'm reinstalling WinXP. This is NOT how I planned to spend my day!

Needless to say, I am NOT a happy camper...

In the future, and a not too distant future at that, we will have quantum-entangled computers that work alongside or as add-ons to our existing computers.

Entangled quantum processors are good at the very class of computing problem that traditional CPUs suck at. And the reverse is also true, so we won't all be switching to quantum computers, we'll be merging the two technologies into a single box capable of tackling both classes of computing problem efficiently.

The issue to society is that current encryption technologies rely on the difficulty of calculations of precisely the type that quantum computers are good for. In the quantum era, it will be effectively impossible to encrypt data in a secure fashion. If you vary your keys fast enough, you might be able to maintain some semblance of security for a specific communications link to another node on the internet, but that would be about it.

That means that all the information on all the centralized data servers running behind every major business or website on the internet is readable.

I realized this years ago. It's one of the reasons I post publicly -- because I know the futility of trying to conceal or limit the access to what I post on the internet.

And it will happen in my lifetime, of that I have no doubt.

I contend that the only way to secure personal data in that future is to have personal servers located at your own home, with maintenance scripted so thoroughly that all the user has to do is pop in a backup cartridge each evening to receive the daily incrementals and weekly full backups of their life.

Instead of you entering in your information to a shared server somewhere, you would grant that shared server's processing systems read-only access to the relevant parts of your information, identified by some sort of unique id code/string (maybe even just a UUID) and the specific IPv6 address of the single host that is being granted that read permission.

Just for safety's sake, every time the application server read your personal information, an access entry would be logged.

It would be forbidden for any application server to retain the data. The sole source of your personal information would be your home node itself.

Sure, some might choose to contract the hosting of that node out to something akin to an ISP or a Google or a MicroSoft, or even an IBM node in a data center/cluster some where, but the key point is that the IPv6 address of each and every individuals information be assigned to one particular node.

I can not imagine any other way of protecting your personal data in the quantum future.

And that's the future I'm building towards.

Your node would assign each application server a corresponding signature, the UUID. The unique id number generator. Basic, simple, effective, and in production for a long time. But hardly anything akin to a password.

Maybe you'd want to look into how the data center at the host is physically architected to protect the token.

Just remember that with the quantum capabilities, passwords will be easily cracked and stolen by anyone with access to a backbone link that can have a good old fashioned network sniffer attached. You're rely relying on the request coming from that particular IPv6 address with the assigned UUID as the unique signature of the authorized request.

Implementing such a system means implementing common data structure standards across all platforms and all systems in due time. You'd choose your hardware/node provider based on your faith in the quality of the system they deliver as a whole.

So you could buy an IBM stack, an Oracle stack, a MicroSoft Windows stack, an Apple stack, or any one of the many Linux and BSD stacks.

Or even smartphone and tablet OS stacks.

Similarly, you'd choose your database service provider from the supported RDBMS vendors, your file system, and so on. Some stack vendors don't let you choose some options, but that's part of what you get when you buy into their stack.

When a snare drum is struck, you should hear the rattle of the wires underneath the bottom drum head, not a tissue paper crackle.

When a triangle is struck, you should hear a bell-like ring soaring above the field of music, not a digitally compressed buzzing sound.

Pat Benatar's high register should soar with authority, not break up into digital noise.

When a cymbal is struck with a stick, it rings with a brassy tone; it does not break up into distortion.

But the past two generations have spent their entire lives listening to 44.1KHz/16bit samples or even more highly compressed MP3s. Their neural pathways have been trained to filter out the digital noise, and now they can't even hear the higher frequencies.

Back when vinyl was king and CDs had just came out, double-blind study after double-blind study proved that analogue was superior, and that the average person could hear the difference.

20-30 years later, the double-blind studies were repeated comparing 192KHz/24bit studio recordings to 44.1KHz/16bit CD quality audio.

Sadly, modern subjects can't hear the difference any more.

They've been robbed of their hearing, and they don't even realize it. Worse, they point to the new study as "proof" that I'm "delusional" and have even come up with some fancy name for the "delusion."

I thought I saw a class-action lawsuit against the *AA and the audio industry in the making for the loss of hearing by the general population, but people are in such denial of the issue that they modded every single one of my posts on the topic down to zero.

How sad. You've all been robbed and you'd rather claim I'm delusional than realize the new study proves you've been robbed.

My number is on the do-not-call list for Canada.

I received one of the robocalls trying to send me to a non-existent polling station, presumably a call made by Racknine.

As Racknine has been unable to identify a political party as approving and being responsible for those calls, Racknine did not perform due diligence and therefore the call made was illegal under CRTC telemarketing restrictions. Only someone who is a duly authorized representative of a political party can contract a robocalling company to call someone who is on the National Do Not Call List.

I believe the penalty for violating the Do Not Call List without proper authorization or exemption status is on the order of $20,000 per call if I recall correctly.

Being able to provide a "burner" cell phone number and an obviously fake name as the "authorization" for these calls means Racknine engaged in wide spread illegal calling of OTHER people who are also on the national do not call list -- I will NOT be the only one who was called an on the NDNC.

I STRONGLY encourage any other Canadian who received such a robocall to contact the CRTC and register a complaint against Racknine. THEY are responsible for ensuring that their business operates within the guidelines of Canadian law.

https://www.lnnte-dncl.gc.ca/pfac-fcca-eng

I finally have some hard oranges-to-oranges comparison numbers between MSS Code Factory 1.8 and 1.9.

With the addition of the GEL compiler and runtimes and other performance tuning, 1.9 takes 1m25s to create MSSBam110 as of 2012.02.18.

The 1.8 release takes 3m25s to produce idential code for 1.9.

That's a 68% reduction in the execution time. Not bad. Not bad at all.

MSS Code Factory