why chrome?

last updated 3/8/26

i only test the site on chrome. that's all.

for the most part, any other browser (With the sole exception of webkit) should work just fine, however i can't guarentee that they will, because, again, i only test in chrome.

statistically, you're probably using chrome too.

i do occasionally test the site in Firefox/Gecko and there's no obvious issues i'm aware of, but if firefox introduces some weird rendering bug or doesn't implement some CSS properly, it won't look right.

if you're using another browser and you find a bug that doesn't appear in chrome (or any bug in general), feel free to submit it at the issue tracker.

known bugs are in a different repo/issue tracker here.

what now about webkit?

WebKit, especially mobile webkit, isn't very standards compliant and has a lot of weird bugs and issues that arent in Firefox or Chrome.

this is especially a problem with the beta music branch, as safari doesn't handle audiocontexts the same way.

TL;DR: If you use safari or are on iOS don't expect the website to work properly. I can't do anything to fix it, blame apple.