Web developer. Lead developer of PieFed

  • 161 Posts
  • 1.73K Comments
Joined 3 years ago
cake
Cake day: January 4th, 2024

help-circle





  • It looks like there is an ‘enable toxic mode’ setting that DOES switch off the auto-updating blocklist. The LLM that wrote this post claimed that there is no way to turn it off.

    from src/lib/policies/system.ts:

    export async function updateSystemFilterPolicy() {  
        if (SBDisabled && get(userSettings).enableToxicMode) {  
            SYSTEM_POLICY.set(BLANK_SYSTEM_FILTER_POLICY)  
            return  
        }  
       // auto-update of blocklist continues below  
    

    The original post was written using AI so it’s going to have a lot of inaccuracies like that.

    Overall though, having gone through the code myself, the LLM is in the right ballpark. The most friendly evaluation I can give is that this does seem poorly documented, too opaque and overly prescriptive. And needlessly encrypting the payload looks very shifty.

















  • Apparently Bun was always an especially bad example of how to use Zig.

    From https://andrewkelley.me/post/my-thoughts-bun-rust-rewrite.html

    The Zig team regularly checks in on our users’ projects. We read source code to find out how the language is affecting users, we test changes to see how problematic breakage might be, and we check for performance regressions.

    We became increasingly horrified at the programming practices we saw in Bun’s codebase. Hacks on top of hacks. Abuse of assertions. Most of all, recklessly speeding past feature after feature with very little time taken for reflection and elimination of bugs and technical debt. Jarred was already writing slop well before he had access to LLMs. Now, it’s not our business to police what our users do, but you may have noticed people screaming in our faces about memory safety constantly. You can imagine how we might want to put some social distance between ourselves and a project whose irresponsible software engineering practices invite the exact kind of criticism that people are eager to level.

    We made futile attempts to guide them towards better programming practices. There were a few exceptional heroes who did their very best in a dysfunctional company. You know who you are. But you can’t stop a rising tide.

    By this time, we all felt at ZSF that Bun was a net liability, and this was before RoboBun became the #1 contributor.