Posts
22586
Following
432
Followers
833
25. θΔδ*& *NIX Developer.Average Paw Enjoyer. ♿ HSD

lotte adds rac- to words a lot but it doesn’t alter meaning

NSFW posts are not for minors (they will be blocked on sight).

Opinions expressed in this profile are representative of those of your employer.

“u are my favorite therianizing biohazard” — @sodiboo@gaysex.cloud
“you know, maybe i will finally learn to read the content warning before clicking 'view' [—] thanks for this lesson @charlotte” — @ariadne@social.treehouse.systems

@5225225 explaining why pointing a laser pointer at a plane is a bad idea

0
0
0

@chjara oh sorry, wrong continent, but Afrika also exist but not near me

0
0
1

@chjara there is a place near where i live called “Afrika”, i’m afraid it’s not just the anglos or their colonies 😔

1
0
1

@nightjar neurotypicals have yet to find the G-Spot 😔

0
1
2

Während der Jugendproteste geht plötzlich eine Schweizer Waffenfirma in Flammen auf.

https://daslamm.ch/aktivistinnen-brennen-mutmasslich-ruestungsunternehmen-in-thun-nieder/

0
2
0

Charlotte lotteheartplural/Cinny cinny_heart_plural thetadelta ursaminor treblesand

fedi subpost
Show content

don’t use fascist rhethoric on people you dislike challenge (impossible)

0
0
2

Charlotte lotteheartplural/Cinny cinny_heart_plural thetadelta ursaminor treblesand

okay so at most 1 user got this one right

according to json all of these interpretations are equally valid

RE: https://akko.chir.rs/objects/dee9665f-1a13-440e-9af1-76d3497fb77f

0
1
1

Charlotte lotteheartplural/Cinny cinny_heart_plural thetadelta ursaminor treblesand

given this JSON object, which of these are correct parses according to ECMA 404, json.org, and RFC 8259?

{
  "a": 123,
  "a": 456
}
2
3
1
Edited 21 days ago
private key rotation
Show content

4

0
5
1

they have merged some llm code duplication but not the part that actually mattered lmao

0
0
0

they are still violating the AGPL licensing requirements, and at this point i wouldn’t say it’s by merit of being banned from github

1
0
0

@miifox detroit: become skunk

1
0
0

@rnd i think you aren’t supposed to vember this month. i still haven’t figured out what vembering is

0
0
0

@hzulla Cron, of course, dates back to a world in which:

- computers were a significantly smaller part of the load on the power grid
- we didn't have tightly synchronized clocks everywhere (no NTP yet)
- we didn't have architectures in which power consumption was as tightly linked to computational load

Software often outlives all sorts of assumptions!

1
4
1
re: a
Show content

@KayOhtie @Yoshi but anyways one thing that literally has happened and has caused security vulnerabilities before is something like this:

{
  "auth": {"scope": "admin"},
  "auth": {"scope": "user", "sig": "lvfgxhcqfvglchgqflcfg"}
}

passed to the authentication service it sees the second auth and grants access, passed to the admin service it sees the first one and grants admin access

0
0
1
re: a
Show content

@KayOhtie @Yoshi the thing is that json doesn’t specify any sort of semantics for it. the rfc handwaves these concerns away too while also saying possible parser actions or what is Common in parsers

1
0
1
re: a
Show content

@KayOhtie @Yoshi error is one valid answer yes.

but all the other answers are equally valid according to the spec. javascript JSON.Parse will do the 4th one

1
0
1

You look like you are in need of a trash panda!

#raccoon #trashpanda

0
1
0
re: a
Show content

@Yoshi defining syntax without semantics makes json IMO useless since every single implementation can implement it however it pleases, which isn’t even just a theoretical concern because maliciously formatted json documents do just parse differently between different json parsers and since every json parser i have used accepts such constructions silently there really isn’t a good way to find it out

anyways regardless nobody has gotten all the answers right yet

1
0
0
Show older