Skip to main content


Are you ready to go down the rabbit hole? To visit a surreal world, where black is white and white is carrots?

A friend, Metacognician in Shanghai, describes the situation as follows: “Life is more absurd than movies. I've gone down the rabbit hole too, when it just becomes more and more strange and you wonder how that all is supposed to make sense.” I asked him if I should just embrace it. He answered, “Why should you ... change the universe?”

It started with a psychotic named Jim Kiraly who resides, we think, at 6329 Twinberry Circle, Avila Beach, California.

Jim Kiraly is a respected citizen. A churchgoer. A Vice President of Transamerica Corporation. And a violent abuser who tried to use an emergency anti-violence measure, one intended to protect battered women, to stop his victim in a wheelchair from writing a book.

Concise enough? :)

For attorneys: Jim Kiraly filed for CLETS against his son and victim, who lived 200 miles away, did not own a car, and was in a wheelchair. His son and victim was not asked to end communications. Jim had no (zero) specific and relevant allegations that were not perjury. But he turned down repeated offers of no-contact and a signed stipulation that gave him everything but CLETS. He insisted on CLETS if his victim ever once “discussed” him with third parties.

In the end, Jim Kiraly signed an agreement far weaker than the ones he'd been offered.

A review of Court paperwork and other materials will tend to confirm that Jim and other parties, including attorneys on all sides, committed multiple felonies, crimes, and faux pas. :P

The word “abuser” is stated here publicly and without equivocation. A formal offer is hereby made to reaffirm the word in writing and under oath. Attorneys will understand the significance of the point. In short, there is little terror of a threatened defamation suit on this side. Actually, we feel that such a suit will fit nicely up Jim Kiraly's abuser ass.

Jim has one son, Ken Kiraly, who invented the Amazon Kindle and is one of the leads at Amazon's secret Lab126. Another son, Tom Kiraly is one of the leads, a Vice President-CFO type, at medical insurance firms, including one of the largest, Humana Corporation.

These people and some of the biggest names in Silicon Valley legal circles have committed or are involved in multiple crimes.

For the next decade or two, we're going to explore the crimes that these people committed, the motivations and the denial involved, the background and histories that led each person to make the choices that they did, and ways to build upon what happened and move towards positive societal goals.

There's plenty to go over. These people committed or were involved in: Spousal abuse, child abuse, DDOS (a highly prosecutable violation of CFAA), extortion, perjury, conspiracy to commit perjury (a possible felony), false police reports, conspiracy to file false police reports (a possible felony), unlawful threats, barratry, defamation, malpractice, civil harassment, criminal harassment, abuse of process, and violations of SCCBA Professional Standards.

The point was to force Jim's oldest son and victim, me, to sign a gag order. I was in a wheelchair. I'd never made a single inappropriate threat against my abuser. I wasn't even asked to not to call anybody. But Jim threatened to put me in a violence database unless I agreed never to write about him.

I won the right to write, but I lost my home of 25 years, most of my possessions, my chances for retirement, everything. Everything but a realization.

I can make a difference. I can conduct research for legitimate and reasonable purposes, document what happened, and analyze the choices of the people involved:

Maggie told me that she didn't know what she could say to me about what happened. However, we have decades to work it out. It will be productive. I'd like to direct the attention of attorneys and other parties to the:

Legitimate and Reasonable Purposes List

Questions or comments are welcome. For technical notes and disclaimers, click here.

Free Downloads

The current free ebook is located at this link:

For details about the ebook, click here.

The point? “The story is already out there, idiots. Keep it up and I'll demonstrate how something known as decentralized distribution works.”


Sunday 2012-08-11 — Salesforce CPAN Test Code

CPAN is a Perl software repository. In 2013, I did some initial tests of CPAN Salesforce support.

1. I started with a Linux VPS. The CPAN framework had been installed on the VPS previously. Note: The following steps were done as superuser.

2. I found that a CPAN module based on Salesforce's Partner WSDL existed. The module was named WWW:Salesforce. It had originally been presented as part of the first Salesforce dreamForce conference in 2003 and was apparently still compatible with Salesforce.

3. I installed WWW::Salesforce on the VPS as follows. When I was prompted regarding built-in tests, I told the software to do them:

cpan WWW::Salesforce

4. The built-in tests were passed. I wrote a code fragment that attempted to log-in to Salesforce using the Perl API provided by the CPAN module. The code was as follows.

Note: For the username parameter, I used the email address associated with one of my Salesforce developer accounts. For the password parameter, I used the Salesforce password associated with the account in question.

To download this code as a text file, use this link.

#!/usr/bin/env perl
                                # Load CPAN modules
use strict; use Carp; use warnings;
use WWW::Salesforce;
                                # Trap warnings
$SIG{__WARN__} = sub { die @_; };

my $sforce = eval               # Log-in to SFDC
        username => '' ,
        password => 'baconpass'
die "Could not login to SFDC: $@\n" if $@;

In theory, this should have worked. But it produced Error 500. Research suggested that since my code was attempting to log-in from an IP address that hadn't been registered with Salesforce, I'd need to use my Salesforce security token to get in.

I changed the password setting to the concatenation of my Salesforce developer account password and the associated Salesforce security token. This worked, The code fragment produced no error messages and the following command at Salesforce confirmed that the code had logged in successfully:

Administration -> Manage Users -> Login History

5. Next, I used the CPAN Salesforce facilities to access Salesforce data. Specifically, I created and ran the following test program. Technical notes:

* This program is based on WWW::Salesforce::Simple as opposed to WWW:Salesforce

* baconpass consists of the concatenation of a Salesforce account password and the associated Salesforce security token

* To download this code as a text file, use this link.

#!/usr/bin/env perl

# Overview.

# This is a simple Salesforce test program.

# Module setup.

                                # Load CPAN modules
use strict; use Carp; use warnings;
use WWW::Salesforce::Simple;
                                # Trap warnings
$SIG{__WARN__} = sub { die @_; };

# Log-in to SFDC.

my $sforce;                     # WWW::Salesforce::Simple object
eval                            # Attempt log-in
    $sforce = WWW::Salesforce::Simple->new
        username => '' ,
        password => 'baconpass'
                                # Handle errors
die "Could not login to SFDC: $@\n" if $@ || !defined $sforce;

# Output a sorted list of Account fields.

my @list = ();                  # Will hold a sorted field list
                                # Get a fields-list object
my     $ref_fields;
eval { $ref_fields = $sforce->get_field_list ('Account'); };
                                # Handle errors
die "Error: get_field_list failed\n" if $@ || !defined $ref_fields;

                                # Build list of field names
for (@{$ref_fields}) { push (@list, $_->{'name'}); }

                                # Print sorted list
print join ("\n", sort @list) . "\n";

This program behaved as expected. Specifically, it printed a sorted list of the Account fields associated with the specified Salesforce account:

AccountNumber, Active__c, AnnualRevenue, BillingCity, BillingCountry, etc.

Note: The __c string signifies that a field is “custom”, in Salesforce parlance, as opposed to “standard”.