@movq@www.uninformativ.de i’m grateful that this works at least!

@kat@yarn.girlonthemoon.xyz lol, oof, well, better than nothing. 🥴 It appears to run quite well. 🤔

@kat@yarn.girlonthemoon.xyz UPDATE: getting it to run natively through a VM and other means all failed! so i did the cursed thing and tried the windows installer in wine…..

GUESS WHAT WORKED

@thecanine@twtxt.net i do not get the reference but this is very cute!

@aelaraji@aelaraji.com fuck yeah!

@movq@www.uninformativ.de missing libraries :( i expected it though

@movq@www.uninformativ.de Yup 👍 Super interesting sruff 👌

@prologic@twtxt.net Ahhh, right, my bad, I could have easily found that. 🤦

There’s also a project page which lists some limitations of this study: https://www.media.mit.edu/projects/your-brain-on-chatgpt/overview/

It certainly sounds plausible. “Use it or lose it.”

@movq@www.uninformativ.de I think it’s here on MIT’s website: Your Brain on ChatGPT: Accumulation of Cognitive Debt when Using an AI Assistant for Essay Writing Task 🤔

Felt the need to make this stupid reference - nobody will get, most likely. Feel free to guess (the file name and todays date, are both a hint), any other notes and opinions appreciated too, idk if I ever drew a standing one, from the front, before.

@prologic@twtxt.net But is there a source for it? Am I too stupid to use that site? 🤪

@movq@www.uninformativ.de I was more interested in the MIT research tbh 😅

@prologic@twtxt.net … or just bullshit.

I’m Alex, COO at ColdIQ. Built a $4.5M ARR business in under 2 years.

Some “C-level” guy telling people what to do, yeah, I have my doubts.

@prologic@twtxt.net This doesn’t cite any sources, might as well be satire. 🤔

@kat@yarn.girlonthemoon.xyz Awww. :( Can you tell why? Missing libraries or does it just segfault?

@doesnm.p.psf.lt@doesnm.p.psf.lt so sorry for your suffering, and loss. :-P

@kat@yarn.girlonthemoon.xyz Cool, that’s a nice summary!

@kat@yarn.girlonthemoon.xyz uh, i use yandex mail which uses HTML by default

https://threadreaderapp.com/thread/1935344122103308748.html Interesting article on how ChatGPT is rotting your brain 🤣

@kat@yarn.girlonthemoon.xyz join the SearxNG cult! the grass is way greener over here 😁

@movq@www.uninformativ.de neither do I 😆 and I’m going full Albert Camus mode. Embracing the Absurdism of life just to cope, it’s the only choice I have left.

@aelaraji@aelaraji.com i’m so sick of AI summaries they piss me tf off

@aelaraji@aelaraji.com I’d love to have a positive, optimistic reply to that, but … uhm … I don’t. 🤣

@kat@yarn.girlonthemoon.xyz Ooh, I’ve got to bookmark that page. 😃

@aelaraji@aelaraji.com I wish I had the luxury of not reading that junk. 😅 But instead, I have a Mutt hotkey that pipes an HTML mail through elinks … Bah.

@prologic@twtxt.net I’m trying to call some libc functions (because the Rust stdlib does not have an equivalent for getpeername(), for example, so I don’t have a choice), so I have to do some FFI stuff and deal with raw pointers and all that, which is very gnarly in Rust – because you’re not supposed to do this. Things like that are trivial in C or even Assembler, but I have not yet understood what Rust does under the hood. How and when does it allocate or free memory … is the pointer that I get even still valid by the time I do the libc call? Stuff like that.

I hope that I eventually learn this over time … but I get slapped in the face at every step. It’s very frustrating and I’m always this 🤏 close to giving up (only to try again a year later).

Oh, yeah, yeah, I guess I could “just” use some 3rd party library for this. socket2 gets mentioned a lot in this context. But I don’t want to. I literally need one getpeername() call during the lifetime of my program, I don’t even do the socket(), bind(), listen(), accept() dance, I already have a fully functional file descriptor. Using a library for that is total overkill and I’d rather do it myself. (And look at the version number: 0.5.10. The library is 6 years old but they’re still saying: “Nah, we’re not 1.0 yet, we reserve the right to make breaking changes with every new release.” So many Rust libs are still unstable …)

… and I could go on and on and on … 🤣

@movq@www.uninformativ.de > That guy over there in the corner…

I’m literally sitting in a corner chuckles. I rarely get any emails nowadays. But if I do and it is not plain-text, then my Mutt gets to bark at it and I, just… won’t read it. 🤷🏽‍♂️

@movq@www.uninformativ.de make that 4 people! i use plain text when i can because this page convinced me lmfao

@movq@www.uninformativ.de Hahaha 😂 This is gold! I’ve been following along with our ramblings on Rust. What’s it gone and done to you now? 🤔 I don’t think I can ever be friends personally, I feel “too stupid” to learn Rust 🤣

@lyse@lyse.isobeef.org :‘-(

Batdo
#catsoftwtxt

@kat@yarn.girlonthemoon.xyz Na, I’m too old for this shit.

@movq@www.uninformativ.de No.

@movq@www.uninformativ.de Yeah. :-( But hey, there are at least six of us using mail as it should be™. :-)

I sent the dealer an e-mail about that with all sorts of other issues as well. Let’s see if they fix anything of that some day. Or yet just even read it.

@lyse@lyse.isobeef.org … because you, me, and that guy over there in the corner are the only three people left using plain-text email. 🫤 (And probably Stallman.)

@movq@www.uninformativ.de I like this idea 👌 Very neat!

@bmallred@staystrong.run Oh sorry I should have explained those terms 🤦‍♂️

• Esta almohada me gusta. ¡Pa mi! -
  #catsoftwtxt

OpenBSD has the wonderful pledge() and unveil() syscalls:

https://www.youtube.com/watch?v=bXO6nelFt-E

Not only are they super useful (the program itself can drop privileges – like, it can initialize itself, read some files, whatever, and then tell the kernel that it will never do anything like that again; if it does, e.g. by being exploited through a bug, it gets killed by the kernel), but they are also extremely easy to use.

Imagine a server program with a connected socket in file descriptor 0. Before reading any data from the client, the program can do this:

unveil("/var/www/whatever", "r");
unveil(NULL, NULL);
pledge("stdio rpath", NULL);

Done. It’s now limited to reading files from that directory, communicating with the existing socket, stuff like that. But it cannot ever read any other files or exec() into something else.

I can’t wait for the day when we have something like this on Linux. There have been some attempts, but it’s not that easy. And it’s certainly not mainstream, yet.

I need to have a closer look at Linux’s Landlock soon (“soon”), but this is considerably more complicated than pledge()/unveil():

https://landlock.io/

@prologic@twtxt.net nice… had to look up “Lamarckian” :-)

“Learn Something Old Every Day, Part XV: KEYB Is Half of Keyboard BIOS”

https://www.os2museum.com/wp/learn-something-old-every-day-part-xv-keyb-is-half-of-keyboard-bios/

@bmallred@staystrong.run Ahhh this is an agent I’m tryining to play the game of Connect3. It uses a library written in Go I’ve been working on that supports Neuroevolution using Genetic Algorithms. Some features include: Mutation, Speciation, Lamarckian Evolution/Inheritence.

@kat@yarn.girlonthemoon.xyz i linked the normal length edit instead of the full 15 minute music video because i’m not gonna subject you all to that amount of my bullshit

(…15 minute version is a great watch though)

REBORN LIKE A PHOENIX WING ❤️‍🔥 👼 https://www.youtube.com/watch?v=D-w2HwG18vg

@kat@yarn.girlonthemoon.xyz thats awesome. my kids still love playing it.

@prologic@twtxt.net what do we have here?

@lyse@lyse.isobeef.org those are so annoying. except when they’re idol tiktoks then they’re fine to me

STOP! this is a dambara ruru video checkpoint. you must watch this video or else i will find you

fn sub(foo: &String) {
    println!("We got this string: [{}]", foo);
}

fn main() {
    // "Hello", 0x00, 0x00, "!"
    let buf: [u8; 8] = [0x48, 0x65, 0x6C, 0x6C, 0x6F, 0x00, 0x00, 0x21];

    // Create a string from the byte array above, interpret as UTF-8, ignore decoding errors.
    let lossy_unicode = String::from_utf8_lossy(&buf).to_string();

    sub(&lossy_unicode);
}

Create a string from a byte array, but the result isn’t a string, it’s a cow 🐮, so you need another to_string() to convert your “string” into a string.

• https://doc.rust-lang.org/std/string/struct.String.html#method.from_utf8_lossy
  
• https://doc.rust-lang.org/std/borrow/enum.Cow.html
  

I still have a lot to learn.

(into_owned() instead of to_string() also works and makes more sense to me, it’s just that the compiler suggested to_string() first, which led to this funny example.)

shared an in-person workshop at ALGOPOÉTICA Madrid: introduction to the qiudanz technique: computational transformation of minimalist movement sequences | https://compudanzas.net/talks_and_workshops.html

@lyse@lyse.isobeef.org Rust is so different and, at the same time, so complex – it’s not far fetched to assume that I simply don’t understand what’s going on here. The docs appear to be clear, but alas … is it a bugs in the docs? Is it a lack of experience on my part? Who knows.

By the way, looks like there was a bit of a discussion regarding that name:

https://github.com/rust-lang/rust/issues/120048