User:)biyibiyibiyi(/Prototyping 03

From XPUB & Lens-Based wiki

Special Issue session with Bodó, in which prototyping was involved

2d diagram.png

2d diagram resulted from Bodó's LibGen data analysis. My intention was to survey file format composition of post-soviet states. The composition of file types of publications in Chinese language reflected the emergence of electronic publishing market, as indicated by diverse percentages in azw3 format used for Kindle.


Visit to Rietveld Library, where an instance of Bibliotecha is implemented

We did not do prototyping in this field trip however it was eye opening to see Bibilotecha being used actively in Rietveld library. I thought it fitted its purpose of fostering a reading community.

Watermarking, DRM w/André

This session is about revealing the materiality of digital book files. Worked on removing digital watermarks embedded in EPUB files downloaded from Verso.

Learned the name Ex Libris, which refer to stamps imprinted on books to signal proprietary right.

In context of digital publishing Ex Libris take form in digital formats. Unlike analog book plates to show signal proprietary right, digital watermarking tools, such as Ex Libris, become a tool for tracking digital files' distribution by attaching user/reader's name onto it.

The prototyping session then began as to understand more forms of digital watermarking tools and how to remove them for future distribution.

By looking into a EPUB file from Verso we discovered several examples of digital watermarking, provided by BooXtream to Verso. The watermarks can be categorized to two types, visible and invisible. The visible ones are visually identifiable on page footers, front pages disclaimers, by printing email address and names entered on Verso online account required for downloading. The invisible ones are embedded in the file structure. EPUB is a zipped file of html pages, each html contains contents of separate chapters. Invisible watermarks are embedded in filenames in the EPUB files (html, stylesheet, hyperlinks, etc). Other examples of invisible watermarking include time stamping and image meta-data watermarks.

To remove meta-data that contained user information, exiftool is used. this tutorial http://xahlee.info/img/metadata_in_image_files.html also showed how to remove geo data from meta data. Which reminded me that during middle/high school when digital camera was used and blogging was popular, I could see camera type metadata by right clicking onto images posted on the blogs...

Aside from removing watermarks as antithesis to copyrights, this prototyping session revealed EPUB file type as structurally interesting. tree command is able to show file structure in tree format. Several organizations to know about: Dublin Core Metadata Initiative, Intl Digital Publishing Forum, which aim is to collaboratively develop EPUB as file type to promote universal accessible e-book exchange.

Epub file structure.png Unzipping EPUB file shows file structure and file types, content.opf contains metadata.

Tesseract OCR algorithm on browser w/Michael

Setting up Raspian

Motivation

During the last Special Issue we all set up Raspberry pi as server, running on Diet-pi. The web server was apache2. I wanted to set up Raspian for several reasons. Sheer curiosity to see the pi's ability other than being a server, such as being a wifi-hotspot (used in Bibilotecha.info project), using pi camera for home smart agents such as surveillance and automated helpers (pet feeding, plant watering, etc).

Aside from these sporadic interests, I would continue using my pi as server. Before I wiped out Diet-pi, I tried to configure apache2's fancyindex module, so that I can make a web gallery to showcase the projects I (and xpub) did. The try out was not successful. Fancyindexing appear to only apply to specific directories and not sub-directories. Anyway! It was fun to edit the configuration file, to notice it's similarity to other markdown languages.

As I noticed the Special Issue 08 mini site is running on Nginx, I wanted to install Nginx and try again. So I decided to wipe out the Diet-pi system as I felt frustrated with Apache2 configuration.

Process

Setup raspian.JPG Setting up raspian Vnc view.png Playing with VNC


I discovered that Raspian's interface is quite revealing about its file structure. The folders start with root / and sub directories had designated purposes for storing specific file types. Browsing on Raspberry pi online development community I found a thread that explained the file system division. http://shumeipai.nxez.com/2018/01/05/directory-introduction-in-raspbian.html I glanced to basics of the naming protocol, i.e. /bin for binary file, /dev for drives (which reminded me that as we played with the dot matrix printer the driver file was stored in this folder) /mnt for mounting. Memorizing the structure and naming of the protocol is not necessary but it's good to have an impression in mind. As in the future if I develop projects, I will be navigating inside the folders, and I would want to know why I am placing certain files inside var/www but not in /bin.

So I thought in general Raspian is a transparent learning, prototyping tool.

Potential leads

I looked up some hack documentations on making Raspberry Pi a device for machine learning, in particular learning image data, such as recognizing faces. I would want to explore potentials using machine learning and pi camera.

Annotation Tools

Collecting some annotation tools for rapid prototyping, an idea for the final event launch. https://d3-annotation.susielu.com/#introduction