shiomiru

4 ms·

1.
by shiomiru 5d ago
This is often repeated in these kinds of threads, but I don't think it's true. You just have to implement it in glibc, which can map the flags to the actual syscalls used on the current architecture and restrict the process to th
2.
by shiomiru 5d ago
> No browsers on FreeBSD today use Capsicum. Strictly speaking, that's false, my hobby project chawan[1] supports capsicum :) Anyway, IME capsicum vs pledge doesn't make much of a difference because seccomp already forces you i
3.
by shiomiru 9d ago
> A single while loop could do the job correctly and use less RAM. It'd probably also be faster. But that wouldn't be a rusty thing to do? No, the "single while loop" is just harder to implement than a naive recursion
4.
by shiomiru 11d ago
I don't think that's related? The bug alluded to looks something like function rm(node) { for (const child of ls(node)) rm(child); unlink(node); } and no amount of tail call optimization w
5.
by shiomiru 1mo ago
I think it's just a divide and conquer approach: if they killed it everywhere at once, there would be a larger backlash, so they are careful to roll out the change gradually.
6.
by shiomiru 2mo ago
I meant it as an euphemism for "it's universally sought after (i.e., you'll probably find a job)". Few would think being a programmer gives you some kind of special "social status"; it's always been a &qu
7.
by shiomiru 2mo ago
There's also the economic problem that programmers had until recently been highly regarded because steps 2-3 were hard. "Open source" solved this partially by utilizing the labor such (relatively) well-paid people gave away
8.
by shiomiru 2mo ago
I can't speak for the other projects you listed, but at least chawan is actively maintained by yours truly.
9.
by shiomiru 2mo ago
I like to have a simple config AND a real scripting language. That way, the UX for changing "simple" things remains straightforward (you can even add a config editor panel), while for less simple things you can use a real program
10.
by shiomiru 4mo ago
> My guess is that OP's browser is getting banned because his WebKitGTK has a weird fingerprint, not because of webgl or whatever. So why is Cloudflare saying the author got blocked because of WebGL? > > Such things are blocke
11.
by shiomiru 7mo ago
> Plenty of internal-only systems are not locked down securely and only thing preventing mass exploitation is browsers CORS settings. CORS has no relation to this issue. Cross-origin means there are at least two origins, but in this c
12.
by shiomiru 7mo ago
Isn't that effectively the same as or-later? I can always fork your project, change the MAINTAINERS file, and relicense without your consent.
13.
by shiomiru 7mo ago
Validation errors aren't really "exceptions" to be thrown, they are indicators for authors that something is probably wrong but they make no visible difference in the output. I'm not sure if any browser even tracks th
14.
by shiomiru 8mo ago
> as we know it today An important nuance you seem to be missing is that SUSv3 is equivalent to "IEEE Std 1003.1-2001" (that is, POSIX 2001). In practice, I've had to work around more POSIX compatibility issues in macOS th
15.
by shiomiru 9mo ago
"ou" is fine too, actually. See the proposal p. 14 (=16 in the PDF): https://www.bunka.go.jp/seisaku/bunkashingikai/sokai/pdf/942... (To differentiate between the case where it's actually
16.
by shiomiru 9mo ago
That "deeper explanation" seems incorrect, considering that the KSC column is empty in the mapping linked above.
17.
by shiomiru 9mo ago
The "other standard" in this case being IBM-944. (At least looking at https://www.unicode.org/versions/Unicode1.0.0/ch06.pdf p. 574 (=110 in the PDF) I only see a mapping from U+212A to that one.)
18.
by shiomiru 9mo ago
w3m doesn't support chafa for inline image display. (You can set a custom w3mimgdisplay command, but it has to speak the same protocol as w3mimgdisplay. If you're feeling adventurous, you can try modifying https://gith
19.
by shiomiru 10mo ago
> which aren't just free to use, but explicitly use the modern SIL Open Font License. Unifont is also dual-licensed under GPLv2/SIL OFL.
20.
by shiomiru 10mo ago
> It would also be nice to have something like `default-styles: none` so I don't have to deal with browsers having differing defaults. This already exists: *, ::before, ::after { all: unset }
21.
by shiomiru 10mo ago
The greatest mistake IMO is the way float state leaks out of blocks, as this is both extremely unintuitive and undesirable for performance reasons.[1] Floats should've been restricted to inline formatting contexts, with all in-flow
22.
by shiomiru 10mo ago
I actually wonder if transpiling calc/min/max/etc. expressions to JS is a viable path to implementation, considering that you already need a fast interpreter for these.
23.
by shiomiru 10mo ago
> just new ones that no automation depends on Except for automations that happen to create new repositories.
24.
by shiomiru 10mo ago
> Rendering Markdown is relatively simple Markdown is a superset of HTML, so your assertion cannot be true. But even an HTML-less subset is very hard to parse efficiently (or, at all ) because of the various grammatical ambiguities. A
25.
by shiomiru 10mo ago
> 1) pledge() lets you give high level "I just want to do I/O on what I already have", and it doesn't matter if new syscalls "openat2" (should be blocked) or "getrandom" (should be allowed) are cre
26.
by shiomiru 10mo ago
> So even if one uses Cosmopolitan libc, if you link to some other library that library may also do direct syscalls. And which syscalls is does, and under which circumstances, is generally not part of the ABI promise. So this can still b
27.
by shiomiru 10mo ago
I've just tried and when I open a bunch of new tabs, Firefox truncates the "new tab" text to "new" and a Firefox logo. Same thing happens with other titles. (Then at some point it stops truncating and scrolls off t
28.
by shiomiru 10mo ago
Popular browsers support tabs. When you have many tabs open, it's hard to show a meaningful title for each one. An icon takes up less place and is easier to scan for visually.
29.
by shiomiru 10mo ago
> Seccomp was never actually usable It's barely usable by itself but I don't think it's an inherent problem of seccomp-bpf, rather the lack of libc support. Surely the task of "determine which syscalls are used for f
30.
by shiomiru 11mo ago
Yeah it's so sparse on actual details of Sumerian or cuneiform that after reading the article I remain unconvinced the "author" either cares for or knows anything about the topic. (To be clear I know nothing about it either,

More ›