• 1 Post
  • 60 Comments
Joined 3 years ago
cake
Cake day: June 23rd, 2023

help-circle
  • What’s aggravating is that SaaS companies have been using that model to skirt around GPL. Amazon has Aurora, a MySQL-based relational database, and because they don’t provide a binary, they don’t have to give out the source code. And because they aren’t freely-available binaries, they aren’t subject to decompiling efforts, either.

    That’s not to say OSS can’t just provide a binary-version of the same kind of product. But, it does mean that SaaS is going to use that as a layer of IP protection, now more than ever. Terraform (HashiCorp), Redis, and Elasticsearch (Elastic) all are trying to shift to SaaS models to increase profits, stealing the contributions from their OSS counterparts.


  • All AI-generated code should be Open Source.

    And, as people are starting to find out, all code is “open source”, in that it is incredibly easy to decompile anything. How does that t-shirt go? “Everything is open source if you know assembly.”

    Well, existing decompiling tools already knew how to reconstitute assembly into higher-level languages, and LLMs can spend the effort to figure out proper variable/function names to make it more readable.







  • You act like this is a new problem with technology. It’s not.

    When one country figures out how to make guns, the other country doesn’t just say “You know what… I’m going to stick with the same sword and shield warfare.” No, they figure out how to make guns of their own, and figure out defenses that are appropriate to gun warfare. It is the new norm, and everybody else must account for it.

    When the Internet popped into the public zeitgeist, some companies were slow to adopt but pretty soon, everybody had a website. Those that didn’t adapt to this new technology failed as a business and died.

    This is an adaptation problem, and unless people take it seriously, there will be one side that uses LLMs to their advantage and one side that doesn’t.


  • “Baseline” is subjective, so I’d recommend just start a global rules file and steer it away from the behaviors you don’t like. Don’t be afraid of quizzing the agent itself on why it did that thing, and what’s a good bit of language to add to the rules file to prevent it from happening.

    Also, for specific tasks, skill files are really useful, and LLMs can write the whole thing, based on what you did the hard way in a session. Same thing for triggering a skill file and then ask it if there are any useful improvements to make to the skills file in the future, at the end of the session.





  • More like AI is much faster at finding obscure vulnerabilities, because it doesn’t get tired of digging into the mind-numbing details of human-generated spaghetti code. Give a human the same kind of task, and they would die of boredom 12 hours into it.

    We’re entering an age where AI is quickly cleaning up the stupid security holes that have been created by decades of human mistakes, and will continue to be this way until increased AI security reviews will become more standard. The tribals wielding spears will continue to get shot by superior firepower until they adapt to the same weapons and protection themselves.