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
This gave me a brilliant idea:
This is peak licensing
Every Villain Is Lemons
E.V.I.L
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.
https://opensource.google/documentation/reference/using/agpl-policy/
AGPL policy: Don't use.
Exactly. It scares them.
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.
Space cops
I'd imagine most things JSON is used for are fairly morally neutral.
a lawsuit waiting to happen. Json has been a real dick lately sending his lawyers after everyone
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.
My comment was more that it's not sacred, it's all just stuff.
fun fact: IBM asked for, and got, an exception from that clause.
I remember when he told that story, it was something like this: one company which I don't want to name, so will just say it's initials - IBM. He also authorised usage for IBM "and it's minions".
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.
I guess they'll use JSON when they're building the database to do the next holocaust.
This isn’t talked about enough.
So do I have to look it up now? Ugh, but I am le tired
It’s talked about in this thread. The short version that IBM built a logistics machine for the Nazis that was used to coordinate the transport of supplies for the war effort and transporting people to concentration camps.
TL:DR: IBM sold machines to the Nazis that they used to track down people to put into concentration camps. It would've been harder to do if they had to rely on paper records only.
Jeez, hard to imagine them not having been paper. Sometimes it's easy to forget. Kind of like the IRS using computers older than some senators, and that's saying something.
So do you use JSON for your endpoints?
No we use XML
Oh interesting why is that?
Uhhh.....no reason
The question on stack overflow: PHP Fatal error: Call to undefined function json_decode()
As a php user, this is hilarious.
The issue shouldn't effect any php users today, as this is a issue with older versions of PHP 5.5, where the "outdated PHP 5.6" was released in 2014.
Anything on PHP 5.6 has been a security risk for half a decade already. So this is like if you were on Ubuntu 14, or Windows 8. If you have problems, it might be you.