Domů Procházet Nápověda
Registrovat se Přihlásit se
thatsmydoing
/
blog
1
0
Rozštěpit 0
Soubory Úkoly 0 Pull Requesty 0 Wiki
Větev: master
Větve Značky
blog
/
output
/
index.html

index.html 22 KB
Trvalý odkaz Historie Surový

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319 
  1. <!DOCTYPE html>
    2. 

  2. <html lang="en-us">
    3. 

  3. <head>
    4. 

  4. 	<meta charset="utf-8">
    5. 

  5. 	<meta name="generator" content="Hugo 0.92.0" />
    6. 

  6. 	<meta name="viewport" content="width=device-width, initial-scale=1">
    7. 

  7. 	<link rel="stylesheet" href="/assets/css/theme.css">
    8. 

  8. 	<link rel="alternate" href="/rss.xml" type="application/rss+xml" title="Pleasant Programmer">
    9. 

  9. 	<script type="text/javascript" src="//use.typekit.net/iwm5axp.js"></script>
    10. 

  10. 	<script type="text/javascript">try{Typekit.load();}catch(e){}</script>
    11. 

  11. 	<title>Pleasant Programmer</title>
    12. 

  12. </head>
    13. 

  13. 

  14. <body>
    15. 

  15. 	<header id="header" role="banner">
    16. 

  16. 		<div id="thomas">
    17. 

  17. 			<img src="/assets/img/thomas.gif" alt="DJ THOMAS IN DA HAUS">
    18. 

  18. 			<img src="/assets/img/thomas.png" alt="Pleasant Programmer">
    19. 

  19. 		</div>
    20. 

  20. 		<h1 class="site-title"><a href="/">Pleasant Programmer</a></h1>
    21. 

  21. 		<nav id="menu" role="navigation">
    22. 

  22. 			<ul>
    23. 

  23. 				<li><a href="/pages/projects.html">projects</a></li>
    24. 

  24. 				<li><a href="/posts.html">archives</a></li>
    25. 

  25. 				<li><a href="/tags.html">tags</a></li>
    26. 

  26. 				<li><a href="/rss.xml">rss</a></li>
    27. 

  27. 			</ul>
    28. 

  28. 		</nav>
    29. 

  29. 	</header>
    30. 

  30. 	<div id="container">
    31. 

  31. 

  32. 

  33. <main id="content" role="main">
    34. 

  34. <div class="postindex">
    35. 

  35. 	
    36. 

  36. 	<article class="h-entry post-text" itemscope itemtype="http://schema.org/Blog">
    37. 

  37. 		<header>
    38. 

  38. 			<h1 class="p-name entry-title" itemprop="headline">
    39. 

  39. 				<a href="/posts/ssh-git-repo-docker.html" class="u-url">SSH Access to Git Repository in Docker</a>
    40. 

  40. 			</h1>
    41. 

  41. 		</header>
    42. 

  42. 		<div class="e-content entry-content">
    43. 

  43. 			<p>With the likes of <a href="https://gogs.io/">Gogs</a> and <a href="https://gitea.io">Gitea</a>,
    44. 

  44. self-hosting a personal git service has become quite common. It&rsquo;s also not
    45. 

  45. unlikely that the software is run via docker but this brings a problem with
    46. 

  46. regards to SSH access.</p>
    47. 

  47. <p>Ideally, the git service container just exposes port 22 but this would conflict
    48. 

  48. with the host&rsquo;s own SSH service. One solution would be to just use different
    49. 

  49. ports for the git SSH and host SSH and that&rsquo;s perfectly fine. But we can also
    50. 

  50. just have the host SSH service forward the request to the git service itself
    51. 

  51. using the <code>command</code> option in <code>authorized_keys</code>. And as we&rsquo;ll find out later,
    52. 

  52. the git service itself is using this functionality.</p>
    53. 

  53. <h2 id="how-git-over-ssh-works">How git over SSH works</h2>
    54. 

  54. <p>When you do a <code>git push</code>, what actually happens is it runs <code>git-send-pack</code> which
    55. 

  55. runs <code>git-receive-pack &lt;directory&gt;</code> on the remote using SSH. The actual
    56. 

  56. communication then just simply happens via stdin/stdout. Conversely, doing a
    57. 

  57. <code>git pull</code> just runs <code>git-fetch-pack</code> and the somewhat confusingly named
    58. 

  58. <code>git-upload-pack</code> on the remote.</p>
    59. 

  59. <p>So far so good, but did you notice that when cloning via SSH, the remote is
    60. 

  60. typically <code>git@github.com:org/repo</code>? If everyone SSHs in as the <code>git</code> user, how
    61. 

  61. does the git service know which user is which? And how does it prevent users
    62. 

  62. from accessing each other&rsquo;s repositories?</p>
    63. 

  63. <p>One typically thinks of <code>authorized_keys</code> as just a list of allowed SSH keys but
    64. 

  64. it can do <a href="https://linux.die.net/man/8/sshd">much more than that</a>. Of particular
    65. 

  65. interest is the <code>command</code> directive which gets run instead of the user supplied
    66. 

  66. command. The original command is passed in as an environment variable
    67. 

  67. <code>SSH_ORIGINAL_COMMAND</code> which can be used to check if we allow it to be run or
    68. 

  68. not.</p>
    69. 

  69. <p>So with an <code>authorized_keys</code> file like so:</p>
    70. 

  70. <div class="highlight"><pre tabindex="0" style="color:#e5e5e5;background-color:#000;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-text" data-lang="text">command=&#34;verify-user user-1&#34; ssh-rsa ...
    71. 

  71. command=&#34;verify-user user-1&#34; ssh-ed25519 ...
    72. 

  72. command=&#34;verify-user user-2&#34; ssh-rsa ...
    73. 

  73. command=&#34;verify-user user-3&#34; ssh-rsa ...
    74. 

  74. </code></pre></div><p>Each key is tied to a particular user by virtue of <code>command</code>. And <code>verify-user</code>
    75. 

  75. can check the <code>SSH_ORIGINAL_COMMAND</code> if the particular user is allowed access to
    76. 

  76. the particular repository. You can also implement additional restrictions like
    77. 

  77. pull-only or push-only permissions with this setup. This is how both Gogs and
    78. 

  78. Gitea work.</p>
    79. 

  79. <h2 id="forwarding-git-ssh-to-docker">Forwarding git SSH to Docker</h2>
    80. 

  80. <p>When running Gogs on the host, it&rsquo;s typically run as the <code>git</code> user and when an
    81. 

  81. SSH key is added or removed, it simply rewrites <code>~git/.ssh/authorized_keys</code>.
    82. 

  82. Thus it just works with the host SSH service without problems. When running
    83. 

  83. inside docker, one thing we can do is bind mount the host&rsquo;s <code>~git/.ssh</code> folder
    84. 

  84. into the docker container so that the host can authorize the SSH connections.</p>
    85. 

  85. <p>The problem lies with the <code>command</code> which only exists inside the docker
    86. 

  86. container itself. So any user trying to connect can authenticate successfully
    87. 

  87. but will get a <code>command not found</code> error. For the Gogs docker image, the command
    88. 

  88. looks like <code>/app/gogs/gogs serv key-1</code>. So we can just make <code>/app/gogs/gogs</code>
    89. 

  89. available on the host and forward the command to the docker container.</p>
    90. 

  90. <p><a href="https://docs.gitea.io/en-us/install-with-docker/#ssh-container-passthrough">Most</a>
    91. 

  91. <a href="http://www.ateijelo.com/blog/2016/07/09/share-port-22-between-docker-gogs-ssh-and-local-system">instructions</a>
    92. 

  92. I&rsquo;ve seen with regards to this involves using <code>ssh</code> to connect to the internal
    93. 

  93. docker SSH service but this just seems overly complicated to me. If you
    94. 

  94. remember, at it&rsquo;s core git really only communicates over stdin/stdout and SSH is
    95. 

  95. just a means to get that.</p>
    96. 

  96. <p>If all we need is for our shim <code>/app/gogs/gogs</code> to be able to run a command
    97. 

  97. inside the docker container with stdin/stdout attached, then we can actually
    98. 

  98. just do that with <code>docker exec</code>. So it can be something like this:</p>
    99. 

  99. <div class="highlight"><pre tabindex="0" style="color:#e5e5e5;background-color:#000;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-shell" data-lang="shell"><span style="color:#0f0;font-weight:bold">#!/usr/bin/env bash
    100. 

  100. </span><span style="color:#0f0;font-weight:bold"></span>
    101. 

  101. <span style="color:#007f7f"># Requires the following in sudoers</span>
    102. 

  102. <span style="color:#007f7f"># git ALL=(ALL) NOPASSWD: /app/gogs/gogs</span>
    103. 

  103. <span style="color:#007f7f"># Defaults:git env_keep=SSH_ORIGINAL_COMMAND</span>
    104. 

  104. 

  105. GOGS_CONTAINER=git-gogs-1
    106. 

  106. 

  107. <span style="color:#fff;font-weight:bold">if</span> [[ $EUID -ne <span style="color:#ff0;font-weight:bold">0</span> ]]; <span style="color:#fff;font-weight:bold">then</span>
    108. 

  108.   <span style="color:#fff;font-weight:bold">exec</span> sudo <span style="color:#0ff;font-weight:bold">&#34;</span>$0<span style="color:#0ff;font-weight:bold">&#34;</span> <span style="color:#0ff;font-weight:bold">&#34;</span>$@<span style="color:#0ff;font-weight:bold">&#34;</span>
    109. 

  109. <span style="color:#fff;font-weight:bold">fi</span>
    110. 

  110. 

  111. <span style="color:#fff;font-weight:bold">if</span> [ <span style="color:#0ff;font-weight:bold">&#34;</span>$1<span style="color:#0ff;font-weight:bold">&#34;</span> != <span style="color:#0ff;font-weight:bold">&#34;serv&#34;</span> ]; <span style="color:#fff;font-weight:bold">then</span>
    112. 

  112.   <span style="color:#fff;font-weight:bold">exit</span> <span style="color:#ff0;font-weight:bold">1</span>
    113. 

  113. <span style="color:#fff;font-weight:bold">fi</span>
    114. 

  114. 

  115. <span style="color:#fff;font-weight:bold">exec</span> docker <span style="color:#fff;font-weight:bold">exec</span> -i -u git -e <span style="color:#0ff;font-weight:bold">&#34;SSH_ORIGINAL_COMMAND=</span>$SSH_ORIGINAL_COMMAND<span style="color:#0ff;font-weight:bold">&#34;</span> <span style="color:#0ff;font-weight:bold">&#34;</span>$GOGS_CONTAINER<span style="color:#0ff;font-weight:bold">&#34;</span> /app/gogs/gogs <span style="color:#0ff;font-weight:bold">&#34;</span>$@<span style="color:#0ff;font-weight:bold">&#34;</span>
    116. 

  116. </code></pre></div><p>So for git SSH access to Gogs running in docker, the necessary steps here are:</p>
    117. 

  117. <ol>
    118. 

  118. <li>Have a <code>git</code> user on the host</li>
    119. 

  119. <li>Bind mount <code>~git/.ssh</code> to <code>/data/git/.ssh</code> in the Gogs container</li>
    120. 

  120. <li>Add the shim script to <code>/app/gogs/gogs</code> (make sure it&rsquo;s owned by root and
    121. 

  121. is chmod-ed <code>0755</code>)</li>
    122. 

  122. <li>Add the listed sudoers rules</li>
    123. 

  123. </ol>
    124. 

  124. 

  125. 		</div>
    126. 

  126. 		<small class="dateline">Posted: <time class="published dt-published" itemprop="datePublished" datetime="2022-01-23">2022-01-23</time></small>
    127. 

  127. 		| <small class="commentline"><a href="/posts/ssh-git-repo-docker.html#isso-thread">Comments</a></small>
    128. 

  128. 	</article>
    129. 

  129. 	</article>
    130. 

  130. 	
    131. 

  131. 	<article class="h-entry post-text" itemscope itemtype="http://schema.org/Blog">
    132. 

  132. 		<header>
    133. 

  133. 			<h1 class="p-name entry-title" itemprop="headline">
    134. 

  134. 				<a href="/posts/android-multisim.html" class="u-url">Android Multisim Pre-5.1</a>
    135. 

  135. 			</h1>
    136. 

  136. 		</header>
    137. 

  137. 		<div class="e-content entry-content">
    138. 

  138. 			<p><strong>NOTE</strong> if you&rsquo;re just looking for a library to use, there&rsquo;s <a href="https://github.com/UseHover/MultiSim">MultiSim</a>. I&rsquo;ve never used this so I can&rsquo;t guarantee anything about it. It also only supports SIM information and not SMS.</p>
    139. 

  139. <p>Phones that can take multiple SIM cards are quite popular in the Philippines. The two major telecoms would have unlimited SMS packages for messages within their networks. It was quite common to have a SIM for each telco and use the appropriate one depending on who you were sending to.</p>
    140. 

  140. <p>Android&rsquo;s API only officially supported multiple SIM cards in 5.1 (API level 22) but Android phones with dual-SIM (and even triple-SIM) capabilities were already available at least as far back as 2.3 (API level 10) when I first needed to support it. Since there was no official API for this, the manufacturers just invented their own and of course each one implemented it in a different way.</p>
    141. 

  141. <h2 id="mediatek">Mediatek</h2>
    142. 

  142. <p>The first phone we started working on was a <a href="https://www.gsmarena.com/lenovo_a60-4711.php">Lenovo A60</a> which used a Mediatek SOC. We somehow got a library from the manufacturer that let us use the dual-SIM functionality, but it was quite a pain to get working as there was limited documentation and we were quite new to Android development at the time.</p>
    143. 

  143. <p>When we disassembled the library that they gave us, we noticed that the names they used for the additional functions were quite interesting. They were all the <code>TelephonyManager</code> and <code>SmsManager</code> methods with a <code>Gemini</code> suffix and they would take an additional <code>int</code> parameter in addition to the original.</p>
    144. 

  144. <p>It turned out that these were available on the standard <code>TelephonyManager</code> instance and could be accessed via reflection. The <code>SmsManager</code> was a bit trickier but we ended up figuring out that there was a <code>android.telephony.gemini.GeminiSmsManager</code> class that had the functionality.</p>
    145. 

  145. <p>In a different phone with a Mediatek SOC, this got renamed to <code>com.mediatek.telephony.gemini.SmsManager</code> for some reason and dropped the <code>Gemini</code> suffix only for the <code>SmsManager</code>.</p>
    146. 

  146. <h2 id="intel">Intel</h2>
    147. 

  147. <p>It was also around this time that Intel started making SOCs for smartphones. We had an <a href="https://www.gsmarena.com/asus_fonepad_7_%282014%29-6394.php">ASUS Fonepad 7</a>. Unlike with the Mediatek device, we didn&rsquo;t have a library to use here and had to use reflection to find the hidden classes / methods.</p>
    148. 

  148. <p>What we found was that instead of having a single instance with every method taking a <code>sim</code> parameter, they instead had separate instances of <code>TelephonyManager</code> and <code>SmsManager</code> for each SIM. You would call <code>TelephonyManager.get2ndTm()</code> and <code>SmsManager.get2ndSmsManager()</code> to have access to the 2nd SIM.</p>
    149. 

  149. <h2 id="qualcomm">Qualcomm</h2>
    150. 

  150. <p>The last phone I looked at was a <a href="https://www.gsmarena.com/motorola_moto_g_dual_sim-5978.php">dual-SIM Moto G</a>. What&rsquo;s interesting about this one is that the API completely changed in the upgrade from 4.4 to 5.0.</p>
    151. 

  151. <p>On Android 4.4, the API was pretty close to the Mediatek one. You had a single instance that could dispatch to other SIMs by having an extra parameter on all the methods. These were in <code>android.telephony.MSimTelephonyManager</code> and <code>android.telephony.MSimSmsManager</code>.</p>
    152. 

  152. <p>On Android 5.0, the API was a weird mix of all the above and also the introduction of <code>android.telephony.SubscriptionManager</code> which was quite close but not exactly the same as what ended up in the official API. Instead of <code>getActiveSubscriptionInfoList</code> there was <code>getActiveSubIdList</code> which only returned <code>long[]</code>.</p>
    153. 

  153. <p>For the information that would normally exist in <code>SubscriptionInfo</code>, you had to query the main <code>TelephonyManager</code> instance which had methods with an extra <code>long</code> parameter for the subscription id. The <code>SmsManager</code> was simpler with just <code>getSmsManagerForSubscriber</code>.</p>
    154. 

  154. <p>With Android 5.1, I assume they just switched to using the official API so this phone would have gone through 3 different multi-SIM APIs over the course of it&rsquo;s life.</p>
    155. 

  155. <h2 id="epilogue">Epilogue</h2>
    156. 

  156. <p>Around the release of Android 5.1, we stopped work on the app so I never actually got to use the official API myself ironically. We also never really got a big deployment so while I saw quite the variety of multi-SIM implementations, that&rsquo;s probably not all that&rsquo;s been out in the wild.</p>
    157. 

  157. 

  158. 		</div>
    159. 

  159. 		<small class="dateline">Posted: <time class="published dt-published" itemprop="datePublished" datetime="2021-09-12">2021-09-12</time></small>
    160. 

  160. 		| <small class="commentline"><a href="/posts/android-multisim.html#isso-thread">Comments</a></small>
    161. 

  161. 	</article>
    162. 

  162. 	</article>
    163. 

  163. 	
    164. 

  164. 	<article class="h-entry post-text" itemscope itemtype="http://schema.org/Blog">
    165. 

  165. 		<header>
    166. 

  166. 			<h1 class="p-name entry-title" itemprop="headline">
    167. 

  167. 				<a href="/posts/isp-issues.html" class="u-url">ISP Issues</a>
    168. 

  168. 			</h1>
    169. 

  169. 		</header>
    170. 

  170. 		<div class="e-content entry-content">
    171. 

  171. 			<p>At the first office I worked at, we had 2 different ISPs. This was supposed to be for reliability, as one was fast but spotty, and the other was slow but reliable. Since they weren&rsquo;t <em>too</em> expensive, we just went and got both.</p>
    172. 

  172. <p>We have monitoring setup to watch our office IPs from the outside so we could see how often the connection goes down. The interesting thing we found was that the fast and spotty connection had perfect uptime. Even when there was clearly no internet from the office, it was still &ldquo;up&rdquo; according to our monitoring.</p>
    173. 

  173. <p>So we tried pinging our office IP using the other connection and to our surprise it was indeed up. There was even a webserver running on it (we only have VPN exposed). Apparently, it was someone elses CCTV admin page. We could actually see a hallway with people walking by sometimes!</p>
    174. 

  174. <p>Apparently someone else had our IP address and nothing good comes from an IP conflict. This was completely baffling as our internet line was supposed to be a &ldquo;business line&rdquo; and that came with a static IP address. So the only scenarios where this could happen is, the ISP mistakenly gave the same IP to 2 different lines or the ISP allows some clients to freely set their own IP.</p>
    175. 

  175. <p>We complained to the ISP and eventually got it resolved. They just gave us an entirely new IP address, but they never explained what went wrong. We already had quite a negative opinion of that particular ISP though, and they somehow managed to outdo themselves.</p>
    176. 

  176. 

  177. 		</div>
    178. 

  178. 		<small class="dateline">Posted: <time class="published dt-published" itemprop="datePublished" datetime="2018-08-16">2018-08-16</time></small>
    179. 

  179. 		| <small class="commentline"><a href="/posts/isp-issues.html#isso-thread">Comments</a></small>
    180. 

  180. 	</article>
    181. 

  181. 	</article>
    182. 

  182. 	
    183. 

  183. 	<article class="h-entry post-text" itemscope itemtype="http://schema.org/Blog">
    184. 

  184. 		<header>
    185. 

  185. 			<h1 class="p-name entry-title" itemprop="headline">
    186. 

  186. 				<a href="/posts/audventure.html" class="u-url">Audventure</a>
    187. 

  187. 			</h1>
    188. 

  188. 		</header>
    189. 

  189. 		<div class="e-content entry-content">
    190. 

  190. 			<p>Sometime around 2013 I wrote a clone of the GBA game <a href="https://www.nintendo.co.jp/n08/bit_g/">bit Generations
    191. 

  191. SoundVoyager</a> called
    192. 

  192. <a href="https://audventure.pleasantprogrammer.com">audventure</a>. SoundVoyager is
    193. 

  193. actually a collection of mini-games where sound is the main focus. You can
    194. 

  194. actually play the game blind, and at some point, that&rsquo;s pretty much what
    195. 

  195. happens.</p>
    196. 

  196. <h2 id="sound-catcher">sound catcher</h2>
    197. 

  197. <p>The signature mini-game in SoundVoyager is sound catcher. In the mini-game, you
    198. 

  198. can only move left and right at the bottom of the stage, while a &ldquo;sound&rdquo; falls
    199. 

  199. from the top. Your goal is to catch the sound which is signified by a green dot.
    200. 

  200. When you catch it, the sound or beat becomes part of the BGM and a new dot
    201. 

  201. appears with a different sound.</p>
    202. 

  202. <p>You can of course use your eyes and move accordingly, but if you put on
    203. 

  203. earphones, you can actually hear where the dot is, either on your left or right,
    204. 

  204. with it getting louder as it gets close to you. As you collect more sounds, the
    205. 

  205. dot gets more and more transparent. Eventually (and this is where it gets fun),
    206. 

  206. you won&rsquo;t be able to see the sounds anymore and will have to rely mostly on your
    207. 

  207. ears.</p>
    208. 

  208. <p>You can see what the original game looks like in <a href="https://www.youtube.com/watch?v=C12WRgfIOC8">this
    209. 

  209. video</a> or you can play it under
    210. 

  210. <em>sound safari</em> in <a href="https://audventure.pleasantprogrammer.com">audventure</a>.</p>
    211. 

  211. <h2 id="webaudio-vs-flash">WebAudio vs Flash</h2>
    212. 

  212. <p>At the time I wrote audventure, only Chrome supported WebAudio. Also, the API
    213. 

  213. looked (and still looks) quite complicated. Flash on the other hand, was
    214. 

  214. starting to die, but still well-supported so I went with that. For the most
    215. 

  215. part, it worked okay though Chrome actually had timing issues when playing
    216. 

  216. sounds. Now, it doesn&rsquo;t work in any browser. I tried to debug the issues but
    217. 

  217. ultimately ended up just rewriting it to use WebAudio instead.</p>
    218. 

  218. <p>For the game, I needed to simulate the source of the sound in 2D/3D space. Flash
    219. 

  219. only really gives you stereo panning and volume control. With some maths, we can
    220. 

  220. actually get an acceptable solution. Less importantly, I needed to be able to
    221. 

  221. get frequency data of the currently playing &ldquo;sound&rdquo; to pulse the background. For
    222. 

  222. this, I actually had to implement the feature in the Flash library I was using.</p>
    223. 

  223. <p>With WebAudio, spatial audio is already built-in and you can simply give it the
    224. 

  224. coordinates of the sounds and the listener. There are some other options to
    225. 

  225. tweak, but for the most part, no complex math is needed. Getting frequency data
    226. 

  226. for a sound is also actually built-in and didn&rsquo;t take too long to integrate.</p>
    227. 

  227. <p>Overall, I was impressed by how much you can do with WebAudio out-of-the-box. I
    228. 

  228. kind of understand why it&rsquo;s complicated, but there&rsquo;s some simple functionality
    229. 

  229. that I wish was included. For example, there is no API to pause and then resume
    230. 

  230. playing an audio buffer. You have to manually save the elapsed time and play
    231. 

  231. from there.</p>
    232. 

  232. <h2 id="other-mini-games">Other mini-games</h2>
    233. 

  233. <p>So far I&rsquo;ve only actually implemented the sound catcher mini-game. There are
    234. 

  234. around 4 different categories with slight variations in between.</p>
    235. 

  235. <h3 id="sound-catcher--sound-slalom">sound catcher / sound slalom</h3>
    236. 

  236. <p>I&rsquo;ve explained sound catcher a while ago; sound slalom is a minor variation on
    237. 

  237. that. Instead of waiting for the &ldquo;sound&rdquo; to reach you, you now have to guide
    238. 

  238. yourself in between 2 &ldquo;poles&rdquo; of sound, as in <a href="https://en.wikipedia.org/wiki/Slalom_skiing">slalom
    239. 

  239. skiing</a>. But this time, you can
    240. 

  240. also accelerate forward. The goal is to finish the course before the time runs
    241. 

  241. out.</p>
    242. 

  242. <h3 id="sound-drive--sound-chase">sound drive / sound chase</h3>
    243. 

  243. <p>In sound drive, you&rsquo;re driving against the flow on a 5 lane road. You have to
    244. 

  244. avoid oncoming cars, trucks and animals until you reach the end. You&rsquo;re allowed
    245. 

  245. to change lanes and accelerate, and the game tracks your best time. Sound chase
    246. 

  246. is pretty much the same, except you&rsquo;re trying to catch up to a &ldquo;sound&rdquo;.</p>
    247. 

  247. <h3 id="sound-cannon">sound cannon</h3>
    248. 

  248. <p>In sound cannon, you&rsquo;re immobile but can rotate within a 180 degree angle. Your
    249. 

  249. goal is too shoot down &ldquo;sounds&rdquo; which are heading your way. If a sound reaches
    250. 

  250. you, it&rsquo;s game over. You win when you kill all the sounds.</p>
    251. 

  251. <h3 id="sound-picker--sound-cock">sound picker / sound cock</h3>
    252. 

  252. <p>In sound picker, you can move in a giant square field where various sounds are
    253. 

  253. scattered around. Your goal is to pick up all the sounds within the time limit.
    254. 

  254. Sound cock is similar, except the sounds are chickens and you have to chase them
    255. 

  255. around.</p>
    256. 

  256. <h2 id="source-code">Source Code</h2>
    257. 

  257. <p>If you want to see the source code, you can check it out
    258. 

  258. <a href="https://git.pleasantprogrammer.com/games/audventure">here</a>. The sound files
    259. 

  259. aren&rsquo;t in the repo though, since I&rsquo;m not quite sure about the licensing. If you
    260. 

  260. want to contribute music or sound effects, I&rsquo;d gladly appreciate it.</p>
    261. 

  261. 

  262. 		</div>
    263. 

  263. 		<small class="dateline">Posted: <time class="published dt-published" itemprop="datePublished" datetime="2017-11-19">2017-11-19</time></small>
    264. 

  264. 		| <small class="commentline"><a href="/posts/audventure.html#isso-thread">Comments</a></small>
    265. 

  265. 	</article>
    266. 

  266. 	</article>
    267. 

  267. 	
    268. 

  268. </div>
    269. 

  269. <nav class="postindexpager">
    270. 

  270. 	<ul class="pager clearfix">
    271. 

  271. 		
    272. 

  272. 		
    273. 

  273. 		<li class="next">
    274. 

  274. 			<a href="/page/2.html">Older posts &rarr;</a>
    275. 

  275. 		</li>
    276. 

  276. 		
    277. 

  277. 	</ul>
    278. 

  278. </nav>
    279. 

  279. 

  280. </main>
    281. 

  281. 

  282. 

  283. 	<footer id="footer" role="contentinfo">
    284. 

  284. 		<p>
    285. 

  285. 		<a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/deed.en_US">
    286. 

  286. 			<img alt="CC-BY-SA" style="border-width:0" src="https://licensebuttons.net/l/by-sa/3.0/80x15.png">
    287. 

  287. 		</a> &copy; 2022 Thomas Dy - Powered by <a href="http://gohugo.io">Hugo</a></p>
    288. 

  288. 	</footer>
    289. 

  289. </div>
    290. 

  290. 

  291. <script src="/assets/js/konami.js"></script>
    292. 

  292. <script>
    293. 

  293. var easter_egg = new Konami();
    294. 

  294. easter_egg.code = function() {
    295. 

  295. 	var el = document.getElementById('thomas');
    296. 

  296. 	if(el.className == "whoa") {
    297. 

  297. 		el.className = "";
    298. 

  298. 	}
    299. 

  299. 	else {
    300. 

  300. 		el.className = "whoa";
    301. 

  301. 	}
    302. 

  302. 	document.body.scrollTop = document.documentElement.scrollTop = 0;
    303. 

  303. }
    304. 

  304. easter_egg.load();
    305. 

  305. 

  306. 

  307. 

  308. </script>
    309. 

  309. 

  310. 

  311. <script
    312. 

  312. 	data-isso="https://isso.pleasantprogrammer.com/"
    313. 

  313. 	src="https://isso.pleasantprogrammer.com/js/count.min.js">
    314. 

  314. </script>
    315. 

  315. 

  316. 

  317. </body>
    318. 

  318. </html>
    319. 

  319.