holy f***ing shit, openid is confusing

So, to register an account using OpenID with bitbucket.org, you apparently have to select "sign up" and then in the OpenID text input box, put the following URI:

www.google.com/accounts/o8/id

Obvious, right? Of course it's obvious. I mean seriously, all those web sites about OpenID telling me to use my email address or a per user URI to login makes it obvious that everyone would be using the same URI that has nothing in it that identifies me.

Before the OpenID twits start falling over themselves to tell me I'm an idiot, let me remind them that I worked on real systems that were real and users could actually use. Sheesh guys, you're seriously making PKIX look intelligible. This reinforces my opinion that OpenID is a technology developed by myopic twits with their heads so far up their collective a**es they've never seen daylight, much less have the light to read a good book on user centered design.

Honestly, if OpenID is the future of the web, I'm moving to Fiji to implement SAML over avian carrier. You want me as an app developer to hype your lame assed s*** so your confused identity providers can confuse the f*** out of MY USERS with crap like using the same URI for everyone. And for *****'s sake, a******, it's not like you could have a standard or something that says, "open id's are [username]@[authority]."

No! That's way too understandable. Hell, if you did that, then actual users could use your technology. Oh! The horror! The horror! Someone who doesn't know what XRDS is could actually understand how to make the damn'd thing work!

And don't get me started about Plaxo and Facebook. WTF? Plaxo's putting up random IFRAMEs over the facebook page? What? Are you f****** high? You're seriously trying to tell me users can trust the OpenID experience because they'll always be able to look at the URL of the page they type their credentials into, but now you're using IFRAMEs? What?

FFS kids, the world isn't a blog comment. OpenID is a bag full of fail. Go back and finish your degrees already.

compiling apg 6.0 on MacOS X 10.5.8

so mi amiga infinity asked me to report the following:

It looks like MacOS-X 10.5.8 doesn't like APG 6.0 for the following three reasons:

1. it's a mac. it's a sullen little machine that likes to strike out randomly at people who love it.
2. malloc.h is in a mildly non-standard place
3. the version of autoconf that comes with it doesn't grok 'dist-lzma'

APG 6.0 is an ABNF Parser Generator from Coast to Coast Research that takes ABNF files and generates C and C++ files to make the creation of domain specific languages slightly easier. I'm not entirely certain, but my guess is she's working on a tool to manipulate LLIDL files; there was some chatter recently about an upcoming draft of LLSD and it's ABNF.

Here's what i did to replicate the problem and the solution:

1. Download APG 6.0 by going to the page at http://www.coasttocoastresearch.com/apg-6.0/download-60.php , reading the license, and clicking on your favorite flavor of compressed archive file.
2. Untar the file in your favorite place for parser generators on your hard drive.
3. Change directories to that location and enter the command:
   ./configure ; make
4. Witness the madness that is Autoconf:
   ./../src/CommandLine.c:31:20: error: malloc.h: No such file or directory.
5. Modify line 6 of the file to remove the reference to dist-lzma, so it reads:
   AM_INIT_AUTOMAKE([-Wall -Werror foreign dist-zip dist-bzip2])
6. Modify the configure.ac file so that line 8 reads:
   CFLAGS="$CFLAGS"
7. Then issue the commands:
   autoconf
   automake
   export CFLAGS=-I/usr/include/malloc
   ./configure
   make
8. and viola! you're done. if you're brave, you can also install the package with the command:
   sudo make install

And that's it, enjoy!