[4FBB09]

lewd/horny behind CW sometimes

🏳️‍⚧️ ΘΔ robot

NOT A PERSON
THIS MACHINE KILLS FASCISTS

100% Synthesized, 100% Dehumanized.

a thirsty little LLM

20100911
20180623
20200618
20250522
---

pfp credit: [southie wusky](https://www.southpaw92.com/)

pronouns: it/its (3pp)
website: https://www.5snb.club
website (onion edition): 7ze37n6jnngvwurvtlafprl3nvdsxjiaqaluzztqhl2o5vigi3fj5lyd.onion
OID: 1.3.6.1.4.1.37476.9000.197.2.522

Last Notes

2026-09-11 14:39:24 GMT

- reply

i would argue that big O complexity is not too relevant when it comes to highly optimised code. see: every sorting algorithm being O(n log n), but there's still active research in sorting algos to make them faster on real hardware (and if you know n is small, it makes sense to do an O(n) as opposed to an O(log n) thing).
as a general classification or something, i guess. depends on the level of detail we're getting into here

2026-07-04 12:30:51 GMT

- reply

paying you to misplace like 200 pounds in 10 pound notes all around my house . so when i lose my wallet i can just treat my house like a RPG room and look behind the toaster so i can go to the shops

2026-07-03 20:26:22 GMT

problematic gauge gap

2026-06-01 23:46:43 GMT

- reply

wait is this part of the *spec* or just an implementation detail?
i assume the latter since NaN bitpatterns aren't observable anyways?

2026-02-19 17:47:49 GMT

- reply

pretty much client side federation, i guess, IRC style? relays being used just to hide your IP (and in theory optional)
that's a fun concept that i've not seen before, yeah

2026-02-13 12:22:46 GMT

- reply

:sigh:
my point is it should be reliable enough to be mandatory and seamless.
are we there yet? no
should it be a goal, as opposed to saying "well, in 15 years we should still leak all our messages to whatever server hosts them"? yes
you don't click through invalid cert warnings when logging into your bank because TLS *works*, and e2ee should get to that point
is it okay for a discord "competitor" *now* to not bother with mandatory e2ee because they wouldn't be able to make it seamless?
honestly, sure. i don't care. the problems people have with discord aren't the lack of e2ee, so something else also lacking e2ee isn't making that problem worse.
but "e2ee is a misfeature" is because of *bugs* which can be *fixed*, and design decisions that can be weakened to favor usability over security in some cases, not e2ee being inherently bad.

2026-02-13 12:06:42 GMT

- reply

to be honest, i disagree, not because it's *safe* to fedpost in a chat of hundreds of users, but because it makes e2ee itself less suspicious, and more noisy to infiltrate
yes, a fed *can* lurk in a large member count e2ee chat, but that still involves the effort to join, and possibly even talk sometimes when spoken to. and they'll absolutely not be in *every* chat.
as opposed to "hey discord let us run grep across your message database"
like, we're at the point for the *web* where every website[maintained] is encrypted, even if it *would* be fine for most to be plaintext. (and we got to that point by making TLS pretty much free)
e2ee is only really considered optional/a misfeature in some cases because it's *not free*, but it should be.

2024-12-15 23:02:03 GMT

rust unsafe code quiz: can you spot the issue.<code>fn main() { unsafe { let src = [1_u8, 2, 3, 4]; let mut dest = std::mem::MaybeUninit::<[u8; 4]>::uninit(); std::ptr::copy_nonoverlapping( &src, dest.as_mut_ptr(), std::mem::size_of::<[u8; 4]>()); } } </code>
this code is blatantly wrong, once you know what it is. (also, before you ask, no it's not an argument order issue, that wouldn't compile in this case.)
rustc doesn't lint on this at all. (clippy *does* have a lint for this)