HN user
This is caused by using CSS grid with "minmax(auto, 57rem)" and an overflowing table. It can be fixed with adding "safe" to "justify-content: safe center" that is defined on main.
https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/P...
https://github.com/darrenburns/posting is another TUI client.
Does this provide a transport plugin for Winston [1], Pino [2], etc.?
[1] https://github.com/winstonjs/winston
[2] https://github.com/pinojs/pino
PS: Your documentation search does not work.
Is there something similar with a lower profile? I use a Logitech MX Keys keyboard and the trackball seems too high to use it comfortably. Either a trackball or a trackpoint (like the one on Lenovos) would be OK.
No, IntelliCode is an extension:
https://marketplace.visualstudio.com/items?itemName=VisualSt...
Combine it with enforced Trusted Types:
https://developer.mozilla.org/en-US/docs/Web/API/Trusted_Typ...
Settings => Search for "Autoplay" => Click "Settings..." => For "Default for all websites" select "Block Audio and Video".
If you need true end-to-end encryption where the provider can't see plaintext, you lose search, real-time collaboration, most of the AI features everyone's been bolting on lately, etc.
Proton has all of these features, despite being end-to-end encrypted. Search works well with their Mail and Calendar solutions, real-time collaboration is a core offering of their Document editor. It surely is harder to implement, but not impossible for many use cases.
You are correct if `noUncheckedIndexedAccess` is enabled. It is off by default (which is a pity, really).
I assumed `Return<User>` was a mistake, not a custom type as you suggest. But your interpretation seems more likely anyway.
I get the same overall FTA score of 7 for both of your examples. When omitting the return type (which can be inferred), you get the exact same scores. Not just the same FTA score. Also note that `Return<User>` should be just `User` if you prefer to specify the return type explicitly. That change will improve several of the scores as well.
Complain to them, give them a bad rating in the Play Store. This is likely caused by using the obsolete SafetyNet Attestation API as outlined here: https://grapheneos.org/articles/attestation-compatibility-gu...
Non-Chinese version: https://apps.apple.com/app/ublock-origin-lite/id6745342698
They mean that https://ladybird.org/posts.rss only includes "news" (last updated in October 2024) but not "newsletters". In another thread, there is a link to the newsletter archive which can be subscribed to with a feed reader: https://news.ycombinator.com/item?id=44765710
Maybe https://github.com/omnivore-app/omnivore. And there are several bookmark managers like https://github.com/karakeep-app/karakeep, https://github.com/linkwarden/linkwarden, https://github.com/goniszewski/grimoire.
German works fine, too.
It, sadly, seems unrealistic to have that API with cross-browser compatibility.
Why "ironic"? The website is using flexbox incorrectly, all spec-compliant browsers have that behaviour on small viewports. Using the "safe" keyword fixes that.
https://developer.mozilla.org/en-US/docs/Web/CSS/align-items...
You can manually install uBlock and just continue using it
Only with Chrome 138 and lower. Chrome 139 will not support Manifest V2 anymore.
https://developer.chrome.com/docs/extensions/develop/migrate...
Seriously, use Firefox if you want to use uBlock Origin.
Firefox has no profiles.
It does now, it is being rolled out gradually:
Fully agree. With Multi-Account Containers [1] and the recent addition of tab groups [2] / vertical tabs [3], Firefox got even better.
[1] https://addons.mozilla.org/en-US/firefox/addon/multi-account...
[2] https://blog.mozilla.org/en/firefox/tab-groups-community/
[3] https://blog.mozilla.org/en/firefox/vertical-tabs-and-the-fi...
From your own link:
The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…
What other voices would you like to get feedback from?
That is also a problem on a side project I've been running for several years. It is based on a heavily rate-limited third-party API. And the main problem is that bots often cause (huge) traffic spikes which essentially DDoSes the application. Luckily, a large part of these bots can easily be detected based on their behaviour in my specific case. I started serving them trash data and have not been DDoSed since.
Anyway, even if someone does visit using mobile Firefox, it only takes one zoom-in/ zoom-out to adjust. So it's not really a webpage code issue, it's more about how Firefox renders pages on mobile devices.
No, it requires constant zooming and panning to be able read anything. And this has nothing to do with Firefox, Chrome and other browsers behave exactly the same. It is absolutely an issue with your website.
<meta name="viewport" content="width=800, initial-scale=0">
Update: Not OP, but I'm on a Pixel 8a with Firefox.
You may be able to debug it with https://github.com/mozilla/readability
HTML Imports went in a similar direction but they do not do what the blog post is about. HTML should be imported and displayed in a specific place of the document. HTML Imports could not do this without JavaScript.
See https://github.com/whatwg/html/issues/2791#issuecomment-3112... for details.
There is an open issue about this at WHATWG (also mentioned in the comment section of the blog post):
Client side include feature for HTML