stephen_mcd

12 ms·

61.
by stephen_mcd 13y ago
Thank you! That's definitely a bug, looking into it :-)
62.
by stephen_mcd 13y ago
The main criticism here doesn't really apply to any readers that apply the slightest effort in making the subscription process streamlined. Take https://kouio.com for example (a Google Reader replacement I've built), i
63.
Django-postgres-fuzzycount: fast / fuzzy PostgreSQL counts for Django models(github.com)
2 points by stephen_mcd 13y ago|0 comments
64.
by stephen_mcd 13y ago
If you've left finding a replacement to now, please take a second to check out kouio: https://kouio.com We posted it to HN a few days ago, and since then have had over 600 signups and processed over 1.5 million feed items!
65.
by stephen_mcd 13y ago
Love this question. It's 5 minutes to start with, but it gradually backs off based on a few things, like average time between the most recent items in the feed. Also right now due to the HN rush our worker queue's a little backed
66.
by stephen_mcd 13y ago
Why do you hate reading?
67.
by stephen_mcd 13y ago
Yeah we've discussed that today actually. It'll either be that, or the blog's favicon - not sure which but it's definitely needed.
68.
by stephen_mcd 13y ago
Yes to both! Apps for other devices are certainly coming, and they'll make use of the same API we've published.
69.
by stephen_mcd 13y ago
Will do, thanks again.
70.
by stephen_mcd 13y ago
1) There are a few little ui functions like "mark all read" still missing, those will come over the next day or so - we just wanted to get this out right now to give people a chance to do the one-step Reader import before it shuts
71.
by stephen_mcd 13y ago
Thanks a lot! I guess it's a little embarrassing, but it's not actually a proper blog - just a static page. We've just been too focused on polishing the app itself to worry about that :-)
72.
Show HN: kouio, the Reader you've always wanted(kouio.com)
49 points by stephen_mcd 13y ago|36 comments
73.
by stephen_mcd 13y ago
It seems like you've tried to support the set/store (sinterstore, sdiffstore, etc) methods across multiple instances in a non-atomic way - won't that lead to potential data loss?
74.
by stephen_mcd 13y ago
Makes sense. Thanks.
75.
by stephen_mcd 13y ago
Why does it need write access to my GitHub account?
76.
Bitwise Lua Operations in Redis(blog.jupo.org)
1 points by stephen_mcd 13y ago|0 comments
77.
by stephen_mcd 13y ago
Mezzanine intentionally works fine without Grappelli, just remove it from your project settings :-)
78.
by stephen_mcd 13y ago
Cool! Doing this from scratch is great for learning. I wrote the same article and demo a month ago, albiet a more comprehensive and complete approach using Mezzanine (a Django based CMS). The article focuses on how most of the features need
79.
Sandboxed Jekyll Hacks(blog.jupo.org)
1 points by stephen_mcd 13y ago|0 comments
80.
by stephen_mcd 13y ago
Direct link to the demo for the impatient :-) http://drum.jupo.org
81.
Building a HN/Reddit clone with Mezzanine/Django: Drum(blog.jupo.org)
4 points by stephen_mcd 13y ago|2 comments
82.
by stephen_mcd 14y ago
Ross Laird wrote an absolutely beautiful Mezzanine tutorial geared towards new developers: http://rosslaird.com/blog/first-steps-with-mezzanine/ That's part one, there are several on his site.
83.
by stephen_mcd 14y ago
Mezzanine contains a fabric installation that can take a vanilla ubuntu install, and have a production server up and running with Postgres, memcached, et al, in a single command: http://mezzanine.jupo.org/docs/deployment.html#fabric I b
84.
by stephen_mcd 14y ago
Mezzanine lead developer here. We'd been tracking Django 1.5 changes during the release candidates and were mostly compatibile with it up until its release. When it was released, a few issues cropped up - those were resolved within a day or
85.
by stephen_mcd 14y ago
Check out Gnotty if you're interested in actual IRC with a responsive mobile interface: https://github.com/stephenmcd/gnotty
86.
by stephen_mcd 14y ago
This is a really good question. I don't know the details around how zmq approaches buffering, I suspect it's much smarter than the approach used by the buffered Redis client in these tests (flush on every 1000 messages and every 200ms).
87.
by stephen_mcd 14y ago
In the Python flavour of these tests there's no concurrency occurring within a single OS process, all the work is CPU bound - adding gevent wouldn't achieve anything. Also as njharman mentioned, you're still running a separate broker with z
88.
by stephen_mcd 14y ago
gevent wasn't used in the benchmarks
89.
Mezzanine 1.4 and Cartridge 0.8 released(groups.google.com)
1 points by stephen_mcd 14y ago|0 comments
90.
by stephen_mcd 14y ago
http://blog.jupo.org/ Python, Django, and my open source work.

More ›