41 lines
2.8 KiB
HTML
41 lines
2.8 KiB
HTML
|
<!doctype html>
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<title>Zk | 31</title>
|
||
|
|
<link rel="stylesheet" type="text/css" href="/style.css" />
|
||
|
|
<meta name="viewport" content="width=device-width" />
|
||
|
|
<meta charset="utf-8" />
|
||
|
|
</head>
|
||
|
|
<body>
|
||
|
|
<main>
|
||
|
|
<header>
|
||
|
|
<h1>Zk | 31</h1>
|
||
|
|
</header>
|
||
|
|
<article class="content">
|
||
|
|
<p>If I assume that there is some subconscious root of my rising feelings toward Kay, and if I am to continue working backwards from a known starting point, then let me step back from that first recognition of those feelings.</p>
|
||
|
|
<p>We have countless hours of conversations over PostFast and email. We have fallen into the habit of at least saying hi to each other once a day. Sometimes, that is all the conversation that we have and the rest of our days will be eaten up by work and study, by reading and hobbies; and sometimes we will spend entire evenings talking, listening to music or watching comfort videos in the background while we engage on a more constant level.</p>
|
||
|
|
<p>Before we both wound up on PF, though, we had been emailing back and forth. We still do, on occasion, for when thoughts require something less immediate, something more structured than instant messaging<sup id="fnref:email"><a class="footnote-ref" href="#fn:email">1</a></sup>. Sending each other essays and bulleted lists and long quotations that we have found interesting.</p>
|
||
|
|
<p>I had planned to dig back through those conversations</p>
|
||
|
|
<div class="footnote">
|
||
|
|
<hr />
|
||
|
|
<ol>
|
||
|
|
<li id="fn:email">
|
||
|
|
<p>I have sometimes considered why this might be the case, and I have two main thoughts on the issue. The first is that email allows for threaded conversations. One can respond to a particular email, perhaps even after the conversation has continued from beyond that point. This also allows one to reply inline, even, interjecting thoughts between points one’s interlocutor has made. The second is that as a self-advertised “mobile first” application, PF limits the width of the text per message to what might fit on a phone screen, even when using their desktop application, and something about reading a very narrow, very long block of text feels like a misuse of the medium. <a class="footnote-backref" href="#fnref:email" title="Jump back to footnote 1 in the text">↩</a></p>
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
</article>
|
||
|
|
<footer>
|
||
|
|
<p>Page generated on 2021-05-25</p>
|
||
|
|
</footer>
|
||
|
|
</main>
|
||
|
|
<script type="text/javascript">
|
||
|
|
document.querySelectorAll('.tag').forEach(tag => {
|
||
|
|
let text = tag.innerText;
|
||
|
|
tag.innerText = '';
|
||
|
|
tag.innerHTML = `<a href="/tags.html#${text}">${text}</a>`;
|
||
|
|
});
|
||
|
|
</script>
|
||
|
|
</body>
|
||
|
|
</html>
|