• 0 Posts
  • 163 Comments
Joined 2 years ago
Cake day: June 30th, 2023

  • what’s likely is that users will scatter across so many sites, apps, proxies, and channels that they’ll become untraceable, guaranteeing the failure of future regulations. And unlike today, many of those new destinations will be dangerous, unmoderated, and openly hostile to enforcement.

    That seems to be the argument; that these verification laws specifically target dedicated porn sites while similar content still exists all over and is not similarly punished, which given people’s extreme and natural aversion to doing KYC for porn will cause them to leave for wherever doesn’t demand it, killing off what protections now exist against especially shady material and practices.




  • What you confuse here is doing something that can benefit from applying logical thinking with doing science.

    I’m not confusing that. Effective programming requires and consists of small scale application of the scientific method to the systems you work with.

    the argument has become “but it seems to be thinking to me”

    I wasn’t making that argument so I don’t know what you’re getting at with this. For the purposes of this discussion I think it doesn’t matter at all how it was written or whether what wrote it is truly intelligent, the important thing is the code that is the end result, whether it does what it is intended to and nothing harmful, and whether the programmer working with it is able to accurately determine if it does what it is intended to.

    The central point of it is that, by the very nature of LKMs to produce statistically plausible output, self-experimenting with them subjects one to very strong psychological biases because of the Barnum effect and therefore it is, first, not even possible to assess their usefulness for programming by self-exoerimentation(!) , and second, it is even harmful because these effects lead to self-reinforcing and harmful beliefs.

    I feel like “not even possible to assess their usefulness for programming by self-exoerimentation(!)” is necessarily a claim that reading and testing code is something no one can do, which is absurd. If the output is often correct, then the means of creating it is likely useful, and you can tell if the output is correct by evaluating it in the same way you evaluate any computer program, without needing to directly evaluate the LLM itself. It should be obvious that this is a possible thing to do. Saying not to do it seems kind of like some “don’t look up” stuff.


  • Are you saying that it is not possible to use scientific methods to systematically and objectively compare programming tools and methods?

    No, I’m saying the opposite, and I’m offended at what the author seems to be suggesting, that this should only be attempted by academics, and that programmers should only defer to them and refrain from attempting this to inform their own work and what tools will be useful to them. An absolutely insane idea given that the task of systematic evaluation and seeking greater objectivity is at the core of what programmers do. A programmer should obviously be using their experience writing and testing both typing systems to decide which is right for their project, they should not assume they are incapable of objective judgment and defer their thinking to computer science researchers who don’t directly deal with the same things they do and aren’t considering the same questions.

    This was given as an example of someone falling for manipulative trickery:

    A recent example was an experiment by a CloudFlare engineer at using an “AI agent” to build an auth library from scratch.

    From the project repository page:

    I was an AI skeptic. I thought LLMs were glorified Markov chain generators that didn’t actually understand code and couldn’t produce anything novel. I started this project on a lark, fully expecting the AI to produce terrible code for me to laugh at. And then, uh… the code actually looked pretty good. Not perfect, but I just told the AI to fix things, and it did. I was shocked.

    But understanding and testing code is not (necessarily) guesswork. There is no reason to assume this person is incapable of it, and no reason to justify the idea that it should never be attempted by ordinary programmers when that is the main task of programming.


  • The problem, though, with responding to blog posts like that, as I did here (unfortunately), is that they aren’t made to debate or arrive at a truth, but to reinforce belief. The author is simultaneously putting himself on the record as having hardline opinions and putting himself in the position of having to defend them. Both are very effective at reinforcing those beliefs.

    A very useful question to ask yourself when reading anything (fiction, non-fiction, blogs, books, whatever) is “what does the author want to believe is true?”

    Because a lot of writing is just as much about the author convincing themselves as it is about them addressing the reader. …

    There is no winning in a debate with somebody who is deliberately not paying attention.

    This is all also a great argument against the many articles claiming that LLMs are useless for coding, in which the authors all seem to have a very strong bias. I can agree that it’s a very good idea to distrust what people are saying about how programming should be done, including mistrusting claims about how AI can and should be used for it.

    We need science #

    Our only recourse as a field is the same as with naturopathy: scientific studies by impartial researchers. That takes time, which means we have a responsibility to hold off as research plays out

    This on the other hand is pure bullshit. Writing code is itself a process of scientific exploration; you think about what will happen, and then you test it, from different angles, to confirm or falsify your assumptions. The author seems to be saying that both evaluating correctness of LLM output and the use of Typescript is comparable to falling for homeopathy by misattributing the cause of recovering from illness. The idea that programmers should not use their own judgment or do their own experimentation, that they have no way of telling if code works or is good, to me seems like a wholesale rejection of programming as a craft. If someone is avoiding self experimentation as suggested I don’t know how they can even say that programming is something they do.







  • If successful employee owned businesses are formed and accumulate capital they should be able to perpetuate employee ownership

    One issue is, that isn’t necessarily the priority the employee owners will have. I followed some news of a successful coop business where I lived, that sold the business because it had become worth so much that the payout was life changing money for all of those people, so they voted to take the money and potentially retire sooner rather than keep going as a coop.



  • This constant surveillance could tax cognition in ways that we don’t yet understand. The faculties compromised by surveillance “are those that allow us to focus on what we’re doing: attention, working memory, and so on,” Belletier says. “If these processes are taxed by being monitored, you’d expect deteriorating capacity to concentrate.”

    Well that checks out



  • Complex requirements for social media websites to verify the identity of users, respond to spurious automated takedown requests, provide authorities with backdoors, etc. I think instead of explicit bans, it’s more likely they pass a regulations that are made for large websites with lawyers and algorithmic moderation, which are in practice not something fediverse instance operators can safely deal with and go against the basic values of the open internet.



  • They mentioned Microsoft updating privacy agreements at the same time as other companies, and OP mentioned that the context was a discussion of a Windows ultra-keylogger type of feature, the implication is they’re in on this shit too, and Linux is a way to not use Windows.


  • Open source code doesn’t mean open API though. Bluesky seems to have made a whole thing out of their technical architecture, and I get the arguments that it’s centralized in practice, but wouldn’t it mean basically scrapping the whole thing to lock down third party clients? Even if that didn’t mean anything I think multiclients could be a good idea anyway, if people were using those and there was a Reddit situation, some portion of users would want to stay with the same clients rather than using whatever proprietary app they try to push.


  • I don’t use these so maybe I’m missing something, but why would you have to choose? Bluesky is centralized but it seems like its design is committed enough to open technology that it would take them a long time to walk it back, and in the meantime there shouldn’t be barriers to using unified clients that put content from both in the same interface, and possibly override any opinionated content algorithm from the company (not sure if that’s feasible or not).