z77dj3kl

This is a really good document:

https://apple.github.io/foundationdb/data-modeling.html

I have been studying these key-value stores with efficient range iteration lately (such as LevelDB, RocksDB, BigTable, FoundationDB, etc). This is a great reference on how to make such a simple abstraction do a lot of useful things.

I'm pretty sure it'd be easy to at least fingerprint/classify your "driving style" given enough of even crappy accelerometer data.

This would be more fun if this could be done with the median. Then the "true" answer to any question would be 50% on both sides. (For example, more than 50% of people have a lower income than the mean income, due to extreme outliers.) I suppose in lay language the distinction gets muddled.

The Friendship paradox has nothing to do with what people think: it's an observed fact and related to the way that node degree in social graphs work (or random graphs in general).

R is used almost exclusively in stats. Most in maths use python, c++ (there's a surprising amount of hpc code, e.g. pde solvers and other stuff floating around in c++), matlab, etc.

What... Have you seen the piping syntax in tidyverse? It's incomprehensible unless you put in a lot of effort to understand all that's going on.

Thank you! Do you know why they were looking to replace Stubby with gRPC? It doesn't seem to me that gRPC is quite customizable enough currently to hook in all the monitoring and tooling that I imagine Google has.

And yes, the completion queue approach is pretty cumbersome, would be very interesting to see how stubby went about it :P

I was hoping to see something about xDS. I've seen a lot of work being done on adding support for it in gRPC on git but (as usual with gRPC) the docs and blog posts seem to be rare and terse, so I haven't had a chance to learn it yet.

Also, does anybody know how gRPC is used at Google? Why do they support its development (other than GCP clients)? I'm under the impression Stubby is a completely different codebase and is far superior and fully integrated in their stack.

How is gRPC used at Google?

I know the Cloud APIs use gRPC, but only on the client side. But I'm under the impression that gRPC and Stubby (the internal RPC framework?) are completely different codebases (even if they are allegedly similar).

The job market is a lemon market for employers.

Very cool! OT but is there a list of protobuf benchmarks somewhere across languages/implementations? How does it compare to JSON or just dumping raw bytes?

Do all defendants not have the right to an attorney in criminal cases?

If evidence is obviously (or with high chance) disputable, then it puts pressure even in those cases where the attorney recommends the defendant to eventually plead.

Or maybe the attorneys available to those who can't afford are just crap in general?

Hope it was those leaving that were sketchy and not those left! Sounds hard as it was already.

Thanks, this is hilarious

> Inflicting that complexity on you all would help with margin control, but ugh. What we've done instead is set a blended price that fits most apps running on Fly.io, and decided to just eat the extra cost from outliers. If you want to exploit that, run an app in Sydney with a whole bunch of users in India. We'll lose money on your app and you will win one round of capitalism.

No, that attack is trivial and direct, that's the problem.

There is a whole field (now relatively mainstream) of differential privacy, concerned with answering questions such as "can I be correlated and de-anonymized across queries" (query might be "what's your current cohort id?").

Is FLoC not built on sound principles of differential privacy? That would be a big shame on Google.

EDIT: Huge shame on Google! From their FLoC whitepaper: "We want to emphasize that, even though differential privacy is now the de facto privacy notion in industry and academia, we decided against using it as our privacy measure for building audiences."

What in the world are they thinking?!

The standard itself looks kind of good, honestly! Have a look at 4.2 (pg 9):

https://static1.squarespace.com/static/5c6dbac1f8135a29c7fbb...

I think tech as an industry has come quite a long way in the past few years of clarifying (and hopefully adopting) what security best practices is. This, OWASP, and other similar initiatives are good: you can have a rough checklist of what's required to have a roughly "secure" app, and what the common loopholes are. This is not easy stuff.

I don't know what this means for the institutional/enterprise side, whether certification will be meaningless, etc. But the document itself seems relatively sensible to me!

The reason for the NDA is obvious: Facebook doesn't want you to know that there are people doing this job. Facebook doesn't want you to even realize that this job needs doing, they want you to think that the platform is just clean and nice without any of this icky stuff.

It's part of what makes Facebook enjoyable for end users, and that they've managed to do: keep the platform clean of most awful things, but it comes at a heavy cost. People don't notice this cost, and that's by design.

Looking very promising, I'll definitely try this once it develops a bit more. Some things echoed by others as well:

- Need clarity/support for timezones (this is critical)

- Months need to be laid out correctly

- I looked around for a bit and didn't at first find any demo, until then I realized it was embedded in the page! Add a link in the navbar that says "Demo" that takes you to that page, and a big demo above the one on the front page saying "Demo:"

- "Open source Calendly alternative" might be a good start as long as you're still piggy-backing off Calendly's hard work in popularizing this kind of idea, but eventually you want to start defining your own product and stand on your own two legs

- I love the pretty design!

Interesting video on Canadians having to do math to win prices: https://youtu.be/jOmnx-V1zBo

Tested only on privacy-respecting browsers? That's what sites mean when they have these "soft" banners on non-supported browsers. If it's not tested on chrome, then users on chrome might experience issues.

I agree, I think the image of Effective Altruism is largely shaped by the somewhat unique group of people who flock to it — in particular those who are very vocal about it.

The fork announcement was announced as a response to the Elastic stuff. I don't think they made any predictions about when it'd be ready in that blog post, so I'm not sure why they would've underestimated anything?

My favorite "conspiracy theory" is that AWS intentionally creates stupidly verbose and numerous headers in all of their APIs just to up the bandwidth usage a few bytes per request at a time.

Hosting a site like this doesn't cost much, their business model is probably to add additional paid features as they go.

It's nothing new, but I also don't think it's nefarious.

I'm not sure if normal scanners detect UV light, but that would break a good chunk of their tracking purpose these days if they were not detectable in scans.

To indicate I edited it (to make it grammatically correct in my sentence).

Do you block Google trackers aggressively? reCAPTCHA uses that very heavily: if you allow all of their stuff and they track you across the web, you'll have to basically never do more than click the button. On the other hand, if you take your privacy seriously and are aggressive about tracker blocking, you'll have a pretty awful time.

I imagine hCaptcha doesn't have enough trackers sprinkled around the web to use those as signals for this.

Seems a bit like Plausible only pays lip service to some of these ideas. Merely 5 months ago the co-founder touted here on HN about how they are "big fans of open source so wanted as permissive [a] licence as possible" [0], then promptly went and changed the license to a strongly copyleft (AGPL) a few weeks later!

They might well be the next Elastic/CockroachDB/MongoDB/etc. Or better yet, they might do the classic bait-and-switch later on: get developer buy in with a good story about openness, then once they'd gotten enough of a customer (aka dev) share, do the switch.

[0]: https://news.ycombinator.com/item?id=24700565

Rust originated from Mozilla...