[XILED]

megalar says:

"enough energy to make 9,000,000 cups of tea."
What a weird measurement system.

• » Tags: coComments, link-blogging, megalar
  Comments

megalar says:

I think its mildly frightening that I'm starting to recognize you dude. I was just surfing around and found this pic and said "isn't that the 0xDECAFBAD dude?" I think this might be a symptom of stalkerishness (I wonder if that's a word).
btw, I just bought both of your books and am really looking forward to 'em cuz I think you might be the only guy who is more of a feed junky than I am. :D

• » Tags: coComments, del.icio.us, link-blogging, megalar
  Comments

I’ve decided to jump on the lifestream bandwagon full force. Check it out at [XILED] . So far I have my del.icio.us, last.fm,
Digg, and CoComment feeds going there. You might ask why I would do this since all that info is available in my sidebar on this site. The answer to me at least is a simple one: I’m marking time.

I recently read quite an interesting post at http://adactio.com/journal/1202/ about the subject of lifestreams where the author makes that a bit more clear:

Every time I ping Twitter, the message is time stamped. Every time I post a link to Del.icio.us, that’s time stamped. Every time I upload a picture to Flickr, a time stamp of when the picture was taken is also sent. Whenever I listen to a song on iTunes, the track information is sent to Last.fm with a time stamp. And of course whenever I blog, be it here, at the DOM Scripting blog or Principia Gastronomica, each entry has a permalink and a time stamp.Just about every time somebody publishes something on the Web, it gets time stamped. Wouldn’t it be nice to pull in all these disparate bits of time stamped information and build up a timeline of online activity?

The technology is already in place. Most of the services I mention above have APIs. In this case, a fully-blown API isn’t even necessary. Each service already offers an easily parsable XML file of activity ordered by time: RSS.

Over the course of any particular day, I could be updating five or six RSS feeds, depending on how much I’m blogging, how many links I’m posting, or how much music I’m listening to. I’d like to take those individual feeds and mush ‘em all up together.

Using the feedwordpress plugin this is almost too easy. Things I’ll add to this: Flickr, Twitter, and other stuff…
This is where you (my imagined audience) come in. Give me some feedback about other services i can mash into this.
I know, you really don’t care about the inane things i do while at the pc, but humor me.

• » Tags: Coffee_Powered_Musings, del.icio.us, lifestream, link-blogging, links, mashup, megalar, twitter
  Comments

An Interesting Idea @ oreilly. Now we wait and see how many splogs end up with the code approved logo

Read the article below:

OReilly Radar > Draft Bloggers Code of Conduct

We celebrate the blogosphere because it embraces frank and open conversation. But frankness does not have to mean lack of civility. We present this Blogger Code of Conduct in hopes that it helps create a culture that encourages both personal expression and constructive conversation.1. We take responsibility for our own words and for the comments we allow on our blog.

We are committed to the “Civility Enforced” standard: we will not post unacceptable content, and we’ll delete comments that contain it.

We define unacceptable content as anything included or linked to that:
- is being used to abuse, harass, stalk, or threaten others
- is libelous, knowingly false, ad-hominem, or misrepresents another person,
- infringes upon a copyright or trademark
- violates an obligation of confidentiality
- violates the privacy of others

We define and determine what is “unacceptable content” on a case-by-case basis, and our definitions are not limited to this list. If we delete a comment or link, we will say so and explain why. [We reserve the right to change these standards at any time with no notice.]

2. We won’t say anything online that we wouldn’t say in person.

3. We connect privately before we respond publicly.

When we encounter conflicts and misrepresentation in the blogosphere, we make every effort to talk privately and directly to the person(s) involved–or find an intermediary who can do so–before we publish any posts or comments about the issue.

4. When we believe someone is unfairly attacking another, we take action.

When someone who is publishing comments or blog postings that are offensive, we’ll tell them so (privately, if possible–see above) and ask them to publicly make amends.
If those published comments could be construed as a threat, and the perpetrator doesn’t withdraw them and apologize, we will cooperate with law enforcement to protect the target of the threat.

5. We do not allow anonymous comments.

We require commenters to supply a valid email address before they can post, though we allow commenters to identify themselves with an alias, rather than their real name.

6. We ignore the trolls.

We prefer not to respond to nasty comments about us or our blog, as long as they don’t veer into abuse or libel. We believe that feeding the trolls only encourages them–”Never wrestle with a pig. You both get dirty, but the pig likes it.” Ignoring public attacks is often the best way to contain them.

We also decided we needed an “anything goes” badge for sites that want to warn possible commenters that they are entering a free-for-all zone. The text to accompany that badge might go something like this:

• » Tags: code_of_conduct, Coffee_Powered_Musings, link-blogging, megalar
  Comments

For lack of a real life outside of work I’m gonna play with a new toy. FeedMagick from l.m.orchard should provide me with a few days entertainment. Inspiration for this idea comes via: http://decafbad.com/blog/2007/04/05/ficlets-enhanced-author-feed-an-xsl-scraper-hack

Docs for FeedMagick may be found here: http://decafbad.com/trac/wiki/FeedMagick
Gonna troll around the web now to see what others have done with the source, hopefully quite a bit as the idea is just fkn nifty.

• » Tags: Coffee_Powered_Musings, feed scraping, FeedMagick, link-blogging, megalar, xml, xsl,
  Comments

megalar says:

I had already decided I was gonna grab your FeedMagick source and try to do something with it but this just gives me more incentive as a Ficlets lover. I recently read your thoughts on pipes and feel much the same way => meh to GUI, especially a buggy one. It seems much more satisfying to just tell php what I want done and watch it go rather than spend 20 minutes fiddling with a silly applet.

• » Tags: coComments, link-blogging, megalar
  Comments

Hello Wordpress!!

elgg is cool and all but the dev community just isn’t as active or as large as wordpress. i couldn’t see the point of trying to implement the things i wanted in elgg when they already exist in wordpress. So now i guess I’ll start fleshing this thing out.

• » Tags: Coffee_Powered_Musings, elgg, link-blogging, megalar
  Comments

http://waffle.wootest.net/2007/03/24/now-in-glorious-html5/

The author makes a few damned fine points: “My main excuse for using is that it’s the only way I - or anyone who reads this, my has a special id so that you can restyle this page as you wish with user stylesheets - can set CSS rules for just the article text, should I want to. Every other solution involves setting rules on the entire , and then undoing them on the or the bread text, as applicable.”

What he fails to mention are the uses in page to feed applications — using a greater number of tags allows for an easier export to xml. Certainly easier than relying on div. Also the page source becomes more readable for me, something about all those divs makes my brain short circuit. I often have to read a section of styled xhtml 3 times to dissect it. Of course that could just be the A.D.D.

• » Tags: Coffee_Powered_Musings, CSS, html, html5, link-blogging, megalar, xml
  Comments

http://open.itworld.com/nl/xml_prac/07112002/

A very insightful article about why mixed content xml is problematic for developers.]]>

• » Tags: Coffee_Powered_Musings, link-blogging, megalar, mixed content xml, xml
  Comments