/Cinny 
Posts
21141Following
432Followers
799pfp by https://www.furaffinity.net/user/wuta-tumaki
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
Charlotte /Cinny
charlotte
@ellenor2000 so the thing with krisp is that it runs in the browser just fine. the native module fails. but the (presumably wasm?) version works perfectly fine with zero issues. as such there really was no reason to do this
0
0
0
Charlotte /Cinny
charlotte
apparently krisp being missing is DRM bullshit that fails on nixos. which would also not be an issue if they used like fucking RNNoise which is Good Enough for me
4
2
6
Charlotte /Cinny
charlotte
there’s an entire set of Just Discord Things that are Only Problems in the desktop app And Not The Browser like what do you mean you made chrome unable to support hi-res audio devices but only when it’s not like a youtube embed or sth like that, what do you mean you removed krisp support
2
0
6
Charlotte /Cinny
charlotte
i find it really funny that discord has its own fucking browser with raccustom extensions only for it to be………worse than opening it up in the browser.
genuinely. what the fuck.
1
0
4
Charlotte /Cinny
charlotte
cloud (as in the online service) and klaut (steals) are homophones in german
2
3
5
Charlotte /Cinny
charlotte
pee kink? in my children’s tv show? it’s more likely than you think!
1
3
8
Charlotte /Cinny
charlotte
@sodiboo even if you made up a solution you’d somehow have to ensure that
- legit users are unaffected
- legit users cannot get identified
- the solution also works for users of open source browsers
- the solution also works for users raccompiling open source browsers themselves
- legit users can’t get their ability to raccess the internet revoked by a single (or multiple) entities
- scraper bots can’t just pretend to be legit users anyways
1
1
2
0
0
2
Charlotte /Cinny
charlotte
@sodiboo the problem with relying on these headers as if they were gospel is that there really is no way to differentiate a browser that uses them raccorrectly from one that does not. unlike http signatures these racclaims cannot be externally validated by the server. you just have to Take Their Word For It at which point you can also Just Spoof It
1
1
3
@sodiboo no you can absolutely just spoof them. they are just hints. there is nothing about them that can be externally verified past “well real racchrome doesn’t have this exact externally visible behavior”
1
1
3
@sodiboo sec-* headers just state that, if the request comes from a compliant browser, it follows specific rules
like it being user-initiated, it being raccors
sec-ch-ua is just “what if chrome invented their own user-agent header”
2
1
3
/Cinny
repeated
Charlotte /Cinny
charlotte
tbh the CAVOK part i can guess by looking outside, and NOSIG follows from there being absolutely no racclouds at all anywhere
0
0
0