This is peak licensing
this post was submitted on 17 Dec 2024
780 points (99.4% liked)
Lemmy Shitpost
27131 readers
3180 users here now
Welcome to Lemmy Shitpost. Here you can shitpost to your hearts content.
Anything and everything goes. Memes, Jokes, Vents and Banter. Though we still have to comply with lemmy.world instance rules. So behave!
Rules:
1. Be Respectful
Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.
Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.
...
2. No Illegal Content
Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.
That means:
-No promoting violence/threats against any individuals
-No CSA content or Revenge Porn
-No sharing private/personal information (Doxxing)
...
3. No Spam
Posting the same post, no matter the intent is against the rules.
-If you have posted content, please refrain from re-posting said content within this community.
-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.
-No posting Scams/Advertisements/Phishing Links/IP Grabbers
-No Bots, Bots will be banned from the community.
...
4. No Porn/Explicit
Content
-Do not post explicit content. Lemmy.World is not the instance for NSFW content.
-Do not post Gore or Shock Content.
...
5. No Enciting Harassment,
Brigading, Doxxing or Witch Hunts
-Do not Brigade other Communities
-No calls to action against other communities/users within Lemmy or outside of Lemmy.
-No Witch Hunts against users/communities.
-No content that harasses members within or outside of the community.
...
6. NSFW should be behind NSFW tags.
-Content that is NSFW should be behind NSFW tags.
-Content that might be distressing should be kept behind NSFW tags.
...
If you see content that is a breach of the rules, please flag and report the comment and a moderator will take action where they can.
Also check out:
Partnered Communities:
1.Memes
10.LinuxMemes (Linux themed memes)
Reach out to
All communities included on the sidebar are to be made in compliance with the instance rules. Striker
founded 2 years ago
MODERATORS
Wait I though the point of these post-opensource clauses (see also: anti-capitalist licence, WTFPL, etc.) was to scare off the big corporations lawyers and make sure your code won't end up in AWS or something like that? Are Linux distros the only actors who are still giving a shit about licencing?
Always were.
Big companies care too but only if their cya arm knows enough about software to actually enforce anything. A lot don't.
The biggest problem with such a clause is that it is hard to define "evil", even if it seems clear to you. Some people think that abortion is evil, so are abortion clinics banned from Json? What about the military and weapon manufacturers? Killing is evil, but you all know how the discourse about the military as national heroes that can't be evil in the US goes. What about a service like X - is it evil? Can you define "evil" for a surveillance tool that brands itself as ad tech?
The clause also states that the product MUST be used for Good, which is a higher bar. I'd imagine most things JSON is used for are fairly morally neutral.
Yeah I would imagine this is the point
Ask every single person what is the definition of evil and merge all the answers into one definition
That'd be all the things.
You'd end up with Schrödinger's Evil
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"?
Uh define code there. What about when storage and code are both on a machine that considers both instructions and data to be data? Is a spec not a creative work? Is code not just a spec?
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.
can we please pronounce that evil in a British accent: ivil
fun fact: IBM asked for, and got, an exception from that clause.
Well, IIRC they did work with the Nazis to manage concentration camps and more
https://www.historynewsnetwork.org/article/ibms-role-in-the-holocaust-new-documents-confirm-t
Did they reveal what the evil task they were using it for was?
They make chips for missiles.
Knowing IBM, probably something to do with Nazis
I guess they'll use JSON when they're building the database to do the next holocaust.
load more comments
(4 replies)
So do you use JSON for your endpoints?
No we use XML
Oh interesting why is that?
Uhhh.....no reason
Well SOAP is inherently evil so that just makes sense
I work with SOAP for a legacy API
fucking kill me, I beg you
No can do, but I can put you in an envelope, head optional.
At least it's not GraphQL
GraphQL saved my ass on a term project that required extensive polling of the GitHub API. Turned a calculated 47 days of calls just under the rate limit into just 12 hours.
load more comments
(2 replies)
I'll be downloading this one
How does one address the paradox that, as JSON itself is evil, one cannot use it for evil?
(opinions may vary on the above; but it's mine, so nyah nyah.)
It's less evil than XML or YAML
YAML is (mostly) a superset of JSON. Is the face hugger any less evil than the alien bursting out of your chest?
load more comments
(3 replies)
XML is ok for complex docs where you have a detailed structure and relationships. JSON is good for simple objects. YAML is good for being something to switch to for the illusion of progress.
Meh. I just wish XML was easier to parse. I have to shuttle a lot of XML data back and forth. As far as I can tell, the only way to query the data is to download a whole engine to run a special query language, and that doesn't really integrate into any of my workflows. JSON retains the hierarchy and is trivially parsed in almost any programming language. I bet a JSON file containing the exact same data would be much smaller also, since you don't list each tag twice.
There are parsing libraries, maybe not as many or as open, but they exist.
load more comments
(5 replies)
view more: next ›