• 0 Posts
  • 10 Comments
Joined 2 years ago
cake
Cake day: August 2nd, 2023

help-circle




  • Well, you can theoretically make a second app-view “instance”, call it “Greenearth” or something, and have different policies than Bluesky on how to verify or select content. But until someone actually does so, it’s not really decentralized. I’m not sure what’s stopping people from doing so, but it’s been a while, so I assume there must be some roadblock.

    There’s also the issue of how Blueky itself was depicted as the decentralized network - when it’s more akin to a single instance, instead.


  • Currently not, because it’s not de-facto decentralized. There would need to be multiple relays, managed by different organizations, AND multiple app views, also managed by different orgs, for me to consider it such.

    The non-existence of de facto decentralization indicates that the ecosystem doesn’t actually promote decentralization, even though it technically allows for it.



  • The fact is, currently, AI can’t write good code. I’m sure that at some point in the future they will - but we’re not there yet, and probably have some years still.

    Imagine at some point in the future, where an AI can program any piece of software you want for you, and do it well. At that point, the value of code itself will be minimal. If you keep your code proprietary, I’ll just get the AI to re-implement the functionality anew and publish it.

    Therefore, all code will be permissive open source. There would be no point in keeping anything proprietary, and also no point in applying copyleft. But at this point the copyleft “hack” would simply be unnecessary, so permissive open source would be just as good.

    Until then, me not using AI doesn’t in any way prevent others from training AI on my code. So I just don’t see training on my code as a valid reason to avoid it. I don’t use AI currently - but that’s for entirely pragmatic reasons: I’m not yet happy with the code it generates.


  • with a long tail of grumpy holdouts who adhere to free software principles

    Nothing in the core free software principles - namely, the four freedoms - actually concerns the development process and tools used - or copyright. It’s all about what you can do with the software.

    The GPL is more of a “hack” that “perverts” copyright to enforce free software principles - because that was the tool available, not because the people who wrote it really liked intellectual property.