MiningTcup/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

lots, voyager post

Browse Source
This commit is contained in:
Ted Pier
2025-09-22 17:46:57 -07:00
parent 216ea0de12
commit 29c5230d62
12 changed files with 381 additions and 114 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
archive.html
View File

@@ -3,6 +3,10 @@
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta
name="description"
content="Ted Pier's collection of questionably redistributable large or endangered files"
/>
<title>MiningTcup's Archive</title>
<link rel="stylesheet" href="style.css" />
</head>
@@ -13,7 +17,7 @@
<div class="h1-container">
<h1>Ted's Grand Archive</h1>
</div>
<a href="/"><img src="images/ted2.jpg" /></a>
<a href="/"><img src="images/ted2.webp" alt="Home" /></a>
</div>
<ul id="index">
<li><a href="/index">Home</a></li>
@@ -47,7 +51,6 @@
</li>
<li>
<strong>Exploits:</strong>
</li>
<ul>
<li>
<a href="/archive/exploits/sipe"
@@ -67,6 +70,7 @@
>
</li>
</ul>
</li>
</ul>
</div>
</div>

3
blog.html
View File

@@ -3,6 +3,7 @@
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta name="description" content="Index of Ted Pier's blog" />
<title>MiningTcup</title>
<link rel="stylesheet" href="style.css" />
<link rel="shortcut icon" href="favicon.ico" type="image/x-icon" />
@@ -20,7 +21,7 @@
<div class="h1-container">
<h1>Ted's Silly Blog</h1>
</div>
<a href="/"><img src="images/ted3.jpg" /></a>
<a href="/"><img src="images/ted3.webp" alt="Home" /></a>
</div>
<ul id="index">
<li><a href="/">Home</a></li>

228
blog/voyager.html
View File

@@ -3,15 +3,15 @@
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta
name="description"
content="Ted Pier's review of the Voyager, a $365 ergonomic keyboard made by ZSA."
/>
<title>MiningTcup</title>
<link rel="stylesheet" href="/style.css" />
<link rel="shortcut icon" href="favicon.ico" type="image/x-icon" />
<link rel="dns-prefetch" href="https://git.miningtcup.me/" />
<link rel="dns-prefetch" href="https://mozhi.miningtcup.me/" />
<link rel="dns-prefetch" href="https://arch.miningtcup.me/" />
<link rel="dns-prefetch" href="https://archlinux.org/" />
<link rel="dns-prefetch" href="https://hypr.land/" />
<link rel="dns-prefetch" href="https://openfreemap.org/" />
<link rel="shortcut icon" href="/favicon.ico" type="image/x-icon" />
<link rel="dns-prefetch" href="https://configure.zsa.io/" />
<link rel="dns-prefetch" href="https://zsa.io/" />
</head>
<body>
<div class="centerer">
@@ -29,8 +29,218 @@
<li><a href="/blog">Blog</a></li>
</ul>
<hr />
They keyboard hasn't arrived yet (as of september 4 2025), update in
about 10 days!
<p>
I recently decided that I should have an actual place to use my
computer, other than in bed. I set up my desk with a big monitor and
an old $4 Acer membrane whos keys were way too heavy. It wasn't
working out. I decided I needed a new keyboard... why not one that
would last the rest of my life?
</p>
<p>
The keyboard I landed on was the
<a href="https://www.zsa.io/voyager">Voyager from ZSA</a>. It's split,
columnar, mechanical, customizable, and very high quality. Which I
would expect, considering it cost me $400, over $500 including tariffs
>:(.
</p>
The first step of getting the keyboard was picking the switches. I chose
Pro Reds because they were the lightest option (definitely not because
they had "pro" in the name). I also decided to add some shocks as I
didn't know how loud the keyboard would be. After ordering it, I had to
wait 11 days for it to arrive. It arrived via UPS, which handled the
tariff (for an additional fee of about $20). First impressions were
great: it came in a clean, undamaged, professional-looking box. Included
were the following:
<ul>
<li>36 extra regular keycaps with a variety of symbols</li>
<li>2 extra tall keycaps</li>
<li>4 extra Pro Red switches</li>
<li>A multi-puller for keycaps and switches</li>
<li>3 USB C-to-C cables, with differing lengths</li>
<li>A headphone-looking "TRRS" cable to connect the two halves</li>
<li>A USB C-to-A converter dongle</li>
<li>A small bag of "Shhhocks"</li>
<li>A carrying case</li>
<li>4 little feet stored on a magnetic bar in the case</li>
<li>The Keyboard</li>
</ul>
On my first attempt, I didn't plug the TRRS in all the way, which didn't
make the keyboard happy. After securing that connection, it lit up.
<h3>The Sound</h3>
<p>
This is actually the first mechanical keyboard I've used, so I'm not
really sure what they're supposed to sound like... but it sounds
pretty damn good. The shocks slightly dampen some part of the noise,
but they also make the keys slightly less enjoyable to type on.
Because it's not all that loud in the first place, for now, I've
decided not to put them in.
</p>
<p>
The sound varies by key, being higher toward the edges, but that
doesn't bother me while I'm typing. The sound also depends on the
surface the board is on and if the keyboard is raised. While you
should keep in mind that my microphone is pretty bad, this is a fairly
accurate representation of how it sounds when placed on wood.
</p>
<audio controls>
<source src="/media/voyager-soundtest.ogg" type="audio/ogg" />
<source src="/media/voyager-soundtest.mp3" type="audio/mpeg" />
</audio>
<h3>The Feel</h3>
<p>
Although the keycaps are slightly grainier than the caps on the laptop
keyboards I'm used to, I've actually started to appreciate that. As
for the chassis, I really don't think they could have done much
better. It's very smooth and pleasant to look at. The feet snap in
nice and easily, and the keyboard never slides, with or without them.
</p>
<p>
The switches I chose, Kailh Choc Pro Reds, are linear, light, and
somewhat loud. I had doubts that I would like them, both because of
the lightness, and the absense of a tactile bump. After I started
using them, however, I don't want to go back to heavy switches.
</p>
<h3>The Lights</h3>
<p>
The lights range from a barely visible tint to almost too bright, and
you can change that whenever you want while using it! You can choose
any color for each key, but lighter and less saturated colors don't
show up very well and are tinted by the red (or other color) of the
switches.
</p>
<img
src="/images/voyager-brightness.webp"
alt="Brightness comparison of the Voyager's lighting at high and low brightness"
/>
<h3>The Cables</h3>
<p>The Voyager comes with 4 cables:</p>
<ul>
<li>Long USB C-to-C (86in)</li>
<li>Short USB C-to-C (15in)</li>
<li>Even shorter USB C-to-C (8in)</li>
<li>Medium TRRS-to-TRRS (35in)</li>
</ul>
<p>
The USB cables, which connect to the left half of the keyboard to
provide power and a connection, are super standard, unbranded, and
replaceable. Their shell is a plasticy, rubbery substance, but they
aren't sticky like some other cables I've used. I do wish they
included a medium-length cable or made the short cables a bit longer
because the only one that works for me in any situation is the long
one, which is way overkill (I only ever use a third of it). Others
might find the short cables work better if their computer's USB-C port
is on the left, but mine isn't. The USB C-to-A adapter is also
standard and unbranded.
</p>
<p>
The TRRS cable, which looks like a
<a href="https://en.wikipedia.org/wiki/Phone_connector_(audio)"
>headphone jack</a
>, but with an extra contact, is also unbranded and normal-looking.
Although not as common or cheap as USB-C, TRRS cables are replaceable.
In fact, I'm considering getting a
<a
href="https://www.customcableco.net/custom-cableco/p/35mm-trrs-split-keyboard-cable"
>coiled TRRS cable</a
>
so that I don't have to roll up the length I'm not using. The TRRS
connectors are at 90 degrees, a design choice I certainly agree with.
</p>
<h3>The Software</h3>
<p>
ZSA's configuration and testing software,
<a href="https://configure.zsa.io/home">Oryx</a>, is incredible-
certainly one of the top reasons to get the keyboard. It's completely
web-based, meaning it works on any system that can run Chromium, even
Linux! The configurator is super easy to use and lets you flash the
firmware right there in your browser.
</p>
<p>
The training part of Oryx is also very easy to use. I love that it
uses actual coherent excerpts from books, as opposed to the jumbled
garbage of, for example, Monkeytype. It's not perfect, though. I've
noticed 2 issues in my time using it:
</p>
<ul>
<li>
A little bit of text, "Start typing," is always white, and therefore
is only visible in dark mode.
</li>
<li>
The text doesn't move down for the first time until the bottom line
is fully completed.
</li>
</ul>
<img
src="/images/oryx-full.webp"
alt="Full screenshot of Oryx training"
/>
<div class="flex m-t">
<img
class="flexy-img"
src="/images/oryx-line.webp"
alt="Demonstration of Oryx training bug"
/>
<img
class="flexy-img m-l"
src="/images/oryx-lightbug.webp"
alt="Demonstration of Oryx training lightmode bug"
/>
</div>
<h3>The Support</h3>
<p>
There's a key on my laptop's keyboard that goes to "Launch2." I
couldn't find a way to add this key to my Voyager, so I asked ZSA
support. After a little less than 24 hours, they responded with this:
</p>
<blockquote cite="">
<p>
Hello Ted — thanks for asking! We don't have any keys that
correspond to the Launch2 keycode in Oryx. In the underlying
firmware, QMK, they do have keycode 157 as the "Prev" key, but we
don't surface that one.  I do think that the higher F keys are
probably your best bet to re-bind that action to.
</p>
<p>
I hope that helps to clarify, and please, let me know if any other
questions come up. I'll be here and glad to help. :)
</p>
<p>
—<br />
Nick Wilson,<br />
Customer Service,<br />
ZSA Technology Labs Inc.
</p>
</blockquote>
<p>
In my opinion, they did a really good job. They're friendly, honest,
and actually answered my question, as opposed to the watered-down
corpo speak you'd get from a bigger company.
</p>
<p>
Additionally, I've contacted them about the two Oryx issues, and I was
told it's been passed off to the dev team. I'll update this page if I
get an update or it's fixed.
</p>
<h3>The Conclusion</h3>
<p>
Would I recommend you get the keyboard? Maybe. If you have experience
making keyboards or other electronics, and you have time to figure it
out, you should consider a cheaper, more DIY keyboard, such as the
<a href="https://keebd.com/en-us/products/lily58-pro-keyboard-kit"
>Lily58</a
>. However, if you don't mind paying more, the Voyager is probably the
best keyboard, customer service for a keyboard, and software for a
keyboard there is.
</p>
<hr />
<ul id="index">
<li><a href="/">Home</a></li>
<li><a href="/lulu">Lulu</a></li>
<li><a href="/archive">Archive</a></li>
<li><a href="/blog">Blog</a></li>
<li class="f-l"><a href="#top">Return to Top</a></li>
</ul>
</div>
</div>
</body>

BIN
images/lulu-perch.jpg
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 3.8 MiB

BIN
images/lulu.webp
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 13 KiB

After

Width:  |  Height:  |  Size: 4.8 KiB

BIN
images/lulu2.jpg
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 1.9 MiB

BIN
images/ted1.jpg
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 4.4 MiB

BIN
images/ted2.jpg
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 4.1 MiB

BIN
images/ted3.jpg
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 4.4 MiB

16
index.html
View File

@@ -3,6 +3,10 @@
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta
name="description"
content="Ted Pier's portfolio and personal website."
/>
<title>MiningTcup</title>
<link rel="stylesheet" href="style.css" />
<link rel="shortcut icon" href="favicon.ico" type="image/x-icon" />
@@ -103,10 +107,10 @@
That's what you're using right now- my website! It's a classic Nginx
webserver. Notice how fast it loaded? That's what happens when a
website is written without any libraries, tracking, or external
fonts. Additionally, this includes a frontend for accessing the
fonts. Additionally, this includes a
<a href="/maps">map</a> frontend using the
<a href="https://openfreemap.org/">OpenFreeMap</a>
public instance. You can access that
<a href="/maps">here</a>. I also have a collection of questionably
public instance. I also have a collection of questionably
redistributable files in my <a href="/archive">archive</a>.
</p>
<h3>DNS Servers</h3>
@@ -165,6 +169,12 @@
</div>
</section>
<hr />
<ul id="index">
<li><a href="/lulu">Lulu</a></li>
<li><a href="/archive">Archive</a></li>
<li><a href="/blog">Blog</a></li>
<li class="f-l"><a href="#top">Return to Top</a></li>
</ul>
</div>
</div>
<script src="script.js" defer></script>

17
lulu.html
View File

@@ -3,6 +3,10 @@
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta
name="description"
content="Portfolio and personal website for Ted Pier's dog, Lulu."
/>
<title>MiningTcup</title>
<link rel="stylesheet" href="style.css" />
<link rel="shortcut icon" href="favicon.ico" type="image/x-icon" />
@@ -14,7 +18,7 @@
<div class="h1-container">
<h1>Lulu Pier<span class="subtitle">&nbsp;a.k.a. Doggo</span></h1>
</div>
<a href="/"><img src="images/ted1.jpg" /></a>
<a href="/"><img src="images/ted1.webp" alt="Home" /></a>
</div>
<ul id="index">
<li><a href="/index">Home</a></li>
@@ -28,14 +32,14 @@
around at the park, going on walks, and greeting my people when they
come home.
</p>
<img class="media" src="images/lulu2.jpg" alt="Happy Lulu" />
<img class="media" src="images/lulu2.webp" alt="Happy Lulu" />
<p>
All that running is tiring! After a long time outside, I'll go to my
perch atop the couch and pant.
</p>
<img
class="media"
src="images/lulu-perch.jpg"
src="images/lulu-perch.webp"
alt="Lulu perched upon the couch"
/>
<p>
@@ -45,6 +49,13 @@
<video class="media" controls src="media/lulu-roll.mp4">
Lulu rolling around
</video>
<hr />
<ul id="index">
<li><a href="/index">Home</a></li>
<li><a href="/archive">Archive</a></li>
<li><a href="/blog">Blog</a></li>
<li class="f-l"><a href="#top">Return to Top</a></li>
</ul>
</div>
</div>
</body>

47
style.css
View File

@@ -42,7 +42,7 @@ a:hover {
text-decoration: underline;
}
:not(h2) > a {
:not(h2)>a {
color: light-dark(darkslategrey, beige)
}
@@ -51,6 +51,15 @@ p {
margin-bottom: 8px;
}
.indent {
text-indent: 1em;
margin: 0
}
audio {
display: block;
}
.bullet-img {
height: 14px;
width: 14px;
@@ -76,6 +85,27 @@ p {
align-items: center;
}
.flex {
display: flex;
}
.f-l {
float: right;
}
.flexy-img {
min-width: 0;
height: max-content;
}
.m-l {
margin-left: 16px;
}
.m-t {
margin-top: 16px;
}
.subtitle {
font-size: 16px;
color: grey;
@@ -109,7 +139,7 @@ p {
padding: 0;
}
#index > li {
#index>li {
display: inline;
border: solid light-dark(black, whitesmoke);
border-width: 0 1px;
@@ -117,18 +147,18 @@ p {
padding: 0 8px;
}
#title-1 > .h1-container {
#title-1>.h1-container {
padding: 16px;
background: light-dark(black, whitesmoke);
width: max-content;
z-index: 1;
}
#title-1 > div > h1 {
#title-1>div>h1 {
margin: 0;
}
#title-1 > a > img {
#title-1>a>img {
z-index: 0;
display: block;
max-height: 71px;
@@ -178,7 +208,7 @@ section {
padding: 8px;
}
.blog-item > img {
.blog-item>img {
position: absolute;
top: 8px;
right: 8px;
@@ -187,14 +217,15 @@ section {
z-index: -1;
}
.blog-item > h3, .blog-item > p {
.blog-item>h3,
.blog-item>p {
max-width: 70%;
background: light-dark(#ffffff88, #00000088);
box-shadow: 8px 0 8px light-dark(#ffffff88, #00000088);
margin: 0;
}
.blog-item > p {
.blog-item>p {
font-weight: normal;
}