So do you use JSON for your endpoints?
No we use XML
Oh interesting why is that?
Uhhh.....no reason
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!
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
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
What happens is that engineers look at a technology and say, this is too complex, I just need something simple. So they invent and/or adopt something simpler than the popular technology of the day.
But as they build more and more things using the technology, they realize that it needs more features, so those get added on. This happens over and over again to the technology with more and more features being added to it, until a new set of engineers look at it and say this is too complex, I just need something simple...
You've just described what is probably the most well-known xkcd comic in a somewhat long-winded fashion.
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.
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.
Ask every single person what is the definition of evil and merge all the answers into one definition
That'd be all the things.
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
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.
It's still using the lesser of 3 evils, we need a fourth human readable data interchange format.
>TOML has entered the channel
Any human-readable format compatible with JSON is inevitably going to be used as an interchange format...
This is peak licensing
Spoilsports. Next they'll be telling me I can't use apple software in the development, design, manufacture, or production of nuclear, missile, or chemical or biological weapons.
Me buying my first IBM ThinkPad online:
IBM: are you planning to use this ThinkPad to produce weapons of mass destruction?
Me: I wasn't before, but now I'm curious
So if I use it to draw a rocket, I'm violating its license?
If its a design for something you plan to build then all your software is going to turn into buggy java applets and Tim Apple will give you a wet willy the next time you're trying to look cool. It's right there in the license.
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?
If you want to scare corporations use AGPL or, if you're feeling spicy, SSPL. Do not use WTFPL, it's too permissive.
Always were.
Big companies care too but only if their cya arm knows enough about software to actually enforce anything. A lot don't.
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.
The FSF also lists any software as non-free which uses the beer license (use the software in any way you want, and should you ever meet the author, pay them a beer).
I can't stand beer - is there a rum & Coke license?
I thought it was free as in speech not free as in beer? So if it costs a beer then isn't it still free (as in speech)? Or is this a OSI vs FSF difference?
Is it really contrarian to like the FSF these days? I mean people seem to hate Stallman too but both are pretty important in the history and continuing existence of free software.
The four essential freedoms are in my view as important as the FSF says, and any license that doesn't meet all four will be met with skepticism from me absolutely.
Also, the GPL is a real, legal license, and even if there's a silly clause that causes it to be incompatible, that's still a legal liability - of course they have to take it seriously.
Everybody gangsta with the "don't be evil" clause until the authors turn out to be a nutjob who thinks trans people are blights against God and must be exterminated.
I doubt (or at least hope) that that's not what they think, but hopefully that illustrates why the clause is dumb.
100%, and it doesn't seem to lay out a legal definition of "good" so it's actually worse than useless - it's ambiguous.
The question on stack overflow: PHP Fatal error: Call to undefined function json_decode()
I'll be downloading this one