Final semester project: interfacing with an API + create physical interface

Final semester project: interfacing with an API + create physical interface

Area of Interest: Single purpose devices, Interactive Furniture, Wearable Physical Archives.

I’m interested in checking provenance of media. I will be working with the Internet Archive API.

More research needs to be done, but each piece of media transferred in via WiFi (through thesis devices) will be subject to a reverse image search or Wayback Machine lookup. This is an unplanned extension of my thesis d2d (device2device?) sharing, hopefully for a show where folks can donate content to a common (physical) space, that so far has only existed in the other dimension (the internet).

If content can’t be found, it gets added. How are duplicates seen in this belief system?

The goal is to outline the life of an internet artifact → eg. first published in X; seen around the internet X times. Eventually, I’d love to create an endangerment score, mixing Google Trends data with Wayback Machine + reverse image search.

If i’m serious about this, the real findings come from analysing what do endangered internet artifacts have in common. Communities, distribution - what does each tree look like.

Connecting unknown, unlinked (edit for logic consistency) source material that arrives through the private network back to a common (family?) tree (OSS ref).

Links back to how we get news today - shaped by algorithms and social websites, that make it harder to back link anything for their own profit. The loss of the link means loss of provenance. This links back to the right to access information. Information, in order to be worthy of that name, needs to be informative - that includes checks, sources and access to the life of this media artifact.

This way, we’re making physical presence a requirement for sharing files, donating them to a common bank and contextualizing them right after to common ground.

>>>>>> Tree analogy

Until finding this API and reading docs, it had not occurred to me that there’s an obvious field of research here within internet media artifacts where so many fun links can be drawn to other social science findings and I don’t think I’ve seen other researchers define it in this way… hm!

Edit: I’m wrong:

The Bit List 2024: Global List of Endangered Digital Species - Interim Review | Policy CommonsThe Bit List 2024: Global List of Endangered Digital Species - Interim Review | Policy Commons

Physicality

There’s a home version and an archive station version of this. I’m inclined to do whatever Archive Station version of this is possible within the timeline.

  • Home: Media collected during the day gets offloaded at night to a sanctuary of sorts / evening routine-esque. With a little connector and magnets (tbd?). Each node or pod returns to a piece of furniture with a screen or light indicator. Data caretaker reunites data with provenance. Connects source material to source. Personal or family device.
  • Archive Station (Cyber Deck adjacent?)

Internet Archive API

Coincidentally, after choosing API and mapping out device flow, just saw this Wired article from 2 hours ago on many journalism entities blocking the wayback machine despite relying on it for research:

Kate Knibbs The Internet's Most Powerful Archiving Tool Is in PerilKate Knibbs The Internet's Most Powerful Archiving Tool Is in Peril

PDF analysis, generation and compression at the Internet Archive — Internet Archive Developer PortalPDF analysis, generation and compression at the Internet Archive — Internet Archive Developer Portal

Command-Line Interface — Internet Archive Developer PortalCommand-Line Interface — Internet Archive Developer Portal

Wayback Machine APIs | Internet ArchiveWayback Machine APIs | Internet Archive
⭐️

Wayback CDX Server API

APIs +

Wikipedia Wikipedia:RandomWikipedia Wikipedia:Random
+
MediaWiki API:Random - MediaWikiMediaWiki API:Random - MediaWiki

Are.na Developers | Are.naAre.na Developers | Are.na

Phillips Hue API (Change light based on state of archive + NeoPixel integration?)

Custom endpoint? (Open Source own project)

Input: Antenna

When RSSI is close enough, API

+Neopixel

Same network, network has internet protocol.

Development Notes

🚨

Archive Box is an open source version of the Internet Archive.

image
image
image
image
image
image

Details URL: https://archive.org/details/{identifier}

metadata API: https://archive.org/metadata/{identifier}

with js tool

curl -s https://archive.org/metadata/2002-09-15_W5YI_Report | jq -r '.metadata.title'

curl -s https://archive.org/metadata/2002-09-15_W5YI_Report | jq -r '.metadata.creator'

curl -s https://archive.org/metadata/2002-09-15_W5YI_Report | jq -r '.metadata.date'

curl -s https://archive.org/metadata/2002-09-15_W5YI_Report | jq -r '.metadata.description'

curl -s https://archive.org/metadata/2002-09-15_W5YI_Report | jq '.metadata.downloads'

Enclosure

image
image
image

Security blogs;

pick your application and stay in the loop from there.

Schneier on Security Schneier on SecuritySchneier on Security Schneier on Security

Problem

How does one access the internet without being on a network with an internet node? You don’t.

I managed to get through to the knowledge node network’s AP. There was a network error after adding the file for upload pipeline.

If this device is a receiver only, the web server needs to lead to a port in whatever local network we’re in with IP access. And that way it doesn’t necessarily need a switcher, which i lost when i replaced my board with the accelerometer attached.

It’s just if there isn’t any kind of switcher then the network connection with the other nodes is effectively lost.

For development, the best is to give this one Internet Access. And let the other nodes connect to it through it, making it a real mesh network minus the initial pairing. The problem is that I don’t see a way of doing this rn.

Wouldn’t the brass node need to have its own network and then we’re back in square one? Is using both processing cores the answer?a