|
|
| Line 1: |
Line 1: |
| == Reading as a timelapse ==
| | Hello this is a log of things from kamo or Francesco. This is a wiki version of my [https://hub.xpub.nl/soupboat/~kamo/ Documentation Workout] on the Soupboat. |
|
| |
|
| Hello these are some writings from <span style="border: 1px solid currentColor; border-radius: 1em; padding: 0 0.25em">kamo</span>. I like to develop software to inhabit complexity with visual and performative outcomes. I think about programming as about magic: before there is nothing and then something new exists. I remember that when I was a child I used to think the same thing about drawing: lucky ones those who can draw (i was not), they can have everything at will. Who knows what will come next, say: in 20 years? The problem with technology is that you always end to walk at the same time above the <span style="border: 1px solid dodgerblue; border-radius: 1em; padding: 0 0.25em">waters</span> and above <span style="border: 1px solid tomato; border-radius: 1em; padding: 0 0.25em">lava</span>. Technical issues sprout from everywhere all the times. This is bad because they kill the relax. But it is also nice in the way that encourages collaborations and plural approaches to face problems.
| | == SI16 Vernacular Language Processing == |
|
| |
|
| == Soupboat ecosystem == | | === Text ⛵ Lifeboats === |
|
| |
|
| I dont like to write here in the wiki, sorry. As I prefer my notebooks to be clean instead of squared or lined, I also like to be more in control when it comes to keep track of my progress. Sorry again! So I'm working more on the [https://hub.xpub.nl/soupboat/~kamo/ Soupboat] right now. In the past few days I tried to set up a super minimal framework to store the results and explorations we do during classes. Even if super simple I like it, because it helps me doing something I really suck at: documenting my work.
| | What if we could use some excerpts from all of what we are reading now as lifeboats in a sea of text? An attempt to play around with the continuous permutations between contents and contexts. |
|
| |
|
| My folder in the Soupboat is a table that works as an index for all the projects I worked on since the first week at XPUB till → now.
| | A funny animated thing developed with Cara, Mitsa and Emma in the first weeks of XPUB. |
| | |
| At the moment ''v0.1 and super wip'': it keeps track of the following properties for each project:
| |
| * A title
| |
| * A list of links (often a pad and a git repo)
| |
| * A list of tags
| |
| * A date
| |
|
| |
|
| Next features will be:
| | [https://hub.xpub.nl/soupboat/~kamo/static/html/lifeboats/ Find the project here] |
| * Filtering through the tags (as in the [https://hub.xpub.nl/soupboat/~kamo/10-06-2021-chat_reader/chat.html chat reader])
| |
| * Differents ways of sorting
| |
|
| |
|
| The contents are loaded from a .json file in the Soupboat, because after the third project it was too stressful for me the idea of adding new contents via markup. Is this stupid?
| | === Text Weaving === |
| Someone said to me that it is not a good idea to rely only on the Soupboat because it is fragile and prones to accidents. It would be better to consider some forms of backup? Need to ask to Manetta and Michael and Aymeric.
| |
|
| |
|
| Another thing that bugs me really really really a lot is the workflow in Jupiter. Need a better solution, maybe connecting git?
| | Weave two texts, like warp and weft. |
| I saw some extension in the Jupiter Lab, need again to ask.
| |
|
| |
|
| '''update: 10/13/2021 🍳'''
| | Code is made of essentialy 2 functions: |
| * init
| |
| * mini json cms
| |
| * added 3 projects:
| |
| :* text weaving
| |
| :* chat reader
| |
| :* cam transcript
| |
| * global style
| |
| * lovely Ortica typeface by [http://collletttivo.it/ Colllettivo]
| |
|
| |
|
| == Worlding, magic, sorcery, demonstration, violence, basket ==
| | # the former is for splitting a text into a list of elements (atm it splits the txt in single words, but could be made to work with phrases or even chapters). With this function we process two texts for the second function. |
| '''10/17/2021''' | | # the latter takes the two arrays and a pattern structured as a string alternating A and B es: 'ABAB', 'AAABBB'. |
|
| |
|
| Oke hello is sunday evening today we went to the demonstration against rent and the whole housing condition in the NL and it was kinda intense. The police managed to block the march on the Erasmus Bridge untill evening, even with meaningless and unnecessary display of violence. They used a tram to take away people WTF At the end everyone was super tired when we finally reached the city center. Well done cops you can call it a day. As for the protest: it was ok. Lot of enthusiasm and positgive energy. Lot of different people: youngs and elders, queer and unqueer, differents social extractions. I liked it but also felt a bit overwhelmed.
| | A cool simple application of NLTK and Python with Emma and Jian |
|
| |
|
| Yesterday with Mitsa and Erica we read [https://tdingsun.github.io/worlding/ Chimeric Worlding, by Tiger Dingsun]. He proposes a world-building approach to graphic design, in order to add a cosmologic dimension to the usually mainly functional-oriented work of designin things. Sound nice to copipaste some excerpts here:
| | [https://hub.xpub.nl/soupboat/~kamo/static/html/weaving/ You can find the project here] |
|
| |
|
| <blockquote>
| | === Chat a Pad === |
|
| |
|
| Poetry, more so than other literatures, is concerned not only with the denotative meaning of words, but also the meaning that arises from the aesthetic quality of words (things like phonaesthetics, sound symbolism, rhyme, metre). In dealing with typography, graphic designers are also interested in both the denotative meaning and aesthetic qualities of a text they are working with. Both have a playful relationship to structure, sometimes adhering to, and sometimes breaking, form.
| | ''Process'' |
| | #🏏 take an academic text and turn it into a chat - translating into vernacular; |
| | #🏏 simplify the text |
| | #🏏 break it into chats |
| | #🏏 illustrate some bits |
|
| |
|
| However, one thing that graphic design does not often do, that poetry does, is making a world, to provide a rich context for their work that reaches towards the poetic, the fantastical, the improbable, the mythological. This is extremely worthwhile for graphic designers to pursue, because worldbuilding allows for the potential for narratives to sprawl out nonlinearly. It invites a non-teleological reading (reading without a prescribed goal) of the text, (or image, or whatever the object of graphic design is) and offers a point of resistance against graphic design’s primary function as lubricant for the smooth flow of capital (be it economic, or otherwise), which relies on a singular, totalizing interpretation of the world.
| | ''Levels'' |
| | # 🏸 touch the inputs |
| | # 🏸 overlap/merge them a bit |
| | # 🏸 mesh them completely |
|
| |
|
| </blockquote>
| | Starting from a difficult but relatable text: [https://pad.xpub.nl/p/SP16_0510 our multi voiced pad of the day]. |
| | Parsed here: [https://cryptpad.fr/sheet/#/2/sheet/view/NC767dOscW2mYdKYg295sEy3GLYwX77op9pUqkngK34/ Spreadsheet ghost] |
|
| |
|
| And again:
| | ''Rules to manipulate text:'' |
| | # 🏑 table of contents - shorts contents - tag them |
| | # 🏑 turn into chat bubbles |
| | # 🏑 illustrate a few |
|
| |
|
| <blockquote> Through offering both references to (perhaps multiple) systems of shared references and collective knowledge and one's own personal frameworks, poets create new worlds from this combination of different shared frameworks for interpreting reality and the poets own personal reality, worlds that the audience is able to semi-inhabit, and explore over time. </blockquote>
| | ''Rules of text simplification (as ⛳️ objective ⛳️ as possible):'' |
| | # 🏓 simple sentences |
| | # 🏓 on point |
| | # 🏓 short paragraphs and short chapter |
| | # 🏓 title on each paragraph |
| | # 🏓 text could become image caption/illustrate chapters/graphs? |
| | # 🏓 page number |
| | # 🏓 navigation (table of contents) |
|
| |
|
| Here to me is super important the focus on the temporal aspect of the fruition of something. We were talking about that also after some lesson with Steve. What kind of temporal experience we want to create? Are we oke in doing something that will be just consumed the 17th of december on the day of the presentation? Can we imagine a more tidal way of accessing knowledge and informatio? The idea of generating an ebb and flow of contents for the distribuition of our final reader triggers me. Also because requires a kind of work that is not only an object, nor only a collection of texts, nor only an extemporary performative moment. It asks the Reader to be something as a sorcery, or rather a sets of instruction of directives usefull in order to cast the spell properly. And i really like the idea, because then it could be something able to walk on its own legs. VLTK as a framework, VLTK as a toolkit, VLTK as an attitude.
| | A nice chit chat moment with Alex and Supi. |
|
| |
|
| Again from Chimeric Worlding:
| | [https://hub.xpub.nl/soupboat/~kamo/projects/chat-reader/ You can find the project here] |
|
| |
|
| <blockquote>This designer is able to connect their (somewhat arbitrary) designs with the existing Western eschatological tradition, loading whatever they are making with the invitation for the audience to step into a world where texts and graphic symbols operate under some hidden logic, and have greater power than in conventional reality.
| | === Cam Transcript === |
|
| |
|
| [...] | | A fun exercise of transcribing a video with Kimberley and Carmen. We described three online webcams from [http://www.insecam.org/ insecam.org]. |
|
| |
|
| There are all of these ways that writers expand a world through it’s lore, and the great thing about that is that building up a lore suggests the existence of even more lore, that just happens to have not yet been made explicit to the audience, and is open to speculation. This is the kind of thing that fuels fandom. What if graphic designers could create worlds capable of garnering fan theories, multiple interpretations, and wild reimaginings? It would mean a depth of engagement with graphic design beyond the singular goal of clarity and communication. </blockquote>
| | [https://hub.xpub.nl/soupboat/~kamo/static/html/cam-transcript/ You can read the transcript here] |
|
| |
|
| Now that taking these notes I recall how exoteric and demanding was the cult built around the Tool band, their aesthetic, the USBs hidden in the toilets during live concerts, the wild speculations that every song triggered.
| | === Rejection list === |
|
| |
|
| And again about the slow process timing thing:
| | First brainstorming for the SI16 theme in the form of a giant bubbles list. |
|
| |
|
| <blockquote>Because if the graphic designer develops a rich, hybridized, internal logic through which their body of work functions, even without explicitly explaining that logic, the audience is able to slowly piece that together, and excavate the lore of the world that is created.</blockquote>
| | Fun and funny and [https://hub.xpub.nl/soupboat/rejection/ here] |
|
| |
|
| It was nice to read this text right now that we are working on this peculiar way to think about natural language processing. Finally I started also reading Technic and Magic, by Federico Campagna and the combo between this book and the NLTK one is crazy. I experienced a similar thing a couple of years ago reading at the same time Hyperobjects and the trilogy of the Area X by Jeff Vandermeer. Now with T&M vs NLTK the relation is more adversarial tho, they are in a way complementary, or they just function as an evidence of what the other book is trying to conveyz.
| | === 🥣 Soup Generator === |
|
| |
|
| On one side you have the critical reconstruction on how Technic reduces the world to a set of identical pieces ready to be configured by its own grammatik, and on the other one you have the very practical way of doing it with text corporas and digital informations. Not that I'm sayng that the NLTK book is something EVIL, but now it kinda makes sense what Cristina and Manetta and Michael and Steve and Aymeric was talking about when they presented us the general trajectory for a Vernacular Language Processing Toolkit.
| | Hey this is a Soup + Diary Cookbook and it is meant to be collaborative! For now you can add a recipe only if you are from XPUB 🤧, but we are working to make it open access. |
|
| |
|
| While we were reading we ended up talking about how language generates value in the technic reality, and how could we digest this idea of (economical) value towards some other kinds of vlaue. (Social? Cultural? Spiritual? Situated? Funcional? Vernacular? we dont know yet). At some point I wrote these phrases on my notebook:
| | (ah ah we should make an open version now) |
| * Taxonomy as enchantment
| |
| * Programming as enchanting
| |
| * Poetic devices
| |
| * Every world (text? cultural object?) is a gated garden
| |
|
| |
|
| Also, because our next meeting for the special issue will be a brainstorming starting from the idea of rejection, some other notes:
| | Developed with Erica during the autumn break |
| * rejection as a discourse
| |
| * rejection as a continous renegotiation between filters
| |
| * rejection as exclusion
| |
| * rejection as fractal
| |
| * rejection as spectrum
| |
| * rejection as contingency (really like this)
| |
| * rejection as violence
| |
| * rejection as ritual
| |
| * rejection as border
| |
|
| |
|
| At the beginnning i was really not to much into this rejection thing, but then i started seeing it as the performative act of rejecting, and so the act of filtering. Something is filtered out, something is filtered in. I would like to investigate the discourse between these two positions, continously influencing each other. The idea of exclusion was more a situated one: an external point of view, the eye of the outsider. The fractal and the spectrum were two images against the binarism of exlcusion / inclusion, in the way that a rejection maybe could be seen as something scalar, more than boolean? This takes me to think about a gradient way of filtering, or bookmarking, or taxonomying? And as in fractals, the more you zoom in the more you still find the complexity and richness that carachterize the visual value of that object. And so in filters maybe? An approach that does not tries to cut again and again in thinier slices something to define it, but rather that tryies to tune in those features to see how they return with ebb and flow, at different scales and in different times.
| | [https://hub.xpub.nl/soupboat/soup-gen/ Add your recipe here!] |
| | |
| Something that was really intresting was the idea of rejection as contingency, or in other words all the coincidences and randomness that end up producing a rejection. The idea that some rejections are more random than justified and the possibility to develope different patterns of contingencies in order to transform some rejections in acceptance, or vice versa.
| |
| | |
| The idea of violence is really only violence, again a situated point of view from the part of the rejected. The ritual was more a focus on the act of rejecting and the border to the actual interface between the rejected and the accepted ones, so, again, a focus on filters.
| |
|
| |
| | |
| '''bonus''': we are playing basket almost every day now and i like it
| |
| | |
| == Reading List ==
| |
| * Life of Lines, Tim Ingold 👌
| |
| * Technic and Magic, Federico Campagna 👀
| |
Hello this is a log of things from kamo or Francesco. This is a wiki version of my Documentation Workout on the Soupboat.
SI16 Vernacular Language Processing
Text ⛵ Lifeboats
What if we could use some excerpts from all of what we are reading now as lifeboats in a sea of text? An attempt to play around with the continuous permutations between contents and contexts.
A funny animated thing developed with Cara, Mitsa and Emma in the first weeks of XPUB.
Find the project here
Text Weaving
Weave two texts, like warp and weft.
Code is made of essentialy 2 functions:
- the former is for splitting a text into a list of elements (atm it splits the txt in single words, but could be made to work with phrases or even chapters). With this function we process two texts for the second function.
- the latter takes the two arrays and a pattern structured as a string alternating A and B es: 'ABAB', 'AAABBB'.
A cool simple application of NLTK and Python with Emma and Jian
You can find the project here
Chat a Pad
Process
- 🏏 take an academic text and turn it into a chat - translating into vernacular;
- 🏏 simplify the text
- 🏏 break it into chats
- 🏏 illustrate some bits
Levels
- 🏸 touch the inputs
- 🏸 overlap/merge them a bit
- 🏸 mesh them completely
Starting from a difficult but relatable text: our multi voiced pad of the day.
Parsed here: Spreadsheet ghost
Rules to manipulate text:
- 🏑 table of contents - shorts contents - tag them
- 🏑 turn into chat bubbles
- 🏑 illustrate a few
Rules of text simplification (as ⛳️ objective ⛳️ as possible):
- 🏓 simple sentences
- 🏓 on point
- 🏓 short paragraphs and short chapter
- 🏓 title on each paragraph
- 🏓 text could become image caption/illustrate chapters/graphs?
- 🏓 page number
- 🏓 navigation (table of contents)
A nice chit chat moment with Alex and Supi.
You can find the project here
Cam Transcript
A fun exercise of transcribing a video with Kimberley and Carmen. We described three online webcams from insecam.org.
You can read the transcript here
Rejection list
First brainstorming for the SI16 theme in the form of a giant bubbles list.
Fun and funny and here
🥣 Soup Generator
Hey this is a Soup + Diary Cookbook and it is meant to be collaborative! For now you can add a recipe only if you are from XPUB 🤧, but we are working to make it open access.
(ah ah we should make an open version now)
Developed with Erica during the autumn break
Add your recipe here!
