testing wp audio
August 23rd, 2008axel_f
This links directly to the file and your browser handles it in whatever way you have defined locally (likely a quicktime browser plugin). It is WordPress’ built-in method for handling audio files.
This, which requires a skosh more work on my part also links directly to the file, but allows you to continue to browse this page while you listen to the music. This option is handled by a plugin called audio player written by Martin Laine. Another advantage is that it does not show you the URL to where the file is stored, offering a modicum of protection to the composer.
…hmm, it seems that there’s a new beta of that plugin available.
Filed under: audio, weblogback once again
March 4th, 2008So maybe you didn’t notice, but this server disappeared for a few days.
I know I’ve been threatening to migrate to a new, faster box for a long, long time and today, finally, that day has arrived.
I’m undertaking this effort because it needs to be done, but partially also in protest of the inanity that is the DFR (read: TPS) reports that I’ve been tasked with at work.
Filed under: weblogmp3 player plugin
January 20th, 2008Testing, testing … c’n you hear it?
tiny:
small:
big:
file with ampersand:
file with parens:
that’s it folks, time for bed.
Filed under: audio, weblogtwitter!
January 16th, 2008Ok, I’ve been sitting on this since xmas but now that I’ve figured out an easy (albeit imperfect) way to integrate it here I’d like to just go ahead and introduce you to:Â twitter.
Note the twitter RSS feed in the lower part of the rightmost column on this page.
That is, at any given moment, a recent answer to the question “what are you doing?” Likely sent via SMS/text message. Is it cool? Hmm, it is interesting … I’ll declare it cool when I figure out what to do with it exactly. It is fun, in this internet-kitch (which means it is stale before it hits the shelves) kind of way. But I read about it in the Economist, so I expect it to be interesting to monitor for a bit.
Filed under: The Internet, weblogScars
January 15th, 2008Lots in here, but I can’t really stop long enough to get a window open to write it down in.
For some reason my head tells me that a laptop mac will help solve this. But I know it to be a lie: I need to prove the corp. vmware image runs in the osx version of vmware and migrate to the new server first.
I want an easy widget to include a “song of the day” via. hopefully a stream.
Anyway, I was repairing the scars on my snowboard and thinking about it and here are a few of those:
- This deck has been with me since 2004. And it has seen more than its share of whoa.
- The p-tex candle trick does fill in the gashes, but it requires a pretty healthy sanding the repair is made.
- Trying to sand it too early is a mistake and will compromise the repair job.
- The repair requires a lot of heat.
- If you rush it, you will have to do it over, eventually.
- After some sanding, the injury will be smoothed over, but the mark will always be visible. It may not be felt, but it will always be seen.
- It will never be “what was”
- Avoiding the rocks is a good way to avoid having to do this.
- Getting a new deck is a arduous, expensive process and I don’t want to deal with that — I like this (
cheap, scratched,imperfect but loved) deck.
It somehow seemed to relate to everything else in my head at the time.
Filed under: mac, snowboard, weblogmysql.sock
January 12th, 2008So this is an old server. It is slow and it has ailments that aren’t worth the effort to fix, since there’s a new box to replace it in the next rack over. It’s just …. finding the time to make the leap has been hard and doing it piece-meal, daemon by daemon, is slow. Anyway, it wasn’t completely surprising to me when J’fy called me yesterday and told me that my mailserver was busted. But when I looked and saw that the weblog was returning “Error: Can’t connect to database.” I thought that the two must surely be related. (spoiler: they weren’t).
Looking around, I got really scared for a minute because I saw the SANS story about a mass attack on SQL servers but then realized that (at the time of the attack) it was thought to only impact MS SQL servers.
In the end, the problem was that the <code>/tmp/mysql.sock</code> file was gone. Executing a simple <code>/usr/local/etc/rc.d/mysql-server.sh stop</code> && <code>/usr/local/etc/rc.d/mysql-server.sh start</code> didn’t fix it and I was stumped for exactly why. However, executing <code>/usr/local/etc/rc.d/mysql-server.sh restart</code> recreated the socket and all became well in happy land once more.
The end. time for breakfast.
Filed under: weblogNow bigger, bolder!
February 13th, 2007Regular readers will notice the larger font style being used on this site. This is to aid those who would happen accross the site from the comfort of their couch while browsing the web on their Nintendo Wii or something.
Filed under: weblog, WiiTEST POST
November 17th, 2006The Absolute Worst, Most Incredibly Terrible Workout I’ve Ever Witnessed In My Entire Life!
Filed under: weblog
