Good lord it's atrocious. Either I see the :/ face or I consciously feel my brain strain to parse it in full because decades of web experience have taught me to

Good lord it's atrocious. Either I see the :/ face or I consciously feel my brain strain to parse it in full because decades of web experience have taught me to ignore the left side of the :// unless I'm specifically interested in the security of the connection to the endpoint. Using non-alphabetic characters in a logo requires a pretty careful execution. An old ISP here used to be Optus@Home. I could parse that fine because it was fairly balanced, relatively minimal and reads smoothly (say it out loud and it is perfectly pronouncable, so reading it in your head is similarly effortless). In contrast, moz://a both looks weird (the / stand far higher than the alphabetic characters in most fonts, there's 3 letters on one side and 1 on the other), it's mentally taxing (how do I pronounce ://? oh wait, that's right, I need to parse it as 'ill' when reading it in my mind's voice. I also need to remember when focusing on it in isolation not to parse it as a smiley like decades of internet usage has conditioned me to. This is the same effect as when you see <3 in some maths/code and parse it as 'heart' rather than 'less than three') and it doesn't smoothly parse as a standalone thing like @ does as 'at'. I really don't like it.