User:Thijshijsijsjss/PTMoMNBM

From XPUB & Lens-Based wiki
< User:Thijshijsijsjss
Revision as of 11:38, 17 April 2024 by Thijshijsijsjss (talk | contribs) (Transclude (currently non-existent) entry for WikiFeed)

A repository of projects that may or may not be made.

2024-04-10 Stickerbook

What is it?

> A stickerbook: a small (pocket-sized) book with written text where each individual page is a sticker.

Why make it?

> What happens to a book with a missing page? If all pages are missing, is it still the same book? Is it still a book at all? How much is the narrative of a book contained in it's physical form?
> There is a suggestion of these pages not having a 'proper' order, in the sense that they can be taken and rearranged if a reader so desires.
> Sometime I want to share a page from a book, or remove one from the whole, or keep one with me. Additionally, I wonder what 

Workflow

(> Zeroeth, research must be done into the method of stickerization: how might one make the stickers? How can these pages be bound together if so desired? Etc)
> First, a text needs to be settled on. It can be an already existing text, or something new. 
> Next, the text needs to be formatted in a way to accomodate for the eventual stickerization.
> Then, stickers need to be made.
> Finally, optionally, the sticker-pages can be bound together.

Timetable

> The are two major factors in the timeline:
   1. the text. If this text is to be created from scratch (maybe specifically for the purpose of this project), this will be the bulk of the work. 
   2. the stickerization. If this is done elsewhere (e.g. through an online service), shipping times should be taken into account.

> All in all, the project should not take longer than 3 days (excl. shipping time): 1-2 to write, 1 to bind. If stickerization is done by self, this happens in between.

Rapid prototypes

A rapid prototype using this story made with the Brother QL-700 label printer.

A stickerbook bound with a clip
The individual pages of this stickerbook

Previous practice

> Building on questions of narrative and interaction in a static medium. Continuing explorations of printed matter.

Relation to a wider context

> It is a reference to stickerbooks that contain no text, but stickers figures.

Choices made

> Choices must be made on:
* Page size
* Fixed page size?
* Include instructions?
* Page numbers (yes or no)
* ...

Talking with Mania, Victor and Zuzu

When someone finds a sticker, can they find the rest? (physical locations of other stickers? Link to full text?)

Alsmost becomes a game to find the rest of the book, like geochaching. Rewarding to find a sticker already, even without considering the contents of the text.

The sticker format implies a spatial format. The book is read 'in space'.

2024-10-17 WikiFeed

What is it?

An app for your mobile device reading RSS feeds from our community wiki. A user downloads and installs the app, logs in with any valid user account, and is able to select any type of feed they want to watch. They could do this in the app. Also, they can enable alerts, alerting them on specific wiki updates.

Why make it?

The wiki is a content feed. I notice myself checking the recent changes all the time, partially triggered by a feeling akin to 'doomscrolling'. In contrast to more conventional media platforms, a wiki is seemingly archaic, static, factual and 'uninteresting' to our dopamine dependent brains. WikiFeed comments on this.

Aside, it has practical use cases, too. Currently it is possible to view the revision history of specific pages on the wiki itself, and view a feed of recent changes. This is convenient information to have. However, sometimes you want this information outside of the wiki. For example:
    1. A pop-up notification on your phone when a specific page is altered
    2. Display up-to-date content from a specific set of pages
Feed of recent changes on this wiki

Workflow

[I'm unsure whether the intention for this section is describing the workflow making the project, or using the project. I will go for the former]
The workflow consists of four stages: research, coding, designing, polishing. They are described in more detail in the Timetable section.
RSS feed with recent changes

Timetable

1 day of research into the mediawiki api: what can we extract and how?
1 day of research into the development platform: what is a suitable suite for developping for mobile?
1 day getting familiar with this suite, playing around, prototyping some tests 
2 day to get the core functionality working
    - compiling feeds
    - selecting feeds
    - switching between feeds
    - adding to feeds
2 days for the design
2 days for polishing and adding nice-to-have features

Rapid prototype

A very rapid prototype made with Processing, just to get a feel for extracting the feed through external software, and displaying it there.

XML xml;

void setup() {
  xml = loadXML("https://pzwiki.wdka.nl/mw-mediadesign/api.php?action=feedwatchlist&wlowner=USER&wltoken=TOKEN");
  //println(xml);
  XML[] items = xml.getChildren("channel")[0].getChildren("item");

  for (int i = 0; i < items.length; i++) {
    println("Now printing a new item!");
    String title = items[i].getString("title");
    println(items[i].getContent());
    println();
  }
}
Prossessing output for user Thijshijsijsjss

Previous practice

WikiBabble: a project that uses the community wiki as a messaging platform. It plays with the dynamics of personal and intimate chatting on an inherently public platform. WikiFeed can be an extension to this project, serving alerts like most instant messagers do.

TL;DR: a project in which logged and unlogged activities of and surrounding the community server chopchop are compiled, annotated and displayed on an E-reader. In the making of this project, we considered using a collection of wiki pages to store information. This would have made use of the feature that any user can edit any page.

Finally, I'm an avid user of this wiki, and would like to explore more possibilities with it. In particular, I have kept a diary that I have been told reads as quite intimate. WikiFeed could explore these 'intrusive tensions' even more.

Relation to a wider context

awef

Useful links:

Feed of USERNAME's watchlist:
https://pzwiki.wdka.nl/mw-mediadesign/api.php?action=feedwatchlist&wlowner=USERNAME&wltoken=TOKEN
TOKEN is obtained by logging in to the wiki > preferences > Watchlist > Manage tokens

Feed of changes of a specific page:
https://pzwiki.wdka.nl/mediadesign/PAGENAME?action=history&feed=rss
e.g. https://pzwiki.wdka.nl/mediadesign/Main_Page?action=history&feed=rss

Feed of all recent changes:
https://pzwiki.wdka.nl/mw-mediadesign/api.php?action=feedrecentchanges&feed=rss

Talking with Alessia, Mania, Victor and Zuzu

  • Could lean into the commentary aspect
  • References on doomscrolling commentary?
  • 'Reading feeds' can mean different things -> could operate an Arduino for example
  • Collaborative?