version 0
This commit is contained in:
Vendored
+107
-2
@@ -9,9 +9,114 @@
|
||||
|
||||
<body>
|
||||
<div class="content">
|
||||
<h1>Portfolio</h1>
|
||||
<p>Up: <a href="/">Home</a>; Last Updated: 2026-09-07</p>
|
||||
|
||||
<h1>Portfolio - harpending.org</h1>
|
||||
|
||||
<p>
|
||||
The purpose of this page is roughly to be a more detailed
|
||||
version of <a href="/assets/misc/PeterHarpendingResume.pdf">my
|
||||
resume</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
The projects here are listed roughly in order of how
|
||||
important/impressive <em>I</em> think they are.
|
||||
</p>
|
||||
|
||||
<h2 id="contents">Contents</h2>
|
||||
<div id="toc"></div>
|
||||
|
||||
<h2 class="enum">Flagship Projects</h2>
|
||||
<h3 class="enum">Rubicon</h3>
|
||||
<p>
|
||||
Rubicon is a first-party addressing and authentication scheme
|
||||
for online services that requires no trusted third party. All
|
||||
data can be stored locally on the client machine. Rubicon
|
||||
eliminates the neccesity for DNS and TLS, consequently
|
||||
eliminating both as vectors for abuse.
|
||||
</p>
|
||||
|
||||
<h5>Links</h5>
|
||||
<ul>
|
||||
<li><a href="https://git.harpending.org/pharpend/rbx">Git repo</a></li>
|
||||
</ul>
|
||||
|
||||
<h3 class="enum">SFP</h3>
|
||||
<p>
|
||||
</p>
|
||||
|
||||
<h3 class="enum">WFC</h3>
|
||||
<p>
|
||||
</p>
|
||||
|
||||
<h5>Links</h5>
|
||||
<ul>
|
||||
<li><a href="https://wfc.harpending.org/">Demo</a></li>
|
||||
<li><a href="https://git.harpending.org/pharpend/fewd">Demo git repo</a></li>
|
||||
<li>
|
||||
<a href="https://www.youtube.com/watch?v=_efyu4uF9b4">Talk explaining demo</a><br>
|
||||
|
||||
<iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/_efyu4uF9b4?si=IRrQOvqtxqgm1ncc" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<h3 class="enum">erlang-sha3</h3>
|
||||
<p>
|
||||
</p>
|
||||
|
||||
<h5>Links</h5>
|
||||
<ul>
|
||||
<li><a href="https://git.harpending.org/pharpend/kek">Pre-optimized implementation</a></li>
|
||||
<li><a href="https://git.harpending.org/pharpend/erlang-sha3">Official product</a></li>
|
||||
</ul>
|
||||
|
||||
|
||||
<h2 class="enum">Miscellany</h2>
|
||||
<h3 class="enum">ansi.hrl</h3>
|
||||
<p>
|
||||
I like making TUIs. This is an Erlang header file that has
|
||||
grown organically across many of my projects. It has macros
|
||||
for the useful ANSI control sequences (e.g. dimming text,
|
||||
underline/bold/color).
|
||||
</p>
|
||||
<p>
|
||||
ansi.hrl has grown organically over time across many
|
||||
different projects. It is <b>NOT</b> comprehensive, nor
|
||||
does it aim to solve every conceivable use case. It only
|
||||
has the macros I <i>actually</i> use, and it only aims to
|
||||
solve the problems I have <em>actually</em> encountered in
|
||||
the wild.
|
||||
</p>
|
||||
|
||||
<h5>Projects that use ansi.hrl</h5>
|
||||
<ul>
|
||||
<li>SFP</li>
|
||||
<li>Rubicon demo</li>
|
||||
<li>WFC TUI</li>
|
||||
</ul>
|
||||
|
||||
<h5>Links</h5>
|
||||
<ul>
|
||||
<li><a href="https://git.harpending.org/pharpend/ansi-hrl">Git repo</a></li>
|
||||
</ul>
|
||||
|
||||
|
||||
|
||||
<h2 class="enum">Deprecated Projects</h2>
|
||||
<h3 class="enum">Jex and Sidekick</h3>
|
||||
<p>
|
||||
</p>
|
||||
|
||||
<h5>Links</h5>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://git.harpending.org/pharpend/Vanillae">Git repo</a>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Up: <a href="/">Home</a></p>
|
||||
</div>
|
||||
|
||||
<script src="/assets/js/enum.js"></script>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
Reference in New Issue
Block a user