@TerryChia hahahahaha. Well, I did see the ones that Monty Python used for their recent stage show. Not sure we'd get away with them. Two ball shaped wheels...a kind of ribbed cannon...I don't think I need to go on
@TerryChia Actually, after we fired them, the scantily-clad, tank-girl-ish girls along the front row had a lot of sparkly confetti covering them. After the gig, one of them did mention she felt like we had attacked her with unicorn j*zz. Which led to many of the unicorn pictures...
@RoryAlsop That makes me think about the shows from Space Unicorn On Fire that I've seen. First time they threw a shitton of condoms into the public, they were apparently sponsored by a sexshop. The second time there was this girl with rainbow colored hair in a bridal outfit with a fake horn on her head.
@Arperum The two things we fire at the crowd are confetti, glowsticks and condoms. Three things. The three things we fire at the audience are confetti, glowsticks, condoms and silly string. Wait. Amongst the things we fire at the audience are: confetti, glowsticks, condoms, silly string, bubbles and fire
But we make it fair - we get them to fire stuff at us too
judas priest. Now how do I save and edit this damn shot.
crap, what. nevermind.
> In Mac OS X v10.6 and later, the screenshots are saved as PNG files on the desktop. They're automatically named "Screen shot (date and time).png." You can open these screenshots with Preview or other image editing apps.
@AviD Just drag the link for the little popoup menu on the left of your message to the textbox, then remove everything but the last numbers, and replace by a ":". I was actually talking about his "plugin" for editing older messages by pressing up.
@TerryChia huh. I was thinking about blowing up the universe and rebooting it again with the Tardis.
Jeebus. What is it about "The registration will close on Sunday", "Sunday is the last day to register", "Register right now, or lose out", "SERIOUSLY YOU WONT BE ABLE TO REGISTER TOMORROW", that is confusing people?
I have had close to 2 dozen people write to me today. As if 700 people registered is not enough.
Anybody knows what to use to exclude a surface from silicon sealant?
I'm applying silicon sealant on a surface and I don't want it to stick on a one particular spot. There's no way but to apply it over that spot, but I don't want to stick, and I want to be able to remove it once everything dries.
@Adnan nice - by the time I got to it it had a total of 2 spam flags and 4 other flags :-)
Was having another look at the Unanswered Questions tab ( security.stackexchange.com/unanswered ) - and I think I will ask the SE devs if we can do a wee competition later in the month. I'll need you folks to help me work out what we can measure that would give us a win for the site on reducing our unanswered total by giving good answers (ie a score of 5 or more etc)
I have some prizes I can throw in (one being a very geeky magic 8-ball we designed a few years back - I still have 2 left from my original stock)
I'm a bit busy this week prepping for big gig next weekend on top of the day job and t'wife going away on holiday, but will try and make time to make a meta post on it
I never ever heard in my 20+ years dev career that using prepared statements would cause something to run slower. Does anyone more versed in PHP have any clue what this one is describing? security.stackexchange.com/questions/66490/…
@Adnan Well considering he/she claims faster run time for additional input sanitisation, I'm pretty sure there's some nice error in his/her code to exploit. At least it might be easier to DoS the shit out of it.
But that's not what my point was. I don't care for PHP input sanitisation, not the least bit. What caught my attention in that question is his/her claim that prepared statements make things run slower.
I only read it because I was reviewing an answer to it anyway
@Adnan Yes, I know, but my only guess as to why this would be happening is that MySQL engine fucks it up somewhere, possibly during SQL parsing and parameterized queries aren't privy to some optimisations that non-parameterized are. Then again, like I said, MySQL is POS and best avoided. Use a proper RDBMS, perhaps some that PHP devs wouldn't rely on so eagerly. It's all about the company you keep ...