[–] 14 points 4 days ago* (last edited 4 days ago) (1 child)

via https://nitter.perennialte.ch/search?f=tweets&q=%22trees+are+a+social+construct%22 (which has lots more):

i wonder if this is the same person as the one in the screenshot? this was maybe their first post about it, with 10 replies. it looks like the main account they were talking to was suspended, but you can see a screenshot of maybe-it here.

edit: yeah it must be the same event, since they also mention palm trees and wood here

  • source
  • parent
  • context
  • [–] 0 points 1 week ago* (1 child)

    I don’t really want to become the judge of what is “heavily-AI-assisted”.

    imo it doesn't really take much in the way of judgement; usually it is pretty obvious when there is one developer and the README is written in LLM voice and the project is a few weeks or days old.

    I think if I were to write a rule I would focus more on self-promotion in general than trying to decide how AI assisted it was

    I think that would also be a good rule, but wouldn't stop people from promoting others' slop or from promoting their own while pretending it isn't.

    I would generally rather rely on user votes to decide if it is “worth it” or not

    unfortunately there are sometimes cases (such as the post i deleted here yesterday) where a post will have mostly upvotes despite being not-even-open-source. there are also things which are freely licensed, but get many upvotes despite being absurdly bad vibe-coded ideas - eg, this centralized IPFS web directory making contradictory privacy claims 🫠 (imo that should be deleted; what do you think?)

  • source
  • parent
  • context
  • [–] 3 points 1 week ago* (last edited 1 week ago) (3 children)

    Curious. Woke up to find my post removed at almost exactly the same time you posted this, complete with an accusation of “slop”.

    yes, after a brief assessment i concluded (correctly, i see now after taking another look at it) that your project is exactly the kind of new, single-developer, vibe-coded slop which i think we should not accept the promotion of here... and yes, seeing and deleting your post was what reminded me that i've been meaning to post something in this thread.

    however, after i deleted it for being slop, i also noticed another reason it is not suitable for this community: as @thingsiplay@lemmy.ml helpfully pointed out in the comments, your README says this:

    To that end, I’m publishing the current 32.71 source code and final release, with the source code frozen at this version.

    Download the APKs from the SmartTube LOCAL GitHub Releases page.

    I’ll continue to publish updated APKs as I hatch them.

    So, it isn't even an open source project going forward: the released source code is "frozen" and future versions will be binary-only? so, in this case you actually shouldn't post this in the !aials@lemmy.ml community either 🤦

    fwiw i am personally not completely opposed to AI-assisted coding; i am also doing some of it myself. however i think everyone should be skeptical of new single-developer vibe-coded projects - most are very low quality and will be abandoned in the near future.

    The latter leads to things like this.

    This is exactly what the new community is meant to address: to have a place for people to share their AI-created softwares without getting a flood of hate for it being made with AI.

  • source
  • parent
  • context
  • [–] -1 points 1 week ago (8 children)

    imo this community should have a rule against posts promoting new primarily-written-with-an-LLM software projects. as an admin, i've deleted a few myself when there are reports of them and the mods aren't resolving them.

    banning all AI-assisted software is obviously no longer reasonable now that many large and old projects are using it (with varying levels of care...) but I don't think we actually need a very firm definition of "slop" to be able to say some things clearly are slop and some AI-involved things clearly aren't. When in doubt about if something is of sufficient quality that we should keep it here, the age of the project and the number of developers involved are useful secondary metrics.

    @gary_host_laptop@lemmy.ml created a new community which I think should be linked in the sidebar here as an alternate place for sharing these things. How about this for a rule (in the !opensource@lemmy.ml sidebar)?

    This is not a place to promote new single-developer heavily-AI-assisted projects. Another community exists for sharing AI-Assisted Libre Software: !aials@lemmy.ml

    note that the word "slop" is intentionally absent from my proposed rule (and from name and description of the community) - the point is that this is a place for people to share their AI-created software, regardless of if it is 100% vibe coded or is actually high-quality "agentic engineering" - only time, review, and users will ultimately tell which category many of these new things fall into. But enough of it is slop that we shouldn't have this community flooded with it, imo.

    cc @CrypticCoffee@lemmy.ml @Lettuceeatlettuce@lemmy.ml @kevincox@lemmy.ml

  • source
  • [–] 5 points 1 week ago (2 children)

    The new edition, known as TUXEDO OS “Continuous Debian,” replaces the distribution’s traditional Ubuntu foundation with Debian Testing. The change denotes a significant shift for TUXEDO OS, which is developed by German Linux hardware manufacturer TUXEDO Computers.

    [...]

    Unlike Debian itself, which periodically promotes its Testing branch to Stable, TUXEDO OS will remain permanently based on Debian Testing.

    🤔

    https://www.debian.org/security/faq#testing currently says:

    Q: How is security handled for testing?

    A: Security for testing benefits from the security efforts of the entire project for unstable. However, there is a minimum two-day migration delay, and sometimes security fixes can be held up by transitions. The Security Team helps to move along those transitions holding back important security uploads, but this is not always possible and delays may occur. Especially in the months after a new stable release, when many new versions are uploaded to unstable, security fixes for testing may lag behind. If you want to have a secure (and stable) server you are strongly encouraged to stay with stable.

    I wonder if TUXEDO Computers plans to be shipping security updates themselves faster than Debian testing does?

  • source
  • [–] [S] 0 points 1 week ago* (2 children)

    LPEs are not RCEs

    They didn't say they were, the post is very clear about the the 948 vulns they're talking about being LPE.

    If it’s a bunch of local jvm consoles or vi escapes into shell

    if it was that, they wouldn't be "Linux LPEs". These are clearly kernel bugs they're talking about.

    And again, stop taking OpenAI at their word about security.

    OpenAI is full of shit about a lot of things but I doubt they're lying about having working exploits for these Linux bugs.

  • source
  • parent
  • context
  • [–] [S] 8 points 1 week ago (5 children)

    Sure, you can generate a list of places to start testing, but each of those has to be validated, reproduced, documented and understood before it’s confirmed

    i guess you didn't actually read the blog post this article links to? The number in the headline (948) is the number of LPE bugs which they say they validated and reproduced and developed exploits (and patches) for.

  • source
  • parent
  • context
  • [–] [S] 14 points 1 week ago* (last edited 1 week ago)

    Something else AI’s ruining…

    can you explain what you mean by this? are they ruining linux by revealing its bugs at a much faster rate? or ruining the security research field by depriving researchers of the challenge and enjoyment of finding these bugs themselves?

    repeating myself from a previous thread: of all the things i hate about LLMs, getting vulnerabilities in important software like linux discovered and fixed is not one of them

    (although, as i said elsewhere in this thread, i find it unlikely that openai is actually disclosing all of the bugs they find 😬)

  • source
  • parent
  • context
  • [–] [S] 30 points 2 weeks ago (2 children)

    it's a bit odd how openai's blog post makes it sound like security bugs in Linux fall in two categories, info leak and local privilege escalation. i would guess that they probably did also ask their model to find some RCEs, but they're selling those to exploit vendors (or perhaps to intelligence agencies directly?) rather than blogging about fixing them.

  • source
  • view more: next ›