Feedback sent to Technorati today:
Please, I beg you, kill those talking “SitePal” ads. I keep my PowerBook plugged into an amplified speaker setup all day, and when the “Pal” begins talking after having been displayed for X seconds (without me so much as mousing over it, I’m pretty sure), it’s heinous. And embarrassing if anyone is within earshot.
Today I worked on a form and script used for registering users on a restricted-access wireless network. Here’s a nice compact regex for checking that MAC addresses have been entered in the correct format. (If you’re using this in a double-quoted PHP string, escape the “$” with a backslash.)
/^([0-9A-F]{2}:){5}[0-9A-F]{2}$/i
Bjoern commented on Mon Jun 4 09:09:14 2007:
Hi,
great regex! exactly what I was looking for.
It only does not match lower case also the windows output of ipconfig/all (using a dash as delimiter) is not covered
In the past 24 hours I’ve seen a wave of comment spam resembling the late August outage. Mostly porn spam. Is it just me? I’m using the Akismet API from my homebrew code (negatives are simply rejected), but maybe this is a sign that I should start using the feedback part of their API to report false negatives.
This also gets me thinking about the need for an Akismet-like service that is run cooperatively, with multiple servers to avoid the single-point-of-failure problem. (And maybe more liberal licensing.) I think Akismet is cool; it’s just impossible not to think about The Next Cool Thing once the Current Thing starts giving you trouble.
Kiko, a Web 2.0-ish calendar company, recently sold itself on eBay. The buyer was Tucows, a company that you may know from their venerable and giant software download archives. Their CEO, Elliot Noss, says in his blog:
[There is] one big reason why we bought Kiko. We needed the functionality, quite desperately, inside of our email platform and it was going to take us a long time to get it. Especially at the level of sophistication Kiko has.
In case you haven’t been following this mini-saga – about two security researchers, an alleged MacBook wireless security vulnerability, and a writer from the Washington Post – here’s your study guide.
The original story at blog.washingtonpost.com (does the “blog” part mean we should lower our journalistic expectations?) has the unassuming title of “Hijacking a MacBook in 60 Seconds.” An alternate, more descriptive title is “Hijacking a MacBook via a Third-Party Wireless Card that Nobody Would Ever Use, in 60 Seconds, and Also Allegedly Hijacking it via the Built-In Card that Everybody Uses, But Wait, Maybe Not, Sorry, We Can’t Talk About That.” You can see why they went with the shorter title.