Install Guix

  • 9 Posts
  • 245 Comments
Joined 5 months ago
cake
Cake day: March 17th, 2026

help-circle
  • The share option within Claude tells a user that “anyone with the link” may view the contents of that link, but does not explicitly state that the link may end up in Google and search results.

    It seems like people clicked the “make chat public” button and then shared the link with someone who eventually posted it on a page that got crawled?

    Maybe there’s two mistakes here: 1: the user made the chat public and 2: Maybe Anthropic didn’t have their robots.txt file set correctly?

    I mean, it seems like the big mistake here is from the users… they clicked the “make this chat public”… unless I’m missing something?



  • lol. Weird article yeah.

    The searches showed Claude chats for which a user had decided to “share” a link had been saved by search engines like Google, leaving them accessible to the broader public.

    So… people created public links, shared them to the public, and got surprised they were public?

    The share option within Claude tells a user that “anyone with the link” may view the contents of that link, but does not explicitly state that the link may end up in Google and search results.

    LOL. Yeah!








  • Spent some time reading this: https://rosenlaw.com/OSL3.0-explained.htm

    Section IV. Source Code And Derivative Works seems interesting.

    … authorizes licensees “to translate, adapt, alter, transform, modify, or arrange the Original Work, thereby creating derivative works (” Derivative Works “) based upon the Original Work.” …

    Only the Source Code of the Original Work or the Source Code of a modified (altered, etc.) Derivative Work must be disclosed.

    If linking (by whatever technical means) can be accomplished by making and using unmodified copies of the Original Work, then 1(a) and 1© permit that; only the Source Code of the Original Work must be disclosed.

    I’m totally not qualified to comment on this, but it kiiiinda seems like OSL 3.0 would capture the work2.go file. At least, it doesn’t seem to give up on work2.go as easily as the MPL 2.0…

    Maybe a better middle ground between GPL and MIT? It seems like: if you purely use my library, then you don’t disclose anything. But if you touch my library, then you have to disclose the (entire) change?


  • Seems kinda pointless, no?.. I mean, I get MPL is a weak copyleft license… but sheesh, that weak? If the consumers get to hide 99% of their code, why not just pick MIT? Having the consumers publish a 1 line change seems pretty worthless.

    I understand if I want stronger protections, I could move to a GPL license, but is there no middle ground? MPL doesn’t really seem like middle… it seems like just 1 step away from MIT.

    LGPL seems interesting, but it doesn’t really seem compatible with languages like Go, where everything is compiled statically.

    I guess I’m missing the context the MPL was created for.




  • uuj8za@piefed.socialtoTechnology@lemmy.worldCodeberg bans vibe coded projects
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    1
    ·
    10 days ago

    Exactly.

    Boosters: There’s no way to enforce this! This rule shouldn’t exist. You can’t be 100% sure a project isn’t slop. Keep the flood gates open.

    Reality: We also can’t 100% enforce that people follow the speed limit, but we have speed limit laws. When we catch someone, we can point to the law. The mere existence of the law also acts as a small deterrent.

    Same with Codeberg. We can’t 100% enforce the ban, but when we catch someone we’ll be able to point to the rule and kick em out. And just seeing an “AI not welcome” sign on the wall will deter some amount of people.







  • And no, AI isn’t perfect. But Christ, anybody who points to the problems at AI had better be looking in the mirror and pointing at themselves at the same time.

    No one is saying humans are perfect either. But Christ, the scale is clearly not the same. Before, an average bad dev had a limit blast radius. Now they can push a million lines of code and write a convincing description of why this is actually correct with little effort.

    later

    (Oops. Wait. You’re right to push back. This is totally wrong. This should have never happend.)