Entries tagged 'fads'

In Chris Ferdinandi’s article about different static site generators (SSGs), he says that they “store content in flat markdown files instead of a database” and that immediately brought to mind “Bake, Don’t Fry,” a blog post from 2002 by Aaron Swartz where he started exploring the concept of baked sites as compared to fried sites.

At the time, you had blogging systems like Blogger and Movable Type that stored their data in a database but generated static pages for viewing, and systems like b2/cafelog (this was pre-WordPress) and OpenACS that stored their data in a database but generated pages on the fly. The first blogging system that I remember that just used the file system to store all of its files was blosxom.

I started this blog on Blogger but quickly switched over to a homegrown PHP/MySQL system in October 2000. I have rewritten it from scratch once or twice since then.

I have been thinking about moving to a setup that baked and published a static version of my site. A reason I haven’t done it is because doing it all fried hasn’t been a performance problem so far.

I’m not convinced that I want all of the content in flat files and not a database. I guess I just don’t see the advantages of working with flat files for how I like to write, and I can’t imagine expecting less technical users deal with things like text files with front-matter and tools to manage those files.

It is strange that all of the popular static-site generators I’ve looked at have filesystem storage baked into their design. It should be rather straightforward to abstract that out a bit, and then you’d be able to pull your content from a database but generate static output. Like Blogger did twenty-five years ago.

A project I have been playing around with the last couple of weekends has been making a Python version of this site. The code, which is very rough because I barely know what I’m doing and I’m in the hacking-it-together phase as opposed to trying to make it pretty, is in this GitHub repository.

I am using the Flask framework with SQLAlchemy and Jinja.

I was interested to see if I could just use the same templates as my PHP version, which uses Twig, but there have been a few sticking points:

1. The Twig escape filter takes an argument to more finely control the context it is being used in so it knows how to escape within HTML, or a URI, or an HTML attribute. Jinja’s escape doesn’t take an argument. I was able to override it take an extra argument, but mostly ignore it for now.
2. Jinja doesn’t have Twig’s ternary ?: operator. Not surprising, Python doesn’t either. I rewrote those bits of templates to use slightly more verbose if blocks.
3. Jinja doesn’t have Twig’s string comparators like matches and starts with. Looks like I can get rid of the need for them, but I just punted on those for now.
4. Jinja doesn’t have a block() function. I think I can also avoid needing it.
5. Jinja’s url_for() method expects a more Python-ic argument list, like url_for('route', var = 'value') but Twig uses a dictionary like url_for('route', { 'var' : 'value' }). I was able to override Jinja’s version to handle this, too.
6. I’ll need to implement versions of Twig’s date() function and filter.

I had cobbled together a way on the Twig side to let me store some templates (side navigation, the “Hire me!” message on the front page) in the database, so my next trick is going to implement template loaders for both the PHP and Python versions so that is more cleanly abstracted. I have the Python side of that done already.

I hope to eventually create a Rust version of this, too, and it will be interesting to see what new complications using Tera will bring.

When I added the support for dark mode, I had to add a little support to the syntax highlighting styles so they looked okay in both light and dark modes.

Today I went in and worked on the JavaScript code a bit to make it a little more modern and refined the styles a little bit more. I also added the language file for YAML, and built it out so it does a better job of highlighting some of YAML’s more special syntax.

I am sticking with this JavaScript-based syntax highlighting for now, mostly because it works.

Here is a YAML sample pulled from the 1.2.2 spec plus a couple of minor additions to show off additional syntax that is handled.

%YAML 1.2
--- !<tag:clarkevans.com,2002:invoice>
invoice: 34843
date   : 2001-01-23
bill-to: &id001
  given  : Chris
  family : Dumars
  address:
    lines: |
      458 Walkman Dr.
      Suite #292
    city    : Royal Oak
    state   : MI
    postal  : 48046
ship-to: *id001
product:
- sku         : BL394D
  quantity    : 4
  description : Basketball
  price       : 450.00
- sku         : BL4438H
  quantity    : 1
  description : Super Hoop
  price       : 2392.00
tax  : 251.42
total: 4443.52
shipped:
  - false
comments:
  Late afternoon is best.
  Backup contact is Nancy
  Billsmer @ 338-4338.

I finally took some time to implement a “dark mode” style for this site. It will default to whatever you have your system set to, but there is also a set of radio buttons that you can use to force it to a particular mode. (It doesn’t save the setting, so you will have to do it on every page if you are browsing around.)

This talk by Sara Joy about light mode and dark mode was part of the inspiration for getting around to this, and this article about light-dark from Bramus is where I stole borrowed the idea for handling the mode switching.

Because I am using the relatively new CSS light-dark() function to implement this, it is possible (likely?) it will degrade less than gracefully on older browsers.

Since the beginning (almost 24 years ago), my entries here have always been written in HTML with just a simple expansion of blank lines to create paragraphs.

A little over 20 years ago, a syntax for marking up plain text called Markdown was released and it has proven to be a fairly persistent and resilient success. And technically, my HTML with blank lines is compatible with Markdown.

That means that now I have plugged in a Markdown parser where my paragraph expansion was, and it just works and I can start using other syntax.

This is all heading down the path where I can plug in more text transformations, like server-side syntax highlighting for code.

<?php
echo "That would be nice.";
?>

(That won’t be highlighted yet, but whenever I do plug in syntax highlighting it should just happen.)

I’m using the Parsedown PHP library for turning Markdown into HTML, but it seems to be unmaintained and I may swap in something else.

It is possible that the Markdown parsing will mangle some old entries, but a quick scan of entries from this year looks okay, and I can easily fix stuff as I run across it. (I did already fix one very old entry that had some mangled HTML which just kinda worked before but got escaped with the new parser.)

The excellent journalists at 404 Media uncovered information about Automattic selling data to “AI” companies from WordPress.com and Tumblr. A number of people have jumped in to say that “WordPress.com != WordPress” which is a fair point, but this is where I touch the onion on my belt and point out that even WordPress sends pings to Ping-o-Matic by default and does anyone know who gets a real-time feed of that data?

I have been working on shutting down some of the (virtual) servers that we used for the store and other things. There were three: one for the store’s website, one for some WordPress sites/blogs, and one for this site.

The server hosting the store was the most expensive one, but now the site has been reduced to just a couple of static pages, I set those up to run off Bunny.net (that’s a referral link). That should cost a few pennies per months, so the $40 credit I have should cover that indefinitely.

I haven’t figured out what to do with the WordPress blogs, but none of them are active and I’ll probably just turn them into static sites and host them on Bunny.net, too.

The last thing is this server which could be a static site but I like tinkering my little blog engine and think I want to keep it dynamic. I may move the hosting over to Oracle Cloud Infrastructure (OCI) because they offer some “always” free services that would be more than adequate. I have been really curious to play with their Arm-based compute servers but there has been no availability in the region I picked when signing up.

I need to decide how I want to set up the server on OCI to run this. I’m currently using a pretty simple docker-compose.yml setup to handle running a php-fpm container, a MySQL database server, and Sphinx, with the system nginx fronting things. I already know I want to replace Sphinx, and I think I want to try using Caddy on the front. I guess if I really wanted to be extra and take advantage of the free resources from Oracle that I’d spin up an Autonomous Database instead of using MySQL.

Between credits I have with Bunny.net and Oracle’s free offering, I’ll be paying almost nothing for hosting all of this except for the domain name renewals. That soothes my cheapskate soul.

It has been almost six years since I did much to the design of this place, and I figured it was time to pay a little attention to it. Nothing major, just some tweaks to the colors, finally applying a little more style to the forms, and generally just cleaning things up. I will keep tweaking things. I have an SVG version of the “Barrel of Monkeys” monkey that I want to incorporate into the logo but I want to try and simplify it and get it down to a size where I am okay with putting it inline into the HTML.

I am using CSS nesting for the form styles which should be okay with recent browsers. Everything should degrade pretty sensibly, or maybe abruptly. It is great that the state of the art for CSS is advancing fairly quickly again and it is possible to do fun stuff without having to adopt big frameworks or tools that require a build step.

I used Adobe’s (free) Color Contrast Analyzer to pick the colors and (try to) make sure they were accessible.

Not sure what’s next, but dark mode is on the list somewhere.

As I add (or re-add) features to this blog again, I find myself spelunking in some of the archives and hitting a lot of dead links. I was a little curious to see what the oldest still-alive link was, and it brought me to this very short link post from the year 2000 to this article by Greg Beato about a media startup called Verde.com that made me think of recent stories about The Messenger, a media website that went bust in under a year.

I have to hold back from digging into this sort of thing too deeply, or I start to wonder what happened to Scient, or Peek Garlington, and suddenly a day is gone chasing geese.

I also came across this old post about the Los Angeles Times partnering with a technology company to launch an RSS reader application and got a little sad that I have never managed to work my way into a job that is journalism-adjacent. Not because I want to take the money and run, but because I think it is a space where I could tremendously effective given enough of a mandate to do so.

When I added auto-posting of entries here to my Mastodon account, it just took the title of the entry and posted that along with the link. But those end up being kind of cryptic, so now I made it possible to actually write the Mastodon post alongside the blog entry.

Just a small step in building out this online presence more fully and making sure it’s connected to other places more thoughtfully.

The next thing I want to do is build a new home for my photos. I stopped renewing my Flickr Pro subscription. I’ve thought about setting up a Pixelfed instance but that seems like overkill. I may use it as an excuse to build something in a language other than PHP because my resume could use that. Nearly all of my non-PHP work has been lost to me because it wasn’t open source.

With the store now mostly behind me, I’m planning to get back to writing more, baking and cooking more, playing with more technology, and just generally casting off the shackles of small business ownership and all that has entailed (and derailed).

I have also finally decided to find the shift key and get past that all-lowercase-affectation that I stuck with for the first twenty-three-ish years of this site.

No resolutions, just some hopes about directions.

(Also, eschewing corporate social media for now even as a consumer. If the internet is going to get weird again, I want to swim in that.)

i guess it only makes sense that i should ping blo.gs when i post things here.

hard to believe that thing has been running for over twenty years now.

not that i think that there is anyone reading this, but you can now comment on entries for seven days after they have been posted.

you can throw html in your comment, but it will get filtered by html purifier.

spam will be deleted promptly if it wasn’t already blocked or sequestered by akismet.

slowly rebuilding the scaffolding beneath this blog and i re-enabled the display of old comments, which led me to re-discover the time when random people would get mad at me because i mistakenly said redman was a member of the wu tang clan.

what really cracks me up in the comments is my wife celia casually noting that she had dinner with odb and had talked to him about being confused as to wu tang clan’s membership.

you can’t post new comments. i am still deciding if i want to implement that again and deal with all the nonsense that will come with it.

i figured that i should do something clever like automatically post to my mastodon account when i posted here, but i was surprised to find that the state of mastodon api clients for php is pretty sad. php-mastodon was what i used to get it working, but it's really an incomplete implementation and the error handling is pretty much non-existent so it took way longer than it should have to get going.

(and put me down as someone who is glad that “tooting” is being pushed into the background as the term of art for posting on mastodon, but couldn’t resist using it this time.)

while being able to write entries and send them via email seemed like fun, the reality is that the setup was fragile. so it was enough of a hurdle to writing anything here that i rarely wanted to deal with it.

i do want to write more here, so i knocked together a basic web interface that will allow me to do that.

the biggest thing that i still haven't figured out is how i want to handle is images. i could go back to using flickr and embedding from there, or i could implement a basic media library. i think the long-term solution is probably doing it myself because that's kind of the reason for this place.

a couple of weeks ago i finally took some time to upgrade the code for this blog to the latest major version of the slim framework. it is still a strange mash-up of framework and hand-coded sql queries and old php code but this should make it easier to for me to tinker with going forward. the main thing i need to do is add a way to post images again.

another three years between entries. some stuff has happened. the store is still going, and i am still finding excuses to code and learn new things.

i wrote before about how i was converting scat from a frankenstein monster to a more modern php application built on a framework, which has more or less happened. there’s just a little bit of the monster left in there that i just need to work up the proper motivation to finish rooting out.

i also took what was a separate online store application built on a different php framework and made it a different face of scat. it is still evolving and there’s bits that make it work that aren’t really reflected in the repository, but it’s in production and seems to sort of work, which has been gratifying to get accomplished. the interface for the online store doesn’t use any javascript or css frameworks. between that and running everything behind cloudflare, it’s much faster than it used to be.

i noodled around a little more, and came up with an ugly way to supply and extract tags in my postings via email. the next step will be extracting attachments so i can post images again.

yes, this is still on. and now it is on a new server with new code, even though it looks the same.

i still need to knock together the "writing a post" bit of code so that i can post without using manual SQL queries. details.

it turns out that this thing is still on. it is kind of funny to me that it still just chugs along, but such is the joy of writing your own software running on your own (virtual) server. it is long past time to rebuild the infrastructure here, which may or may not happen. but it is something that i am thinking about again.

i get tired of dealing with spam on very old entries here, so the comments now automatically close on posts after one week. you know, on the off chance that i ever post anything of interest again.

you might remember a little over a year ago, when automattic acquired blo.gs. no signs of life yet.

the new york times has an article about how the fast pace of innovation is creating mini-generations.

while the story focuses on the users of all these technologies, the part of it that is of more immediate interest to me is the makers, since i’m one of them. the craft of making computers do what you want is progressing at least as fast as their uses.

new languages, new techniques, new environments. there are people who stand aside and laugh at the reinvention they see, but i would not count myself among them. there are people in the thick of it that think the current new thing is the one that will change everything. i am not one of them, either. there are people who get caught up in an eddy, where what was once the new thing has become their only thing. they are the next generation’s cobol programmer.

i think i am becoming one of them. i don’t think i mind. i don’t code in my free time any longer. i am moving on in other ways. my value as a programmer is not in knowing the newest things.

so today i happened to stumble across the news from last week that yahoo “transferred” blo.gs to automattic.

i guess i can finally let the domain names lapse that i had planned to create a service like blo.gs on.

i haven’t had much to say. very out of character, i know.

or maybe i’ve had a lot to say and don’t know how to say it.

i am looking forward to the dr. horrible’s sing-along-blog session at paley fest 2009.

maybe i’ll write about that next month.

as celia wrote earlier, we are in riga, latvia for a meeting of the mysql developers. she is holed up in the hotel room working on a screenplay (or maybe in the atrium where the wifi is better), and i am in a presentation about blogging.

celia already posted pictures from our excursion day on sunday (the day we didn’t sit around in the meeting rooms at the hotel). i took some video which i will figure out how to deal with once we are back home.

chyrp is a nice looking piece of blog software. individual posts can have different styles, something it borrowed from the hosted tumblr service. i was interested to read about “the sql query massacre of january 19th, 2008” but the numbers gave me pause — 21 queries to generate the index page? that is down from an astounding 116, but that still seems ridiculous to me.

the number of queries to generate the index of this site? two. one of them is SET NAMES utf8. i could see boosting that to three or four if i moved some things like the list of links in the sidebar into the database, or added archive links. call it five if i had user accounts.

but right now, the number of queries used to load the index page on a chyrp site grows with the number of posts displayed on the front page. not only that, it grows by two times the number of posts on the front page.

chyrp could use a security audit, too.

if downtown los angeles was the 3rd bloggiest neighborhood six months ago, things are really exploding now. walter has become frighteningly prolific at scribeskidrow. joe, of joe and ruby fame, has started a blog at big city poz. the guys at angelenic are doing a fantastic job of digging up the news on the downtown development front. white boy/white dog has all the news from 2nd and main. nearby, the lofty dog is one of the first businesses to start up a downtown blog (disclaimer: with my wife and dog’s help). bert green also has a blog as a business owner, resident and player. and dodger is another downtown dog with a blog.

that is a whole lot of new blood in the downtown blog-la-sphere. but i think my favorite part about is that i have been lucky enough to meet all of these new bloggers in person, and they are all fantastic people (and dogs!).

at a party the other night, i was talking with another of our new downtown friends (not yet a blogger) who mentioned how small-town that downtown feels. it is amazing to see how this community is growing up, and to be a part of it while it happens. and i know that the little network of people i know is just one of many such networks downtown.

in his infoworld blog, zack urlocker (vp products at mysql) passes on a good link about smaller software teams. and says very kind things about me, since he read the article after i posted it to our internal business-intelligence list. i used to report directly to zack, but i have managed to shoehorn in three other people between us on the orgchart since then.

that business-intelligence list is kind of a funny beast. it is mostly industry news (who bought who), with some interesting mentions of mysql in the press and blogs, and my ongoing implicit criticism of our development processes. it would make a pretty good blog. i should at least start posting the things i have been sending to the list.

i knew that dave would get me back for tagging him eventually.

1. i am a published poet.
2. i have appeared on a local newscast.
3. i did telemarketing (cold-calling) for an insurance agent.
4. i used to work the weekend opening shift at burger king.
5. i failed two classes in my major in college.

tagging: angel, angel, shannon, jeremy and sam.

over at franklin avenue, mike coined the ridiculous term blog-la-sphere and a few misguided domain-name look-ups later, i ended up registering blog-la-sphere.com (and variants). now i’m proud to launch blog-la-sphere. or relieved. or mildly amused. or maybe i just ate something bad for breakfast.

i finally saw someone make mention of the plugin that adds the load of awful crap to the end of some people’s blog entries which clutters things up on sites like planet mysql. it’s called “better feed.”

clearly, “better” is in the eye of the beholder. i find it to be an eyesore.

so we started a new blog.

my girlfriend celia tagged me with the “meme/chain letter/time suck that’s been going around.” if you read closely, you’ll notice that i have mutated it slightly.

four jobs i’ve had in my life in los angeles: programmer at mysql, programmer at homepage.com, programmer at knowledge adventure, and college (public) relations intern at harvey mudd college.

four movies about los angeles i could watch over and over: crazy/beautiful, repo man, assault on precinct 13, and collateral.

four places i’ve lived all over los angeles (with food memories from each): downtown los angeles, where i still haven’t exhausted the possibilities (but engine co. no. 28 has really won me over); north hollywood, where i discovered chinese deli t&d way too late in my stay; glendale, where i had many great lunches with my coworkers from knowledge adventure, the best at places whose names i don’t remember; and claremont, where making milkshakes at platt (the school cafeteria) probably caused my lactose intolerance.

four los angeles-themed shows i love(d) to watch: boomtown, the shield, 24 (and none of this “only the first season” weaseling — i still love it), and entourage.

four places i would vacation at in los angeles: downtown, the beach, the hills, and downtown. (i’d have added disneyland and laguna beach like celia, but that’s orange county….)

four los angeles-based websites i visit daily: 5th and spring, l.a. observed, blogdowntown, and sha in la. (but to be honest, i use blo.gs to only visit them when they’ve updated.)

four of my favorite foods found in los angeles: strawberry donut from donut man (aka foster’s) in glendora, meat loaf at engine co. no. 28 in downtown los angeles, everything at chinese deli t&d in north hollywood, and celia’s white chocolate sweet potato cake and lasagna.

four places in los angeles i would rather be right now: the central library rotunda, the city hall observation deck, the watercourt at california plaza, and wherever celia is.

four los angeles-based charities you should support: los angeles conservancy, library foundation of los angeles, childrens hospital los angeles, and the midnight mission. (i could go on.)

tagged: shannon, ask, dave (eecue), and eric.

last night was the ambassador hotel wake, which mack of lavoice.org has already covered (although our paths did not cross). there was a large number of los angeles bloggers there: mike of franklin avenue, will and jillian of blogging.la, josh of curbed la (no, i don’t know which one, but i’m just “a reader”), carolyn of laist, kevin of la observed, joseph of martini republic, shannon, and my girlfriend celia.

there may have been more we met and i forgot, and almost certainly more that we just didn’t meet.

this “outside the tent” piece whining that the recent los angeles times blogging article didn’t feature political bloggers is colossally dumb. “wah, the times didn’t write about me and my friends. they suck!”

if you read any los angeles blogs, expect to see a lot of mentions of this los angeles times article about los angeles blogs. no, i’m not mentioned.

martin jansen pointed out that my feed wasn’t showing up as updated on bloglines, and it turns out to be because i had broken the conditional get handling for the feed. oops.

so if you’ve been relying on bloglines, you’ve missed a lot.

this wired article about myspace is interesting, but what really caught my eye was justin’s comment about it: “interesting, MySpace has evolved into "indie music + SNS", like Flickr is "photos + SNS"; also, each of the SNSes seems to have found a niche.”

i was thinking almost the exact same thing this morning, but in relation to yahoo! groups. where the groups concept is “form a group, here’s tools for them to use,” the new model appears to be “here’s a tool, form some groups around their use.”

okay, since everybody else has finally tossed a link their way, now i have to point out the new curbed la, a blog about los angeles real estate and neighborhoods. they’ve gotten off to a great start.

it finally dawned on me what the building was in their header — it’s city hall. you’d think i would have picked up on that sooner considering i can see city hall from my desk.

“breaking the web wide open!” is a long article by marc canter about new open standards on the internet. i’m named as a “mover and shaker” in the pinging space, which i think says volumes about the limits of that space.

evan williams (of blogger and odeo) says that most people read blogs via their web sites, and not an rss reader. (he doesn’t cite any evidence, but i believe it is probably true.) this was in response to information from bloglines about how many feeds “matter.”

i’m one of those — i like reading personal blogs via their web pages, not in an rss aggregator. it is why i built blo.gs. it is why i might have to build something to replace blo.gs, now that blo.gs has become nearly useless for tracking updated blogs.

why do i prefer to read blogs via their sites and not rss? i like to see jason kottke’s remaindered links, reviews, and longer posts in their overall flow. i like to see the random pictures and latest comments on blogdowntown. i like to see what picture of herself shannon has decided to feature now. i like to look at the comments left on recent posts i found interesting by jeremy zawodny.

and for all of the blogs i read, the design of their site gives me a little context, and a little reminder of who they are. (not in the “who the hell is that?” sense, but the “hey, shannon likes pink!” sense.)

five years and two days ago, i wrote my first blog entry. i started out using blogger. four days later, i made my first entry with my own blog software.

when leonard got in touch with me to pick my brain a little bit about the blo.gs acquisition experience, i didn’t have an inkling that he would be joining yahoo! along with the rest of the upcoming.org team.

congrats!

when i look at the hobbled state of blo.gs, i lament, a little bit, my decision to not go to yahoo with the site.

ugh. so much more i could say. but no more angsty bullshit.

i feel like i’ve already seen this discussion about elevator/metro etiquette.

kaj arnö is the latest mysql executive to get bitten by the blogging bug. he’s going to be taking up the mantle of vp/community relations soon. zack urlocker, our vp/marketing, was the first executive to jump on the bandwagon.

doc searls has sometimes explained how he blogs as just answering emails in public.

it has come up in some recent conversations with people i know that they keep up with what i’m up to by reading this site. (which, it frightens me to say, is probably pretty effective. there’s not much that goes on behind the curtains here.)

in conversation, i ask few questions and give short answers. i wonder if blogging has become a sort of conversational crutch for me. by blogging about something, i don’t have to talk about it.

or maybe by blogging about something, i figure out a good answer for the questions that nobody needs to ask because they’ve already read the answer.

cnet news.com reports on the results of the pew internet study that says for nearly half of the bloggers surveyed, blogging is a form of therapy.

that doesn’t surprise me. a lot of what i’ve been blogging recently has been motivated by that.

i felt like i’ve been posting a lot lately — here’s a graph of posts per month since i started (way back in october 2000).

for the 1792 days i’ve been blogging, i have averaged 1.38 posts per day. my longest entry was my notes from the vsda home entertainment conference, the shortest entry was the percentage chance i gave to moving out of my then-current apartment.

trying to read through my archives can be a bit of a chore. it’s one of the things i’m looking to fix with the redesign that i’m slowly working on. so far, it’s not really too radical of a change — but i’ve just been focused on removing things.

businessweek’s blogspotting noticed in a wall street journal article that technorati is making deals to get ping data first, or at least that’s the claim in the article. it would be interesting to know who those deals are with. i can’t imagine it’s with either blogger (google) or six apart.

of course, i’m not sure it helps for technorati to have the data first if nobody can ever actually get at it because of their persistent inability to handle their search load.

jeremy zawodny says that “trackback is dead” and jason kottke says “so long, technorati”, which are both observations i find fairly interesting.

but not so interesting that i have much of anything to add. i don’t get into the stats/links/whatever navel-gazing side of blogging very often. it’s been nearly a couple of years since i’ve even bothered to run stats on the logs for this site.

the only stat that really matters most to me are the number of cool people i’m connecting with, and if they’re just reading, it’s not a very meaningful connection.

kevin roderick passes on the old news that the los angeles times is working with another company to build an rss aggregator. what a terrible idea. the first step for the times should be to publish their own damn rss/atom feeds.

when i graduated college (ten years ago!), one of the places i applied to work was the times. they didn’t get back to me before i had found a job. while at the gym this morning, all that was going through my head is how much of a blast i could have at a place like the times if simply given a mandate to kick ass. (another is that i am probably way more qualified to do that now than i would be even if i had been working at the times for that last ten years.)

if it’s a great time to be an entrepreneur, it should also be a great time for everyone trying to do kick-ass things on the web. if i were at the times, and the team at a paper from a small town in kansas was continuously out-innovating me, i’d go nuts. especially when they have have released their web-building framework as open-source, and the best thing i’ve got going is an rss aggregator that is going to suck being built by an external company.

the number of unique blogs added to or updated in the blo.gs database, per day:

(the data for this is a couple of months old because i stopped logging this information. the way i was logging it was having trouble with the volume of data, and i lacked the interest to do it right.)

some people have been interested in the growth of the data that blogs collects. here’s some numbers. this is from a snapshot of the database from sunday morning, so it isn’t to-the-minute.

of the 6,602,676 entries in the blo.gs database snapshot i used, rss/atom feeds were known for 2,512,959 of them. that doesn’t mean more didn’t have rss/atom feeds, just that blo.gs didn’t know about them.

of the blogs that were updated in the last 30 days of the snapshot data, 71% had known rss/atom feeds.

this is the number of blogs added to the database each month. i wasn’t tracking this before september 2003, so the earlier number is all the blogs prior to that.

the big jump in january is from getting a feed that includes the livejournal data from pubsub.com.

here’s the count of blogs last updated in each given month:

and based on the ip address, here’s the top hosts:

needless to say, the entries for the spammer are gone now. blogdrive.com shows up multiple times because they use multiple ip addresses.

here is where i would insert all sorts of caveats about how these numbers are derived if i cared to hold people’s hands when dealing with numbers like this. these are free numbers, and you’re getting what you paid for them.

so i sort of understand the fascination with tags (although i haven’t provided any way for browsing my entries here by tag), but it seems a shame that the common implementations eschew spaces within tags.

one thing that is fun about tags is that they can provide a bit of meta-commentary about an entry, sort of like a title sometimes does.