Completely agreed on avoid Tampermonkey, but Violentmonkey fails to detect the page on one of my scripts very often. If I refresh it works. This is a match with no wildcards and just a simple path after the URL.

Perhaps a simple bug, but doesn't give me much faith in the project.

That's a shame, never happened to me, have you tried changing it to an include or adding a wildcard at the end? The project has been active for a very long time, I've been using it since it was only an Opera 12 extension, the developer seems very responsive, try reporting a bug.

I haven't tried that yet but I'll give both a try, thank you. I'm not giving up on it yet. Good to know they're responsive, I might look at fixing it myself.

That's interesting. To confirm, it doesn't appear in the 'Matched scripts' list when that occurs?

Yes that's correct, but I think it appears everytime with a refresh.

The same often goes for security without the .txt too.

Congratulations! Really good to hear, and definitely a nudge to me to let people know when their blog was useful.

I'm not sure this is true. In my experience a lot of people actually do think that it's case sensitive. Many times I've heard someone describe the capitals while verbally telling someone their addresss.

However it being insensitive has probably helped a lot of times where people make mistakes in explaining or copying those capitals.

Regarding email it doesn't hurt to think they are case sensitive but opposite would be a massive problem

As a sender, you should always treat email as case sensitive. As an email host/receiver, you can and probably should chose to be insensitive. But never assume any other host works like that.

Similar to how gmail ignores . in emails but other hosts do not.

> In my experience a lot of people actually do think that it's case sensitive.

I don't think they really do. They may think case matters somehow, and so may be careful to reproduce the exact case that they used before, but I don't think many people would expect JohnDoe@gmail.com and johnDoe@gmail.com to be too different email accounts.

By maps to, they mean it counts as the same email address. 111@ and lll@ do not do that. The font has no impact on the email spec. However it can add extra confusion.

I doubt anyone is crazy enough to implement the email spec for comparing emails, to be fair. I would honestly be surprised if any publicly available mail agent or server supports that craziness.

This doesn't really make any sense. It's not just gmail that does this, dots are almost always ignored before the @.

Nobody else can register an email that is the same as yours but without a dot. So the only way you receive someone else's email is if they give the wrong address.

> It's not just gmail that does this, dots are almost always ignored before the @.

That's not my experience. Which non-gmail email software ignores dots before the @?

Thinking about this, I guess the sending MTA doesn't care about dots; it goes RCPT TO: <address.with.dots@example.com>. The receiving MTA then has to validate that address; it does that using some account database that isn't typically part of the MTA - it could be a unix account (no dots!), a database table, or an LDAP user. Finally it passes the mail off to a delivery agent, which hopefully relies on the same account database.

So the elision of dots appears to be a feature of certain account databases. So which account databases elide dots?

MTAs can be configured to additional transforms before looking up the account. For example, postfix's virtual table [0] can be used for this and on my server it does elide dots in the local part (along with everything else).

[0] https://www.postfix.org/ADDRESS_REWRITING_README.html#virtua...

It may be that some other specific email servers implement similar behaviour to gmail, but that is not true as a general rule.

I think it looks beautiful, but have to echo the comments about not having the home, end, pgup, pgdown + numpad keys making it impractical. Would 100% get this if it had a full sized version.

I feel like those comments about layout are misplaced. It’s like saying “nice motorcycle you designed, but really I need a cargo van.”

I believe it is mac-inspired, where cmd/alt+arrow are usually used for that.

But overall, yeah, people split around mac/60, tkl and full. No idea why keyboard makers tend to fix on only one of them. Budget reasons - yeah, but isn’t it strange to cut off large parts of potential customers.

I agree on the numpad. I do bioinformatics/data science work that sometimes involves some manual spreadsheet surfing and definitely use the numpad. A lot of numerical identifiers for genes that you end up incidentally memorizing after a while, and want to ctrl/cmd-F for.

You could change the option of where to save downloads. Instead of automatically putting them in the downloads folder, if you change it to ask every time, then you will get the file browser prompt before the download starts.