|
|
<!DOCTYPE html>
|
|
|
<html lang="en">
|
|
|
<head>
|
|
|
<meta charset="UTF-8">
|
|
|
<title>Ideas | tait.tech</title>
|
|
|
<link rel="stylesheet" href="/assets/css/style.css">
|
|
|
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
|
|
</head>
|
|
|
<body>
|
|
|
<div id="wrapper">
|
|
|
<nav>
|
|
|
<input type="checkbox" id="menu">
|
|
|
<label for="menu">☰</label>
|
|
|
<div class="menu-content">
|
|
|
|
|
|
<a href="/" class="nav-link" >Home</a>
|
|
|
|
|
|
<a href="/tutoring/" class="nav-link" >Tutoring</a>
|
|
|
|
|
|
<a href="/blog/" class="nav-link" >Blog</a>
|
|
|
|
|
|
<a href="/links/" class="nav-link" >Links</a>
|
|
|
|
|
|
<a href="/ideas/" class="nav-link" class="on-page" >Ideas</a>
|
|
|
|
|
|
<a href="https://github.com/TTWNO/" class="nav-link" target="_blank" rel="noopener noreferrer" >Code</a>
|
|
|
|
|
|
</div>
|
|
|
</nav>
|
|
|
|
|
|
<h2 id="ideas">Ideas</h2>
|
|
|
|
|
|
<h3 id="1-accessibility-ideas">1. Accessibility Ideas</h3>
|
|
|
|
|
|
<h4 id="11-bsd-accessibility">1.1 BSD Accessibility</h4>
|
|
|
|
|
|
<p>An Open/FreeBSD driver to make bootup and shutdown (as well as any plain tty) accessible by visually impaired users.
|
|
|
Speech and/or braille display.</p>
|
|
|
|
|
|
<p>The console is the perfect interface for visually impaired users,
|
|
|
as the console is required to be text based (damn you ncurses!).</p>
|
|
|
|
|
|
<h5 id="inspiration-speakup">Inspiration: <a href="http://linux-speakup.org/">Speakup</a></h5>
|
|
|
|
|
|
<h4 id="12-bsdlinux-braille-notetakers">1.2 BSD/Linux Braille Notetakers</h4>
|
|
|
|
|
|
<p>Use standard UNIX tools and command line interface instead of custom
|
|
|
systems for each notetaker.</p>
|
|
|
|
|
|
<p>Being able to use standard utilities not only helps with transferable skills,
|
|
|
but it also opens up the world of Linux tools to visually impaired users.
|
|
|
Enabling them to use any tool compatible with the command line,
|
|
|
not just any tool installed on their system or written for their device.</p>
|
|
|
|
|
|
<p>I have the suspicion that the fancier notetakers are using Windows at this point.
|
|
|
But for low-cost braille notetakers, it certainly could be plausible.</p>
|
|
|
|
|
|
<h4 id="13-raspberry-pi-based-notetaker">1.3 Raspberry Pi-based notetaker</h4>
|
|
|
|
|
|
<p>This could potentially decreese the size and expense of notetakers,
|
|
|
and if running a *NIX
|
|
|
system would also integrate well with idea 1.2</p>
|
|
|
|
|
|
<p>Would need to:</p>
|
|
|
<ol>
|
|
|
<li>Find a manual for controlling a braille display.</li>
|
|
|
<li>Implement a driver within the raspberry pi Raspbian OS using USB/gpio.</li>
|
|
|
<li>Package it up.</li>
|
|
|
</ol>
|
|
|
|
|
|
<p>With the Linux Speakup project already written, would this mean I
|
|
|
could just plug a RPi up to a braille display and be on my merry way?</p>
|
|
|
|
|
|
<h4 id="14-accessible-meme-description">1.4 Accessible Meme Description</h4>
|
|
|
|
|
|
<p>Using a image matching algorithm (no idea which one or how).
|
|
|
Or, frankly, even a scaled down image with binary closeness algorithm.</p>
|
|
|
|
|
|
<p>Either way, take the best matching picture and use that as the basis to describe the picture.
|
|
|
Unsure how I would go about describing unlimited amount of new memes, but that is to be seen.</p>
|
|
|
|
|
|
<p>Best idea is to get in contact with the guys who make <a href="https://imgflip.com/memegenerator">this meme generator</a> as most memes there are at least partially described.</p>
|
|
|
|
|
|
<h4 id="15-talking-anarchy">1.5 Talking Anarchy</h4>
|
|
|
|
|
|
<p>I would like to make a Linux distro which combines the easy of installation of <a href="https://www.anarchylinux.org/">Anarchy Linux</a>
|
|
|
with the speech tools available from <a href="https://talkingarch.info/">Talking Arch</a>.</p>
|
|
|
|
|
|
<p>This should require relatively little effort, as Talking Arch has a tool to build your own ISOs with additional packages (IIRC).</p>
|
|
|
|
|
|
<h3 id="2-nix-ideas">2. *NIX Ideas</h3>
|
|
|
|
|
|
<h4 id="21-fansensor-driver-for-my-old-toshiba">2.1 Fan/Sensor Driver for My Old Toshiba</h4>
|
|
|
|
|
|
<p>FreeBSD and Linux both have the right driver for sensing my CPU
|
|
|
temp/spinning my fan properly.</p>
|
|
|
|
|
|
<p>OpenBSD does not have this working, and it is annoying to run it this way.
|
|
|
Full fans at all times on OpenBSD.</p>
|
|
|
|
|
|
<h4 id="22-zfs-nas">2.2 ZFS NAS</h4>
|
|
|
|
|
|
<p>I would really like to setup my own NAS with the ZFS file system.
|
|
|
I’d want to chronicle the adventure of finding hardware,
|
|
|
setting up OS, ZFS, frontend.</p>
|
|
|
|
|
|
<h4 id="23-mirror-important-open-source-projects">2.3 Mirror Important Open-Source Projects</h4>
|
|
|
|
|
|
<p>Setup a mirror for OpenBSD, Arch Linux, and other important projects
|
|
|
I want to contribute to where I know my level of coding is not helpful.</p>
|
|
|
|
|
|
<h5 id="also-considering-tor-relay-void-linux">Also considering: <a href="https://community.torproject.org/relay/">Tor Relay</a>, <a href="https://voidlinux.org/download/#mirrors">Void Linux</a></h5>
|
|
|
|
|
|
<h4 id="24-systemd-service-randomizer">2.4 Systemd Service Randomizer</h4>
|
|
|
|
|
|
<p>Systemd can start a VPN on startup with the following command:</p>
|
|
|
|
|
|
<pre class="terminal">
|
|
|
# systemctl enable wg-quick@mullvad-ca1
|
|
|
</pre>
|
|
|
|
|
|
<p>or</p>
|
|
|
|
|
|
<pre class="terminal">
|
|
|
# systemctl enable openvpn-client@mullvad_ca
|
|
|
</pre>
|
|
|
|
|
|
<p>These commands are nice, but why is there not a <code class="highlighter-rouge">openvpn-client@random</code> so that I can randomize out of the possible files?</p>
|
|
|
|
|
|
<p>I am sure there would be a way to have a systemd service envoked like so:</p>
|
|
|
|
|
|
<pre class="terminal">
|
|
|
# systemctl enable random@[wg-quick|openvpn-client]
|
|
|
</pre>
|
|
|
|
|
|
<p>This would enable a randomization service for that interface, relinking
|
|
|
the boot-time process by looking in the directory the VPN interface
|
|
|
should be looking in, and chosing a random file.</p>
|
|
|
|
|
|
<p>Very useful for VPN clients. I have no idea if this has currency anywhere else.</p>
|
|
|
|
|
|
<h3 id="3-language-ideas">3. Language Ideas</h3>
|
|
|
|
|
|
<h4 id="31-add-zhuyin-support-for-epub-with-pinyin">3.1 Add Zhuyin Support for <a href="https://github.com/TTWNO/epub-with-pinyin">epub-with-pinyin</a></h4>
|
|
|
|
|
|
<p>It currently only supports Pinyin.
|
|
|
At the time, HTML <code class="highlighter-rouge"><ruby></code> support was low,
|
|
|
and so even when implemented properly the characters showed at the top.
|
|
|
They should be shown on the left hand side.</p>
|
|
|
|
|
|
<h4 id="312-make-epub-with-pinyin-easier-to-use">3.1.2 Make <a href="https://github.com/TTWNO/epub-with-pinyin">epub-with-pinyin</a> Easier To Use</h4>
|
|
|
|
|
|
<p>Currently it requires setting up Python and some libraries.</p>
|
|
|
|
|
|
<p>Ideally it could be a web application, executing in Javascript.
|
|
|
Storing .epub files on a webserver even temporarily (especially if they are copywrited) is
|
|
|
a legal risk I am not willing to take.</p>
|
|
|
|
|
|
<h4 id="32-look-into-linq">3.2 Look Into <a href="https://www.lingq.com/en/">LinQ</a></h4>
|
|
|
|
|
|
<p>I have heard this system implements something very similar to an idea I had called “Minks”.</p>
|
|
|
|
|
|
<p>The general idea was that you could save words you knew,
|
|
|
thus stopping their pronunciation to appear above them (Pinyin/Zhuyin).</p>
|
|
|
|
|
|
<p>Given my interest in similar things, possibly apply to work for them,
|
|
|
or encourage them to BSD some of their libraries.</p>
|
|
|
|
|
|
<h3 id="4-other-crazy-ideas">4. Other Crazy Ideas</h3>
|
|
|
|
|
|
<h4 id="41-podcast-not-sure-what-about">4.1 Podcast: Not Sure What About</h4>
|
|
|
|
|
|
<p>I’ve always wanted to interview people.
|
|
|
Seems liks fun.</p>
|
|
|
|
|
|
<h4 id="42-dd-minimalistic-game-player">4.2 D&D Minimalistic Game Player</h4>
|
|
|
|
|
|
<p>I would have to look into the legal implications of this;
|
|
|
whoever owns D&D has been rather hostile to third-party developers making things to promote their game.
|
|
|
I don’t get the whole thing, but that’d be the first thing I’d check.</p>
|
|
|
|
|
|
<p>In theory it would need to implement the following:</p>
|
|
|
<ol>
|
|
|
<li>Player character storage w/ stats</li>
|
|
|
<li>DM mode w/ map</li>
|
|
|
<li>Automatic rolling and stat challenges at request of DM.</li>
|
|
|
<li>A database of standard enemies, races, classes, weapons.</li>
|
|
|
<li>Two player modes: in person, online.
|
|
|
In person would disable automatic rolling and stat challenges, leaving the user with essentially a character sheet.</li>
|
|
|
</ol>
|
|
|
|
|
|
|
|
|
<footer>
|
|
|
This page is mirrored on <a href="https://beta.tait.tech/ideas/">beta.tait.tech</a>.
|
|
|
</footer>
|
|
|
|
|
|
</div>
|
|
|
</body>
|
|
|
</html>
|
