Acá los dejo con un video.

Aprenda a usar Facebook...por favor XD

Vía StumbleUpon (muy aburrido hoy XD)

Vía StumbleUpon

S.e.d. + Malroch + Superchango, 22 de Agosto

Se viene la segunda patita miércale…

Los esperamos este Sábado 22 de Agosto en el Bar El Purgatorio, Antonia Lopez de Bello #42 en el barrio Bellavista, para seguir con la fiesta del rock. Esta vez la fuerza estará a cargo del punk rock de S.E.D., la potencia del metal de Malroch y concluimos con un espectacular vacilón al ritmo de Superchango y su pachanga.

Están todos invitados, tanto los que fueron a la anterior como los que se la perdieron y los que tampoco nos conocen, para que vengan a vacilar con nosotros. Los esperamos y lleguen acompañados si quieren.

Este proyecto empezó hace una semana, como otro chiche en Javascript útil para poder desarrollar páginas y otras aplicaciones. En general una de las partes más tediosas de desarrollar algo en el ambiente web(sea un formulario de contacto, de envío de datos personales, o de cualquier otro tipo de aplicación que necesite ingresar algo) es validar la información que el usuario envía a la aplicación. La idea es darle más simpleza a esto, por lo tanto desarrollé este ayudante implementado como un objeto Javascript.

Demás está decir que actualmente está en estado beta, así que lo usan bajo su propia responsabilidad (si es que lo usan).

• Leprosystems Form Validator v0.95 (tar.gz)
• Leprosystems Form Validator v0.95 (zip)

Modo de uso

Para usarlo, lo descomprimen y viene una carpeta (js)  con el script que deben incluir. Una vez incluido en el sitio, para invocar el validador, deben crear un objeto de tipo LsFormv de esta forma :

var myformv = new LsFormv(’id_item‘, focus);

donde id_item es el atributo id de un formulario que deseen validar al ser enviada la información que este contiene y focus un boolean que indica si queremos que al momento de que detecte un campo inválido, el focus del navegador vaya hacia este. Esto creara el validador y podremos entonces utilizarlo, ya sea al enviar los datos del formulario o con alguna llamada a su API.

Para poder validar el formulario, se necesita ingresar reglas a este. Las reglas indian que campo se valida y que tipo de datos se puede colocar en él. Para poder añadir una regla, usamos el método add de esta manera :

myformv.add(’input‘,’regla‘, ‘mensaje‘);

Aquí, le indicamos al validador que valide el campo de nombre ‘input‘ (el atributo name del campo) y que si este es inválido, al momento de enviar el formulario, detenga el proceso y muestre el mensaje indicado en ‘mensaje‘. La regla indicada en ‘regla‘ le indica al validador que tipo de dato es válido, esta regla puede ser :

• ‘ req ‘ : Requerido, solo necesita que el campo contenga algo.
• ‘ num ‘ : Numérico, el campo debe contener datos numéricos(acepta números y puntos solamente).
• ‘ alpha ‘ : Solo letras.
• ‘ alphanum ‘ : Solo letras y números.
• ‘ mail ‘ : Una dirección de correo (a@b.c).

Métodos

También existe una humilde y modesta API para este validador XD. Estas funciones existen por el momento :

• LsFormv.getForm() : Devuelve una referencia al formulario que usa el validador.
• LsFormv.valid() : Valida el formulario, sin enviar sus datos. Devuelve true o false dependiendo si el formulario es válido o no.
• LsFormv.submit() : Envía la información del formulario, si esta es correcta. Caso contrario, devuelve false junto con indicar que campo es el incorrecto.

To-Do

Algunas cosas que pretendo agregar en el corto o mediano plazo :

• Añadir más reglas de validación.
• Optimizar un poco más.
• Alguna otra función interesante en la API.

¿Qué cresta es el correo electrónico?

From trey@sage.org Fri Nov 29 18:00:49 2002
Date: Sun, 24 Nov 2002 21:03:02 -0500 (EST)
From: Trey Harris <trey@sage.org>
To: sage-members@sage.org
Subject: The case of the 500-mile email (was RE: [SAGE] Favorite impossible task?)

Here’s a problem that *sounded* impossible… I almost regret posting the story to a wide audience, because it makes a great tale over drinks at a conference. The story is slightly altered in order to protect the guilty, elide over irrelevant and boring details, and generally make the whole thing more entertaining.

I was working in a job running the campus email system some years ago when I got a call from the chairman of the statistics department.

“We’re having a problem sending email out of the department.”

“What’s the problem?” I asked.

“We can’t send mail more than 500 miles,” the chairman explained.

I choked on my latte. “Come again?”

“We can’t send mail farther than 500 miles from here,” he repeated. “A little bit more, actually. Call it 520 miles. But no farther.”

“Um… Email really doesn’t work that way, generally,” I said, trying to keep panic out of my voice. One doesn’t display panic when speaking to a department chairman, even of a relatively impoverished department like statistics. “What makes you think you can’t send mail more than 500 miles?”

“It’s not what I *think*,” the chairman replied testily. “You see, when we first noticed this happening, a few days ago–”

“You waited a few DAYS?” I interrupted, a tremor tinging my voice. “And you couldn’t send email this whole time?”

“We could send email. Just not more than–”

“–500 miles, yes,” I finished for him, “I got that. But why didn’t you call earlier?”

“Well, we hadn’t collected enough data to be sure of what was going on until just now.” Right. This is the chairman of *statistics*. “Anyway, I asked one of the geostatisticians to look into it–”

“Geostatisticians…”

“–yes, and she’s produced a map showing the radius within which we can send email to be slightly more than 500 miles. There are a number of destinations within that radius that we can’t reach, either, or reach sporadically, but we can never email farther than this radius.”

“I see,” I said, and put my head in my hands. “When did this start? A few days ago, you said, but did anything change in your systems at that time?”

“Well, the consultant came in and patched our server and rebooted it. But I called him, and he said he didn’t touch the mail system.”

“Okay, let me take a look, and I’ll call you back,” I said, scarcely believing that I was playing along. It wasn’t April Fool’s Day. I tried to remember if someone owed me a practical joke.

I logged into their department’s server, and sent a few test mails. This was in the Research Triangle of North Carolina, and a test mail to my own account was delivered without a hitch. Ditto for one sent to Richmond, and Atlanta, and Washington. Another to Princeton (400 miles) worked.

But then I tried to send an email to Memphis (600 miles). It failed. Boston, failed. Detroit, failed. I got out my address book and started trying to narrow this down. New York (420 miles) worked, but Providence (580 miles) failed.

I was beginning to wonder if I had lost my sanity. I tried emailing a friend who lived in North Carolina, but whose ISP was in Seattle. Thankfully, it failed. If the problem had had to do with the geography of the human recipient and not his mail server, I think I would have broken down in tears.

Having established that–unbelievably–the problem as reported was true, and repeatable, I took a look at the sendmail.cf file. It looked fairly normal. In fact, it looked familiar.

I diffed it against the sendmail.cf in my home directory. It hadn’t been altered–it was a sendmail.cf I had written. And I was fairly certain I hadn’t enabled the “FAIL_MAIL_OVER_500_MILES” option. At a loss, I telnetted into the SMTP port. The server happily responded with a SunOS sendmail banner.

Wait a minute… a SunOS sendmail banner? At the time, Sun was still shipping Sendmail 5 with its operating system, even though Sendmail 8 was fairly mature. Being a good system administrator, I had standardized on Sendmail 8. And also being a good system administrator, I had written a sendmail.cf that used the nice long self-documenting option and variable names available in Sendmail 8 rather than the cryptic punctuation-mark codes that had been used in Sendmail 5.

The pieces fell into place, all at once, and I again choked on the dregs of my now-cold latte. When the consultant had “patched the server,” he had apparently upgraded the version of SunOS, and in so doing *downgraded* Sendmail. The upgrade helpfully left the sendmail.cf alone, even though it was now the wrong version.

It so happens that Sendmail 5–at least, the version that Sun shipped, which had some tweaks–could deal with the Sendmail 8 sendmail.cf, as most of the rules had at that point remained unaltered. But the new long configuration options–those it saw as junk, and skipped. And the sendmail binary had no defaults compiled in for most of these, so, finding no suitable settings in the sendmail.cf file, they were set to zero.

One of the settings that was set to zero was the timeout to connect to the remote SMTP server. Some experimentation established that on this particular machine with its typical load, a zero timeout would abort a connect call in slightly over three milliseconds.

An odd feature of our campus network at the time was that it was 100% switched. An outgoing packet wouldn’t incur a router delay until hitting the POP and reaching a router on the far side. So time to connect to a lightly-loaded remote host on a nearby network would actually largely be governed by the speed of light distance to the destination rather than by incidental router delays.

Feeling slightly giddy, I typed into my shell:

$ units
1311 units, 63 prefixes

You have: 3 millilightseconds
You want: miles
* 558.84719
/ 0.0017893979

“500 miles, or a little bit more.”

Trey Harris

Enlace original : The case of the 500-mile email.

El primero es el maestro de maestros, Coco Legrand. Rey de la comedia por donde se le mire.

El segundo es el Rey del chiste. Pipo Arancibia, no necesita mayor presentación. Probablemente ese chiste que uno cuenta por ahí lo inventó este tipo, imitado por muchos, igualado por nadie.

De bonus track…un tipo genial. Steffan Kramer

Este 22 de Agosto se repite la historia en el mismo local.

Malroch en vivo 30/07/09, Bar el Purgatorio

Acá unas fotos :