Home Explore Help
Register Sign In
thatsmydoing
/
blog
1
0
Fork 0
Files Issues 0 Pull Requests 0 Wiki
Tree: e0dde4226a
Branches Tags
blog
/
output
/
page
/
2.html

2.html 34 KB
History Raw

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413 
  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/openpreppad.html" class="u-url">OpenPrepPad</a>
    40. 

  40. 			</h1>
    41. 

  41. 		</header>
    42. 

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

  43. 			<p>Smart electronics and IoT (Internet of Things) are all the rage these days. You
    44. 

  44. have a lot of companies sprout up trying to make the next big thing, which also
    45. 

  45. leads to a lot of failures big and small. Pebble, the maker of my smartwatch,
    46. 

  46. got bought out by Fitbit recently. This left watch owners without any official
    47. 

  47. support, but thankfully, community members <a href="http://rebble.io/">stepped up</a> to continue
    48. 

  48. maintaining it.</p>
    49. 

  49. <p>Another casualty of the IoT boom was the <a href="http://theorangechef.com/">Orange Chef</a> <a href="https://www.amazon.com/Orange-Chef-Smart-Scale-Silver/dp/B00KFW8L90">Prep Pad</a>. It&rsquo;s a
    50. 

  50. bluetooth connected weighing scale to make it easy to track your calories and
    51. 

  51. carb/fat/protein intake. My dad bought it last year only to find out that the
    52. 

  52. app was incredibly buggy. The search function doesn&rsquo;t work which makes the whole
    53. 

  53. thing practically useless. I also found out later that you can&rsquo;t even download
    54. 

  54. the app to use the scale anymore.</p>
    55. 

  55. <p><strong>Note</strong> I just found out as I was writing this post that it <em>may</em> get supported
    56. 

  56. by <a href="http://www.prnewswire.com/news-releases/perfect-company-acquires-orange-chefs-prep-pad-related-ip-continues-momentum-in-the-connected-kitchen-300383178.html">another company</a>.</p>
    57. 

  57. <p>So the app is useless, but at least you can use it as a scale, right?</p>
    58. 

  58. <p><img src="/galleries/openpreppad/preppad.jpg" alt="Prep Pad"></p>
    59. 

  59. <p>Nope. The device has no display whatsoever. The only controls on it are the
    60. 

  60. on/off button and a green LED that isn&rsquo;t even that useful at telling you whether
    61. 

  61. it&rsquo;s on or not. At this point, it&rsquo;s just a giant paperweight.</p>
    62. 

  62. <h2 id="reverse-engineering">Reverse Engineering</h2>
    63. 

  63. <p>Since I essentially had nothing to lose, I tried poking at the thing to figure
    64. 

  64. out how it works. I didn&rsquo;t really have experience with bluetooth besides trying
    65. 

  65. to get my bluetooth mouse connected on Linux. The main thing I used then was
    66. 

  66. <code>bluetoothctl</code> which is essentially a CLI for managing bluetooth devices so I
    67. 

  67. started there.</p>
    68. 

  68. <p>I started up <code>bluetoothctl</code> and turned on the Prep Pad. And it showed up!</p>
    69. 

  69. <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">[bluetooth]# power on
    70. 

  70. [CHG] Controller ... Class: 0x00010c
    71. 

  71. Changing power on succeeded
    72. 

  72. [CHG] Controller ... Powered: yes
    73. 

  73. [bluetooth]# scan on
    74. 

  74. Discovery started
    75. 

  75. [CHG] Device 1C:BA:8C:21:7C:BB RSSI: -51
    76. 

  76. [CHG] Device 1C:BA:8C:21:7C:BB Name: CHSLEEV_00
    77. 

  77. [CHG] Device 1C:BA:8C:21:7C:BB Alias: CHSLEEV_00
    78. 

  78. </code></pre></div><p>I then connected to it, which was surprisingly easy.</p>
    79. 

  79. <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">[bluetooth]# connect 1C:BA:8C:21:7C:BB
    80. 

  80. Attempting to connect to 1C:BA:8C:21:7C:BB
    81. 

  81. [CHG] Device 1C:BA:8C:21:7C:BB Connected: yes
    82. 

  82. [CHG] Device 1C:BA:8C:21:7C:BB Name: CH BTScale_00
    83. 

  83. [CHG] Device 1C:BA:8C:21:7C:BB Alias: CH BTScale_00
    84. 

  84. </code></pre></div><p>Now normally, when you turn the device on, the green light flashes occasionally.
    85. 

  85. Once I connected to it, the green light stayed on permanently. Clearly, I was
    86. 

  86. making progress. A lot of services were also discovered but I had no idea what
    87. 

  87. those things were at that point.</p>
    88. 

  88. <p>After a lot of poking around, I could check the general device information. You
    89. 

  89. could get the hardware, software and firmware version. There&rsquo;s also the device
    90. 

  90. serial number which was nowhere on the actual physical device.</p>
    91. 

  91. <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">[CHSLEEV_00]# select-attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0010/char0017
    92. 

  92. [CH BTScale_00:/service0010/char0017]# attribute-info
    93. 

  93. Characteristic - Firmware Revision String
    94. 

  94. 	UUID: 00002a26-0000-1000-8000-00805f9b34fb
    95. 

  95. 	Service: /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0010
    96. 

  96. 	Value: 0x31
    97. 

  97. 	Value: 0x2e
    98. 

  98. 	Value: 0x31
    99. 

  99. 	Value: 0x33
    100. 

  100. 	Value: 0x41
    101. 

  101. 	Value: 0x00
    102. 

  102. 	Flags: read
    103. 

  103. [CH BTScale_00:/service0010/char0017]# read
    104. 

  104. Attempting to read /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0010/char0017
    105. 

  105. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0010/char0017 Value: 0x31
    106. 

  106. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0010/char0017 Value: 0x2e
    107. 

  107. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0010/char0017 Value: 0x31
    108. 

  108. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0010/char0017 Value: 0x33
    109. 

  109. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0010/char0017 Value: 0x41
    110. 

  110. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0010/char0017 Value: 0x00
    111. 

  111.   31 2e 31 33 41 00                                1.13A.
    112. 

  112. [CH BTScale_00:/service0010/char0017]#
    113. 

  113. </code></pre></div><p>There was also a service which contained Accel Enable, Accel Range, Accel
    114. 

  114. X-Coordinate, Accel Y-Coordinate, and Accel Z-Coordinate. I guess it stands for
    115. 

  115. accelerometer, which is probably what it uses to weigh things.</p>
    116. 

  116. <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">[CHSLEEV_00]# select-attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char0024/desc0026
    117. 

  117. [CH BTScale_00:/service0023/char0024/desc0026]# read
    118. 

  118. Attempting to read /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char0024/desc0026
    119. 

  119. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char0024/desc0026 Value: 0x41
    120. 

  120. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char0024/desc0026 Value: 0x63
    121. 

  121. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char0024/desc0026 Value: 0x63
    122. 

  122. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char0024/desc0026 Value: 0x65
    123. 

  123. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char0024/desc0026 Value: 0x6c
    124. 

  124. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char0024/desc0026 Value: 0x20
    125. 

  125. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char0024/desc0026 Value: 0x45
    126. 

  126. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char0024/desc0026 Value: 0x6e
    127. 

  127. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char0024/desc0026 Value: 0x61
    128. 

  128. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char0024/desc0026 Value: 0x62
    129. 

  129. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char0024/desc0026 Value: 0x6c
    130. 

  130. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char0024/desc0026 Value: 0x65
    131. 

  131.   41 63 63 65 6c 20 45 6e 61 62 6c 65              Accel Enable
    132. 

  132. </code></pre></div><p>I couldn&rsquo;t read from any of the Accel Coordinates. It kept saying permission
    133. 

  133. denied. I could however, notify on them. But that didn&rsquo;t yield anything as well.
    134. 

  134. What I <em>could</em> read was Accel Enable, which was set to 00. I guess that means it
    135. 

  135. was off. After writing 01 to Accel Enable, I found I could get values out of
    136. 

  136. Accel X-Coordinate! Also, the green LED which was permanently on turned off.</p>
    137. 

  137. <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">[CHSLEEV_00]# select-attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char0024
    138. 

  138. [CH BTScale_00:/service0023/char0024]# write 01
    139. 

  139. Attempting to write /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char0024
    140. 

  140. [CH BTScale_00:/service0023/char0024]# select-attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char002a
    141. 

  141. [CH BTScale_00:/service0023/char002a]# notify on
    142. 

  142. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char002a Notifying: yes
    143. 

  143. Notify started
    144. 

  144. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char002a Value: 0x5b
    145. 

  145. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char002a Value: 0xa3
    146. 

  146. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char002a Value: 0x02
    147. 

  147. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char002a Value: 0x00
    148. 

  148. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char002a Value: 0x55
    149. 

  149. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char002a Value: 0xa3
    150. 

  150. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char002a Value: 0x02
    151. 

  151. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char002a Value: 0x00
    152. 

  152. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char002a Value: 0x59
    153. 

  153. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char002a Value: 0xa3
    154. 

  154. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char002a Value: 0x02
    155. 

  155. [CHG] Attribute /org/bluez/hci0/dev_1C_BA_8C_21_7C_BB/service0023/char002a Value: 0x00
    156. 

  156. </code></pre></div><p>I tried pressing the scale down a few times, and the values changed accordingly.
    157. 

  157. Now, I just had to figure out how to convert the values into grams. It looked
    158. 

  158. like the values were 32-bit integers sent as 4 bytes. In the above example it
    159. 

  159. would be <code>0x0002a35b</code>, <code>0x0002a355</code>, <code>0x0002a359</code> or 172891, 172855, 172899. The
    160. 

  160. values also decrease as you exert more effort on the scale. So assuming you take
    161. 

  161. the initial value as <em>tare</em>, you simply subtract any succeeding value from that
    162. 

  162. <em>tare</em> and you get the &ldquo;weight&rdquo;.</p>
    163. 

  163. <p>The values I got didn&rsquo;t seem to be in grams though. After weighing some things
    164. 

  164. on an actual scale and comparing the values I got, I found I can just divide the
    165. 

  165. values by 14 and get something in grams. That 14 is entirely a magic number
    166. 

  166. though and I have no idea whether other Prep Pad&rsquo;s would have the same constant.</p>
    167. 

  167. <h2 id="openpreppad">OpenPrepPad</h2>
    168. 

  168. <p>With all that figured out, I went ahead and made a <a href="https://github.com/thatsmydoing/openpreppad">simple CLI application</a>
    169. 

  169. to interface with the Prep Pad. Ironically, node was the simplest thing I found
    170. 

  170. that had <a href="https://github.com/sandeepmistry/noble">nice bluetooth library support</a> so that&rsquo;s what I wrote it in. I
    171. 

  171. also added most of the technical details in the README for that as well.</p>
    172. 

  172. <p>While this is all well and cool, I doubt the intersection of Linux users and
    173. 

  173. people who <!-- raw HTML omitted -->got ripped off<!-- raw HTML omitted --> bought the Prep Pad is anyone besides me. In
    174. 

  174. light of that, I&rsquo;m in the process of making a React Native version of the app,
    175. 

  175. but that&rsquo;s still a work in progress. Who knows, if the new owners of Prep Pad
    176. 

  176. are good, I might not even need to finish it.</p>
    177. 

  177. 

  178. 		</div>
    179. 

  179. 		<small class="dateline">Posted: <time class="published dt-published" itemprop="datePublished" datetime="2017-01-15">2017-01-15</time></small>
    180. 

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

  181. 	</article>
    182. 

  182. 	</article>
    183. 

  183. 	
    184. 

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

  185. 		<header>
    186. 

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

  187. 				<a href="/posts/haproxy-charset.html" class="u-url">Haproxy Charset</a>
    188. 

  188. 			</h1>
    189. 

  189. 		</header>
    190. 

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

  191. 			<p>A common problem we encounter is for things like <em>ñ</em> not showing up correctly. This actually caused <a href="http://www.rappler.com/nation/politics/elections/2016/132894-human-error-hash-election-results-code-mismatch">some issues</a> in the recent Philippine elections, but this isn&rsquo;t about hash codes or anything like that.</p>
    192. 

  192. <p>By default, we use UTF-8 for text storage and rendering. A problem is that browsers don&rsquo;t assume UTF-8 as the default and you need to have either a <code>&lt;meta charset=&quot;utf-8&quot; /&gt;</code> in the HTML or <code>Content-Type: text/html; charset=utf-8</code> in the headers. A few of our services don&rsquo;t set the <code>Content-Type</code> with the <code>charset=utf-8</code> part so you&rsquo;d get piñata instead of piñata.</p>
    193. 

  193. <p>Being lazy, we usually just correct this at the reverse proxy side. It&rsquo;s trivial to do in nginx. You just need to add <code>charset utf-8;</code> to your configuration and you&rsquo;re good. For haproxy though, I couldn&rsquo;t readily find a solution for it and had to go through the docs to see what I could do.</p>
    194. 

  194. <p>After a bit of experimenting, I had success with this:</p>
    195. 

  195. <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"># set content-type to utf-8 if not already
    196. 

  196. acl has_charset hdr_sub(content-type) -i charset=
    197. 

  197. rspirep (Content-Type.*) \1;\ charset=utf-8 unless has_charset
    198. 

  198. </code></pre></div><p>This is probably not the best way to do it. Arguably, we should just fix our services to have the correct <code>Content-Type</code> in the first place, but I can do that some other time.</p>
    199. 

  199. 

  200. 		</div>
    201. 

  201. 		<small class="dateline">Posted: <time class="published dt-published" itemprop="datePublished" datetime="2016-06-24">2016-06-24</time></small>
    202. 

  202. 		| <small class="commentline"><a href="/posts/haproxy-charset.html#isso-thread">Comments</a></small>
    203. 

  203. 	</article>
    204. 

  204. 	</article>
    205. 

  205. 	
    206. 

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

  207. 		<header>
    208. 

  208. 			<h1 class="p-name entry-title" itemprop="headline">
    209. 

  209. 				<a href="/posts/cloudflare-shenanigans.html" class="u-url">Cloudflare Shenanigans</a>
    210. 

  210. 			</h1>
    211. 

  211. 		</header>
    212. 

  212. 		<div class="e-content entry-content">
    213. 

  213. 			<p>An old client of ours managed to convince a telco to zero-rate the data for their app. In order to whitelist it though, we needed to use plain HTTP for domain whitelisting. For HTTPS, they can only whitelist by IP address. Like any good developer, we were using HTTPS. Also, like any good developer, we put our server behind Cloudflare.</p>
    214. 

  214. <p>Now the problem is that Cloudflare can put you behind <a href="https://www.cloudflare.com/ips/">any IP they own</a>, which is a huge range. There&rsquo;s no guarantee that the IP we have now is going to be the same later on. So we did the reasonable thing and asked them to whitelist all of the Cloudflare IPs. And the telco agreed! We were in total disbelief when that happened. But hey, if life gives you free internet, you take it.</p>
    215. 

  215. <p>We never actually empirically tested whether other sites hosted on Cloudflare were also actually zero-rated. But I like to think that we saved a lot of people on their data costs from browsing Reddit and 4chan. But alas, good things must come to an end.</p>
    216. 

  216. <p>A few months after we started beta testing the app, Cloudflare added more IPs to their range. Unfortunately, our server got moved to those new IPs which were not whitelisted yet. Apparently, the telco whitelisting process was incredibly convoluted and time consuming. Our client didn&rsquo;t want to bother asking them to whitelist more IPs. We also tried asking Cloudflare to move us back to the original IP range, but they could only do that if we were in their enterprise tier. We couldn&rsquo;t really afford that, so we looked for other options.</p>
    217. 

  217. <p>Since Cloudflare was essentially just a giant reverse proxy, theoretically there should be no distinction between one IP address from another. The specific IP we get is probably just for load balancing. So we tried accessing the IPs in the range directly and just setting the Host header and it worked! But we get SSL errors because the IP itself doesn&rsquo;t have its own certificate.</p>
    218. 

  218. <p>After more testing, we figured out that you could actually use any Cloudflare backed domain so long as we properly set the Host header. We just needed to find one still in the old range. Coincidentally, 4chan.org was. Which led to this wonderful commit</p>
    219. 

  219. <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-diff" data-lang="diff">commit 123456789abcdef
    220. 

  220. Author: ~~~~~~
    221. 

  221. Date:   ~~~~~~
    222. 

  222. 

  223.     4chan hack
    224. 

  224. 

  225. <span style="font-weight:bold">diff --git a/src/com/client/common/Util.java b/src/com/client/common/Util.java
    226. 

  226. </span><span style="font-weight:bold"></span>--- a/src/com/client/common/Util.java
    227. 

  227. +++ b/src/com/client/common/Util.java
    228. 

  228. <span style="font-weight:bold">@@ -210,7 +210,8 @@ public class Util {
    229. 

  229. </span><span style="font-weight:bold"></span>        }
    230. 

  230. 

  231.         public static String getServerAddress(Context context) {
    232. 

  232. -               String address = &#34;https://backend.client.com&#34;;
    233. 

  233. +               // String address = &#34;https://backend.client.com&#34;;
    234. 

  234. +               String address = &#34;https://4chan.org&#34;;
    235. 

  235.                 if(!isDebug(context)) return address;
    236. 

  236.                 try {
    237. 

  237. <span style="font-weight:bold">diff --git a/src/com/client/common/logging/APIClient.java b/src/com/client/common/logging/APIClient.java
    238. 

  238. </span><span style="font-weight:bold"></span>--- a/src/com/client/common/logging/APIClient.java
    239. 

  239. +++ b/src/com/client/common/logging/APIClient.java
    240. 

  240. <span style="font-weight:bold">@@ -101,6 +101,7 @@ public class APIClient {
    241. 

  241. </span><span style="font-weight:bold"></span>        private HttpResponse postInternal(String url, List&lt;NameValuePair&gt; data, boolean forRegistration) throws ClientProtocolException, IOException {
    242. 

  242.                 HttpPost request = new HttpPost(Util.getServerAddress(mContext)+&#34;/api/&#34;+url);
    243. 

  243.                 request.setHeader(&#34;X-API-VERSION&#34;, apiVersion);
    244. 

  244. +               request.setHeader(&#34;Host&#34;, &#34;backend.client.com&#34;);
    245. 

  245. 

  246.                 if(data == null) {
    247. 

  247.                         data = new ArrayList&lt;NameValuePair&gt;();
    248. 

  248. </code></pre></div><p>Eventually, we did decide to just abandon Cloudflare for the server. We probably weren&rsquo;t going to be the target of a DDOS or anything. This also allowed us to do more secure things like pinning the server certificate in the application itself. Clearly, this is what we should have just done in the first place, but at the time we just wanted a stopgap solution.</p>
    249. 

  249. <p>I just still find it funny we were making people&rsquo;s phones go to 4chan.org everyday for more than a year.</p>
    250. 

  250. 

  251. 		</div>
    252. 

  252. 		<small class="dateline">Posted: <time class="published dt-published" itemprop="datePublished" datetime="2015-12-25">2015-12-25</time></small>
    253. 

  253. 		| <small class="commentline"><a href="/posts/cloudflare-shenanigans.html#isso-thread">Comments</a></small>
    254. 

  254. 	</article>
    255. 

  255. 	</article>
    256. 

  256. 	
    257. 

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

  258. 		<header>
    259. 

  259. 			<h1 class="p-name entry-title" itemprop="headline">
    260. 

  260. 				<a href="/posts/tiddlywiki-in-the-sky-or-tiddlyweb-for-tw5.html" class="u-url">TiddlyWiki in the Sky (or TiddlyWeb for TW5)</a>
    261. 

  261. 			</h1>
    262. 

  262. 		</header>
    263. 

  263. 		<div class="e-content entry-content">
    264. 

  264. 			<p>I&rsquo;ve always liked <a href="http://tiddlywiki.com">TiddlyWiki</a>. Back when it first came out, it was really amazing. A wiki all in one file, that worked in the browser. It didn&rsquo;t need a backend, it would just save itself as an all new HTML file with all your posts inside. I&rsquo;ve used it a lot over the years, as a personal wiki/journal and a class notebook. I even had a blog with it at one point using one of the server-side forks.</p>
    265. 

  265. <p>Now, there&rsquo;s TiddlyWiki5 which is a rewrite of the original TiddlyWiki that looks a whole lot snazzier, and I assume has better architecture overall. It also has experimental support for all the server-side platforms (particularly TiddlyWeb) that have cropped up.</p>
    266. 

  266. <p>If you&rsquo;re just looking for a simple server setup for TiddlyWiki5, it has native support for that on its own. There&rsquo;s plenty of documentation on the site. But if you&rsquo;re looking for more advanced features (like storing your posts in git or a database), then you&rsquo;ll need to use it with TiddlyWeb. The problem is that most of the documentation for TiddlyWeb still refers to the old TiddlyWiki.</p>
    267. 

  267. <p>To support TiddlyWiki5, we&rsquo;ll need a version of the wiki which has the TiddlyWeb plugin already installed and configured. After that, some tweaking is necessary to get TiddlyWeb to provide what the wiki requires.</p>
    268. 

  268. <h2 id="setting-up-tiddlywiki">Setting Up TiddlyWiki</h2>
    269. 

  269. <p>TiddlyWiki5 provides a command line tool via <code>npm</code> that allows building custom versions of the wiki. In fact, it comes with templates, called &ldquo;editions&rdquo;, that we can use for our setup. Assuming you already have it installed, create the wiki using</p>
    270. 

  270. <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-sh" data-lang="sh">tiddlywiki mywiki --init tw5tank          <span style="color:#007f7f"># create wiki from template</span>
    271. 

  271. </code></pre></div><p>This creates a wiki intended for use with <a href="https://tank.peermore.com/">Tank</a>, which is built on top of TiddlyWeb. From here, you should look in <code>mywiki/tiddlers/system</code> which contain the entries for <code>SiteTitle</code>, <code>SiteSubtitle</code>, <code>DefaultTiddlers</code>, and <code>tiddlyweb-host</code>. The first 3 should be configured however you want. These are necessary because they&rsquo;re needed before the wiki can load them from the server. <code>tiddlyweb-host</code> contains the location of the TiddlyWeb server, this should be <code>http://localhost:8080/</code> if you&rsquo;re just testing locally. With everything configured, you can build the new wiki by running</p>
    272. 

  272. <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-sh" data-lang="sh">tiddlywiki mywiki --build
    273. 

  273. </code></pre></div><p>This will output the wiki to <code>mywiki/output/tw5tank.html</code>. You can now serve it using your favorite local webserver, like <code>python -m http.server</code>.</p>
    274. 

  274. <h2 id="setting-up-tiddlyweb">Setting Up TiddlyWeb</h2>
    275. 

  275. <p>The TiddlyWeb tutorial recommends using <code>tiddlywebwiki</code> which has all the plugins setup for a nice wiki instance for the old TiddlyWiki. It has a lot of features that aren&rsquo;t really needed, so we won&rsquo;t go with that. So first, we&rsquo;ll need to install TiddlyWeb and any plugins we might want to use.</p>
    276. 

  276. <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-sh" data-lang="sh">pip install tiddlyweb tiddlywebplugins.status tiddlywebplugins.cherrypy tiddlywebplugins.cors
    277. 

  277. </code></pre></div><p>Next, we&rsquo;ll need the tiddlyweb configuration in <code>tiddlywebconfig.py</code></p>
    278. 

  278. <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-python" data-lang="python"><span style="color:#007f7f"># A basic configuration.</span>
    279. 

  279. <span style="color:#007f7f"># `pydoc tiddlyweb.config` for details on configuration items.</span>
    280. 

  280. 

  281. <span style="color:#fff;font-weight:bold">import</span> tiddlywebplugins.status
    282. 

  282. 

  283. config = {
    284. 

  284.     <span style="color:#0ff;font-weight:bold">&#39;system_plugins&#39;</span>: [<span style="color:#0ff;font-weight:bold">&#39;tiddlywebplugins.status&#39;</span>, <span style="color:#0ff;font-weight:bold">&#39;tiddlywebplugins.cors&#39;</span>],
    285. 

  285.     <span style="color:#0ff;font-weight:bold">&#39;secret&#39;</span>: <span style="color:#0ff;font-weight:bold">&#39;36c98d6d14618c79f0ed2d49cd1b9e272d8d4bd0&#39;</span>,
    286. 

  286.     <span style="color:#0ff;font-weight:bold">&#39;wsgi_server&#39;</span>: <span style="color:#0ff;font-weight:bold">&#39;tiddlywebplugins.cherrypy&#39;</span>,
    287. 

  287.     <span style="color:#0ff;font-weight:bold">&#39;cors.enable_non_simple&#39;</span>: <span style="color:#fff;font-weight:bold">True</span>
    288. 

  288. }
    289. 

  289. 

  290. original_gather_data = tiddlywebplugins.status._gather_data
    291. 

  291. 

  292. <span style="color:#fff;font-weight:bold">def</span> _status_gather_data(environ):
    293. 

  293.     data = original_gather_data(environ)
    294. 

  294.     data[<span style="color:#0ff;font-weight:bold">&#39;space&#39;</span>] = {<span style="color:#0ff;font-weight:bold">&#39;recipe&#39;</span>: <span style="color:#0ff;font-weight:bold">&#39;default&#39;</span>}
    295. 

  295.     <span style="color:#fff;font-weight:bold">return</span> data
    296. 

  296. 

  297. tiddlywebplugins.status._gather_data = _status_gather_data
    298. 

  298. </code></pre></div><p>The tweaks involved are:</p>
    299. 

  299. <ul>
    300. 

  300. <li>using the status plugin which the wiki requires</li>
    301. 

  301. <li>monkeypatching the status plugin for the wiki to use the correct &ldquo;recipe&rdquo;</li>
    302. 

  302. <li>using cherrypy server instead of the buggy default one</li>
    303. 

  303. <li>using cors since we&rsquo;re not hosting the wiki itself on the same server</li>
    304. 

  304. </ul>
    305. 

  305. <p>With that, we just need to create the store that will hold our data</p>
    306. 

  306. <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-sh" data-lang="sh">twanager recipe default <span style="color:#0ff;font-weight:bold">&lt;&lt;EOF
    307. 

  307. </span><span style="color:#0ff;font-weight:bold">desc: standard TiddlyWebWiki environment
    308. 

  308. </span><span style="color:#0ff;font-weight:bold">policy: {&#34;read&#34;: [], &#34;create&#34;: [], &#34;manage&#34;: [&#34;R:ADMIN&#34;], &#34;accept&#34;: [], &#34;write&#34;: [&#34;R:ADMIN&#34;], &#34;owner&#34;: &#34;administrator&#34;, &#34;delete&#34;: [&#34;R:ADMIN&#34;]}
    309. 

  309. </span><span style="color:#0ff;font-weight:bold">
    310. 

  310. </span><span style="color:#0ff;font-weight:bold">/bags/default/tiddlers
    311. 

  311. </span><span style="color:#0ff;font-weight:bold">EOF</span>
    312. 

  312. 

  313. twanager bag default <span style="color:#0ff;font-weight:bold">&lt;&lt;EOF
    314. 

  314. </span><span style="color:#0ff;font-weight:bold">{&#34;policy&#34;: {&#34;read&#34;: [], &#34;create&#34;: [], &#34;manage&#34;: [&#34;R:ADMIN&#34;], &#34;accept&#34;: [], &#34;write&#34;: [], &#34;owner&#34;: &#34;administrator&#34;, &#34;delete&#34;: []}}
    315. 

  315. </span><span style="color:#0ff;font-weight:bold">EOF</span>
    316. 

  316. </code></pre></div><p>Finally, we can start the TiddlyWeb server</p>
    317. 

  317. <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-sh" data-lang="sh">twanager server
    318. 

  318. </code></pre></div><h2 id="putting-it-all-together">Putting it all together</h2>
    319. 

  319. <p>Once you have the TiddlyWeb server running, you can just go to wherever you&rsquo;re hosting the wiki html and it should work. You can try creating some posts, and the check mark on the sidebar should be red for a while and then turn black. Once that&rsquo;s done it&rsquo;s saved. You can refresh your browser and your posts should still be there.</p>
    320. 

  320. <p>At this point, you can start customizing your TiddlyWeb instance, by changing your store to something like a database, or adding authorization. You can also tweak the server setup so you won&rsquo;t need CORS anymore.</p>
    321. 

  321. <p>TiddlyWiki5 is still relatively new. I hope that eventually, support for server-side and the plugin ecosystem grows to be as great as the old TiddlyWiki.</p>
    322. 

  322. 

  323. 		</div>
    324. 

  324. 		<small class="dateline">Posted: <time class="published dt-published" itemprop="datePublished" datetime="2015-12-24">2015-12-24</time></small>
    325. 

  325. 		| <small class="commentline"><a href="/posts/tiddlywiki-in-the-sky-or-tiddlyweb-for-tw5.html#isso-thread">Comments</a></small>
    326. 

  326. 	</article>
    327. 

  327. 	</article>
    328. 

  328. 	
    329. 

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

  330. 		<header>
    331. 

  331. 			<h1 class="p-name entry-title" itemprop="headline">
    332. 

  332. 				<a href="/posts/is-my-terminal-window-active.html" class="u-url">Is My Terminal Window Active?</a>
    333. 

  333. 			</h1>
    334. 

  334. 		</header>
    335. 

  335. 		<div class="e-content entry-content">
    336. 

  336. 			<p>I&rsquo;ve been working in OSX for almost 3 years now, but I recently switched back to Linux because of all the problems people encountered with Yosemite. There are some things I missed from OSX though. One of which is <a href="https://github.com/marzocchi/zsh-notify">zsh-notify</a>. It&rsquo;s a zsh plugin that alerts you if your long-running task is complete, and whether it failed or not.</p>
    337. 

  337. <p>It&rsquo;s pretty convenient when you&rsquo;re compiling something and then go on to browse reddit while waiting. Usually, I spend too much time just reading and forget about the compilation entirely. With the plugin, I get the notification and maybe go back to work.</p>
    338. 

  338. <p>One nice feature it has is that if you&rsquo;re currently looking at the terminal window of the job that just finished, it won&rsquo;t notify you. It only notifies on windows that aren&rsquo;t currently in focus. To do this, it has to actually talk to Terminal.app or iTerm2 to see if the window and tab are active.</p>
    339. 

  339. <p>This is alright in OSX since those 2 are the generally most used terminal emulators. On Linux though, everyone has their own favorite terminal. Given that, I figured I could probably rely on talking to X to see if the window is active instead of each single terminal emulator. X can&rsquo;t tell if the tab is active though, but I don&rsquo;t use tabs in my current setup so it should still be good.</p>
    340. 

  340. <h2 id="xdotool">xdotool</h2>
    341. 

  341. <p><a href="http://superuser.com/questions/382616/detecting-currently-active-window">Preliminary research</a> reveals that we can easily get what the active window is with xdotool. <code>xdotool getactivewindow</code> gives us the X window id of the active one. Now all we need is a way to get the window id of the terminal we&rsquo;re in.</p>
    342. 

  342. <h2 id="first-attempt-windowid">First Attempt: $WINDOWID</h2>
    343. 

  343. <p>Apparently, xterm and similar terminal emulators define an environment variable called <code>$WINDOWID</code> with the window id of the terminal. Obviously, this is too good to be true. In xterm and konsole the <code>$WINDOWID</code> was correct, but in VTE-based terminal emulators, <code>$WINDOWID</code> had the wrong value. In terminology, it didn&rsquo;t define <code>$WINDOWID</code> altogether. So <code>$WINDOWID</code> wasn&rsquo;t going to work.</p>
    344. 

  344. <h2 id="second-attempt-xdotool-search-magic">Second Attempt: xdotool search $MAGIC</h2>
    345. 

  345. <p>My second idea was that you can use zsh to change the window title to a magic number and then just check if the active window is the same one as the window with the magic number. This sort of worked for most terminals, except konsole which does whatever it wants with the window title. There&rsquo;s also the problem of some zsh configs automatically settings the window title to the current command.</p>
    346. 

  346. <p>In hindsight, I could probably have just done <code>xdotool search --name xdotool</code> since in most cases, when you run the search, zsh or konsole will set the window name to the current command. Maybe that&rsquo;s another option I can explore some day.</p>
    347. 

  347. <h2 id="third-attempt-ppid">Third Attempt: $PPID</h2>
    348. 

  348. <p>My third idea was another environment variable called <code>$PPID</code>, which is the process id of the parent of the shell. As it happens, the parent is the window containing the zsh instance. This is actually pretty consistent across most terminals. The only problem was if you launched zsh from another shell since your new zsh&rsquo;s parent will now be another zsh instance instead of an X window.</p>
    349. 

  349. <p>At first glance, launching zsh within zsh doesn&rsquo;t seem like something most people would do, but this is what happens when you run screen or tmux. To work around this, we can actually just save the original <code>$PPID</code> in a different variable and use that instead.</p>
    350. 

  350. <p>Now that we have the PID of the window from zsh, we can once again use xdotool to get the PID of the current active window with <code>xdotool getactivewindow getwindowpid</code>. We just simply compare that with our <code>$PPID</code> and we can tell if we&rsquo;re in an active window or not. Overall, this approach worked surprisingly well so that&rsquo;s the final solution I went with.</p>
    351. 

  351. 

  352. 		</div>
    353. 

  353. 		<small class="dateline">Posted: <time class="published dt-published" itemprop="datePublished" datetime="2015-06-07">2015-06-07</time></small>
    354. 

  354. 		| <small class="commentline"><a href="/posts/is-my-terminal-window-active.html#isso-thread">Comments</a></small>
    355. 

  355. 	</article>
    356. 

  356. 	</article>
    357. 

  357. 	
    358. 

  358. </div>
    359. 

  359. <nav class="postindexpager">
    360. 

  360. 	<ul class="pager clearfix">
    361. 

  361. 		
    362. 

  362. 		<li class="previous">
    363. 

  363. 			<a href="/">&larr; Newer posts</a>
    364. 

  364. 		</li>
    365. 

  365. 		
    366. 

  366. 		
    367. 

  367. 		<li class="next">
    368. 

  368. 			<a href="/page/3.html">Older posts &rarr;</a>
    369. 

  369. 		</li>
    370. 

  370. 		
    371. 

  371. 	</ul>
    372. 

  372. </nav>
    373. 

  373. 

  374. </main>
    375. 

  375. 

  376. 

  377. 	<footer id="footer" role="contentinfo">
    378. 

  378. 		<p>
    379. 

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

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

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

  382. 	</footer>
    383. 

  383. </div>
    384. 

  384. 

  385. <script src="/assets/js/konami.js"></script>
    386. 

  386. <script>
    387. 

  387. var easter_egg = new Konami();
    388. 

  388. easter_egg.code = function() {
    389. 

  389. 	var el = document.getElementById('thomas');
    390. 

  390. 	if(el.className == "whoa") {
    391. 

  391. 		el.className = "";
    392. 

  392. 	}
    393. 

  393. 	else {
    394. 

  394. 		el.className = "whoa";
    395. 

  395. 	}
    396. 

  396. 	document.body.scrollTop = document.documentElement.scrollTop = 0;
    397. 

  397. }
    398. 

  398. easter_egg.load();
    399. 

  399. 

  400. 

  401. 

  402. </script>
    403. 

  403. 

  404. 

  405. <script
    406. 

  406. 	data-isso="https://isso.pleasantprogrammer.com/"
    407. 

  407. 	src="https://isso.pleasantprogrammer.com/js/count.min.js">
    408. 

  408. </script>
    409. 

  409. 

  410. 

  411. </body>
    412. 

  412. </html>
    413. 

  413.