The screenshot clearly is not talking about the json text file format, but a PHP extension called json.
Comment on Evil
renzev@lemmy.world 4 weeks ago
OK but how can json have a license? I understand a particular json parser having a license, but how can a specification, which contains no code, even be considered “software”?
shasta@lemm.ee 4 weeks ago
renzev@lemmy.world 4 weeks ago
Yes, but the “shall be used for Good, not Evil” part is part of the json license, not the PHP extension? json.org/license
Nomecks@lemmy.ca 4 weeks ago
Where do I report Twitter?
frayedpickles@lemmy.cafe 4 weeks ago
Uh define code there. What about when storage and code are both on a machine that considers both instructions and data to be data?
AnyOldName3@lemmy.world 4 weeks ago
It’s generally accepted that file formats aren’t protected IP, so you can write a compatible reader or writer and be in the clear as long as you reused no code from the original reader/writer. The specification may have licence terms that restrict who you can share the spec with, but you don’t necessarily need the official spec to come up with a compatible implementation. Plenty of file formats have been reverse engineered over the years even when the original didn’t have a written spec.
frayedpickles@lemmy.cafe 4 weeks ago
My comment was more that it’s not sacred, it’s all just stuff.