Maybe I should have been more insightful for this blog’s very first entry. But, the fact that it’s not is probably the best indicator of what’s to come. Most everything you’ll find posted to this blog will be thoughts that are too lengthy for my Twitter feed. I’ll always tweet links to new entries I post here, along with my daily spurts of wisdom, punditry, and sheer foolishness! Come on over and follow my tweets.
Elsewhere Online
- Formspring.me
- MySpace
- Geocaching
- Google Earth
- Photo Albums
- Flickr Stream
- TwitPic
- YouTube
- Second Initial
- D.T.P. by Lee
- Media Collection
- Card.ly
Social Networking
Photo & Video
Old Blogs
Miscellaneous
Posted on April 25, 2008 at 10:05 pm
ALBj.net’s First Entry
You can skip to the end and leave a response. Pinging is currently not allowed.
One Response to “ALBj.net’s First Entry”
Leave a Reply
Recent Blog Entries
- Seven-year blogging anniversary
- Eight years ago…
- Six letters
- User registrations
- Apple, please stop removing pre-existing functionality
- WordPress 2.8
- Iconfactory missed the point
- A soapbox moment about HTML (rich text) formatted e-mail
- Gallery upgrade
- WordPress 2.7.1
- A soapbox moment about text messaging
- A cool idea to help with Australia bushfire relief
- Finally got the iPhone WordPress app working
- Dealing with negative people
- Celebrating six years of blogging
- ZÜCA Pro mini review
- I’m at Macworld 2009!
- Did we really need a full press release on this?
- Want some floppy disks?
- Bright House essentially removed features—not added
- Grammar quandary (your response welcome)
- How will you use your spoon?
- Why are logic board replacements always a source of grief?
- Delicious Library improvements forthcoming
- Feelin’ like some Chicago
- This is only a test
- Are you here yet?
- Checking out Twitpress
- Why the switch?
- ALBj.net’s First Entry
Lee on April 26th, 2008 at 2:56 pm says:
I’m leaving a comment to my own page for a very specific reason…the comments RSS feed (see left) was acting weird because it had no entries. So, this comment solves that issue.