akarve

this link is now hammered because of cloudflare. hard day for the internets.

there has to be some missing information on how he found the area of water that fully consumed exactly that amount of oil as it simply doesn’t make sense without that. for instance one can spread a teaspoon of oil over 1, 2, n square meters and at some point the oil goes from m later thick to one to less than one.

more popular than i expected

we know what's important here on hn

This is one of those “so cool yet so silly” brainstorms that I’m grateful someone was audacious enough to entertain. I’m both relieved and saddened that it never came to fruition.

There’s a word, chindogu, to describe things that are less than useless. In some sense this project engendered more problems than it solved. Like so many other attractive brainstorms.

Most SO answers were non-answers or word salads. Thankfully one of you added an answer explaining that the cursor is already straight given that it must be visible from the graphics coordinate origin (upper left) and is 45 degrees wide.

https://ux.stackexchange.com/a/149837/45927

I was sure to read “the forces of vim have invaded our headquarters and now hold our CEO hostage.”

Hard agree. Civil & mechanical engineering have a culture and history of blameless analysis of failure. Software engineering could learn from them.

See the excellent To Engineer is Human in just this topic of analyzed failures in civil engineering.

Technically I think so, so there’s a tiny bit of faith for RSA but absolutely none for primality in general https://en.wikipedia.org/wiki/AKS_primality_test

If you just make up a number claim it’s prime and nobody disputes it

You can test if a number is prime in polynomial time, much faster than a sieve. There’s no need to test every divisor to know whether a number is prime or not.

Algos like RSA generate large primes millions of times every day—-there’s nothing to take on faith.

He's probably a *-sulfide or copper-* expert. Or maybe just a physical chemist that the press is ginning up. Actually, the latter. His page doesn't even mention copper or sulfide; and makes only one mention of conductors.

https://chemistry.illinois.edu/jain

Jack Dorsey is corroborating it on nostr npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m

No. The backups have their own secrets and no relationship to one another. You register them as distinct keys with each app.

There’s no need to carry both keys. Leave one in a secure location. Carry the other.

Use a calendar app. It parses and translates appointments into local time as an essential part of its existence.

Algorithms do not shun creativity. They are born creatively. But they do set a high bar for new contributions. You either beat the existing complexity or you don't.

If you can improve upon either the space/time complexity or even the comprehensibility/maintainability of algorithms, the industry is your oyster.

This is close to home. Our approach to DevOps for ML Data is to use S3 as the git core and build immutable datasets and models on top of S3 object versioning. I wrote the piece below on "Versioning data and models for faster iteration in ML" earlier this year. The key idea is for every model iteration to be a pure function F(code, environment, data). Ideas welcome: https://medium.com/pytorch/how-to-iterate-faster-in-machine-...

The question one must ask: where were the chances of zoonosis greatest (where did people have the most contact with relevant animals)? and everything else falls into place

The reported dosage is less than half what the Chinese Government recommends (500mg x 2 (BID)). So it's possible that they didn't hit the effective dose. https://medium.com/@balajis/the-official-chinese-government-...

Not quite. Abstraction layers like min.io support versioning. More importantly, Quilt manifests only require a "fully qualified physical key" that points to the data. In theory, the manifest can work with any URI: S3, local disk, etc.

Here is an example of the "Irish Setter" query: https://open.quiltdata.com/search?q=irish%20%2B%20setter

You would type "irish + setter" in the search box.

You can do that :) See here for search syntax https://www.elastic.co/guide/en/elasticsearch/reference/6.8/... (there is a faint link under the big search bar). Let us know how that works for you.

Good questions. First, services like open.quiltdata.com and Amazon's Registry of Open Data cover the S3 costs for public data. So that's one incentive. Second, the cost of cloud resources are highly competitive (if not superior) to on-premise data centers (see https://twitter.com/mohapatrahemant/status/11024016152632238... I don't think it's correct to think of S3 as expensive.

There are many ways to shave S3 costs (e.g. intelligent tiering, glacier), but at some point the data become so slow to access that you can't offer a pleasant user experience around browsing, searching, and feeding pipelines.

Most importantly, the "my data, my bucket" strategy gives users control over their data. A university with their own bucket has more control over their data than they do if Google, Facebook, etc. host and monetize it.

The package landing page is essentially that: a list of all of your datasets. This is constructed from the special s3://.quilt/* directory. Since a Quilt manifest is a list of keys, you can compose N manifests into a single manifest using the API, see e.g. https://docs.quiltdata.com/advanced-usage/working-with-manif...

That is an interesting idea. What kind of performance could we expect, especially in the federated case of searching multiple buckets? Elastic has sub-second latency (at the cost of running dedicated containers).

Contingent upon support in something like ceph or minio, yes.

We have a data curators program on Quilt and I encourage you to apply (page bottom on open.quiltdata.com). For high-value public data sets, AWS's registry of open data will, if accepted, cover the costs of storage and egress. We went through this process with Allen Cell and I'm happy to help.

Just peeked at Ohayo and it looks neat. Feel free email me: aneesh at quiltdata dot io. We have also been thinking about integration with Jupyter Lab data explorer and perhaps there's a common shim that we can use.

Oh I would love to get the UH Cancer Center data into Quilt! Do you happen to have an S3 bucket with that data live? If the bucket is publicly permissioned it should "just work." We can talk about indexing the data for search. We are comfortable in the TB-PB range :)

I will look more closely at Ohayo.

Not quite ;) S3 is the primary data and metadata store, so that the rest of the stack is a pure function of S3 data (including Elastic). We don't use git at all yet. We use S3 object versioning and then capture the version, SHA-256, etag, etc. in a JSONL-based manifest https://open.quiltdata.com/b/quilt-example/tree/.quilt/packa.... Said JSONL manifest is simply a "locked list" of all the S3 objects in that package. The same manifests can be checked into git for fork/merge of data sets, but we're still exploring the right way to do that.

I'll let Kevin answer the database fragments question.

Not yet. But it's closer than one might think. Spaces has an S3-compatible API, and we have plans to use something like min.io to make Quilt work "all the blobs": GCP, Azure, Digital Ocean, etc. OSS contributions welcome :)

What would you use Quilt for in Spaces?