642 karma · joined March 31, 2007
Get in touch and I'll add you to the list.
https://github.com/wetalky/privacy-policy/blob/master/POLICY...
We're trying to be completely open with updates to this document, and we welcome outside commits. We intend to do the same with our ToS.
I'm not sure anyone has tried this before, so I'm really excited to see where this experiment goes.
It actually inspired me to draft up a blog post: http://blog.matthewghudson.com/post/9497957290/the-public-an...
alias show='defaults write com.apple.finder AppleShowAllFiles TRUE; killall Finder'
alias hide='defaults write com.apple.finder AppleShowAllFiles FALSE; killall Finder'How long has the refactor been on your mind? Has it been at least a month or two? Has your mental picture of the rebuild been consistent, or does it change week-to-week?
Here's my advice to get you going: Write down your general refactor plan in detail. Next, create a todo list / timeline that gets you to production deployment as quickly as possible based on your current codebase. Focus on other things a bit. Launch, marketing, etc.
Once this thing has been out in the wild for a bit, reassess that refactoring plan you wrote down and see if it still makes sense based on your application's performance - both as a product, and as a piece of software.
Imagine when folks are able to be just as discerning when they are shopping for clothes (was this made in a sweat shop? is it american-made?) or grocery shopping (were these chickens treated humanly?).
Good work man! The digital democracy is coming.
Big picture, the W3C spec is not what matters here. What matters is making the same HTML document render exactly across different browsers. So maybe they could drop <html><head> according to W3C, but does that break the document in other browsers?
My guess is that Google doesn't care about the W3C spec in this specific regard. What matters is delivering the smallest document possible that can be rendered by as many browsers as possible.
*Grammar edit.
I got a new job and just couldn't focus on it. Bummer!
Anyone want the source code?
Don't say that HTML5 (canvas) has a long way to go. It does - but the basis for your argument is wrong. Don't compare two different projects - with different goals, and in different stages of development - and then say one is weaker based on its current phase of development.
I definitely recommend it: http://video.google.com/videoplay?docid=8448974573505946013
I've since abandoned the project but it's still online. Cool to see someone pick up the banner though.
>>> x = re.compile("[\\?&](seller|item|hr)=([^&#]*)")
>>> x.findall(url)
[('item', '290277158797'), ('seller', 'la-wheel-and-tire'), ('hr', 'http://shop.ebay.com/?_from=R40')]
>>> x = re.compile('(?:(item|t|hr)=(\d+))')
>>> x.findall(url)
[('item', '290277158797'), ('t', '1227377775000')]
I can't for the life of me figure out how to get the hr value. I started messing around with regex again, but no luck so far.
I can do the same with Python's string methods:
>>> hr_start = url.find('hr=')
>>> hr_end = url.find('&',url.find('hr='),len(url))
>>> url[hr_start:hr_end]
'hr=http://shop.ebay.com/?_from=R40'
It's just messy as hell, it'd be nice to do everything in one swoop.
Nothing to be "depressed" about. Happens all the time.
"Happens all the time" is a reason not to be depressed? I think "landscape changes" take place because someone/some group got tired of being depressed and actively sought some sort of change.
OTOH, this is an excellent example of the advantages of being small and nimble - you can adapt quickly while the big boys are stuck struggling.
What? The big boys are eating Apple pie because they, I assume, had an easier time getting to the table than the small and nimble.