Disqus - Latest Comments for cheeaun

Re: Faster Loading Through Eval()

okito — Fri, 30 Oct 2009 15:00:51 -0000

That is for up front loading. Lazy loading is performed through an
iframe in which said file is loaded.

By the way - comments ARE parsed on page load. They are just faster
to parse than regular code. When you want to get the code out of the
comment, you have to regex to extract the code and then eval() again.
There is a cost to loading code as JavaScript vs something else.

Re: Faster Loading Through Eval()

cheeaun — Wed, 28 Oct 2009 11:52:37 -0000

Uh, I don't see any mention of the word 'iframe' though. From my understanding, Google Mobile just puts the whole script at the end of the page, without loading it as a separate file, thus resulting in a greater latency with the initial "download" (of the page itself). Since all the code is commented, nothing is parsed, till the browser read the code from another <script> tag that contains code to read the commented script and eval() them.

Re: Faster Loading Through Eval()

okito — Wed, 28 Oct 2009 11:33:29 -0000

Take a look at the Gmail for Mobile post I linked to. They described the issue. Loading as comments requires you to be able to access the script text. To do that, you need to load the content within an iframe.

Re: Faster Loading Through Eval()

cheeaun — Wed, 28 Oct 2009 08:15:20 -0000

One question on this sentence, "Using comments to defer parsing is clever but it requires some hacks involving an iframe and it won’t work across domains". What does it got to do with iframes?

Re: cheeauntumb

cheeaun — Mon, 23 Mar 2009 01:12:40 -0000

testing

Re: git ready » where to find the git community

cheeaun — Tue, 03 Mar 2009 06:50:27 -0000

There's also the GitHub Google Group: http://groups.google.com/group/github/

Re: git ready » easily fetching upstream changes

davglass — Fri, 13 Feb 2009 11:13:54 -0000

Ha, looks like great minds think a like, I hadn't see that guide :D

Re: git ready » easily fetching upstream changes

qrush — Fri, 13 Feb 2009 08:05:37 -0000

I had the tip submitted to me via the submission form so I figured it was original. I will update the post with the reference to the guide, but still...it's a good tip! :)

Re: git ready » easily fetching upstream changes

cheeaun — Fri, 13 Feb 2009 06:16:25 -0000

This tip is actually from here, I think.
http://github.com/guides/keeping-a-git-fork-in-...

Re: cheeauntumb

cheeaun — Mon, 19 Jan 2009 00:47:59 -0000

No problem. It's not really that difficult anyway :)

Re: cheeauntumb

cheeaun — Sat, 17 Jan 2009 22:01:11 -0000

Oh thanks! Updated.

Re: Death Note Offline

nicol — Tue, 21 Oct 2008 17:30:57 -0000

hola quers hacer el amor con migo nicol

Re: How to make your own Lifestream Blog › Yongfook | Web Producer and Usability Consultant based in Tokyo

yongfook — Fri, 01 Feb 2008 07:54:01 -0000

oh and ETA for point 1)

Yes I'm using Tumblr to write "blog" posts. Basically the rule I set
up is that if the tumblr post is a text post with a title, it's a blog
post and I label it as such in my db. Download the code to see what
I'm doing in the import process.

Re: How to make your own Lifestream Blog › Yongfook | Web Producer and Usability Consultant based in Tokyo

yongfook — Fri, 01 Feb 2008 07:52:02 -0000

cheeaun,

I don't claim to have built the perfect system here - there are still
holes to plug, for sure. So don't be surprised if it doesn't do
everything that you expect it to. It took maybe 2 days to throw
together.

1. I didn't. The old blog is archived on a separate domain and it
still runs good ol' Wordpress.

2. Yep, that was the whole point of using Tumblr in the first place.
There are a few other sites that provide this kind of RSS aggregation
service, but I liked Tumblr as it was well-presented.

3. Depends on your definition of decentralized. I think you're
talking more about network redundancy. What I'm more interested in is
getting away from this idea of one centralised, monolithic location
(wp-admin) to manage content that I have to keep updating. Especially
since I am already managing content on external services anyway (e.g.
flickr). So because I outsource the management of this content to
other places (who take care of the management of the software
themselves) the actual app that brings it all together (my blog) is
very, very simple and much easier for me to maintain than if I were
trying to manage all that content on my own server. Just because I am
keeping the data on my server doesn't mean I'm managing it - if I
wiped my server I could just re-import it all from tumblr again, so
really they are the ones taking care of my data, not me.

4. Yes in a perfect world the comments system would all tie up with
the external services that provide the data in the first place and
we'd have one big mashed-up comments feed. My brain hurts thinking
about that one.

5. You'll probably notice a lot of borked things. If it's something
simple, I'm probably aware of it and will attend to it in time.
Fixing a whole bunch of trivial things on my own blog is not a high
priority for me right now, unfortunately.

Cheers
Jon

Re: How to make your own Lifestream Blog › Yongfook | Web Producer and Usability Consultant based in Tokyo

cheeaun — Fri, 01 Feb 2008 07:36:46 -0000

Just stumbled your site and am very interested in your 'lifestream' concept. I've been trying to do something like it but you beat me to it :D

Ok, I didn't try your 'app' yet but I'll make this snappy. Few questions:

1. As you've ditched Wordpress, how did you convert your wordpress posts to tumblr? So, you are posting 'blog' entries from tumblr now?

2. Since you're using the tumblr api, i supposed you set tumblr to fetch all your 'other' sites' feeds such as flickr's?

3. Since you're throwing Tumblr API's data to your own server's database, isn't that non-decentralized anymore?

4. I notice you use disqus as the commenting system (it's a good one :D ). Just wondering, aren't comments that reply to your twitter statuses should be @username replies? Even flickr has its own commenting system, though.

5. Also, I notice some permalink 'clones' especially the twitter messages. Two different URLs pointing to the same thing? Same applies to flickr.

Re: cheeauntumb

cheeaun — Mon, 28 Jan 2008 07:50:08 -0000

well, uh, in icon design, drawing a face is a no-no. Includes animal face as well.

Re: Why Are You Departing?

Lmirukami — Tue, 18 Dec 2007 13:04:38 -0000

He is probably going to use that disk of his...

Re: Why Are You Departing?

syeina — Tue, 18 Dec 2007 04:37:18 -0000

DxHlover@gmail.com

If I can help in any way, tell me.

Re: Why Are You Departing?

cheeaun — Mon, 17 Dec 2007 20:59:52 -0000

started with what? At least give a hint?

Re: Why Are You Departing?

zelkura — Thu, 13 Dec 2007 14:05:49 -0000

I thank those of you who have cooperated.The reason I have asked for your e-mail addresses is to ensure that I can still contact you in the event that this site closes before I can save it.If you wish to contact me, my email is posted.You may have some difficulties though.If you have any ideas as to further the plan,do not be afraid to speak up.You've seen everyone's e-mail address.So there should be no problems continuing in the event of the unforseen.Once you have read this,please reply by stating your username.

Re: Why Are You Departing?

cheeaun — Wed, 12 Dec 2007 19:59:42 -0000

They sent a ceast & desist letter.

Re: Why Are You Departing?

zelkura — Wed, 12 Dec 2007 14:36:06 -0000

I don't like miscooperation.Besides you can just think of it as a trust execise

Re: Why Are You Departing?

cheeaun — Wed, 12 Dec 2007 13:44:16 -0000

I supposed my email is obviously on the site.

Re: Why Are You Departing?

zelkura — Wed, 12 Dec 2007 13:15:17 -0000

Give me your e-mail address and I can show you. As for you two.Check your inbox .There should be a secret code e-mailed to you.Be searching for it.Print it and delete the e-mail.Got it?(By the way try sitting like L in front of your computer,It really does help you think.)

Re: Why Are You Departing?

cheeaun — Wed, 12 Dec 2007 04:58:56 -0000

what kind of plan?