It'll just get escaped by quotes.
EDIT: it might be a better idea to use non-ascii characters.
this post was submitted on 03 Nov 2025
1147 points (98.2% liked)
memes
17943 readers
1921 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads/AI Slop
No advertisements or spam. This is an instance rule and the only way to live. We also consider AI slop to be spam in this community and is subject to removal.
A collection of some classic Lemmy memes for your enjoyment
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 2 years ago
MODERATORS
Correct me if I'm wrong, but doesn't text with commas in it get put in double quotes in acsv file to avoid this exact thing?
Like if I had cells (1A: this contains no comma), (2B: this, contains a comma), and (3C: end of line), the csv file would store (this contains no comma,"this, contains a comma",end of line)
A CSV is just a long string of text with a few control characters tossed in for end lines. There are practically no rules enforced by the file type itself. You can dump that unsanitized and poorly awk'd data into whatever awful mess you want. Nobody's stopping you. Sure, excel will force it's CSV formatting rules on you when you export like a child's training wheels. But that's not relevant here.
Only if it's actually using a standard like rfc 4180 https://www.ietf.org/rfc/rfc4180.txt
Also just noticed it specifies CRLF as the line ending, not LF, which is kind of weird.
load more comments
(1 replies)
load more comments
(1 replies)
That's why I use "" to escape the commas.
Mine are typical error messages.
See you next time!
Guys calm the fuck down. The point of this joke is not that you’ll be bulletproof a few in sort of a few commas and passwords every now and then. The point is that a lot of these guys use terrible scripts that do not parse data correctly and they dump all of this shit into large CSV files. One or two people put an errand, in there that it doesn’t expect and it fucks the whole thing sideways for the entire set everything after the asshole with the comma password gets fucked. People that know what they’re doing will be just fine with it, but scammers generally don’t know what the fuck they’re doing and they pass this data along over and over and over again it change his hands frequently. So there’s more chances for it to get fucked along the way.
Comma, single quote, double quote, escape last \ and all your cases are covered.
ngl this got a good fucking chuckle out of me
Why did the creator add an incorrect apostrophe in "commas," but not "passwords?" At least be consistent!
This is why I always use random Korean characters to seperate my columns.
load more comments
(3 replies)
Use a long series of spaces as your password. At least that way they'll have to do a double take when they crack the hash.
load more comments
(1 replies)