didn't even a16z do this once?

[ah, yes, here](https://news.ycombinator.com/item?id=41016768)

SimpleStacker

Yeah you need to run something like [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/) AND ask Github support to delete orphaned commits after you force-pushed rewritten history afaik

fun fact even if you delete the commits they are still there

carter

BlokchainB

0xbitcoiner

We learn more from our mistakes than anything else.


Solomonsatoshi

https://r2.primal.net/cache/e/d0/b0/ed0b0ada9a24dc6220e24c6e8afc7ca2d99bd7c4b01fc465ca129874ced5bc41.jpg

![@delete in 1 day]()

anon

asoltys2

realBitcoinDog

SwapMarket

PictureRoom

security

In case you wondered how the [original Coinos nostr profile](https://njump.me/nprofile1qyg8wumn8ghj7cm0d9hx7uewd9hj7qpqh2qfjpnxau9k7ja9qkf50043xfpfy8j5v60xsqryef64y44puwnqtvj95h) got compromised:

The nsec was uploaded to Github in [this commit](https://github.com/coinos/coinos-server/commit/ac63d9cb30690f335616aa046e2b6512b05ecb44) on September 5, 2024.

![](https://m.stacker.news/110043)