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

help-circle



  • The problem is the cat’s out of the bag.

    Open source image generators already exist and have been widely disseminated worldwide.

    So all you’d end up doing is putting up a roadblock for legitimate uses. Anybody using it to cause harm will not be seriously impeded. They can just pick up the software from a Russian/Chinese/EU host or less official distribution methods.

    It would be as effective as the US trying to outlaw the exporting of strong encryption standards in the 90s. That is to say, completely ineffective and actually harmful. Enemies of the US were still using strong encryption anyway.












  • 520@kbin.socialtoProgrammer Humor@lemmy.mlcodeStyle
    link
    fedilink
    arrow-up
    1
    arrow-down
    2
    ·
    11 months ago

    So this looks like it’s based in Java code.

    A public class means that any bit of Java code, including that injected by an attacker, can see and mess with the contents of that class.

    A private class, in contrast, means that other bits of Java code are restricted to running the class’s predefined functions.

    In theory it is supposed to help with the security of the data. In practice if an attacker gets to this point, you’ve got much bigger issues.