myfonj

6 ms·

1.
by myfonj 8d ago
The "fifth" was probably from their essay < https://vale.rocks/micros/20260908-1315 >, that was fourth on Lobsters (?) > People often pair initial-scale=1 with overflow-x: hidden in their CSS […] (That
2.
by myfonj 8d ago
Ha, I stay corrected! Crawling back under rock to re-read WHATWG and historical W3C docs to fill the voids… Note to self: Apparently, I mentally froze around 2009, so I have some decades to catch on. It seems the breaking point was after 20
3.
by myfonj 8d ago
Well from the (incomplete, as turned out) info I gathered it turned out that it was never standardised to begin with (unlike meta description, for example), so it did not even have to be "deprecated". (Like it ever meant something
4.
by myfonj 8d ago
Ha! Last year I did some preliminary research, and all contemporary sources I've found agreed that last public search engine stopped supporting meta keywords around 2018, IIUC. So good catch about Yandex, thanks for the headsup! Funny
5.
by myfonj 8d ago
There is similar collection in the joshbuchea/HEAD project, in DEPRECATED.md [0]. (It reminds me to finally gather and record remaining info about <meta name="keywords" content="..."> that's miss
6.
by myfonj 1mo ago
> That seems rather dodgy. I fully agree, yet in this particular case it probably holds, with possible exception of 2009 Safari, IIRC [1]. And absolutely agree that defensive @supports is better and more robust way to go. Just aimed to
7.
by myfonj 1mo ago
Some caveats worth mentioning yet missing there: 1. many, MANY implementation bugs in `background-clip: text` across browsers, especially Firefox [1], basically safe only for simple cases with no additional transforms or filters. 2. `color:
8.
by myfonj 3mo ago
I think that the domain knowledge still matters: if for nothing else, then at least it can make the communication both with savvy AI tools and savvy humans more effective compared to "outsiders": acquired vocabulary, truly grokked
9.
CSP: Bookmarklets should bypass pages' policies (2013 → Infeasible 2026)(issues.chromium.org)
2 points by myfonj 3mo ago|0 comments
10.
Who's Running Last.fm Now?(support.last.fm)
6 points by myfonj 3mo ago|0 comments
11.
by myfonj 4mo ago
> Chasing enemies is much more annoying than them coming to you, so that would be a punishment to the player. It seems I've failed to express myself clearly. The idea was that at some point, "low-level" adversaries simply
12.
by myfonj 4mo ago
Sure, but I don't think they must be mutually exclusive; on the contrary: in the late stages when your character is a tank, swarms of minions that posed a challenge in early stages become just a nuisance, mostly. You are walking legen
13.
by myfonj 4mo ago
> As a result, the game offers no easy satisfaction of hacking and slashing through weaker opponents. Besides the questionable morality of kill=experience=progress in typical hack'n'slash or roguelike, what started to irritate
14.
by myfonj 4mo ago
Haha, blushing in awkward uncertainty that I've failed to detect irony …? (Is this HN, right?) But even if, thanks anyway! I'm glad I could vent the lore I've spent gathering in unhealthy amount of unproductive research; I ca
15.
by myfonj 4mo ago
Someone here. OP most certainly knows that precisely, but for the rest: It was Netscape® Communicator, which interpreted everything after `<` up to either white-space or `>` as a tag name. Technically that wasn't even that much i
16.
by myfonj 4mo ago
Plus, when curious about formal syntactic correctness, there is the validator.w3.org [1]. [1] https://validator.w3.org/nu/?showsource=yes&showoutline=yes&...
17.
by myfonj 4mo ago
Fair point, though /DT and /DD are also optional just like /TH, /TD and /TR are. So in effect, def…scription list could structurally save you one TR for each entry and two "BLE"s: <table><t
18.
by myfonj 4mo ago
Ran into this discrepancy myself. On top that, what seemed also odd to me were the "dots" (tittle, period, semicolon) where oversized becomes hollow in the middle, like it cancels out itself. No other shape I've tried did tha
19.
by myfonj 5mo ago
When (rarely) using hex editors, one thing constantly comes to my mind: isn't base 16 arabic-roman numerals a bit awkward for "skimmable" overview? Color-coding indeed helps immensely there, but wouldn't simply letting b
20.
by myfonj 6mo ago
That's peanuts. LI's third-party bot prevention service, "protechts.net", took 42 GB RAM on my laptop with 32 GB the other day. Obviously found out because it got suspiciously slow and wheezing, and Firefox swapping like
21.
by myfonj 8mo ago
These "dots appearing only while (not) focused" are known as "extinction illusions", namely "25 - Appearing Dots" is "McAnany's type" [1], and "26 - Disappearing Dots"
22.
by myfonj 9mo ago
The "guesswork" done by browsers is actually pretty nuanced and not standardised in a slightest way. Some defaults are pretty common, and could be maybe considered de-facto standard, but I wouldn't want to draw the line where
23.
by myfonj 11mo ago
> I am an app developer. How do I protect my users? > We are not aware of mitigation strategies to protect apps against Pixnapping. If you have any insights into mitigations, please let us know and we will update this section. IDK, I
24.
by myfonj 11mo ago
Ha ha, really glad to hear that. (The fact is, I am kinda freak/junkie about human voices, and that particular one stands really high on my list of irresistible tingles-inducing specimens. So happy to hear I am not alone.)
25.
by myfonj 11mo ago
I've made something (probably) very similar for quick GB vs US pronunciation check that also leeches on Google's snapshot of what I believe is a licensed copy of the Oxford collection the same way the shell script does, but mine &
26.
by myfonj 11mo ago
> I do think an interesting approach would be a browser extension that lets you override the prefers-color-scheme property on a per-domain basis, similar to the toggle in dev tools. Presumably, most users wanting flashbang-less browsin
27.
by myfonj 1y ago
Good question! Actually (to my minor dismay): not completely . Disabling "font support" in Firefox surprisingly still has a hatch for "well-known" icon fonts, with intention to prevent "blind" icons in webpage
28.
by myfonj 1y ago
> Great! Then the user gets his preferred font, as requested, instead of the one the page specified. No. You've misread the main point. The user would have gotten his preferred font if the font stack was either just plain
29.
by myfonj 1y ago
> esoteric browser prefs That hurts. I see where you are standing, and can confirm you expressed opinion of the contemporary majority of browser users, but man, how sad it that. The attitude diverged by a light years, when "Settin
30.
by myfonj 1y ago
This is excellent analysis, but I think you've forgot to mention one particular detail in your environment description: - Firefox Browser Privacy Enhanced Tracking Protection setting changed to "Strict". It is not de

More ›