bfm

We can help resurrect Murmur via https://github.com/De-Novo-Group/rangzen-revival

Here’s Tamir’s call for action https://www.linkedin.com/feed/update/urn:li:activity:7419994...

TL;DR TOS

Summary of the KX Community Edition License Agreement:

Key Points:

What you get:

- Free license to use KX software for personal or internal business purposes only

- No support or maintenance services included

- Software provided "as is" without warranties

Major restrictions:

- NO commercial use

- Cannot sell, distribute, or monetize any product that uses or depends on this software

- Cannot bundle it with commercial products

- Cannot reverse engineer, modify, or create derivative works

- Cannot remove copyright notices or trademarks

- Software may phone home to verify valid license

Important limitations:

- KX's liability capped at $100

- They disclaim all warranties including fitness for purpose

- You must delete software if agreement terminates

- Subject to export control laws

- KX can audit your compliance

Legal terms:

- Governed by New York law

- You retain no IP rights in the software

- Confidentiality obligations for 5 years

- KX can terminate at any time

Bottom line:

This is a restrictive free license meant for evaluation/personal use only. Any commercial use or distribution is strictly prohibited. If you need commercial rights, you'll need a different license.

This is awesome! Thank you for building it!

Another open source app that I’ve been using to practice is https://github.com/sightread/sightread

Neither Claude Sonet 3.5 or 3.7 could solve this correctly unless you add to the prompt “ Prove it with the js analysis tool, please use an efficient combinatorial algorithm to find the solution”… and I had to correct 3.7 because it was not following the instructions as 3.5 did

Open Source app to learn how to play the piano https://github.com/sightread/sightread

I don't know what in my comment made you assume I use an EQ.

As a first-time Hi-Fi headphone buyer, the reviews on Amazon and Youtube didn't surface the nuances of the different headphone models using quantitative information as DIY-Audio-Heaven does.

After purchasing the Beyerdynamic DT 770 PRO, I discovered the Superlux HD 662 EVO on this website and decided to buy them for $38 to see how they would compare. I was pleasantly surprised by the significant difference in quality, considering the Superlux headphones were almost five times cheaper. This experience led me to return the Beyerdynamic headphones and approach overpriced headphone reviews with more skepticism.

Given the recent discussions about hi-fi headphone misleading marketing https://news.ycombinator.com/item?id=36377875, and how hard it is to quantify quality, I found this resource a while ago and loved how they tear them apart and fixed the shortcomings of $40 headphones with simple hacks like adding a coffee filter on the cup to make them sound better than $500 models

Shameless plug. I open-sourced https://snapdir.org/ to explore how to solve these exact issues.

It's an early prototype to gather feedback around the ergonomics of the interface and the manifest format, and I would love to learn if people might find it useful enough for the use cases where LFS falls short.

Shameless plug for https://snapdir.org which focuses on this particular use case using regular git and auditable plain text manifests

I enjoyed Jane Street's podcast during my last long drive https://signalsandthreads.com/

The performance is directly related to the number of files you track. The first time it runs, it will be slow for large datasets, but incremental changes can use the local cache to speed up things.

That said, I built the bash version as a proof-of-concept with the idea of implementing it using Zig once I'm happy with the tool's usability.

Full title of the article: "I'm Probably Less Deterministic Than I Used to Be: Embracing randomness is necessary in cloud environments.".

Here is a link to the pdf: https://dl.acm.org/doi/pdf/10.1145/3546935

This 2015 post and the code on the 20k challenge to find correctness and liveness bugs on TiggerBettle's implementation are helping my understand better what VSR is all about.

I wonder what other projects are using it in the wild.

A couple of videos discussing this paper https://www.youtube.com/watch?v=MXb76NtoduA and https://www.youtube.com/watch?v=Wii1LX_ltIs, the last one within the context of Viewstamped Replication, which pre-dates Paxos and Raft.

How prevalent is XDG? The only place I have seen it used is on [Caddy's Dockerfile].

The defaults do not seem to match what the [Filesystem Hierarchy Standard] is proposing, but they do seem reasonable:

    # user data (/usr/share)
    XDG_DATA_HOME="${XDG_DATA_HOME:-$HOME/.local/share}"
    # config files (/etc)
    XDG_CONFIG_HOME="${XDG_CONFIG_HOME:-$HOME/.config}"
    # cache files (/usr/share)
    XDG_CACHE_HOME="${XDG_CACHE_HOME:-$HOME/.cache}"
    # state files (/var/lib)
    XDG_STATE_HOME="${XDG_STATE_HOME:-$HOME/.local/state}"

  [Caddy's Dockerfile]: https://github.com/caddyserver/caddy-docker/blob/master/Dockerfile.tmpl#L40
  [Filesystem Hierarchy Standard]: https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard

I recommend reading the book “ Panic: The Story of Modern Financial Insanity” by Michael Lewis. It’s a series of articles and expert opinions before and after modern market crashes that helps gaining perspective of expert opinions during the ups and downs of the market.

It makes sense, DuckDB's documentation has significantly improved, but it is still lacking when it comes to the limitations of using parquet. We have also hit some roadblocks when updating schemas backed by parquet files, so we now only use DuckDB for querying parquet via SQL.

What was the motivation for building your own instead of using something like DuckDB which support parquet out of the box? What are the differences?

A self hosted alternative we've been using for our infrastructure is innernet, which was discussed on https://news.ycombinator.com/item?id=26628285 last year

The control server is not open source. Thankfully headspace https://github.com/juanfont/headscale is filling that gap

Relevant discussion comparing KeyCloak to the Ory stack https://news.ycombinator.com/item?id=25763320

We are currently evaluating self hosting supabase auth.

Not one-liners, but some of the tools that I have found helpful for working with large bash codebases are:

  - shellcheck and shfmt for linting and formatting
  - sub for organizing subcommands
  - bashdb for debugging scripts interactively via the VSCode extension

[shellcheck] https://github.com/koalaman/shellcheck [shfmt] https://github.com/mvdan/sh [sub] https://github.com/qrush/sub [bashdb] http://bashdb.sourceforge.net/ [vscode-bash-debug] https://github.com/rogalmic/vscode-bash-debug

Thanks for sharing, I love the animations and diagrams.

From the OP

  Rules were established after the “flash crash” of May 2010 to govern when trades should be canceled. Knight’s buying binge did not drive up the price of the purchased stocks by more than 30 percent, the cancellation threshold, except for six stocks. Those transactions were reversed. In the other cases, the trades stood.

Today there was a 300B oopsie in Europe caused by a Citibank "glitch" bloomberg.com/news/articles/2022-05-02/citi-s-london-trading-desk-behind-rare-european-flash-crash

Updated the title

It is challenging, although, with financial markets, it seems like it would be simpler to have some automatic anomaly detection mechanism to unplug or slow things down to prevent further damage.

The OP details how poor software engineering practices brought down a 1.4B market marker with 1400 employees in 2012.

Some of the issues mentioned include:

  - Keeping synthetic test data generation as part of a production build.
  - Keeping dead code for years.
  - Re-purposing a feature flag.
  - Refactoring without regression tests.
  - Manual deployments without peer reviews. They forgot to update one of their servers with the new code.
  - Automated alerts sent via email were ignored.
  - Rolled back to a version of the code running on the server they forgot to update, making things worse.
  - Rushing out a release without proper software engineering hygiene.

For those here who are in HFT circles, have things improved after the Knight Capital Group debacle?

edit: formatting