• 2 Posts
  • 20 Comments
Joined 2 years ago
cake
Cake day: June 26th, 2023

help-circle






  • Before I forget: many thanks for your response! It’s nice to discuss this.

    That distinction is important indeed. I could always add a notice to the README to underline that for potential users.

    I’m going to make a dependency map of our own libs and license the language tools and their dependencies as LGPL such that they can be relatively freely embedded in other products. The post-processing and analysis libs/applications will then be licensed under the AGPL (dual licensing). We had other libraries under the GPL before, but in the current landscape it seems wise to cover the hosted/embedded variations as well.


  • Hmm, I don’t know of many widespread (programming) languages with an AGPL-alike license, but would love to see examples! Wouldn’t a language have a better chance of adoption with an easy to integrate licensed library?

    As for some full featured visualization and analysis applications that accept the language’s data format: those might be a good fit for AGPL as they generate valuable insights.

    With non-core stuff I meant a tiny wrapper around some 2D data or some color palette management. I’m fine with MIT/Apache there and would consider LGPL to keep the landscape simpler.







  • I think they should stick to the “email provider” analogy. Whole paragraph should be something like:

    The only thing you need to start interacting with the Fediverse is an account with one of the many providers, just like with email! Providers are freely available across the globe: pick one that suits your location or interests best! You can start browsing the content of nearly the entire Fediverse from whatever provider you choose. Don’t worry, you can always create an account with a different provider later.

    You could add a sentence or two about where to find sensible defaults or link an article that explains the more subtle things.

    I think the emphasis on instances (and not naming them the more familiar providers) hinders adoption.









  • I love building my own uBlue image. Tinkering is done in toolbox containers, definite changes are baked into the image. Completely custom (to me) and when you get it right it will just work anywhere. If I would brick my PC/storage I can just boot up another and restore my (back-upped) home dir with very little effort.