The Omarchy team admitted it was a mistake and corrected it quickly.
It’s strange that so many people are trying to call this security error intentional.
It’s strange that so many people are trying to call this security error intentional.
So there's nothing weird. It being on originally was intentional and not crazy. Only it going all they way wasn't.
They didn't forget. They never knew it was there. https://news.ycombinator.com/item?id=49502099
Overly active analytics / tracing stuff is not uncommon during dev. Likely they just did it to be able to debug things better in the weirdest cases; doing a full session replay basically when you have the whole original state of the repo