We're fighting fraud on marketplaces and spam on social networks.
Looking for another experienced infrastructure engineer to ensure we don't fall over with the clients we have in our pipeline.
1,036 karma · joined July 12, 2010
Previously: Instagram (Facebook), SnapBill
http://www.github.com/qix
[ my public key: https://keybase.io/jyud; my proof: https://keybase.io/jyud/sigs/gpvgfbbChwQ2UYzmAoa1yKWjK68nsglbOCQ63jOjak0 ]
We're fighting fraud on marketplaces and spam on social networks.
Looking for another experienced infrastructure engineer to ensure we don't fall over with the clients we have in our pipeline.
Definitely check the docs as Pete suggested, but would also like to point out that we'll take just as much data as you're comfortable with and/or can send for privacy reasons.
We have a ton of different signals that make our system tick, but based on whatever you send us it'll function as best as it can.
I never quite got around to functions, but there is basic support for arithmetic, for loops and rand()
[1] https://github.com/qix/c2brainfuck [2] https://github.com/qix/c2brainfuck/blob/master/samples/beer.... [3] https://github.com/qix/c2brainfuck/blob/master/samples/beer....
If bitcoins ever take off in the larger population I foresee trustworthy banks that will hold your bitcoins for you. Transactions from them can immediately be trusted due to trust in the bank that is sending them.
Currently we simply write each heartbeat to our redis database, along with the UTC time it occurred. Some heartbeats are global (string key) and others we have one per server (hash key, server name => last heartbeat). There is an API endpoint set up that some of our systems use to trigger heartbeats.
We then have a public page at a secret url that renders out the full status check. Pingdom is set up to check this page for "warning-status: OK" and if its not there send us an email. It also checks for "final-status: OK" and if that is not there, it triggers PagerDuty which will wake us up if needed.
I would prefer if PagerDuty could check it directly, then they would be our only point of failure.
-- Edit -- I added a screenshot to the post which should make it a bit clearer.
$ traceroute -m 100 216.81.59.173 | awk '{print $2}'
... cut ...
*
Episode.IV
A.NEW.HOPE
It.is.a.period.of.civil.war
Rebel.spaceships
striking.from.a.hidden.base
have.won.their.first.victory
against.the.evil.Galactic.Empire
During.the.battle
Rebel.spies.managed
to.steal.secret.plans
to.the.Empires.ultimate.weapon
the.DEATH.STAR
an.armored.space.station
with.enough.power.to
destroy.an.entire.planet
Pursued.by.the.Empires
sinister.agents
Princess.Leia.races.home
aboard.her.starship
custodian.of.the.stolen.plans
that.can.save.her
people.and.restore
freedom.to.the.galaxy
0-------------------0
0------------------0
0-----------------0
0----------------0
0---------------0
0--------------0
0-------------0
0------------0
0-----------0
0----------0
0---------0
0--------0
0-------0
0------0
0-----0
0----0
0---0
0--0
0-0
00
I
By.Ryan.Werber
When.CCIEs.Get.Bored
CCIE.38168
FINBasically it uses bcrypt with the site name in the salt, so you get a completely unique password that can't be reversed for each site. Each employee will get access to our master password which can be changed on a semi-regular basis and then we keep a tab-completeable list of all seperate site names that were used.
There is a 'pw sync' command which does send your password to the server (in order to confirm your access while updating saved comments/etc) but that is all.
Unfortunately while changing the 10 to 13 was a rather trivial change yesterday, now that the site has launched its not really possible. It would change and break everyones password on the site.
That said the entire thing is open-source, so anyone 'could' set up a version of password.ly with length=13 for themselves if they wanted.
If you're worried about not trusting anyone, then you would need to set up your own solution - but for most people thats completely out of their league. This is intended for people who would be typing their master password in different websites, and now instead only need to type their master password into one.
I can't argue against the problem of only having one password, but the small set never worked for me. I have a couple plans to integrate password migration into password.ly.
It's really just a MVP at the moment. There are quite a few improvements planned, and definitely a browser extension if there is any interest.
At the moment it is limited to the password generator, site names along with comments saved when you've signed up and a simple command line tool.
There is no database to lose, or not have access to if you're on another machine. It also has a command line client which works completely offline (though has sync if you're signed up and want to save sites/comments)
We're a small, bootstrapped, and profitable startup developing a highly flexible billing system for companies with 50 to 500,000 clients.
Hiring two full time developers in the next couple months. Contact me directly for more details.
The sub-commands are handled simply by having a primary baker that calls the execute method on the children: 'b git' => 'import git; git.execute(['b git'] + argv)'
Before pushing a job to beanstalk we encode the entire job a 'current-jobs' hashmap in redis, our worker transfers it to a 'busy-jobs' hashmap before processing, and then deletes it if successful or transfers back to current-jobs if failed gracefully.
This way we get the full useful features of Beanstalk (tubes, delays, etc) while knowing that our jobs are always sitting in Redis too if the beanstalk server dies (its persistence features are lacking) and our commit function is atomic (Redis MULTI/EXEC).
They have the man-power required to displace it, as well as the serious need... although the only potential solution they have come up with HipHop / HPHPi is really lacking in community support. Its open source but rather undocumented, and took an entire day to get set up.
If they could produce a viable alternative to PHP... something that fixes the clear fuckups but doesn't try to fix everything I think it would have a real shot.
They only last year enabled payments into South Africa and even that is through some strange bank interface for tracking/tax reasons.
As for the "yet-another" argument - I know. Convincing developers to switch to a language that is not leaps-and-bounds ahead of their choice language is hard to impossible. The reality is that I'm simply not happy with any of my options and decided it would be an interesting experiment to write my own. I'm not planning on writing any serious applications in it myself -- unless somehow it can pick up a community.
The remixing though I find interesting. This is simply an attempt at making something "better" than the other options. Languages get stuck with broken features in order to maintain backwards compatibility. I see this as a way to take the good parts of any languages and turn it into something I would like to use. I'd rather stick with what works.
[1] http://yannesposito.com/Scratch/en/blog/Yesod-tutorial-for-n...
If it was possible to print notes that could not be easily detected as counterfeit -- millions would be printed and it would devalue the entire currency.
In terms of actually finding website hosting for an application?
Saying PHP is the hardest was likely an over-exagguration, but the market for Heroku PaaS style hosting is growing massively and its Ruby runs on it very easily.
Its not hard (at all) to find hosting for either, the only reason in my mind PHP is harder is because of how beautifully PaaS works and that its free for small applications (good luck finding a reasonable free php host -- I know they exist but you'll have to dig through a whole lot of crud first)
Best for generating web pages is a meaningless metric, and...
To be honest my main issue with PHP relates to the defense that "PHP is not as bad as people like to say.". I mean, really - its true. PHP5 is significantly better language than the previous versions, and people always over-exaggerate how bad it is. The problem is that PHP is not a good language.
Whenever I develop in Python/Ruby I actually enjoy the 'feel' of the language, and I'm often impressed by the power it has to do really complicated things in simple concise instructions. Most of the time when I'm working with PHP the feeling is very different. I can perform the same operations but generally theres far more cruft, and a couple manual lookups to see why functions behave differently when hashes ("arrays") have numeric indices (I'm looking at you array_merge!)
Everyone has their own languages of preference, and personally I really dislike working with python (not too much experience in ruby) while dealing with websites. I cringe each time I'm forced to check the manual for random function behavior, but its not enough to make me move over.
What I'm really looking for is an improved version of PHP. One that keeps most of its style but removing the backwards-compatible crap. It looks like HipHop may go down that path in the near future (they've already added python-style yield generator functions)
Surprisingly (or perhaps not) its actually very effective for cheap hosting. Machines can handle quite a lot and rather than having many points of failure and failovers, you have one, and only one, single point of failure for the system (excl network connectivity/power/etc.)
Every couple of years something goes horribly wrong, but it turns out most users can deal with (or rather -- have no choice and are willing to accept) a five-ten hour downtime every couple of years.
While the problems with the REPL and trying to delete text are obviously a problem (and a hard one to solve), I'm not sure the issue with leaving out the quotes is. Obviously if the text was replaced with "I don't know anything called liz" instead of "liz is not defined" would be a minor improvement -- but at the same time anyone should be able to sit back, look at what they were asked to code ("Ryan".length) and notice the difference to what they typed (liz.length). The "Oops, try again" might be enough of a message there.