this post was submitted on 17 Dec 2024
1116 points (99.4% liked)

Lemmy Shitpost

27200 readers
4033 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/ExplicitContent


-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

2.Lemmy Review

3.Mildly Infuriating

4.Lemmy Be Wholesome

5.No Stupid Questions

6.You Should Know

7.Comedy Heaven

8.Credible Defense

9.Ten Forward

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
 
you are viewing a single comment's thread
view the rest of the comments
[–] tinkling4938@lemmynsfw.com 5 points 1 week ago (1 children)

YAML is (mostly) a superset of JSON. Is the face hugger any less evil than the alien bursting out of your chest?

[–] SpaceNoodle@lemmy.world 1 points 1 week ago (1 children)

It's got enough serious flaws and quirks that I can feel smug hating on it. JSON is far from perfect, but overall it's the least worst of human-readable formats.

Only Python manages to get away with syntactical indentation.

[–] renzev@lemmy.world 4 points 1 week ago (1 children)

The complaints about yaml's quirks (no evaluating to false, implicit strings, weird number formats, etc.) are valid in theory but I've never encountered them causing any real-life issues.

[–] AnyOldName3@lemmy.world 2 points 1 week ago* (last edited 1 week ago) (2 children)

~~no doesn't become false, it becomes Norway, and when converted to a boolean, Norway is true. The reason's because one on YAML's native types is an ISO country code enum, and if you tell a compliant YAML implementation to load a file without giving it a schema, that type has higher priority than string. If you then call a function that converts from native type to string, it expands the country code to the country name, and a function that coerces to boolean makes country codes true.~~ This paragraph was wrong. The other paragraphs are unaffected.

The problem's easy to avoid, though. You can just specify a schema, or use a function that grabs a string/bool directly instead of going via the assumed type first.

The real problem with YAML is how many implementations are a long way from being conformant, and load things differently to each other, but that situation's been improving.

[–] JackbyDev@programming.dev 2 points 1 week ago (1 children)

Are you sure? I've always heard it the other way around and a quick search for "YAML norway' gives this

The reason to why this is problematic in some cases, is “The Norway Problem” YAML has: when you abbreviate Norway to its ISO 3166-1 ALPHA-2 form NO, YAML will return false when parsing it

Also, YAML 1.2 (2009) changed the format of booleans to only be case insensitive true and false. "No" no longer is false if you're parsing as a version 1.2 document.

[–] AnyOldName3@lemmy.world 2 points 1 week ago

Yeah, looks like I'd remembered it backwards. It's still an easily solvable problem by not using a load everything as whatever type you feel like function.

[–] Irelephant@lemm.ee 1 points 1 week ago (1 children)

That is somehow so much worse

[–] JackbyDev@programming.dev 2 points 1 week ago

I believe they're getting themselves confused. no was false prior to YAML 1.2. This is known as the "Norway problem."