Writing "/etc/hosts" breaks the Substack editor

The Mysterious Network Error I was working on a technical post about DNS resolution when I encountered something unexpected. Every time I typed the path to the hosts file ( /etc/h*sts - intentionally obfuscated to avoid triggering the very issue I'm discussing), my Substack editor would display a "Network Error" and fail to autosave my draft. At first, I assumed Substack was experiencing an outage. However, their status page showed all systems operational. Something else was happening. The Investigation Begins I noticed this error appeared consistently when I typed that specific file path. But when I wrote variations like /etc/h0sts or /etchosts , the editor worked fine. Curious about this pattern, I tested more system paths: Path Result /etc/h*sts ❌ Error /etc/h0sts ✅ Works /etchosts ✅ Works /etc/pass*d ❌ Error /etc/password ✅ Works /etc/ssh/sshd_conf*g ❌ Error /etc/ssh ✅ Works /etc/h*sts.allowed ❌ Error /etc/h*sts.foo ❌ Error (Note: the * is used to replace the actual character ... Read full article.