cultural reviewer and dabbler in stylistic premonitions

  • 39 Posts
  • 245 Comments
Joined 5 years ago
cake
Cake day: January 17th, 2022

help-circle

  • But why rewrite programs that existed for decades and have proven their stability and safety? Rewriting them to Rust won’t make them safer, it will just introduce the kind of issues original versions have got fixed long ago.

    Of course rewriting them will introduce some new issues, but it will also eliminate classes of bugs from which there are definitely still a great many in old “stable” C code (bugs which are now being discovered and will presumably continue to be discovered at a much faster pace due to LLMs).

    The whole project is about abolishing GPL. And Rust is just an excuse.

    I don’t think it is just an excuse; I believe that improving security is also a goal… but removing GPL code is clearly also part of their motivation :(






  • For each participant, Dialog logs a membership status, every retreat the person has attended, a biography, a home city, and a private access token. WIRED is not publishing the tokens, which function as login credentials, or the personalized account links that contain them.

    This is an odd thing to say given that neither Wired nor their source (“the Swiss hacktivist maia arson crimew”) appear to be publishing any of the actual data whatsoever, beyond the handful of mostly nonspecific references to it in the article text. (Eg, lots of sentences like “The website directory names sitting Trump administration officials, two US senators, six members of the Paypal Mafia, a former Middle East chief of intelligence, and a sitting ambassador to the United States, along with the founders and directors of many of the country’s largest surveillance, data-broker, and advertising-data companies.” - omitting names of any of these people.)

    Also, the linked archive says:

    Update 6/16/2026, 5:47 pm EDT: WIRED updated this article to correct a conflation of two people named Jeff Epstein. A small revision was also made to address a security concern raised by a Dialog representative.

    Someone helpfully had already made an earlier archive before that, so we can see what information Wired journalists Dell Cameron and Yulia Almazova removed at the request of a Dialog representative: where it now says “The retreat is scheduled for August 12-16 at a venue near Dublin” it originally said “The retreat is scheduled for August 12-16 at the Powerscourt Hotel outside Dublin”.


  • One shot rewriting the whole test suite

    tridge’s blog post makes it clear that this was not “one-shotted” at all.

    You should read the whole thread

    I regret reading it; I’ll assume in good faith that it wasn’t LLM generated but it is ironically as confidently wrong as if it were.

    It almost (and should have) lost me when it started by quote-agreeing with someone else saying “rsync was basically done until the maintainer discovered vibecoding” - no, pay attention, it was not “basically done”, there were/are a mountain of CVEs!

    But then this got my interest:

    This does not “translate tests into pytest” or a unit testing framework, it writes its own testing framework where tests are whole python scripts that redefine basic test functions in every script. Surely there would be a single way to “run rsync and get the results” - nope, well, there is, but then every test file will randomly redefine its own _run_and_capture function.

    tridge says he has used pytest on other projects and had good reasons not to use it here; I’m inclined to believe him.

    But the notion of every test defining its own way to invoke rsync sounded like a valid criticism, and an easy one to verify, so I checked: It turns out that there is in fact a common run_rsync function which is used by the majority of the tests. One test defines its own _run_and_capture function (which differs in that it writes the output to a file, for reasons I didn’t investigate), and it looks like a few others invoke rsync other ways, but the majority of them use the common function.

    So, that rambling thread’s sole concrete criticism of rsync’s new python tests turns out to be false.











  • Nice, thanks.

    It would certainly be nice to be able to pre-download language pair models without selecting to and from and then actually initiating a translation using the model i don’t have yet.

    re: getting uBlock externally, i also see the attraction of that approach but unfortunately Debian’s package was last updated in October (from 1.62 to 1.67) while AMO has a release from January (1.69) :/

    imo it would be better to bundle UBO and ship its updates along with browser updates.

    are there plans to distribute Konform via flathub?




  • could Red Hat eventually take control of the project

    Fedora started in 2002 and merged with “Red Hat Linux” in 2003.

    Red Hat, Inc has had full control of it ever since then.

    It is a “community project” inasmuch as there are Fedora developers who are volunteers (and some who are paid by companies other than Red Hat), and the Fedora Council includes people who are not employed by Red Hat - but the Project Leader is always a Red Hat employee, and if the Council ever has an irreconcilable difference with Red Hat then Red Hat can simply ignore and/or dismiss them.

    Red Hat owns all Fedora-related trademarks, and the Fedora Project is not an independent legal entity: it is a part of Red Hat.

    If Fedora developers don’t like Red Hat’s decisions regarding the project, they can fork it but they’d need to change the name and find some other sources funding.

    Also, icymi, Red Hat became a subsidiary of IBM in 2019.


  • I don’t think anyone called those “web apps” though. I sure didn’t.

    As I recall, the phrase didn’t enter common usage until the advent of AJAX, which allowed for dynamically loading data without loading or re-loading a whole page. Early webmail sites simply loaded a new page every time you clicked a link. They didn’t even need JavaScript.

    The term “web app” hadn’t been coined yet but, even without AJAX I think in retrospect it’s reasonable to call things like the early versions of Hotmail and RocketMail applications - they were functional replacements for a native application, on the web, even though they did require a new page load for every click (or at least every click that required network interaction).

    At some point, though, I’m pretty sure that some clicks didn’t require server connections, and those didn’t require another page load (at least if js was enabled): this is what “DHTML” originally meant: using JavaScript to modify the DOM client-side, in the era before sans-page-reload network connections were technically possible.

    The term DHTML definitely predates AJAX and the existence of XMLHTTP (later XMLHttpRequest), so it’s also odd that this article writes a lot about the former while not mentioning the latter. (The article actually incorrectly defines DHTML as making possible “websites that could refresh interactive data without the need for a page reload” - that was AJAX, not DHTML.)