kingryan

yeah, reminds me of working at technorati in 2005

You mention meta.org, you know you could work with us on it https://chanzuckerberg.com/join-us/openings/?team=engineerin... (search "meta" on that page)

As of several years ago the putlic http endpoints would easily do 1M/sec at peak times. Not just api, but web, images, et al.

In California you can get a DL without proof of legal residency.

Nope. (I work there).

But no one can do anything to generate new webhooks.

Bolt (bolt.com) - San Francisco, CA- https://bolt.com/jobs

Bolt is radically simplifying online commerce in a way the world has never seen before. We combine top technology with a very careful and unique approach to processing online transactions. We are an elite, engineer-first team with lead players out of Facebook, Twitter, Google, Apple, PayPal, and CyberSource adding a few core members to our team. In the middle of our process, we do a product/tech deep dive at which point we promise there’s no going back. :)

A bit about Bolt’s culture:

- We care about output, not input or “busyness"

- We value our time immensely.

- We prioritize respectful directness

- We think Silicon Valley startups are built for failure, and are doing things radically differently

- We don’t care about PR or any startup vanity

If you want to join a team of seasoned professionals that prioritize productivity, alignment of vision and unyielding commitment to quality, then email me directly: rk@bolt.com.

... and pay taxes

Bolt - San Francisco, CA - https://bolt.com/

Bolt is a new payment platform that radically simplifies the exchange of money; it’s a reimagined money moving engine to solve the largest unsolved problems in payments.

We are an elite team of engineers from Facebook, Twitter, Google, and Apple adding a few core members to our team.

If you want to join a team of seasoned professionals that prioritize productivity, alignment of vision and unyielding commitment to quality, then email me directly: rk@bolt.com.

We’re only replying to serious applicants with 5+ years of high production experience.

Bolt | San Francisco, CA | Platform, DevOps, Security and Infrastructure Engineers | Full Time | Onsite

https://bolt.com/jobs

Bolt is a team of elite engineers from Stanford, MIT, Facebook, Twitter, Square, and other top companies. We are passionate about technology, finance, and the future of payments. As we explore the bleeding-edge in payments and fintech, we're looking for teammates who are ready to join a top team and take charge of large responsibilities as we sail deep into uncharted waters.

Though the sneaker page makes it very clear that its not ready for production use.

If you're classified as an "insider" then you can't even trade in the trading windows without a 10b5-1 plan.

So at TWTR (I'm a former employee) knowing things like the MAU would probably make you an insider, which means you can only sell on a plan.

Not knowing the MAU is a blessing in this case.

Right, because no matter how much RAM you put in a machine, access is always the same speed.

The messages are not repeated in fanout, just the ids. I guess you would know that if you actually the links.

San Francsico, though remote work is plausible.

Twitter is looking for all sorts of good engineers. The up to date list is always at http://twitter.com/positions.html.

yes

San Francisco: Twitter is hiring like crazy.

We're working on about a million interesting problems at scale, with resources and the ability to open source almost everything. We also have a good deal of fun. twitter.com/jobs or ryan@twitter.com

Version 1 UUIDs require 128 bits.

Except in email everyone has a separate mailbox. On twitter everyone's mailbox overlaps and there are an infinite number of possible public views of the tweets (searches, lists, etc.)

NTP seems to work fairly well for this. It takes into account network latencies and attenuates over time.

That's the time of the first tweet. It saves us 30-something years of id space.

It turns out big problems are big. We're moving moving existing data to cassandra and putting a lot of new (mostly internal) data on cassandra.