Timothee

Mailgun changed their Optimizely config to switch all images to kittens and text to kitten-related copy. Well played.

That's great to know! I have a few forks that are there only because I wanted to offer a tiny change to the doc or the website, etc. but I thought I'd have to keep them around until it was merged. (I can certainly leave them there, but it leaves a big mess of mostly untouched forks)

edit: my git tip will be "git stash --keep-index". This stashes only the stuff that you haven't staged. I've been using it when I want to keep unrelated changes out of the build process before committing. Or you can run that, and then "git stash" to have two (or more) separate stashes from your current state.

The thing you need to remember is that CSS Zen Garden was big around 2004 and most of the designs are from that period. The site was a big inspiration at the time to show that with a single HTML file, you could completely change the appearance of a site. This was huge!

So the downvotes are likely coming with a thought along the line of "how dare you show disrespect for that venerable site!".

For example, if you're looking for a job as a designer or an engineer (or whatever else), you're likely to have a site to show some of your projects. Potential recruiters that end up visiting your site can then be advertised to specifically.

I was also thinking of blogs: you can probably recapture an audience when you write a new post. I.e. one of your posts gets popular on Hacker News, but people won't necessarily start following you or subscribing, but you could advertise for your new posts later.

I'm surprised not to have heard of another story similar to that Google one since then, but there is potential if you think about it.

edit: actually, I remember reading about a guy who had targeted his significant other using a Facebook ad for some purpose (maybe a proposal?).

https://twitter.com/olesovhcom/status/301964179890401283

Translation: "To get your best staff poached by Google, just let them publish patches on github.com".

I find it interesting/odd to blame GitHub. (he does in a later tweet, saying it let them see the "real GitHub")

Anyway, just some good ol' drama.

What is this referring to? Google brings up nothing at all on this paragraph.

What do you mean by that? (honestly curious)

If it's over, I doubt a one-second difference will make one (difference).

I agree but one thing I've realized recently is how all the history and discussion happening in a PR tend to be lost once the PR is merged. Not completely lost because it's still there in the "closed" PRs, but undiscoverable.

For example, you come across one line that doesn't make sense to you but you sense that there's a reason behind it. 'git blame' will tell you the specific commit but the commit message might not be explicit and you won't be able to find the corresponding pull-request easily.

I mentioned it on Twitter and exchanged with a GitHub employee that seemed to understand my issue. Hopefully they'll improve on that…

Where you follow the given steps carefully and one fails because whichever version of something is not the right one, then you end up in a weird state where you have a hard time going back to how your setup was before, and you have to google things like "Compiler error: missing dependency foo.h" even though you can see that foo.h is right there. You then finally fixed the foo.h error to discover that you need to update Ruby for whatever reason, but the system doesn't pick up the version you installed with Homebrew anymore but is using the old default one, you then start updating Homebrew. Etc., etc. until you don't even know what you were trying to achieve in the first place and you are now super irritable.

(yes, I had a recent experience with that kind of yak shaving :))

For example, you could go to Ikea buy something there (with a credit card to leave a log of a transaction) and mail your letter. Ikea because they aren't that many Ikea stores but it's not out of the ordinary to drive quite a while to go to one.

My point is that if you have reasons to want to send an anonymous letter, you might want to make sure that a drive that doesn't fit your regular patterns can be explained by something reasonable.

edit: I'm not sure the credit card is a good idea. Likely not. It might be better to pay cash, and keep the receipt. This way, you can't be immediately cross-referenced, but if asked, you have an alibi. Yeah, I really don't know. :)

To be fair to your skepticism, I have probably followed Twilio more than you've had. I seem to remember that they switched to Flask, so I don't think it was technical debt that they had to work around later on. (like it might have been the case with Facebook and PHP)

Let's say that "Twilio uses Flask for their API" answers the question "can it be used in production?" (or "is it a serious project today?"). "Should you use it in production?" is where context matters more.

"Flask-RESTful was initially developed as an internal project at Twilio, built to power their public and internal APIs" http://flask-restful.readthedocs.org/en/latest/

I think the page doesn't emphasize enough the easy customization of these buttons: you can set the class names and base colors in one file and Sass will create the CSS for what you want. "Base" colors because the gradients, highlights and glows are then derived from only one color.

See this file in particular: https://github.com/alexwolfe/Buttons/blob/master/scss/_optio...

The defaults look pretty yummy but the customization is key for your own use IMO.

That being said, I still find it odd to bring up the inconvenience of not being able to use Facebook Events.

A+++++ would get hired again.

This statement lacks arguments supporting it.

DOZ is "Search and Social Media Marketing done by professionals" according to their website, and Moz is "Software and Community for better Marketing". IANAL but I feel like there could indeed be confusion between the two, especially considering DOZ was CapSEO before, and Moz, SEOMoz.

So now it's a matter of trademarks and specifically timeline on who was first, but the details are not provided in the post.

I like the humor of the machine but I arrived at the tests about conditional but couldn't remember the command to ask for a key. A way to get back to what I've seen could be nice.

To me, the API endpoints should behave the same way in a browser as with curl without ever redirecting to the login page.

But, once again, it might have been fixed in the meantime… I haven't tried recently.

With curl, the doc says to use a blank username and the token as password in Basic Auth. When I do that with XMLHttpRequest, the token is completely ignored and the main site's cookie is used. There is no way not to pass the cookie with XMLHttpRequest unfortunately, so I would have to rely on if the user is logged in or not. That would bring other problems: I could only use the API for one account at a time for example, and I would have to add checks to see if the user is logged in, etc.

So my work-around was to write a proxy that would just pass around the requests to Heroku and the response back to the XMLHttpRequest client. (https://github.com/Timothee/Passeplat) With it, I can make the same requests I would make to https://api.heroku.com but instead make them to mypasseplatinstance.heroku.com.

Making this a Heroku-ready app is of course not a coincidence: my plan is to use my Heroku instances (the proxy and the yet-to-be-written git clone) to bootstrap a couple of Heroku instances with the user's own Heroku account. Then the extension would use these to start up other apps. I like the bootstrap idea: it's like compiling a compiler. :)

I'm now realizing that it might even be done with a buildpack… I'd have to look into that. (that would remove the need for that second "git clone" app) Hum, I'll really have to look into that! That could make things much easier and cleaner. (and also cooler)

There would still be the issue of specific configurations and add-ons to deal with, but that shouldn't be too hard if the rest is done.

edit: I haven't checked if this is still a problem with today's announcement. Also, I contacted Heroku support about it, but they only suggested I use a proxy.