Week 12 audio

Desclaimer

Desclaimer

Desclaimer - fast

Part 1

Radio 1 - 3

Week 1

Week 2

Week 3

Student meetings / Tyranny of Xpub

• Part 1: Meeting Formats

Tessa: We need to take two minutes to resolve meeting format. So, who’s going to be responsible for the agenda? And can they update us on how it’s going? For any new topics that come up, we can organize separate meetings depending on how urgent they are.

Eleni: On that note, can we add a voting system for issues we want to discuss?

Kim: I wasn’t really happy with the last round of polls. It felt chaotic—maybe because there was a bit of a “joke” element to them? I found it pretty ineffective.

Charlie: If we’re prioritizing urgency, maybe we need a timekeeper—someone to keep things on track during discussions.

Imre: Realistically, though, we often only have two or three things on the agenda, and even then, decision-making can be tough. I get that voting can feel chaotic, but what if we introduce time limits or something to make it more efficient?

Fred: Or we could rotate responsibilities alphabetically?

Imre: People feel different about tasks on different days, though.

Kiara: Strongly agree. As we mentioned earlier, we should prepare for the next meeting ahead of time, but keep the roles flexible. That way, we can adjust if someone can’t take on a role for any reason.

Fred: Right, as long as responsibilities are shared so no one feels too overwhelmed.

Tessa: Exactly. We can designate roles, but they should stay flexible—especially in situations where someone isn’t feeling well or something comes up.

Eleni: Still, there are certain roles some of us might not feel comfortable with, or might not be the best fit for.

Charlie: Fair point. But with only five weeks left, we could rotate the roles equally so everyone gets a turn.

(The group agrees, raising consensus on this approach.)

• Part 2: The Alphabet Soup

Feline: So, what do we want Alphabet Soup to be? How is it going to serve us as a useful apparatus?

Chrissy: I kind of like it messy. Do we want it to be like a real dictionary, though? Personally, I wouldn’t go to «soup» to find a word.

Eleni: Maybe we separate the content of the word from the meaning of the word? (Wait, I kind of lost my train of thought there...) But I think the protocols we use are the most important part.

Sevgi: It would make more sense to keep it experimental, but it also has to be legible. I really don’t like its current state—it’s not interesting to read.

Charlie: Agreed. We shouldn’t drop the experimental aspect entirely, but maybe we could at least have one section that functions like a dictionary?

(Everyone agrees)

Kim: That way, it can still be helpful for understanding.

Kiara: Maybe we voted on this too early? I think we need a protocol for choosing the protocol. Like, a better selection process.

Kim: I actually appreciate that approach, Kiara. At the same time, I liked Steve’s proposal too—looking at what we have now and then deciding where it can go from here.

Eleni: What if we made a list to categorize the protocols? The current system with groups feels confusing. For instance, we could have a protocol for definitions and another one for grouping. That would create a general structure.

Chrissy: Another idea—what if Alphabet Soup had two sections? One could stay experimental, and the other could function more like a dictionary.

Fred: I like that! To add to it, we could keep the experimental part on the bottom side. But just to be clear, I don’t want to do too much editing myself so maybe just don’t listen to me.

Charlie: Editing is tricky anyway, especially since we’re using transclusion right now. It makes later adjustments really hard.

Kiara: So, to wrap this up, the question for a future agenda is: how are we going to structure the page? Should we agree on some common rules for layout and so on?

Eleni: (excitedly) I LOVE TRANSCLUSION!

Tessa: So it sounds like the goal is to either keep it very experimental or find a balance between experimental and useful. Having two sections in Alphabet Soup—one experimental and one practical—might work for everyone?

(Consensus remains mixed but leaning toward agreement.)

Kim: I’d prefer to sort the protocols into clear chunks. Those could then be used selectively—for example, picking one definition protocol, one image protocol, and so on.

Sevgi: That makes sense. Should we wrap this up with a vote so we can actually start working on it?

Charlie: Love that idea. If we use the protocol approach, we wouldn’t need to copy-paste protocols directly into the glossary. That might just make everything messier.

Imre: What if we create a separate page just for the protocol glossary? (Not totally sure about this, but throwing it out there.)

Fred: If we go with the protocol idea, we could attach hyperlinks to the glossary instead of copying everything over.

Tessa: Right, and we’ve already got a lot of protocols to work with. We could review them and sort them into different categories. That way, we’d have various ways to define words. Do we have any volunteers for sorting? Maybe we could even decide on an editor.

(The group nods and murmurs in agreement, a team is created.)

Tessa: Should we task the Alphabet Soup team with coming up with a concrete proposal for the structure?

Eleni: Quick question—can Alphabet editors mess with other people’s stuff?

Fred: I’d say yes, as long as it’s non-destructive. (Strong agreements.)

• Part 3: Special Issue #25

Sevgi: So, the idea is to have an open event at Ubik, and we get to decide the nature of it. (Silence while the class reads through ideas written on the pad.)

Eleni: Please feel free to share your ideas and suggestions! 💖

Fred: I’ve been thinking about how to structure the day. Should we work on a collective theme or focus on different things? Maybe it’s more about working collectively rather than strictly collaboratively? And how do we distribute responsibilities?

Eleni: It would be nice if the public could come in and interact with all this new information, like a fair.

Sevgi: Does that mean everyone would be working during the day?

Eleni: Maybe we could have suggested time slots for everyone?

Kiara: It depends. We could rotate roles depending on what we want to do. Maybe we could also have a place for merch?

Kim: How long will the event be?

Sevgi: According to the schedule, it seems like it’s two hours.

Kim: It’s during the week, though. Who’s going to have time to attend during the week?

Tessa: Michael suggested we do it earlier in the day. Sevgi: Events tend to get more traction around 5:30 PM or later.

Claudio: (pauses, then adds) Michael also suggested we could make it longer but involve fewer people at any given time. Maybe have results ready to present for later visitors?

Sevgi: Let’s imagine what the event would look like. Once we visualize that, we can better time it—maybe it’s easier to stick to two hours in the evening.

Eleni: Workshops could have time slots throughout the day.

Tessa: And then the main event could happen in the evening.

Eleni: Also, workshops could be documented in a booklet.

Sevgi: Maybe this is a conversation we can have later?

(Strong agreements)

Kim: For now, let’s go through the pad and discuss the ideas.

Eleni: Here’s an idea: something that turns speech into music.

Kiara: I like the concept of speech-to-text. Maybe a radio show that also prints speech live? It could be turned into a zine or even sent out as a fax!

Sevgi: I think the idea is great, but I’m not a fan of workshops.

Charli: I’m not really into workshops either, but it depends on what the workshop is about. Honestly, the title of the event doesn’t really scream “workshops” to me.

Claudio: I don’t think we need to limit ourselves to just one format. A workshop could also be shared via a booklet, so people could try it on their own later. A guide would work well.

Claudio: That reminds me of Manetta’s booklet examples—those could be an inspiration.

Eleni: What about something interactive with Graphiz? People could engage with it and make their own little notes.

Charli: I’m still not a fan of workshops, but I like the Graphiz idea. It could involve collective performances with visitors, where participation is optional.

Kim: I agree with Charli. The Graphiz idea could also take the form of readings or something live.

Sevgi: I’m on board with these ideas. I’ve updated the Graphiz file on the pad—maybe we could use it on the day? Smaller performances could make it more accessible.

Eleni: I just realized “protocol” feels like a heavy word. Maybe we could use “Graphiz” instead? It could be an interesting outcome of the day—Graphiz becomes our protocol.

Kiara: Could we incorporate music somehow?

(The group reacts positively.)

Charli: I loved that huge jam session we did before. What if we invited people to bring their own materials and jam together? We could even record it.

Fred: Going back to Graphiz—what if we did something like speech-to-text with live updates of what’s happening in the room?

Kiara: About the jam session—what if it included objects that people had on them in the moment?

Tessa: That’s a great idea! The jam session could be a corner of the event, with maybe an instrument-creation workshop that leads into it.

Eleni: Protocols for sound-making could be a cool way to combine objects and instruments.

Kim: I wasn’t really into live jamming last time. It felt like there was no context. It would be better if we had some sort of framing for what we’re making with the public.

Charli: I agree, but this applies to all the components of the event. We need to prepare the message as much as possible in advance. Even the “bring your own instrument” part could benefit from preparation beforehand.

Fred: For the jam session, maybe we could add a layer to it—like building a collaborative track together.

Sevgi: Okay, let’s vote on this. Are we building the event around different workshops or stations? (Everyone agrees)

Tessa: We should created sub-teams for this?

Kiara: Good idea, and we could also form a subgroup specificallydocumenting the event. It’s important to establish a common ground for capturing what happened on the day—some kind of “interface” for the documentation.

Charli: And maybe we could do two radio shows after the event—one for reflecting on the experience and one for looking back on specific moments.

META MOMENT, WE ARE DOING THIS RIGHT NOW

weather hands sound effect

Super Happy Crowd

Skeptical Crowd

Booing Crowd

Crickets

Part 2

Radio 4 - 5

Week 5

Fake Radio Week 7 with Steve Reich

was an amazing show as we got an exclusive guest, Mr stevie reich himself. after studying his work in class it was such an honour to interview him. Here is a little clip where we discussed his work with canon and tape recordings

Part 3 / Sounds of Making

Radio 8 - 9

Week 8

Week 9

Script at the event

Fake Reviews

agitated, art-skeptical citizen's review

Part 4

Radio 10 - 11

Week 10

Week 11

Quiz

Game show theme song

Countdown clock

Millionaire suspense