Shutting down the conversation

Recovered from the Wayback Machine.

What’s particularly difficult about writing something such as my posting Girlism? is seeing the gentlemen in the community linking to Halley’s post, but not my refutation. Huzzahs for Halley’s refreshing honesty and blowing the lid off the terrible games we women play.

Perpetuating the myth by controlling the links, and thereby controlling the discussion. Well done. Is this another lesson we women should learn?

But then, I’m picking on Halley with my posting, aren’t I? And members of the same community are not supposed to do this. We either agree, or stay silent. Another lesson to learn.

Why are more women’s voices not heard in technology? Because men control technology’s voice. I guess the same could be said for weblogging.

Update: Thankfully, the conversation is starting up again, which is what I really was hoping for. I knew there had to be other voices with something to say on this issue. See ElaineSteveDorotheaMike, and Jen. And associated comments attached to all the postings.

Second Update And Sam! Of course, Sam! Sam, who is the first official member of Burningbird’s Anonymous! I would never forget to link to Sam. Nah uh. Not me.


RSS push back

I guess I won’t be finding any interest in my SORSS syndication format because the weblogging kingdom is now circling about XHTML as a syndication format. In other words, publish your page as XHTML and let aggregators scrape it.

It looks as if Anil Dash started the discussion with a well written suggestion:

My new syndication format is called XHTML. I propose that existing syndication and aggregation clients should be able to read an HTML file, detect if it has the appropriate XHTML doctype, and then render the contents of each XHTML node in the appropriate place in the client’s display. All that would be needed is standardization of names and classes for page elements like DIVs and headers. A post/entry title would always be an H3, with a class set to “title”, for example. Permanent links would always be P tags with their classes set to “permalink”. Simple.

What was particularly nice about Anil’s posting is that it generated a lot of good discussion and commenting, and no animosity. Pay particular attention to Timothy Appnel’s comments, which I think were quite good. (Thanks to Chris for heads up on excellent discussion.)

The “RSS Rebellion” has now spread elsewhere:

Mark wrote a Python program to scrape HTML and generate an RSS stream. You know, that boy do like Python, doesn’t he? Wait a sec — he just turned 30. Excuse me, I should have said that man do like Python.


Mark based his efforts on the discussion at tantek/log.


Aaron Swartz likes the idea and provides an XSLT implementation (and links to other discussions).

Personally, though I have just finished a template re-design for most of my pages that validates as strict XHTML 1.0 (not implemented yet, so don’t test this page), I have no interest in someone grabbing whatever they want for syndication from my web page, including the entire posting. I’d rather they take the excerpt I give them, which I can control by having a seperate syndication feed. Besides, I’m going to implement SORSS for my site. You know, that Dark and Beautiful Queen thing.

So why am I interested in and promoting this debate? I’m all for bubbling the Daypop joy juice, watching to see what floats to the top.