If you're planning on using these as serious reference tools for newbies, I'd make a few changes.
Firstly, there's a great nubmer of background sounds from other open apps you have running that sometimes make it difficult to hear what you're saying.
There's a lot of background hiss under your voice, which might benefit from being toned down if possible.
Mike is quite robotic to modern audiences, so I'd recommend changing him or at least slowing him down.

In terms of this specific recording, writing to the root of the c drive isn't always recommended, and the fact you're doing it in a VM just adds tremendous confusion to anyone learning about these things, and your repeated references to bad crashes don't really enspire confidence adnd talking about your USB's from before only mean something if you're a regular listener.
And it's generally bad practice to show something that doesnt work. Like, if you tick the box to keep your config and for whatever reason that didn't work, you probably don't want to show that as typical behaviour.
The repeated shitting isn't overly professional, either.
I bring these up not to complain, but to query the future. If you're doing it for your regular audience who're already familiar with what you're doing, that's fine.
If you're making something for people wanting to learn something new, you might want to adjust your approach slightly.

Wie wird das bei Euch in Bezug auf #Datenschutz, #Datenverarbeitung und #Verwertungsrecht gehandhabt?

Soweit ich erinnere verkauft #Canva, bzw. die Firma dahinter, nicht nur Daten, sondern kauft auch bei Dritten ein um zu verknüpfen.

Und war es nicht auch so, dass man an den erstellten Produkten keine eigenen Rechte mehr hat, auch für den eigenen Content, den man einbringt, oder z.B. in der Gemeindearbeit dann von anderen (Content von Veranstaltungen z.B.)?

Dazu würde mich der aktuelle Stand und eine Einschätzung/ Korrektur meines Verständnisses intetessieren.

Vielleicht wissen @ChristianBrecheis@kirche.social und @fxneumann@bonn.social etwas?

Because it already happened: if you read my post and you feel an urge to respond with something along the lines of "it's just a hallucination", "it's just a bug", "it will be better in ChatGPT 6", or anything even close into that direction, please stop. Read this post and the next post, think about them, and if you have a factual argument to respond to me, only then reply. Focus on my factual claims, not on some inaccuracies in my analogy because of course it's not 100% accurate, that's the nature of analogies.

ChatGPT making up ZSTD compression in the Compression framework is not a bug. It's not even a weird edge-case. ChatGPT is doing exactly what it is designed to do. Let me try to explain.

If we grossly oversimplify what an LLM is, it's "just a statistical model" that generates "language" based on a chain of "what is most likely to follow the previous phrase". "language" can be anything: it can be human language, a fictional language, but it also can be code or even genetic information. Any kind of textual thing that you can feed large amounts of into a model works. "Not having an answer" is not a possibility in this system - there's always "a most likely response", even if that makes no sense.

ChatGPT inventing ZSTD compression in the Compression framework isn't due to a lack of training data. If you request an overview over all compression algorithms supported, it answers correctly with a comprehensive list that does not include ZSTD. So, if you want to anthropomorphize ChatGPT, you could say "it knows that ZSTD isn't supported", but that doesn't matter. LLMs do not possess the ability of logical thinking, deductive reasoning, or anything else. "It knows" that there are a bunch of compression algorithms available, the constants are all called COMPRESSION_[method], so there's a high likelihood of COMPRESSION_ZSTD to be the answer to a user asking for ZSTD compression in Swift. And so it generates that.

The only way ChatGPT will stop spreading that nonsense is if there is a significant mass of humans talking online about the lack of ZSTD support. For example a bunch of StackOverflow questions asking "How do I do this?" and people responding "you don't, Apple doesn't support it, you have to use third-party libraries" - or if you have a bunch of white dudes working in tech complaining on social media about Apple not supporting ZSTD in the Compression Framework.

My next post will be an attempt at comparing human thinking and LLMs generating text. As mentioned earlier, it's an analogy - and it's not going to be 100% accurate. If you want to reply, focus on the factual claims. If you only want to nit-pick my analogy, I have to assume you're not interested in productive argumentation.

ChatGPT - Apple compression algorithms

Shared via ChatGPT

^ChatGPT

Let's imagine you're colorblind. The kind of colorblindness that only allows you to see grayscale - no colors at all - but everything else is fine.

You're stressed and need fidget toy - so a friend hands you a ball, roughly filling your hand. It's hard, but somewhat squishy, and has a weird fabric-like, furry texture. You now want to know what color that ball is. But, well, you're colorblind, and your friend already disappeared and isn't reachable - probably riding a Deutsche Bahn train or something.

So you take a picture and post it to a "what color is this?" subreddit. Seems reasonable. You get 200 responses - 198 of them say "it's yellow", two of them say "it's pink". A few people helpfully say it's a "tennis ball". That's helpful, because even the Wikipedia article states that only yellow and white tennis balls are officially approved colors. Sweet.

A few days later, a random person approaches you and says "wow, cool ball - what color is it?" and you say "yellow!". Alright, end of the chat. A LLM would do exactly the same - given the "yellow" responses far outnumbered the "pink" responses, your ball is probably yellow. Ball==yellow is something both you and the LLM "learned". A few weeks after that, another friend asks you "ALice has a ball, too! Do you know which color her ball is?" - and now it gets interesting.

The LLM would immediately say "yellow". Of course it would. It makes sense. Yellow is the most likely response to that question.

But you're not an LLM - you're a human, and your brain is cool. Instead of saying "yellow", you respond "huh I don't actually know that? My ball is yellow, maybe she has a similar ball. But it could also be that she has a completely different ball that might a different color! Also, lol, I'm colorblind, so I can't really answer that anyway - you should ask Alice." And now, your brain is already doing better than any LLM. Your logical thinking engine already realized that you don't actually know something, and you're honest enough to just say that. Your job isn't to be a ball color guesser, you're just a person.

Wait, it's gets more fun! A few weeks after that, you hang out with me. You hand me your ball, and say "hey look at my cool yellow ball!". Oddly enough, my reaction is "huh? this ball isn't yellow, it's a pink tennis ball..." and now things get funky. If you were an LLM, you would either insist that no, your ball is absolutely yellow - or you'd come up with some kind of "oh, sorry for the misunderstanding - it's pink, you're correct", almost implying that my definition of color is different - and the next time someone asks you about the color of your ball, you'd still say "Yellow!!" again. Because of course, there's still only three people claiming it's pink, and still 198 people saying it's yellow.

But you're not an LLM. You're human, and your sexy human brain immediately goes into a "uhhh we have a conflict of information! how exciting! let's figure things out!" You now have to conflicting hypotheses, and you're thinking about ways to experiment on your ball to learn more. And you have an idea! You know your additive color mixing theory, so you realize that your phone camera can take pictures and you can look at the RGB values. If it's yellow, you'd expect to see lots of red and green but no blue - but if it's pink, you'd see lots of red and blue, but no green! You can test that!

So you take a photo, and... rgb(255, 0, 255). Turns out your ball is actually pink! It's still a tennis ball, but a fun one not meant for official tournaments, so it's pink! Wow! You immediately learned something new - and from now on, if someone asks you about the color of your ball, you'll say "pink!" and you'll have a heck of a story to tell alongside. Also, after some self-reflection, you realize that the subreddit your posted your image to wasn't a real "what color is this?" subreddit - it was one of those "false answers only" shitposting subreddits. Whoops.

This process of having assumptions, but being able to question them, to come up with tests for it, and to immediately change your opinion on something when you have good evidence for it is what makes humans awesome. You don't rely on the majority of people screaming "pink!" at you. You don't need to rely on manual weights that give some sources more weight than other sources - you can independently process information and deduct things. Give your brain a pat on the.. uh.. cranium.

LLMs can be a useful tool, maybe. But don't anthropomorphize them. They don't know anything, they don't think, they don't learn, they don't deduct. They generate real-looking text based on what is most likely based on the information it has been trained on. If your prompt is about something that's common and the majority of online-text is right, you'll most likely get a right answer out of the LLM. But if you're asking something that not a lot of real people had interactions on, the LLM will still generate text for you - but it might be complete nonsense. You're just getting whatever text is "statistically most likely".

If you're a coder stuck on something, identify a colleague or friend who is more knowledgeable in that specific area. They'll happily help you out and provide all sorts of fun added context that'll allow you to learn. If you're a nerd on the internet who enjoys ranting on social media, just do it yourself instead of having an LLM generate it, because that'll allow you to insert some bad jokes and a bit of your own personality to it instead of just getting a "default-feeling" text. If you're a manager in charge of something and you need to come up with new directions to push your company towards, go take a walk outside and listen to some cool music and let your ideas roam free - don't ask an LLM to generate the statistically-most-likely direction for your project, because that's by definition the opposite of creative and innovative.

Use your brains.

Had a blast at our little #OpenStreetMap birthday celebration. 🍰 🧉

It ended up being too windy to fly drones for long. Instead we recorded street-level images for #panoramax and GPS tracks, in addition to doing a lot of live surveying – using a huge range of tools that allow contributing to OSM!

In no particular order we at least used: @everydoor, @streetcomplete, @MapComplete, @CoMaps, HOTOSM's ChatMap, iD and JOSM.

Having so many different ways of making contributions is a real feature.

Sensitive content Reveal/hide