<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Disqus - Latest Comments for zeeg</title><link xmlns="http://www.w3.org/2005/Atom" rel="http://api.friendfeed.com/2008/03#sup" href="http://disqus.com/sup/all.sup#usercomments-12dc1c86" type="application/json"/><link>http://disqus.com/people/zeeg/</link><description></description><language>en</language><lastBuildDate>Sun, 15 Mar 2009 23:53:01 -0000</lastBuildDate><item><title>Re: Review of Great New Premium Wordpress Theme Designed for Lifestreamers</title><link>http://lifestreamblog.com/review-of-great-new-premium-wordpress-theme-designed-for-lifestreamers/#comment-7248201</link><description>Glad to see Lifestream getting more and more support! I really like the idea of including the plugin in theme designs, and it's a great starting with WooThemes.&lt;br&gt;&lt;br&gt;However, I wanted to make one comment, which bothered us a bit. The Irreistable theme from WooThemes has some not-very-nice CSS included by default, which forces your page to hide Lifestream credits (which are opt-in only) as well as the date headers. &lt;br&gt;&lt;br&gt;I would have preferred to see them as an option rather than putting this on the user without a choice.&lt;br&gt;&lt;br&gt;Please see this post, &lt;a href="http://www.ibegin.com/labs/forums/index.php?topic=76.0" rel="nofollow"&gt;http://www.ibegin.com/labs/forums/index.php?top...&lt;/a&gt;, for the lines which cause the problems.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zeeg</dc:creator><pubDate>Sun, 15 Mar 2009 23:53:01 -0000</pubDate></item><item><title>Re: How FriendFeed uses MySQL to store schema-less data - Bret Taylor's blog</title><link>http://bret.appspot.com/entry/how-friendfeed-uses-mysql#comment-6749108</link><description>Well this probably isn't the place to find that opinion. They're all close enough that it's not going to matter that much unless you're scaling on the level of Facebook.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zeeg</dc:creator><pubDate>Sun, 01 Mar 2009 16:20:24 -0000</pubDate></item><item><title>Re: How FriendFeed uses MySQL to store schema-less data - Bret Taylor's blog</title><link>http://bret.appspot.com/entry/how-friendfeed-uses-mysql#comment-6733228</link><description>As some have stated this really takes the use of an RDBMS out of the picture, but until there are things like Big Table which are actually on the open market, and are reliable, this seems to be a very common approach to handling large scale database applications. It's what we do, and will continue to do for any application which expects to see a large amount of traffic. However, rather than creating tables for each index (although this is a decent approach to handling parts of the denormalization set), we try to keep each attribute which needs indexed outside of the JSON BLOB, and simply leave it up to MySQL to index.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zeeg</dc:creator><pubDate>Sat, 28 Feb 2009 19:32:57 -0000</pubDate></item><item><title>Re: How FriendFeed uses MySQL to store schema-less data - Bret Taylor's blog</title><link>http://bret.appspot.com/entry/how-friendfeed-uses-mysql#comment-6733137</link><description>APC is a very common choice. They all more or less do the same thing.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zeeg</dc:creator><pubDate>Sat, 28 Feb 2009 19:25:54 -0000</pubDate></item><item><title>Re: LifeStream WordPress Plugin</title><link>http://www.davidcramer.net/my-projects/lifestream#comment-4302707</link><description>&lt;a href="http://davidcramer.net/wp-content/lifestream-0.85.zip" rel="nofollow"&gt;http://davidcramer.net/wp-content/lifestream-0....&lt;/a&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zeeg</dc:creator><pubDate>Tue, 09 Dec 2008 22:34:32 -0000</pubDate></item><item><title>Re: LifeStream WordPress Plugin</title><link>http://www.davidcramer.net/my-projects/lifestream#comment-4302430</link><description>I'm committing version 0.85. If this doesn't fix the download link on &lt;a href="http://WP.org" rel="nofollow"&gt;WP.org&lt;/a&gt; I will host a copy here as well.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zeeg</dc:creator><pubDate>Tue, 09 Dec 2008 22:16:32 -0000</pubDate></item><item><title>Re: Spaceless HTML in Django</title><link>http://www.davidcramer.net/code/369/spaceless-html-in-django.html#comment-4202306</link><description>We GZIP as well. Sadly, everyone's still not on broadband today, so even shaving off 5 or 10k from the request can be quite useful (especially when the amount of time it takes to do that is immeasurable).</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zeeg</dc:creator><pubDate>Fri, 05 Dec 2008 06:55:54 -0000</pubDate></item><item><title>Re: Singletons in Django</title><link>http://www.davidcramer.net/code/375/singletons-in-django.html#comment-4133145</link><description>Ah if you are correct then I will be renaming the project. I haven't done much research (in terminology), but had assumed it was correct via the ticket on Django.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zeeg</dc:creator><pubDate>Tue, 02 Dec 2008 15:21:50 -0000</pubDate></item><item><title>Re: Singletons in Django</title><link>http://www.davidcramer.net/code/375/singletons-in-django.html#comment-4132227</link><description>Personally, I plan to use it throughout the codebase to prevent some data issues. The one area this doesn't affect right now (due to complications we had with it at Curse) is serialization. It will ignore the instance caching when you unserialize objects (such as from the cache).</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zeeg</dc:creator><pubDate>Tue, 02 Dec 2008 14:34:51 -0000</pubDate></item><item><title>Re: Singletons in Django</title><link>http://www.davidcramer.net/code/375/singletons-in-django.html#comment-4132169</link><description>I think per query is a bit out of scope for what I want to achieve. Doing this would require the queryset/manager to be aware (to some extent) of the singleton model. This wouldn't quite achieve the same performance benefit.&lt;br&gt;&lt;br&gt;The biggest thing about this, while it IS an obvious performance boost, its not the sole intention of the project. Having unique instances of an object in memory can solve a lot of other issues as well.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zeeg</dc:creator><pubDate>Tue, 02 Dec 2008 14:31:28 -0000</pubDate></item><item><title>Re: Spaceless HTML in Django</title><link>http://www.davidcramer.net/code/369/spaceless-html-in-django.html#comment-4125147</link><description>Have you confirmed this? I believe the whitespace tag is designed to avoid that, but I haven't fully tested it.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zeeg</dc:creator><pubDate>Tue, 02 Dec 2008 06:27:09 -0000</pubDate></item><item><title>Re: Spaceless HTML in Django</title><link>http://www.davidcramer.net/code/369/spaceless-html-in-django.html#comment-4122433</link><description>It's mostly indentation that actually contributed to the whitespace :)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zeeg</dc:creator><pubDate>Tue, 02 Dec 2008 00:57:25 -0000</pubDate></item><item><title>Re: Spaceless HTML in Django</title><link>http://www.davidcramer.net/code/369/spaceless-html-in-django.html#comment-4121088</link><description>Does mod_deflate allow removing the extra whitespace? In your example you are correct, that it's not a huge savings for that individual request, and gzip I would highly recommend, but the CPU time is negligible.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zeeg</dc:creator><pubDate>Mon, 01 Dec 2008 23:13:39 -0000</pubDate></item><item><title>Re: Impressions of the BlackBerry Storm</title><link>http://www.davidcramer.net/other/366/impressions-of-the-blackberry-storm.html#comment-3969862</link><description>My expectations might not have been as high as some I guess, but I've been very pleased with it so far. It's really going to depend on what RIM does in the next month or two to see if they can really compete with Apple.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zeeg</dc:creator><pubDate>Sun, 23 Nov 2008 13:27:04 -0000</pubDate></item><item><title>Re: MediaWiki markup and SphinxSearch for Django</title><link>http://www.davidcramer.net/code/54/mediawiki-markup-and-sphinxsearch-for-django.html#comment-3671097</link><description>It was used for &lt;a href="http://Curse.com" rel="nofollow"&gt;Curse.com&lt;/a&gt; (slightly modified, as we had a full wiki app at one point). I'm willing to maintain it, but as I don't use it myself in any production environments, I'd have to be encouraged in order to add features.&lt;br&gt;&lt;br&gt;However, if there is interest, I'd gladly accept patches, or even requests.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zeeg</dc:creator><pubDate>Mon, 10 Nov 2008 19:38:29 -0000</pubDate></item><item><title>Re: Tips for Scaling a Web App</title><link>http://www.davidcramer.net/code/django/345/tips-for-scaling-a-web-app.html#comment-3641140</link><description>In some situations, yes. We happen to have more than just a username and user id though. We use it to pass other dynamic information pages as well. But the solution is far from silly, and it's a lot more common than you may think.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zeeg</dc:creator><pubDate>Sun, 09 Nov 2008 00:03:26 -0000</pubDate></item><item><title>Re: Tips for Scaling a Web App</title><link>http://www.davidcramer.net/code/django/345/tips-for-scaling-a-web-app.html#comment-3627618</link><description>Yes there are, but there is no need to use signals (extra overhead) when it's a simple task like this.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zeeg</dc:creator><pubDate>Sat, 08 Nov 2008 16:30:02 -0000</pubDate></item><item><title>Re: Tips for Scaling a Web App</title><link>http://www.davidcramer.net/code/django/345/tips-for-scaling-a-web-app.html#comment-3619128</link><description>On initialization (__init__) you can store the state of things. I may throw up an example here in a few days, the code above doesn't actually match what we use, but it was a quick clean example :)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zeeg</dc:creator><pubDate>Sat, 08 Nov 2008 02:08:16 -0000</pubDate></item><item><title>Re: LifeStream WordPress Plugin</title><link>http://www.davidcramer.net/my-projects/lifestream#comment-3574589</link><description>It seems as if it's possibly not doing relative includes. This is very strange behavior. I will change them to absolute in the next commit. Thanks!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zeeg</dc:creator><pubDate>Thu, 06 Nov 2008 15:18:39 -0000</pubDate></item><item><title>Re: How Things Have Changed</title><link>http://www.davidcramer.net/code/333/how-things-have-changed.html#comment-3320817</link><description>I have noticed increased traffic on keywords which should have been weighted better before.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zeeg</dc:creator><pubDate>Mon, 27 Oct 2008 02:34:07 -0000</pubDate></item><item><title>Re: Lifestream data and plugins</title><link>http://shripriya.com/blog/2008/10/27/lifestream-data-and-plugins/#comment-3320096</link><description>Well it uses RSS for Twitter. I guess you could manually import them into the DB with a small bit of work, but it imports any that it finds in your Twitter RSS feed.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zeeg</dc:creator><pubDate>Mon, 27 Oct 2008 01:43:47 -0000</pubDate></item><item><title>Re: Lifestream data and plugins</title><link>http://shripriya.com/blog/2008/10/27/lifestream-data-and-plugins/#comment-3319936</link><description>Well, what lifestream does is allow you to collect all your information into one stream, much like the activity feed on Facebook. Right now it only works in Wordpress, using a few tables in your blog database which it creates. As for the display issues, I've tried to use fairly generic styles and not to override much, but there may be something that is conflicting.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zeeg</dc:creator><pubDate>Mon, 27 Oct 2008 01:16:22 -0000</pubDate></item><item><title>Re: Lifestream data and plugins</title><link>http://shripriya.com/blog/2008/10/27/lifestream-data-and-plugins/#comment-3319670</link><description>Hey,&lt;br&gt;&lt;br&gt;Author of wp-lifestream (#3 on your list). I'm very open to suggestions on how to improve the frontend display to allow users, like yourself, easier formatting. I've also been looking into the database issues, but they've been hard to reproduce and not everyone has them.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zeeg</dc:creator><pubDate>Mon, 27 Oct 2008 00:37:15 -0000</pubDate></item><item><title>Re: Django Scaling Numbers for iBegin</title><link>http://www.davidcramer.net/code/django/328/django-scaling-numbers-for-ibegin.html#comment-3320740</link><description>It was just a quick test using the "siege" application available on unix-based systems.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zeeg</dc:creator><pubDate>Wed, 01 Oct 2008 06:25:27 -0000</pubDate></item><item><title>Re: Django Scaling Numbers for iBegin</title><link>http://www.davidcramer.net/code/django/328/django-scaling-numbers-for-ibegin.html#comment-3320734</link><description>This is single server, that's fairly mediocre in hardware. The only modifications to Django is our composite primary key support.&lt;br&gt;&lt;br&gt;Thanks Tomek, sphinx (search) was down. We're still having some issues with error emails and sphinx didn't have an init.d script setup yet.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">zeeg</dc:creator><pubDate>Mon, 29 Sep 2008 18:05:20 -0000</pubDate></item></channel></rss>