LaVillaStrangiato

joined 2 weeks ago
[–] LaVillaStrangiato@infosec.pub 3 points 1 week ago (1 children)

With licenses, I don't think the goal is to create one universal standard. More options is typically better.

I'm afraid that might be correct :( perhaps closing off software to the public will be the only way to prevent it from getting stolen

 

Built for data storage in small personal projects, or mocking an API for development. Advantages are simplicity, interoperability (JSON files, APIs, multiple filesystems) and performance (using the cache system).

The API is based on your JSON files/structure. So, the example below is for CRUD-ing [key1][key2] in file.json. The value (which can be anything) is then added to the body of the request. Moreover, there are helper functions for appending and incrementing values. As a result, the data creates the API.

DELETE/PUT/GET: /api/file/key1/key2/...

*neil peart...but yes very true

Not a lawyer, but I don't think so. there are licenses that extend existing licenses with that clause, like BSD NON-AI

[–] LaVillaStrangiato@infosec.pub 5 points 1 week ago (1 children)

tenfingers looks cool btw, hadn't heard of it yet. Is it your project?

[–] LaVillaStrangiato@infosec.pub 9 points 1 week ago (2 children)

If you have software using this license, feel free to share under this post :)

 

TLDR: It's compatible with other copy-left licenses like GPLv3. However, it's available in multiple languages, which technically makes it more applicable.

I started using it for my own project. If you want a practical example: https://github.com/TimoKats/emmer