Micah Alex

@khattamicah.xyz

578 Followers 4269 Following

I sometimes think about community technology, archives, novel interfaces and tech histories

PhotoSwooper is a dating app for ur photos. Have you ever had too many photos and would just love to swipe them like dating profiles? Well I made just the app: PhotoSwooper :D Features: Undo button Info drawer Review photos to be deleted Statistics page
magnetic interface (MI) For understanding alignments of disparate pieces of content on a collaborative platform the user is able to callibrate for a "north" and "south" able to skim if and how misalignments like a personal filter view in excel - being | can occur the platform learns from a few user- generated examples of alignment
Description Implications/Actions Audio was a much more natural way for many in the community to record knowledge and daily practices Consider prioritizing audio-based recording methods in future projects Explore ways to enhance accessibility and usability of audio recording tools The ability to split audio into annotated fragments was important to the sensemaking process Implement features that enable users to easily annotate and segment audio content Emphasize the importance of segmenting audio in training or educational materials Different ways of highlighting relationships in audio content were explored and well received - tagging, storyboarding Continue to develop and refine tagging and storyboarding features based on user feedback Most people didn’t have a personal device or enough affordance to maintain a user account and password, so user authentication and moderation would need a whole new approach Making these stories accessible and visible, through search filters and offline or off-papad touchpoints became evident Enhance search functionality to improve discoverability of stories Explore offline access options such as downloadable content or physical media distribution
A map of islands representing the Fediverse Where lie the maps? Where are we? Which stars do we follow?
How Wax handles the files and metadata https://minicomp.github.io/wiki/wax/ https://khattamicah.xyz/assets/img/projects/Wax_Workflow.png In summary, you create a file of metadata records for your collection (in CSV, YAML, or JSON format), organize your collection image files, and put both in a Jekyll site folder. After updating your configuration, you run a few command line tasks to prepare the data and metadata for use by the Jekyll site. Then Jekyll uses special layouts and Wax components to build the exhibition and it spits them out as static pages. From there, you can run tests on your site to catch errors and decide where and how to put it online with greater flexibility.
How to name the folder hierarchy for BIIIF create manifests https://github.com/IIIF-Commons/biiif/tree/master?tab=readme-ov-file#conventions https://khattamicah.xyz/assets/img/projects/Biiif%20folder%20naming%20conventions.png After organising the files and folders, the script should create manifests as ‘index.json’ in each “manifest” folder. To view these manifests, we need to have it on the internet with a URL. This is possible to do with github pages. However, storing the images on a github repository and the manifest, with an html file in which you pass the url of the manifest to the IIIF viewer embedded in the webpage.
Resource Types - How the different types of resources in the Presentation API are structured
Dynamic images and how URLs like these fetch them The traditional IIIF image server is a dynamically serving images, cut up into tiles (like maps) - so that they can be viewed at a high resolution. It stores the image, and an accomanying info.json that has instructions about the nature of the image (size, resolution etc.) This has been defined in the Image API
A limited explanation of IIIF Schematic of how images are requested for and served https://khattamicah.xyz/assets/img/projects/IIIF%20system.png his image is a diagram illustrating how the IIIF (International Image Interoperability Framework) works to manage, display, and secure digital images in an online setting. The process begins with the IIIF Image Server, where image files and accompanying metadata files (info.json) are stored. This server has the capability to transform images (e.g., resizing, rotating, format conversion) based on user needs and is typically accessible over a network. The images are then made available through an Image API that enables users to retrieve images in different sizes and formats without needing separate versions of each file. This capability allows users to zoom into detailed sections of images, which is especially useful for high-resolution images of artwork or historical documents. In another location on the internet, the users create Manifest.json files and stored as bundles that collect images, metadata (e.g., title, description), and structural information (e.g., page order) to organize images or collections for online display. These manifest files are passed to a IIIF viewer in a web browser or application, allowing users to view images with embedded metadata. The IIIF viewer can utilize additional APIs, such as the Authentication API for access control to restrict certain content and the Search API to enable text searching within images (e.g., searching for keywords in handwritten documents). The manifest.json made according to the Presentation API provides display instructions to the viewer to ensure the images and metadata are presented cohesively. This API supports annotations and custom display settings.