Need to let loose a primal scream without collecting footnotes first? Have a sneer percolating in your system but not enough time/energy to make a whole post about it? Go forth and be mid: Welcome to the Stubsack, your first port of call for learning fresh Awful you’ll near-instantly regret.

Any awful.systems sub may be subsneered in this subthread, techtakes or no.

If your sneer seems higher quality than you thought, feel free to cut’n’paste it into its own post — there’s no quota for posting and the bar really isn’t that high.

The post Xitter web has spawned soo many “esoteric” right wing freaks, but there’s no appropriate sneer-space for them. I’m talking redscare-ish, reality challenged “culture critics” who write about everything but understand nothing. I’m talking about reply-guys who make the same 6 tweets about the same 3 subjects. They’re inescapable at this point, yet I don’t see them mocked (as much as they should be)

Like, there was one dude a while back who insisted that women couldn’t be surgeons because they didn’t believe in the moon or in stars? I think each and every one of these guys is uniquely fucked up and if I can’t escape them, I would love to sneer at them.

Last week’s thread

(Semi-obligatory thanks to @dgerard for starting this)

  • froztbyte@awful.systems
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    8 hours ago

    an idea I just had (which would need some work but talking hypothetical): wouldn’t it be lovely if IDEs VS Code[0] automatically inserted “Copilot Used Here” start/end markers around all generated shit. could even make it a styleguide/editorconfig so it’s universally set across projects[1]

    [0] - because lol ofc it’s mainly vscode rn

    [1] - and then when you find colleagues who lie about whether they’re using it you wrap all their desk shit in foil

    • nightsky@awful.systems
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 hours ago

      I like the idea. Or maybe marking such changes in the commit message… I might try to bring that up when the time comes.

      • froztbyte@awful.systems
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 hours ago

        in the current most-typical mode of engagement, commit messages are too disconnected from the actual contents. it requires someone who gives a shit to go looking

        conversely, what I mean is something like “a hook that guarantees that the moment the plugin is engaged and output from it is scribed in source, metadata about that event is simultaneously co-written”

        it’s already generating a pile of other things, it may as well generate timestamps and callsig and callhash and shit too…

        the number one problem with this, of course, is that it’s going to be extremely unpopular with a Vocal Set Of People who rely on this shit to make themselves look good