malgorithms

> Without sample-and-hold circuitry, this meant the stereo channels were approximately 11 μs out of sync.

Am I correct in assuming this wouldn't be perceivable on a stereo, based on the speed of sound?

I wrote the “ai” for one of the early popular forks of Slime Volleyball. I have a lot of fond memories! Recently I wrote a modern interpretation of the game in pure TypeScript/html canvas. It requires a real keyboard or gamepad - sorry no phones. Some of the single player ooponents are pretty fun. It’s at https://tippycoco.com and it’s all open source.

You’re probably in the process of learning this now, but in case you’re just getting started: effective multiple myeloma treatments are being approved at an astonishing rate. It was a death sentence 20 years ago. Now it’s indefinitely treatable for many people.

A close family member was diagnosed 5 years ago and went through a stem cell transplant at Dana farber and the cancer still hasn’t returned…although statistically by now I believe it should have. But when it does return there is now a massive menu of next treatments for her that will likely hold it at bay.

Things are changing so fast now that I’m not sure the stem cell treatment is the first step.

Good luck to your dad.

I'd been waiting/hoping for someone to make something like this. Well done. A few ideas that will not clutter the UI but you might consider:

  - when a user changes the score slider, encode that in the URL with a hash tag, so they can bookmark the page with their preferred settings
  - a left button allowing me to step back to yesterday's news
  - to simplify newsletter signups, just accept an e-mail address right on that page
  - your **advanced** options:
    - have GPT score each news story across common labels: science, politics, entertainment, news, etc. Then allow these as a filter. If I want to see the top science stories of the day, that should be easy.
    - have GPT write a 2 sentence summary of each story as a lead-in after the headline title
    - a user/saved whitelist/blacklist of news sites
    - any advanced setting should be shareable. For example, if someone puts the effort in to make a page with just Australian news sources, focused on sports, with a minimum score of 5.0, they could save that with a title that can be shared for anyone.

Congrats on a well-executed project.

According to GPT-4, and I think this is a good summary: A "Foundational Model" in AI programming refers to large-scale machine learning models that serve as a basis for a wide range of applications and tasks. These models are pre-trained on massive amounts of data and can be fine-tuned or adapted for specific tasks, domains, or applications.

One of the most well-known examples of a foundational model is the GPT (Generative Pre-trained Transformer) series developed by OpenAI. GPT models, like GPT-3 or GPT-4, are trained on large datasets containing diverse text from the internet, which enables them to generate human-like text, answer questions, translate languages, and perform various other tasks.

Foundational models are significant in the AI field because they allow researchers and developers to create a wide range of applications and solutions without having to train a new model from scratch for each specific task. This approach saves time, resources, and computational power while still providing a high level of performance across different tasks.

Slime Volleyball directly inspired it! I mention that on the about page, https://tippycoco.com/about . And ~20 years ago, I actually programmed one of the popular Slime Volleyball bots.

I say this because investors sit on boards and work alongside these lawyers once they invest. They learn pretty quickly who is great and can often give very direct recommendations: a specific lawyer, not just a firm. At the startup stage you should choose the lawyer, not the firm.

If you’re talking to investors at all, ask them for recommendations. That’s a good place to start.

As an example of the magic referred to in the post, here's some encrypted text that could be read by `pg` here on HackerNews: https://pastebin.com/raw/bxRaymaB . As explained in the article, the unlocking step trusts HackerNews at one step in the process.

P.S. I'm the blog post author. BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zk7RUjCs bLeGBWHRNe047t1 63n5tVSjvbZwtwt nQVqdDHEZIR4kgD PpRDesKecb1Y4U2 jcnOUuLfKvsiGZY PP7SbO79zoRFEuv e8gXRm44Brjfdym iwy2mGXI9VW5PDf WMxwJdTflgruGMK SUkEhjqwUOEc8KR AC6aF8iJadgq3bz oGMLpY750H1Deus EGPgtQQVIeh05mx HY7K3oFOn3SjeS3 cL1duil9YgmZi1y zKu3bfFSbjelgzc 5UMZ42xTJJs0gT. END KEYBASE SALTPACK SIGNED MESSAGE.

Official response here - I work for Keybase.

This article isn't just misleading; it's entirely false, and the title is both highly damaging AND false. Someone below threw out the word "libel" here. I don't know about that, but it's incredibly frustrating to read this title on HN right now.

* THERE IS NO BACKDOOR HERE. Neither the especially scary kind suggested by the title (everyone assumes encryption breaking!), nor the coerced attestation kind suggested in the text.

* Put simply, KEYBASE HAS NOT BACKDOORED its apps and cannot coerce them into signing someone else's Stellar address into a profile.

Further, THIS USER VOLUNTARILY GENERATED A STELLAR PRIVATE KEY. What follows is the flow for generating a Stellar wallet and attaching it to one's profile. The author of this post went through this flow on Feb 4, 2019:

1. Visited the "wallet" tab in the app

2. read a brief description of Stellar in a modal.

3. Saw our disclaimer in a modal (not hidden - printed out front) about how scary cryptocurrency is, how it's permanently attached to your identity, and how it's important to backup your private key if you plan on leaving Keybase.

4. Only once they accepted that, then their client app (not our server) generated a Stellar private key. The app signed the public Stellar address into his sig chain. And the Stellar private key counter-signed, proving bidirectionally. The stellar key was then encrypted in a way so their devices could gossip them to each other.

So to be clear (1) this writer did in fact have that Stellar Key. And (2) we, Keybase, did not. And (3) they knew they were doing it. I encourage anyone curious to go try it out -- the flow has not changed.

I don't understand what their agenda is here. Offering some charity, perhaps they went through this flow late at night and forgot. (Looks like they generated their Stellar account well after midnight in Europe.) But the claims in the post are just false.

I accept some people don't like the opinionated cryptocurrency partnership Keybase has formed. We do like Stellar. However, that doesn't change our security story. Nor does it force users to set up Stellar keys, and something like half of our users have not. Actually - we spent a great effort building around the fact that many users wouldn't be interested in the cryptocurrency side of things.

For those who generate Stellar keys and then change their mind, not wanting them, we'll add the feature to delete all of them.

Anyway, this is just not true. All of it.

Nope, that's not the case, in fact you'll get the Lumens automatically within a day or so. If you want to _continue_ after the first month, you'll need to click the button in the app saying you want to. But you have a month to do that.

Not a dark pattern, an accidental leftover string from our testing. Any account registered before today qualifies. I'll deploy a fix to that shortly. Update: deployed, although you may need to restart your app to update the text.

This was a summer internship project at Keybase, and the whole team is thrilled with how it turned out. The OP of this post is the author of the project and would be happy to answer questions here in HN.

One of the biggest devops pain points for a large team and large infrastructure is updating N servers every single time a team member is added or removed. Of course there are some other solutions to this problem, but the Keybase one is extra slick and just works automatically once it's set up.

It's also entirely powered by an open-source 3rd party bot, so it can be forked for improvement or to build something else triggered by cryptographic team membership changes.

Further: Keybase is a security product and it wasn't deemed worth the risk for the CEO. And while Keybase isn't made of money, the $5k was roughly irrelevant compared to the other costs mentioned here and the _magnitude of the risk_.

If you haven't been through this kind of thing, it's hard to understand how scary it is to have a break-in of unknown origin. If you use strong, unique passwords as Max did, then you're almost certain it's a server break in (and again, this is why Slack is scary for sensitive info)...but being 99% certain isn't enough. Removing that computer permanently from the team gave peace of mind.

There is giphy integration, and how it works is described here. https://keybase.io/docs/chat/linkpreviews . Similarly we'll be launching a location-sharing (including realtime) feature soon, working on a similar model.

Ah spell-check in the desktop app. We explored one library and weren't happy. We're visiting option soon, but yeah, privacy is critical.

David Mazières (designer of the protocol) has given a number of talks. Here's a good video of his talk at Google, and I believe it's the one I watched a couple years ago: https://www.youtube.com/watch?v=vmwnhZmEZjc

CoinMarketCap's paid API. We're open to considering other data sources.

Good q - this step will likely be automated soon. Still, there will always be one final step of our approving any integration, otherwise there would be 10,000 pr0n sites or ad sites. (We mention this in the FAQ.) But we can automate everything up to turning it on.

For now, we want to talk to everyone working on integrations, so we can see what steps are working and what are confusing, what could be improved, etc. So we're talking to everyone doing an integration.

Oh, wow, this jumped the gun for us. We weren't expecting to announce this until next week! It's also in a bit of a draft form, and we expect to improve this integration guide as we add partners.

Keybase's view: identity on the Internet should not be just about Twitter, Facebook, and the other superpowers. Your membership to any site might be meaningful to other people, whether that membership is to something small like a phpBB forum about motorcycles, or something big like LinkedIn or Etsy. Often, the smaller the community, the more meaningful and close-knit membership is. And the more that community might want access to secure tools such as Keybase. If you're on the forum, you might _really_ need to reach out to another user of that forum, securely.

It might be a good time to mention that Keybase is looking to hire an Identity Evangelist[1]. This would be someone with a tech background (i.e., from the HN crowd), who has great presentation skills and experience, and who wants to help other sites and apps integrate with Keybase.

[1] https://keybase.io/jobs#evangelist

a16z - also Chris Dixon - led our round at Keybase. We only have great things to say about both the firm and Chris. Chris sits on our board and has been a class act the whole time.

Also: during our fundraising, we faced a number of the "Monday pitch meetings" -- this is where you've gone through the early crap talking with VC's and are invited in to pitch to the partners. It's typically the last step before an offer. a16z's partner meeting was, by far, the most tech-savvy and aware group. It seems obvious that VC's would understand the technology they're investing in, but honestly, that's often not the case. We faced a lot of brand-name VC firms that couldn't understand what we were working on. We'd get a sense of that and quickly adjust our pitch to focus on what they could understand.

For those asking "Why give them so much credit when they're just doing their job?" -- there are special occasions when a startup's interests and its investors' interests are not aligned. The first big opportunity for a VC to mess with you is the period between a letter of intent and closing the round, when all the smaller details come up and are negotiated. a16z was excellent in the process and we closed quickly without issue.

A later possibility of disagreement is what ar7hur describes here, and here's why it happens: VC's have zero risk aversion and aim to maximize expected value in dollars, which is what you'd want as an investor in the VC. But especially if you're a first-time founder, your dollar-to-utility curve is anything bit linear. Most humans wouldn't trade $5 million for a 1-in-10 chance at $100 million. This discrepancy is the source of a lot of possible problems. How VC's behave during both subsequent rounds and possible exits is perhaps the most important measure of them from a founder's perspective.

tl;dr very happy with a16z and Chris Dixon.

<3