Props - inlaterdays Edition

You sincerely want to make people around you happy, and aren't afraid to try difficult things to do so.  Some people steamroll the feelings and attention of others as if it's an ugly lawn ornament; you're quick to apologize for stuff that almost nobody would notice if it went unremarked, and you mean it.  You've been through some intense stuff, but there's an African proverb that suits - "Calm seas to not make good sailors."

*snerg*

moink! is love
brought to you by the isLove Generator

Weekend Wibblings

( So, to sum up: Hanging out, car shopping, carnage, landscaping, and gaining levels. )

And today, the first installment of the Sil-free workplace. I'm just wondering who keeps calling and leaving her voice mail.

F*ckholes

hel_ana does her part to get my blood pressure up this morning by bringing this bullshit to light.

Church. State. Separate, motherfuckers.

attn: thewronghands et al. - Security advice solicited

We're trying to implement a fairly basic widget here for supervisors to be able to submit one-shot text data via a web-based form (password req'd - minimally secure, but adequate for tracking purposes in case of evil) that will subsequently be rendered by Flash (actionscript) calling on an xml file.

the initial solution was to have an on/off pointer in the xml to an external .txt file where the submitted text would be written-to. The security-through-obscurity approach took about three minutes to be subverted by our trained management monkey (which is why we asked him to try and break it). hence, this request.

this is far from mission-critical, but we don't want it to be easily circumvented and abused by bored phone drones. do you have any suggestions as far as submitting form data to a secure-enough file for rendering, while still allowing the text file to be modified by the submission form (and, presumably, those of us who wrote it)?

[yes, i'm finally learning to code, albeit tentatively]