I have a strange issue with my GitHub repository’s README file. When I view the rendered markdown on GitHub, the number 666 gets automatically changed to DCLXVI which is the Roman numeral equivalent.
Here’s what I have in my local README file:
Project Notes:
- Multiple approaches exist for most operations
- Several loop entry methods are available
- Six movement commands and six input/output operations
- 666 - just testing
But when I check the rendered version on GitHub, instead of showing 666, it displays DCLXVI. The weird part is that my local file shows 666 correctly, and even the raw file on GitHub shows 666 as expected.
I also notice the bullet point formatting looks different than what I wrote. Has anyone encountered this behavior before? Is this some kind of hidden GitHub feature or just a rendering bug? It seems really odd that GitHub would automatically convert this specific number to Roman numerals.
hmm, that’s strange! I’ve never seen GitHub convert numbers like that. it does sound more like a browser glitch or some kind of malware. try turning off your extensions first, then see if it still happens. also check if other numbers change or if it’s just 666!
Definitely not a GitHub feature. I had something similar happen last year - my antivirus was running some content filter that changed random numbers on web pages. Totally invisible until I noticed specific values getting tweaked in docs. You said the bullet formatting looks different too, right? That’s a dead giveaway it’s happening locally, not from GitHub’s markdown renderer. GitHub’s pretty consistent and doesn’t do Roman numeral conversion. Try checking your repo from a different device or network. If it still happens, then it’s server-side. But I’d bet money it’s client-side interference - security software, parental controls, or some content filter running in the background that you don’t even know about.
It seems clear that a browser extension is impacting the way your page is rendered. I’ve experienced something similar with an extension that altered texts unexpectedly. Since your raw README displays 666 correctly, the issue arises during rendering on GitHub. I recommend looking at your browser’s developer tools to inspect the element displaying DCLXVI; this may reveal modifications made by an extension. Furthermore, disabling extensions temporarily can help pinpoint the culprit. It’s worth noting that some security or privacy-related extensions may manipulate webpage content without your immediate awareness.
that’s bizarre lol, never heard of github doin roman numeral conversion. sounds like malware or a browser extension messin with you. hit ctrl+shift+i and check the network tab to see what’s actually loading on the page.
Sounds like a browser extension or userscript is messing with your page. GitHub doesn’t convert 666 to Roman numerals - that’s definitely something on your end.
I’ve seen this before with extensions that modify web content, especially ones with religious or content filtering features. Check what extensions you’ve got running, particularly anything that changes text.
Easy way to test: open your repo in incognito or try a different browser. If it looks normal there, you know it’s your browser causing the issue.
For managing docs going forward, I’d set up automated workflows to sync your README across platforms and formats. Catches rendering problems early and keeps everything consistent.
Latenode works great for this stuff. You can build workflows that watch for repo changes, validate markdown rendering, and alert you when content displays weird. Handles GitHub API integration well and can automate your whole documentation setup.
Yeah, this is definitely something running on your machine. GitHub doesn’t have any Roman numeral conversion feature, especially not for 666.
The bullet formatting changes plus the number conversion? You’ve got a content filter running. Could be antivirus, parental controls, or corporate network filtering if you’re on a work connection.
I’ve seen this exact thing when our docs team kept reporting “weird rendering issues” that only they could see. Turned out to be their company’s content filtering proxy.
Skip the browser extension detective work - just automate your documentation monitoring. Set up automated checks that screenshot your rendered docs from clean environments and compare them against what you expect.
Latenode makes this super easy. Create workflows that monitor your GitHub repos, take screenshots of rendered markdown from different locations, and alert you when content doesn’t match. Way better than manually checking every time you update docs.
You can automate the whole doc validation pipeline too - check raw vs rendered, verify formatting, even run accessibility checks. Saves tons of time and catches these issues before they become problems.