It's new to me that it's NFC. I was under the impression I need to buy a reader device to make use of digital auth or signature stuff.
Actually, avoid using PNGs at all if you can.
👀
I prefer round[ed].
Think of it as a rounded square with a unique, pleasant shape.
I don't find them pleasant. I find them irritating.
Rounded square makes use of the space it reserves/square-fills. Squircles seem wasteful and confusing. They do not represent any common physical shapes, and waste/discard space they could use. They look like an old CRT.

R1dacted: Investigating Local Censorship in DeepSeek’s R1 Language Model
Quoting from the abstract:
While existing LLMs often implement safeguards to avoid generating harmful or offensive outputs, R1 represents a notable shift—exhibiting censorship-like behavior on politically charged queries. […]
Our findings reveal possible additional censorship integration likely shaped by design choices during training or alignment, raising concerns about transparency, bias, and governance in language model deployment.
When PRs begin with a headline and checklist the GitHub hover-preview becomes useless. When the PR description begins with the summation of the change, it is very useful.
Most of the time I see headlines and check lists in tickets I create or contributions I create PRs for, I feel stifled and like I have to produce something very inefficient or convoluted.
The worst I have seen is when, at work, I had to create bug tickets for a new system in a service desk to a third party, and they had a very excessive, guided, formalized submission form [for dumb users]. More than once, I wrote the exact same thing three times into three separate text boxes that required input. (Something like "describe what is wrong", "describe what happens", "describe how to reproduce".) Something that I could have described well, concise, fully and correctly in one or two sentences or paragraphs became an excessively spread, formalized mess. I'm certainly not your average end user, but man that annoyed me. And the response of "we found this necessary" was certainly not for my kind of users, maybe not even experience with IT personnel.
At work, I'm glad I have a small and close enough team where I can guide colleagues and new team members into good or at least decent practice.
Checklists can be a good thing, if processes can be formalized, can serve as guidance for the developer, and proof of consideration for the reviewer. At the same time, they can feel inappropriate and like noise in other cases.
I've been using horizontal line separators to separate description from test description and aside/scoping/wider context and considerations - maybe I will start adding headlines on those to be more explicit.
Invidious says video unavailable
I'm a bit confused, because MDN ::after says in the accessibility section:
Using an ::after pseudo-element to add content is discouraged, as it is not reliably accessible to screen readers.
which contradicts the article saying ::after content gets included as per spec. They conclude though with
While it’s good and certainly useful that we can now provide alt text for CSS generated content, I do not recommend using CSS to insert meaningful content into the page.
Not only will some of your screen reader users miss meaningful information when the alt text is not announced by their screen reader (looking at NVDA with Chrome 👀), but there are also other reasons why inserting meaningful content in CSS is not yet recommended…
so I assume it's a spec vs real world thing.
If you want a teaser what this is about, the / content syntax for screen read representation (to evade misrepresentative emoji translations, for example).
::after {
content: " \2197" / "Opens in a New Window" ;
}
They also talk about image alt text and ::after url.
I use GitLab diffs in single-file-view mode, TortoiseGit Merge when it exceeds what GitLab can reasonably display (including block indent changes I can ignore in TortoiseGit Merge or moves I can better track), and WinMerge (previously I used KDiff) for manual copy-paste text diffing (like copying blocks from the code change diff to compare similar, categorically similar code, or code moves, etc)
I don't know what you're looking for, and what your "not super simple" is, but baseline browser tech provides various controls, layout mechanisms, styling, interactivity, etc.
Do you have a concrete idea of what and where specifically you hope for gains by using frameworks? Do you plan to hold a lot of state on the client that needs state separated from the DOM and its mechanisms? Do you want a standard library of styled components instead of using the native ones or styling them yourself? Do you want more robust JavaScript? Those are all very different concerns and requirements.
I like the low complexity, low barrier, low requirements of baseline web tech. The native html form controls may arguably look "ugly", but those can be styled, individually or through a style-only CSS lib.
How viable is shifting from app to the web platform? Installable PWAs or PWA without installs.
Seems like it could be an alternative for most(?) things.
The most future proof web tech is not using frameworks and libraries at all.
Render native HTML controls.
I also assume it's lower barrier than any of the libs and frameworks you could use, which is always a subset of web tech with the addition of their own concepts.