Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
shiomiru
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
91.
▲
by
shiomiru
1y ago
Another POSIX shell in Rust I remember: https://github.com/nuta/nsh But it no longer seems to be in active development.
92.
▲
by
shiomiru
2y ago
> Let's not go blaming vulnerabilities on those exploiting them. Exploitation is also bad but being exploitable is a problem in and of itself. There's "vulnerabilities" and there's "inherent properties of a
93.
▲
by
shiomiru
2y ago
Chrome has randomized its ClientHello extension order for two years now.[0] The companies to blame here are solely the ones employing these fingerprinting techniques, and those relying on services of these companies (which is a worryingly l
94.
▲
by
shiomiru
2y ago
Among less technologically literate acquaintances, getting a gazillion browser notifications on startup seems to be the modern equivalent of accidentally installing tons of useless toolbars.
95.
▲
by
shiomiru
2y ago
The problem is that the very purpose of a textbox is to submit data. So you'll have to add the caption to every single textbox. (I've actually tried to do something similar in my browser, but it was an eyesore so I removed it.)
96.
▲
by
shiomiru
2y ago
htcrack.ai is available...
97.
▲
by
shiomiru
2y ago
> Besides, throwing an exception is a terrible way to do range checking. There's a huge number of projects out there banning exceptions that would benefit from safe interfaces. I thought "banning exceptions" would mean fno
98.
▲
by
shiomiru
2y ago
> Sure, but the same is true for unsigned commits as well, isn't it? Yes, I think so. As I understand, GP's idea was to sign your commits proactively.
99.
▲
by
shiomiru
2y ago
> git does allow you to rewrite history arbitrarily. Technically yes, but the price is too great - everybody who has cloned the repos will now have to nuke their local copies too.
100.
▲
by
shiomiru
2y ago
> Would you expect a "privacy focused" browser to offer you networking disabled by default Obviously not, because at that point it can no longer be used to browse the web. (That said, "do no network requests" should b
101.
▲
by
shiomiru
2y ago
Developers can use whatever features they want, but users can only watch as their computer uses up more and more energy because it suddenly has to perform yet another build step that previously was done on the server.
102.
▲
by
shiomiru
2y ago
Another solution for the pre-command part is "trap 'some command' DEBUG".
103.
▲
by
shiomiru
2y ago
Another option I'm working on: https://sr.ht/~bptato/chawan Chawan also renders CSS + images, but unlike the above two, it comes with its own browser engine (from scratch). It also does JS with QuickJS - if you&#
104.
▲
by
shiomiru
2y ago
It seems well-intentioned, but not particularly well informed... * It mixes concerns of HTML and CSS - e.g. <pre> eating newlines is a result of the HTML parser, but whitespace collapsing is specified in CSS. * It suggests turning HTM
105.
▲
by
shiomiru
2y ago
Throwing any codepoint sequence at two separate compliant HTML5 parsers will result in the same DOM, and to my knowledge, all major browsers use compliant parsers.
106.
▲
by
shiomiru
2y ago
In my text browser I came up with a way to implement these that doesn't move boxes around the page.[0] In short: treat "position: fixed" as an absolute child of the root box, and ignore "position: sticky" (mostly).
107.
▲
by
shiomiru
2y ago
> * Author claims to speak English very poorly, but writes incredibly well! Maybe they leaned on LLMs, but this seems pretty good even for an LLM. The author claims their pronunciation is poor. Writing is a completely different skill.
108.
▲
by
shiomiru
2y ago
Sixel is a fun side quest as well, if you want to encode it on your own. You get to work on a color quantization and/or dithering algorithm in $CURRENT_YEAR. And if you're doing text with images, integrating both Sixel and Kitty i
109.
▲
by
shiomiru
2y ago
So that's why they broke loading issue comments without JS. As if the (post-M$) UI hadn't been sluggish enough before...
110.
▲
by
shiomiru
2y ago
> "Why didn't they do it earlier?" is a fallacious argument. I never said that, but admittedly I could have worded my argument better: "In my opinion, shadow banning non-JS clients from result computation would be sim
111.
▲
by
shiomiru
2y ago
If it's such a common issue, I would've thought Google already ignored searches from clients that do not enable JavaScript when computing results? Besides, you already got auto-blocked when using it in a slightly unusual way. Goo
112.
▲
by
shiomiru
2y ago
And it hijacks my back button. It took two clicks to get back to HN. (Fennec/Android)
113.
▲
by
shiomiru
2y ago
> The goal with Ladybird is to be "independent" in the sense that nobody influences their decisions. However, they have no desire to be independent from a technology stand-point (other than being Open Source). Wouldn't a h
114.
▲
by
shiomiru
2y ago
The sad part is that it's trivial to get around CF's bot protection if you're writing a bot (just use curl-impersonate and buy residential IPs), but it's pretty much impossible to bypass as a human if their magical black
115.
▲
by
shiomiru
2y ago
I believe Netscape worked like this back in the day. (ETA: as in, resizing the window would reload the page.)
116.
▲
by
shiomiru
2y ago
> string parsing: innerHTML, querySelectors, console.log I don't have numbers, but I doubt an in-browser JS implementation without these APIs would be useful on many websites. Even HN uses innerHTML.
117.
▲
by
shiomiru
2y ago
> when the same people simultaneously moan and complain any time Mozilla tries to branch out and cultivate independent revenue streams. I don't know what "same people" you're talking about, but the criticism I see is
118.
▲
by
shiomiru
2y ago
> Have you considered what happens if not-utf8 data winds up in an environment variable that you are writing to stdout? What if it contains malicious VT commands? Unless you're talking about terminal bugs in parsing invalid UTF-8 -
119.
▲
by
shiomiru
2y ago
> As any good programmer knows, division is slow, it’s a serializing instruction, and we want to avoid it as much as possible. The favourite programmer tricks to avoid division are to use bit shifts (for division by multiples of two) or
120.
▲
by
shiomiru
2y ago
For best ergonomics, both should be well supported. If I'm programming and want to look up something in the docs, then it's annoying to switch to the mouse and then back, but I pretty much have to with traditional browser UI. (Or
More ›