What's up Eric? How do you feel about AirDrop?

airdrop — one of those features that, when it works is like magic, but when it doesn’t is utterly infuritating.

AirDrop kind of reminds me of communicating in language to other humans. When it works, it's like magic. And when it doesn't ... is it like a blob?

Btw, how did you create that blob? Nice data. (I checked the source.)

i love that. i feel like there is also something to be said for when airdrop, or language doesn’t work and how that is dealt with. i realized that apple designs airdrop to just “work,” so when it doesnt’t, they never thought to design for that state. funnily, when language doesn’t work, i suppose there are a myriad of fallbacks that we can resort to, such as pointing. what would airdrop look like if you could only point? very blobby indeed.

i made the blob a while back — i wanted to mask an image and drew the mask, scanned it, and then traced it to an SVG. the blob is the source image, and i converted it to base64 so i could include it in this page.

That's so true ... the error state is nonexistent with AirDrop.

I get excited about AirDrop whenever I use it and it magically works. It would be fun to come up with activities or games to play with AirDrop only.

Anyway, it's fun making websites without the internet. If I were online, I might google "how do to convert image to base64" but since I'm not, I can just ask people around me, like you. (Btw, could you share? Also are there limitations to what kind of images I can convert t base64? I imagine they should all be pretty simple, right?)

an airdrop game would be so fun! it is also interesting to imagine that it is perhaps the easiest interface for two devices to send files to one another. i remember how i would have to use a usb stick otherwise.

here is a simple game, perhaps…

 | |
-----
 | |
-----
o| |
    

i was telling elliot the same thing — it feels like programming on hard mode without a phone! i am tethering, but it is like a drop of data here and there. i’ve base64 encoded images before, and you can do the same with fonts. you run it through something that will take a file and base64 encode something like this:

      openssl base64 < /Users/eric/Downloads/image.jpg  | tr -d '\n'
    

and then, you have to tell the browser that the data is infact base64 encoded, and not a url…

      < img src="data:image/jpeg;charset=utf-8;base64,[encoded image here]" >
    

Good idea for a game ...

 | |
-----
 |x|
-----
o| |
  

And cool, thanks for the tips on base64. Now I can present to you this image:

Someone who came to the freewrite today said that the reason they heard about HTML Energy was because of one of these flyers, which totally amazed me. I posted them in 2020, somewhat for fun, but also somewhat seriously too.

Something we were talking about at the end of our freewrite was the idea that when you're in a park or a green space and using the web, you actually don't really need a website with colors or much complication since the world is already so rich around you. It made me excited to design for this predicament. And maybe the best place to design pages for the park is actually in the park.

wow — that is so amazing. i was just talking to someone yesterday about coding boot camps, and this is flyer is so un-bootcamp like. i never really considered this, but it is kind of funny that bootcamps teaching a “raw” skill still require quite a slick tech-y site to convince people of their legitimacy. perhaps getting back at the idea of html energy, and projects like fruitful school..

i was ruminating on that outdoor coding discussion too. it definitely reminds me of how architects design for a certain environment too, and how more raw buildings are meant to give way to their natural surroundings. that feels similar to keeping a website more black and white so as to let the natural environment envelop it. perhaps to capture that, we need to start including an image in the source code of where the code was written. perhaps in ascii art?

Ah yes, good idea. It's funny, it seems like Dexter already did this for us, right next to us in the park...
I could also see a short audio recording of the place being another nice way.

a sensory documentation of the space that surrounds us! dexter’s ascii documentation reminds me also of crypto art, which is generated on ssh’ing into a device. i believe the term is actually ‘randomart’, which looks a bit like this:

+--[ED25519 256]--+
|          .+*E.. |
|       .   o+B+..|
|        + . *.*.o|
|     o + o + *.+o|
|    . * S + . o =|
|     . @   .   +.|
|      O o       .|
|     o.+..       |
|      .+o        |
+----[SHA256]-----+
  

now that i say ‘crypto art’, i realize that this conversation has veered towards NFTs. but this randomart is most decidedly not that type of art, but rather cryptographically generated art. it was devised as a way for users to verify the identity of a server visually.

it feels like there is some relationship between identity and space that i can’t quite put my finger on...

Wow, yes. This visual "server fingerprint" does feel place-like. Maybe it could be a map of the park from overhead, with its different plant species scattered around? Or it's like this café, with people at work drinking their various caffeinated drinks, buzzing with energy. Alternatively, it looks like a freeze frame of a petri dish. Something about it certainly feels "alive."
Going back to AirDrop for a moment. We began this conversation in Prospect Park by airdropping an index.html file back and forth to each other, gradually adding onto it. The next day (today), we moved to a café in Manhattan to continue the conversation. I wonder: should we share this growing index.html? If so, how? And with who, and where?

i also had the thought that certain parts of a website reveal itself based on your location — perhaps based on where parts of it was coded? that might allow you to share a sense of being with the creator of the site.

in thinking about this conversation — there are many pieces of it that exist because of how airdrop works. the fact that there are new index.html files created (we are currently on index9.html) each time one of us speaks, and that we are base64 encoding data into this page, all speak to the technological constraints of airdrop.