millisecond

I don't think that's emphasis, but a general rule that you should break if you need to.

B is tough. Would be interesting to see the sum of the karma of all users who upvote a single one.

Another thing to watch would be the mean user karma of all votes. A bunch of low-karma vote stuffing would actually bring a post down.

If you can get a ton of massive karma users to upvote and game this, maybe you should just get in by default?

NYC ONSITE: Roost (YC S14) https://goroost.com

Roost: - Is the leading SaaS provider of web push notifications. - Is currently handling over 100k requests / minute. Scale and speed are incredibly important to us. - Well funded, high growth.

We’re looking for engineers of all stripes who: - Has experience with AWS cloud technologies. - Prefer deep experience with node and/or Java. - Takes scaling incredibly seriously. - Experience with NoSQL databases at large scale. - Experience in and willing to help with ops. -Wants autonomy to create awesome products

Benefits: -Flex vacation policy -Manhattan offices -Healthcare -Competitive equity

Email casey@goroost.com with resume for more information.

I wonder if they're protected large existing revenue streams that would be reduced to 0 if they opened up all patents to anyone.

Awesome that you're using Roost! Founder of Roost here, feel free to reach out if you ever have questions on our side of things.

Sounds like a magnetic coupling to the motor rather than gears, not no moving parts at all. Imagine it saves wear-and-tear and is easier to disengage on winds that are too strong.

Once these trucks are out there in numbers, the financial incentive to eliminate drivers will be so high (and there will be safety data) that the laws will change to allow true driverless.

37 Signals blogged about running a startup to good effect. Although worth noting that I believe they stopped doing conferences and lightened up on blogging considerably in the past few years.

There are several safe-guards, with more to come.

The biggest one that's coming is being able to unsubscribe directly from the notification pop-up itself. This will shut down abusers very quickly.

Beyond that:

-All notifications traverse GCM. Which means you've signed a ToS with Google and they can shut you down (also a little scary).

-Opt-in must happen on the main page, or have the main pages "consent". This prevents iframed ads registering people, for example.

-9/10 pushes must display a user visible element (that will have the unsub feature) which prevents people from being malicious on the background Service Worker thread.

More will come as this feature develops and it's seen how things play out in the wild.

I'm one of the founders of Roost (YCS14 - goroost.com). We're based on this standard and have been (a small) part of getting it out.

Happy to answer any questions on the base tech or our layer on top of it.

This (and current Safari support) is what we (Roost - https://goroost.com - YCS14) are building off. Moving toward a complete web-push suite that supports all browsers on both desktop and mobile. Long road in front of us, but it's going to be an exciting world.

FWIW, I've hearing "late this year" and "early next year" from some contacts.

Hey, check us (Roost YCS14) out at https://goroost.com - we already do this in a way that will abstract the browser part so you don't have to change anything once the other non-Safari browsers come online.

Fixed :)

Yeah, Safari doesn't even need to be open. I use Chrome as my main browser but subscribe to interesting things with Safari.

Chrome is definitely coming soon... _maybe_ have something to announce mid-August-ish to coincide with some important YC events ;)

Shoot me an email at casey at roost.me and we can coordinate.

Interested in doing Web-Push on the same data? Can hook you up to a totally free roost.me account.

We're waiting on some tech inside Chrome / FF. Our stuff relies on a new standard that the browser manufacturers have to integrate. We know they're all (even MS!) working on it, but hard to give a definitive timeline - hopefully measured in a few months.

The opt-out controls are built into the web push system, which should keep the channel relatively clean. If marketers are abusing it, users will very quickly deny their future pushes (after the fact, Safari -> Preferences -> Notifications). If email had such a built-in opt-out feature, I doubt spam would be what it is today.

Beyond that, we're definitely aware that there needs to be a steward of the channel. If people abuse it, we lose. There are things that can be done with throttling that we hope to implement soon. Hasn't been necessary to this point.

One of the founders here, open to any questions!

HLL also has two nice real-world optimizations possible depending on use-case.

We're storing 100,000+ unique counters, but only around 1% have more than 100 unique objects counted. Some of those 1% have millions of records so HLL is very useful. As the HLL itself is a fixed size (~10kb for decent accuracy) regardless of #counted objects, in the small case you can replace the HLL with a pure set of counted values and produce a HLL when it grows beyond a bound. Because you're storing the raw values, the transition to HLL is seamless.

Once you've moved beyond raw storage of values there's a harder but still space-saving technique. If you look at the raw bytes of a ~10kb HLL structure with "only" 10's of thousands of counted values around 90% of them will be zero. Below a certain bound it can save a lot of space to have a map of locations and non-zero byte values rather than a raw array of bytes.