Hacker News

“When I was growing up in the hills of East Tennessee, I knew my dreams would come true. I know there are children in your community with their own dreams. They dream of becoming a doctor or an inventor or a minister. Who knows, maybe there is a little girl whose dream is to be a writer and singer.

The seeds of these dreams are often found in books and the seeds you help plant in your community can grow across the world.”

What surprised me was how empty some of the biggest companies looked.

Nvidia is worth $5.2 trillion but employs only 42,000 people. That's around $124 million in market cap per employee. Meanwhile, Accenture employs 814,000 people and is worth $146 billion.

Each stick figure represents 10,000 employees. You can zoom in and explore individual companies.

I wrote a bit more about what I found here: https://bigwhalehunting.com/blog/workforce/

Would be interested to hear what you think.

I've been working on reVault for about 2 years. It was originally written in Dart, but with the improvements in AI, I decided to port it to Rust using AI.

It's now in beta, so I'm looking for feedback, particularly around the different language bindings.

A lockbox is encrypted, signed and compressed by default. Each can be disabled selectively.

  - Hybrid post-quantum or passphrase encryption, including metadata.
  - Zstd compression.
  - Pure Rust libraries wherever possible.

We intend to phase out remaining C code as alternatives become available. The project has been scanned using OpenAI's Daybreak cyber security tools.

The manual is a work in progress: https://docs.revault.onepub.dev/

reVault supports Linux, macOS and Windows, x64 and arm64, plus Wasm. The core is Rust, with bindings for C/C++, Java, Dart, Python, Ruby, JS/TypeScript, Go, C#, Kotlin, Lua, PHP and Swift.

Within a lockbox you can store:

  - Files, directories, permissions and symlinks.
  - Variables.
  - Forms.

Variables, forms and the lockbox itself can have descriptions.

reVault uses a portable vault (just another lockbox with structured content) to hold your keys, contacts' keys, lockbox aliases and form definitions.

It ties into your platform's secure store, so logging into your desktop unlocks your vault. You don't have to enter a passphrase every time you access a lockbox. You can disable this.

There are lots of shortcuts. Creating a lockbox stores an alias in your vault, based on its filename or a name you choose:

  lbx create /some/path/mybox.lbox
  lbx mybox open --duration 1h
  lbx mybox var set KEY VALUE

Set a default lockbox and you can leave its name out:

  lbx session default mybox
  lbx var get KEY

You can mirror a directory tree into a lockbox and update it when the directory changes:

  lbx store.lbox mirrors project create --from ./project --to /projects/project
  lbx store.lbox mirrors update

The API lets you read, write and seek within files without extracting them to the filesystem. Each lockbox has a table of contents, so extracting a single file from a multi-gigabyte lockbox is fast.

Recovery

Updates are transactional, with automatic rollback for failed updates. The format is designed for recovery: content is stored in pages, allowing unaffected content to be recovered if part of a lockbox is corrupted.

Sharing

An encrypted lockbox is more useful if you can share it.

reVault has an open-source keyserver for exchanging public keys, with validation through a second trusted channel. It's still experimental.

OnePub has donated a server to run a single keyserver. If you're interested in donating resources, I'd like to bring up a second redundant server. It's pure Rust, uses under 100 MB RSS and supports rate limits.

To publish your default profile's public key:

  lbx vault profiles email you@example.com
  lbx vault profiles publish

Give the publish code to your contact. They can import your key:

  lbx vault contacts receive <publish-code> <contact-name>

Display your profile's fingerprint and exchange it through a second trusted channel:

  lbx vault profiles fingerprint

Repeat the process in the opposite direction to get their key. Once you have it, grant them access to your default lockbox:

  lbx access grant alice

You can then email the encrypted lockbox to Alice.

To install the CLI and get started:

  cargo install revault_cli
  lbx vault init
  lbx completion install

Completion installation detects your shell. To diagnose issues:

  lbx doctor

The language bindings are published to their respective package repositories.

I'm looking for constructive criticism of the project on its own merits, particularly the APIs and language bindings. I'm not interested in a debate about using AI.

Since 2021, I’ve been collecting fully consented voice data from over 20,000 people, 1M audio recordings, and over 1,800 hrs of audio captured to date. For this model, I used a small part of the data, 136 hrs, to finetune Maya1 and expand it’s capabilities.

Hurston-1 is a narrowband TTS model that focuses the output on telephone use because that is still where most of these voices will be heard. I’ve used it to support customers such as Amazon and Salesforce and generated over half-mill revenue with it. Now I’m open sourcing it to help unlock opportunities for others as well.

Limitations: this model doesn’t maintain the exact same voice across prompts and doesn’t support voice cloning. For many use cases, this is fine but maybe not so - if you’re creating podcasts.

This is the first release - I’m already working on the next version with improvements.

I would appreciate, if anyone is interested in this space, download the model from huggingface, check it out and let me know any feedback. Also, open to connecting with others in this space as well.

https://twitter.com/ID_AA_Carmack/status/2113704269274636568

"Samsung running a TensorFlow lite model on 960x540 image to track you": https://twitter.com/mike64_t/status/2114150399406202896

"Samsung TVs look for microphones in your house via Bluetooth and then spy events": https://twitter.com/freddier/status/2114042326758867453