<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Myth of Sisyphus</title>
  
  
  <link href="https://blog.zzhou612.com/atom.xml" rel="self"/>
  
  <link href="https://blog.zzhou612.com/"/>
  <updated>2024-09-19T08:48:57.000Z</updated>
  <id>https://blog.zzhou612.com/</id>
  
  <author>
    <name>Z.Zhou</name>
    
  </author>
  
  <generator uri="https://hexo.io/">Hexo</generator>
  
  <entry>
    <title>毕业旅行：宇治</title>
    <link href="https://blog.zzhou612.com/2024/09/19/graduation-trip-uji/"/>
    <id>https://blog.zzhou612.com/2024/09/19/graduation-trip-uji/</id>
    <published>2024-09-19T08:48:57.000Z</published>
    <updated>2024-09-19T08:48:57.000Z</updated>
    
    <content type="html"><![CDATA[<p>《吹响吧！上低音号》圣地巡礼。</p><span id="more"></span><h1 id="前言"><a href="#前言" class="headerlink" title="前言"></a>前言</h1><p>在京都周末的某一天前往宇治进行不怎么专业的《吹响吧！上低音号》圣地巡礼，因为白天实在太热了，没有去从黄檗站下来还要走很远才能到的京都府立菟道高校（北宇治高校的原型&#x2F;取景地），外加当天京阪线出了事故停运了，所以也没有坐久美子她们上下学乘坐的京阪列车（而且京吹联动痛车也并不在宇治线），希望下次可以在一个凉爽的季节重返宇治，多做功课多拍照片，弥补上这些遗憾。</p><p>宇治市本身也是个有着悠久历史和文化的地方，《源氏物语》最后十回就是以宇治为舞台展开，京都动画2024年也做了《有故事的宇治》作为宇治市的宣传短片。</p><iframe width="560" height="315" src="https://www.youtube.com/embed/O7SWkkOGKEQ?si=S0Yf37bQ158ZPhOu" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe><iframe width="560" height="315" src="//player.bilibili.com/player.html?isOutside=true&aid=1101859467&bvid=BV13w4m1R7fQ&cid=1474166047&p=1&autoplay=0" scrolling="no" border="0" frameborder="no" framespacing="0" allowfullscreen="true"></iframe><h1 id="京都动画本社"><a href="#京都动画本社" class="headerlink" title="京都动画本社"></a>京都动画本社</h1><p>当天京阪列车停运了，所以改乘坐了JR线（从酒店出发其实JR更快），JR木幡站下车就是京都动画本社。</p><img src="/2024/09/19/graduation-trip-uji/kowata.jpg" class=""><p>JR木幡站这边除了京都动画本社，还有京都动画第五工作室（就在车站路口边上），也是曾经的京阿尼商店所在地（可惜现在永久关门了）。再往前走两步，在京阪电车的木幡站边上则是第二工作室。京都动画第一工作室的遗址在六地藏站附近，2019年的纵火案现在想来依旧令人无语凝噎。</p><img src="/2024/09/19/graduation-trip-uji/kyoto-animation-1.jpg" class=""><img src="/2024/09/19/graduation-trip-uji/kyoto-animation-2.jpg" class=""><p>只拍了几张本社的照片，还能看到京吹第三季的角色宣传海报，右边的『はぐれ星のうた』是京阿尼音乐工坊的首部作品，似乎是音乐绘本。</p><img src="/2024/09/19/graduation-trip-uji/kyoto-animation-3.jpg" class=""><h1 id="宇治桥-三之间"><a href="#宇治桥-三之间" class="headerlink" title="宇治桥 三之间"></a>宇治桥 三之间</h1><p>从JR宇治站下来，第一个目的地就是京吹圣地，宇治桥！也被称为苦呀西桥，贯穿《吹响吧！上低音号》全系列始终的命运之桥。</p><img src="/2024/09/19/graduation-trip-uji/uji-bridge.jpg" class=""><p>我想起那天在宇治桥上的奔跑，那是我逝去的青春。</p><img src="/2024/09/19/graduation-trip-uji/hibike-euphonium-ep12-16.25.jpg" class=""><img src="/2024/09/19/graduation-trip-uji/hibike-euphonium-ep12-16.27.jpg" class=""><p>夕阳下的宇治桥。太阳落山前走在桥上的时候都能听到零星的中国游客嘴里蹦出“苦呀西桥”这几个字，毕竟是冲着大吉山方向走的。</p><img src="/2024/09/19/graduation-trip-uji/uji-bridge-sunset.jpg" class=""><p>宇治桥上游一侧凸出来的“三之间”是过去祭祀守护神“桥姬”的遗迹。</p><img src="/2024/09/19/graduation-trip-uji/san-no-ma.jpg" class=""><p>当然对我们吹吹人来说这里也是不交部费的秀一同志好不容易在剧场版《誓言的终章》中登场的地方。</p><img src="/2024/09/19/graduation-trip-uji/hibike-euphonium-chikai-no-finale-00.07.53.jpg" class=""><p>下游一侧能看到JR铁路桥。</p><img src="/2024/09/19/graduation-trip-uji/jr-train.jpg" class=""><p>想要吹得更好！</p><img src="/2024/09/19/graduation-trip-uji/hibike-euphonium-ep12-17.41.jpg" class=""><p>照片放大之后发现河中浅滩上的某种鸟也和动画里出现的长得一模一样（只有24-70，无力打鸟，只能疯狂放大全损画质了）。</p><img src="/2024/09/19/graduation-trip-uji/uji-bridge-bird.jpg" class=""><img src="/2024/09/19/graduation-trip-uji/hibike-euphonium-chikai-no-finale-00.07.35.jpg" class=""><p>宇治桥西侧的路口。</p><img src="/2024/09/19/graduation-trip-uji/uji-bridge-west.jpg" class=""><p>纪念紫式部的雕像。</p><img src="/2024/09/19/graduation-trip-uji/murasaki-shikibu.jpg" class=""><h1 id="萨莉亚宇治里尻店-黄前相谈所"><a href="#萨莉亚宇治里尻店-黄前相谈所" class="headerlink" title="萨莉亚宇治里尻店 黄前相谈所"></a>萨莉亚宇治里尻店 黄前相谈所</h1><p>宇治桥西侧的萨莉亚，是动画第一季中葵退部后和晴香谈心的地方，后来久石奏登场之后就变成了黄前相谈所。</p><img src="/2024/09/19/graduation-trip-uji/uji-saizeriya.jpg" class=""><p>下午为了躲避酷暑，在萨莉亚点了个畅饮和肉酱多利亚饭，因为还要吃晚饭就没有点完整的久石奏套餐。久美子和小奏的固定位置去的时候已经被占了，走的时候用手机拍了一张。</p><img src="/2024/09/19/graduation-trip-uji/hibike-euphonium-chikai-no-finale-00.56.59.jpg" class=""><p>下次我要坐这里！</p><img src="/2024/09/19/graduation-trip-uji/uji-saizeriya-table.jpg" class=""><p>从萨莉亚出来还偶遇了久石奏痛车。</p><img src="/2024/09/19/graduation-trip-uji/kanade-1.jpg" class=""><img src="/2024/09/19/graduation-trip-uji/kanade-2.jpg" class=""><p>顺便一提在宇治转悠的时候还看到了少林拳法道场<del>少林功夫好耶</del>。</p><img src="/2024/09/19/graduation-trip-uji/uji-shaolin.jpg" class=""><p>不知道小奏的猫猫拳是不是在这里学的。</p><img src="/2024/09/19/graduation-trip-uji/kanade-punch.gif" class=""><h1 id="京阪宇治站-志を繋ぐ碑"><a href="#京阪宇治站-志を繋ぐ碑" class="headerlink" title="京阪宇治站 志を繋ぐ碑"></a>京阪宇治站 志を繋ぐ碑</h1><p>位于宇治桥东侧的京阪电车的宇治站也在京吹系列中反复出现，我功课没做到位，就随便拍了几张联动的海报&#x2F;立牌。</p><img src="/2024/09/19/graduation-trip-uji/uji-station-1.jpg" class=""><img src="/2024/09/19/graduation-trip-uji/uji-station-2.jpg" class=""><p>宇治站旁边的“茶和宇治的历史公园”有一个2024年7月14日新落成的纪念碑，“志を繋ぐ碑”。</p><img src="/2024/09/19/graduation-trip-uji/kyo-ani-memorial-1.jpg" class=""><p>2019年7月18日京都动画第一工作室遭遇纵火恐怖袭击，36人遇难。五年前听到京都动画遭受火灾的消息时，我还以为只是小事故，后来随着新闻中出现遇难者，名单里又出现了木上益治、武本康弘、西屋太志、池田晶子这些耳熟能详的名字，我才意识到事情的严重性。我是在《凉宫春日的忧郁》以及《Clannad》的时代入宅并开始看京都动画的作品，京阿尼的动画基本都看过，然而这些带给我无数快乐与感动的作品的创作者们就这样葬身于火海之中，令人感到愤怒与心痛之余也有些恍惚。在这个世界上很多悲剧并没有任何道理可言，即使是对于这些在工作室兢兢业业工作的无辜者，最残酷的无妄之灾也随时都可能降临。</p><p>不由得想起2019年，在上海的最后一个夏天。和朋友们一起参加了7月21日举办的BMLSP，不论是唱了Clannad三连的<em>Eufonius</em>（到第三首小小的手心的时候我已经哭的稀里哗啦了），还是最后登场的<em>Flow</em>在MC中都提到了这次事件，悼念了遇难者。五年过去了，损失惨重的京都动画也逐渐从过去的阴影中走出，虽然《吹响吧！上低音号》的第三季确实也有种种不尽人意的地方，毕竟失去了人设池田晶子，以及高桥博行这个劳模全乐器作监，剧情上的改编也充满争议。但对我个人而言，还能看到这个远离首都圈的动画公司的作品，就像看到梦想的延续一样，已经足够了。当然还是希望之后京都动画能多多培养&#x2F;招揽新的人才，补上缺口，重回巅峰。</p><img src="/2024/09/19/graduation-trip-uji/kyo-ani-memorial-2.jpg" class=""><blockquote><p>将梦想和激情在人与人之间传递，<br>通过动画传递无止境的梦想，即使是一根线条的绘制也需要多年培养的技术和深厚的情感<br>传递给孩子们，以及所有世代确切的影像和故事<br>在这里，宇治·京都，向全世界发出信号<br>我们展翅飞翔，迈向不间断的未来</p></blockquote><h1 id="伊藤久右衛門-宇治本店"><a href="#伊藤久右衛門-宇治本店" class="headerlink" title="伊藤久右衛門 宇治本店"></a>伊藤久右衛門 宇治本店</h1><p>再往前走有一家挺有名的抹茶店，毕竟提到宇治就是抹茶，先来点抹茶芭菲和抹茶刨冰压压惊。</p><img src="/2024/09/19/graduation-trip-uji/matcha-parfait.jpg" class=""><img src="/2024/09/19/graduation-trip-uji/matcha-shaved-ice.jpg" class=""><h1 id="宇治川河畔"><a href="#宇治川河畔" class="headerlink" title="宇治川河畔"></a>宇治川河畔</h1><p>沿着宇治川河畔散步，远处左边是朝雾桥，右边是橘桥。</p><img src="/2024/09/19/graduation-trip-uji/uji-riverside-1.jpg" class=""><p>风景还是很不错的。</p><img src="/2024/09/19/graduation-trip-uji/uji-riverside-2.jpg" class=""><h1 id="井川用水機場-久美子椅"><a href="#井川用水機場-久美子椅" class="headerlink" title="井川用水機場 久美子椅"></a>井川用水機場 久美子椅</h1><p>不愧是京吹圣地，黄前部长思考决策触发剧情的地方，Google Map上甚至直接标出了Kumiko Bench。</p><p>动画中实在出现过太多次了，我就随便挑几张截图。</p><img src="/2024/09/19/graduation-trip-uji/kumiko-bench-1.jpg" class=""><p>剧场版《誓言的终章》，黄大叔思考人生。</p><img src="/2024/09/19/graduation-trip-uji/hibike-euphonium-chikai-no-finale-00.46.26.jpg" class=""><p>第三季最终话最后的蒙太奇。</p><img src="/2024/09/19/graduation-trip-uji/hibike-euphonium-3-ep13-23.08.jpg" class=""><img src="/2024/09/19/graduation-trip-uji/kumiko-bench-2.jpg" class=""><p>第三季第二集久美子和丽奈决定全国金出场曲目。</p><img src="/2024/09/19/graduation-trip-uji/hibike-euphonium-3-ep02-20.44.jpg" class=""><img src="/2024/09/19/graduation-trip-uji/kumiko-bench-3.jpg" class=""><p>第一季第一集，秀一同志为自己年轻时犯下的错误付出代价。</p><img src="/2024/09/19/graduation-trip-uji/hibike-euphonium-ep01-15.35.jpg" class=""><h1 id="平等院"><a href="#平等院" class="headerlink" title="平等院"></a>平等院</h1><p>来都来了，还是交个门票钱去看一下平等院。里面还有个博物馆，里面有大量藏品，以及冷气非常足。</p><img src="/2024/09/19/graduation-trip-uji/byodo-in-1.jpg" class=""><img src="/2024/09/19/graduation-trip-uji/byodo-in-2.jpg" class=""><h1 id="宇治市观光中心"><a href="#宇治市观光中心" class="headerlink" title="宇治市观光中心"></a>宇治市观光中心</h1><p>久美子椅沿路往前走就是宇治市观光中心，快被晒晕的我立马躲进了空调房，一进去发现全是京吹各季度TV动画和剧场版的海报和立牌，吹吹人狂喜。</p><img src="/2024/09/19/graduation-trip-uji/ujishi-kanko-center-1.jpg" class=""><img src="/2024/09/19/graduation-trip-uji/ujishi-kanko-center-2.jpg" class=""><img src="/2024/09/19/graduation-trip-uji/ujishi-kanko-center-3.jpg" class=""><img src="/2024/09/19/graduation-trip-uji/ujishi-kanko-center-4.jpg" class=""><p>留言小册子。</p><img src="/2024/09/19/graduation-trip-uji/ujishi-kanko-center-5.jpg" class=""><p>声优的纪念签名。</p><img src="/2024/09/19/graduation-trip-uji/ujishi-kanko-center-6.jpg" class=""><p>还挂出来不少动画原画进行展示。</p><img src="/2024/09/19/graduation-trip-uji/key-frame-1.jpg" class=""><img src="/2024/09/19/graduation-trip-uji/key-frame-2.jpg" class=""><img src="/2024/09/19/graduation-trip-uji/key-frame-3.jpg" class=""><img src="/2024/09/19/graduation-trip-uji/key-frame-4.jpg" class=""><h1 id="喜撰桥"><a href="#喜撰桥" class="headerlink" title="喜撰桥"></a>喜撰桥</h1><p>从观光中心出来再往前走就是喜撰桥，又是一个在动画中反复出现的京吹圣地。</p><p>第一季第二集久美子和葵在久美子椅谈心的时候闪现过的画面。</p><img src="/2024/09/19/graduation-trip-uji/kisen-bridge-1.jpg" class=""><img src="/2024/09/19/graduation-trip-uji/hibike-euphonium-ep02-19.59.jpg" class=""><p>第二季加长版第一集致死量的高黄，有段时间感觉流行动画第一集搞个40分钟加长版，记忆中第一个这么干的好像是Fate Zero，第一集的二人转实在是印象深刻。</p><img src="/2024/09/19/graduation-trip-uji/kisen-bridge-2.jpg" class=""><img src="/2024/09/19/graduation-trip-uji/hibike-euphonium-2-ep01-44.16.jpg" class=""><img src="/2024/09/19/graduation-trip-uji/hibike-euphonium-2-ep01-44.58.jpg" class=""><p>换一个角度看。</p><img src="/2024/09/19/graduation-trip-uji/kisen-bridge-3.jpg" class=""><img src="/2024/09/19/graduation-trip-uji/hibike-euphonium-2-ep01-45.54.jpg" class=""><img src="/2024/09/19/graduation-trip-uji/kisen-bridge-4.jpg" class=""><p>不知道晚上灯笼亮起来是什么样的。</p><img src="/2024/09/19/graduation-trip-uji/kisen-bridge-5.jpg" class=""><img src="/2024/09/19/graduation-trip-uji/hibike-euphonium-2-ep01-44.32.jpg" class=""><h1 id="朝雾桥"><a href="#朝雾桥" class="headerlink" title="朝雾桥"></a>朝雾桥</h1><p>越过喜撰桥就是宇治川中的小岛，走到宇治公园，差不多久美子椅对面的位置就是部长失格现场，朝雾桥。</p><img src="/2024/09/19/graduation-trip-uji/asagiri-bridge-1.jpg" class=""><p>第三季本来原作武吹的剧情就相当迷惑，强行空降真由来制造矛盾冲突，顺带把高坂丽奈彻底塑造成塑料姐妹，动画改编还把最后的大团圆包饺子给改成了久美子承担下了所有，实在是难以评价。但由于沙雕网友们的二次创作过于有力，我现在看到这个桥只能想到<em>北宇治王朝1566–北宇治举重冠军怒斥高太尉</em>了。</p><img src="/2024/09/19/graduation-trip-uji/hibike-euphonium-3-ep09-20.43.jpg" class=""><img src="/2024/09/19/graduation-trip-uji/asagiri-bridge-2.jpg" class=""><h1 id="炭焼き肉と京の野菜-Nico"><a href="#炭焼き肉と京の野菜-Nico" class="headerlink" title="炭焼き肉と京の野菜 Nico"></a>炭焼き肉と京の野菜 Nico</h1><p>晚饭是在一家同学的朋友（据称是二刺螈Ph.D.）推荐的店里解决的，可能因为去的比较早店里并没有别的客人，有一种包场的感觉。</p><img src="/2024/09/19/graduation-trip-uji/nico-1.jpg" class=""><p>就餐环境和味道都很不错！</p><img src="/2024/09/19/graduation-trip-uji/nico-2.jpg" class=""><p>走的时候在某条小路边上看到了谜之画风的妹抖龙。</p><img src="/2024/09/19/graduation-trip-uji/dragon-maid.jpg" class=""><h1 id="大吉山展望台"><a href="#大吉山展望台" class="headerlink" title="大吉山展望台"></a>大吉山展望台</h1><p>吃完晚饭就直奔大吉山，也是本次圣地巡礼的终点站。山上还是不少人的，其中一大半都很明显是京吹观众，还有带着京吹周边来巡礼的。</p><img src="/2024/09/19/graduation-trip-uji/daikichiyama-1.jpg" class=""><p>没有带三脚架，所以主要是在“蓝调时刻”进行拍摄。</p><img src="/2024/09/19/graduation-trip-uji/daikichiyama-2.jpg" class=""><img src="/2024/09/19/graduation-trip-uji/hibike-euphonium-chikai-no-finale-00.50.04.jpg" class=""><p>这里本来想用第一季第八集的截图，后来发现剧场版的夜景细节更丰富，也和我拍的照片更接近些。</p><img src="/2024/09/19/graduation-trip-uji/daikichiyama-3.jpg" class=""><img src="/2024/09/19/graduation-trip-uji/hibike-euphonium-chikai-no-finale-00.50.21.jpg" class=""><p>第一季第八集最后大吉山上的那一幕真的经典，永远怀念山田尚子的超神演出。虽然也懂得天下没有不散的宴席的道理，但想到山田尚子在2021年离开京都动画，还是感到十分惋惜。</p><img src="/2024/09/19/graduation-trip-uji/daikichiyama-4.jpg" class=""><img src="/2024/09/19/graduation-trip-uji/hibike-euphonium-ep08-19.57.jpg" class=""><img src="/2024/09/19/graduation-trip-uji/daikichiyama.gif" class=""><p>我已经过了想要成为特别的人的年纪，现在只要日子过得下去，普普通通就好。</p><h1 id="尾声"><a href="#尾声" class="headerlink" title="尾声"></a>尾声</h1><p>宇治是真的好玩，本抹茶爱好者也算爽吃了一把各种抹茶甜品，京吹的圣地巡礼虽然谈不上尽善尽美（下次把北宇治高校补上！），但也算满足了我多年以来的心愿。“毕业旅行”系列还差最后一篇博文，终章会侧重于“毕业”而非“旅行”，大概会随便写点什么纪念Ph.D.这场漫长旅途的完结。</p>]]></content>
    
    
    <summary type="html">&lt;p&gt;《吹响吧！上低音号》圣地巡礼。&lt;/p&gt;</summary>
    
    
    
    <category term="Life" scheme="https://blog.zzhou612.com/categories/Life/"/>
    
    <category term="Newfound Adventure" scheme="https://blog.zzhou612.com/categories/Life/Newfound-Adventure/"/>
    
    
    <category term="日本" scheme="https://blog.zzhou612.com/tags/%E6%97%A5%E6%9C%AC/"/>
    
    <category term="宇治" scheme="https://blog.zzhou612.com/tags/%E5%AE%87%E6%B2%BB/"/>
    
    <category term="圣地巡礼" scheme="https://blog.zzhou612.com/tags/%E5%9C%A3%E5%9C%B0%E5%B7%A1%E7%A4%BC/"/>
    
  </entry>
  
  <entry>
    <title>毕业旅行：京都</title>
    <link href="https://blog.zzhou612.com/2024/09/12/graduation-trip-kyoto/"/>
    <id>https://blog.zzhou612.com/2024/09/12/graduation-trip-kyoto/</id>
    <published>2024-09-12T09:46:57.000Z</published>
    <updated>2024-09-12T09:46:57.000Z</updated>
    
    <content type="html"><![CDATA[<p>在迷宫般的东京站找到了前往京都的新干线站台，下一站，京都！</p><span id="more"></span><h1 id="前言"><a href="#前言" class="headerlink" title="前言"></a>前言</h1><p>日本铁路系统比较复杂，各个区域都有自己的公司&#x2F;网站&#x2F;App，新干线也是如此。虽然是在东京站取票出发，但JR东日本的App和网站做的实在太烂了，甚至不支持Chase的Visa信用卡（不支持也没有说明，只是注册的时候会把账号锁住，也不告知任何原因），JR西日本网站的购票体验就好多了，网上订好票后去东京站指定的售票机取票即可，体验丝滑。</p><p>在京都的时候住在Hyatt Place Kyoto，2021年新建成的酒店，设施新住宿条件好，丸太町站出来就是，交通非常便利，而且一晚上只要8000点。</p><h1 id="鹿苑寺"><a href="#鹿苑寺" class="headerlink" title="鹿苑寺"></a>鹿苑寺</h1><p>多年前来京都的时候的时候只有一天时间行程紧张（甚至还住在大阪需要当天往返），没能来成较为偏远的金阁寺（其实真名叫鹿苑寺，金阁只是其中舍利殿的简称），这次从酒店慢悠悠坐着大巴来看了一眼，确实没白跑一趟，还是金光闪闪挺好看的。</p><img src="/2024/09/12/graduation-trip-kyoto/rokuonji-1.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/rokuonji-2.jpg" class=""><h1 id="鸭川-祇园四条"><a href="#鸭川-祇园四条" class="headerlink" title="鸭川 祇园四条"></a>鸭川 祇园四条</h1><p>京都街头经常能看到卖艺的，晚上也很热闹，祇园四条站下来就能看到Pro贝斯哥激情演奏。</p><img src="/2024/09/12/graduation-trip-kyoto/gion-shijo.jpg" class=""><p>四条大桥这边的鸭川夜景也挺有感觉的。</p><img src="/2024/09/12/graduation-trip-kyoto/kamogawa-night.jpg" class=""><h1 id="八坂神社"><a href="#八坂神社" class="headerlink" title="八坂神社"></a>八坂神社</h1><p>沿路走到了八坂神社，这地方还是得晚上来。</p><img src="/2024/09/12/graduation-trip-kyoto/yasaka-shrine-1.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/yasaka-shrine-2.jpg" class=""><h1 id="二年坂-三年坂"><a href="#二年坂-三年坂" class="headerlink" title="二年坂 三年坂"></a>二年坂 三年坂</h1><p>二年坂和三年坂其实晚上都有不少人，趁着没人的时候赶紧拍几张，可惜天已经彻底黑了，外加灯光颜色的缘故，夜景效果不太好。</p><img src="/2024/09/12/graduation-trip-kyoto/ninenzaka.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/sannenzaka.jpg" class=""><h1 id="京都御苑-紫宸殿"><a href="#京都御苑-紫宸殿" class="headerlink" title="京都御苑 紫宸殿"></a>京都御苑 紫宸殿</h1><p>烈日炙烤下的石子路，不知道我的防晒霜能否顶得住。</p><img src="/2024/09/12/graduation-trip-kyoto/kyoto-gyoen-national-garden.jpg" class=""><p>京都御所中的紫宸殿和唐朝长安城大明宫的紫宸殿同名<del>当年日本遍地精唐的又一力证</del>，我也不是很懂古建筑，不知道能不能当作唐宋建筑代餐。</p><img src="/2024/09/12/graduation-trip-kyoto/shishinden-1.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/shishinden-2.jpg" class=""><h1 id="出町桝形商店街"><a href="#出町桝形商店街" class="headerlink" title="出町桝形商店街"></a>出町桝形商店街</h1><p>玉子市场中兔山商店街的原型，能看见纪念《有顶天家族》动画十周年的挂画。《有顶天家族》我没看过，查了一下第一季是2013年（和《玉子市场》TV动画同年），第二季是2017年，虽然也是老东西了，但还是比2014年的《玉子爱情故事》新一点点。商店街比我想象中热闹许多，商店街门口还有一家卖和果子的店（出町ふたば）生意极为火爆，而且似乎都是本地人在排<del>京爷严选</del>，可惜每次路过的时候都没狠下心来排队，下次一定。</p><img src="/2024/09/12/graduation-trip-kyoto/demachi-masugata-shopping-street-1.jpg" class=""><p>商业街里有个小电影院，甚至还有之前贾玲翻拍的《热辣滚烫》，这里毫不客气地用了原作《百元之恋》作为影片名，《在这世界的角落》和《奥本海默》出现在了一起也让人浮想联翩。</p><img src="/2024/09/12/graduation-trip-kyoto/demachi-masugata-shopping-street-2.jpg" class=""><p>商业街一侧入口处《玉子市场》留下的痕迹，这种抽象画风的人物立牌在京都周边也见过不少次。</p><img src="/2024/09/12/graduation-trip-kyoto/demachi-masugata-shopping-street-3.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/demachi-masugata-shopping-street-4.jpg" class=""><p>在商店街的另一端找到了《玉子市场》以及《玉子爱情故事》的悬挂海报，《玉子市场》的海报看起来饱经风霜，剧场版的海报倒还是崭新的。</p><img src="/2024/09/12/graduation-trip-kyoto/demachi-masugata-shopping-street-5.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/demachi-masugata-shopping-street-6.jpg" class=""><h1 id="鸭川三角洲"><a href="#鸭川三角洲" class="headerlink" title="鸭川三角洲"></a>鸭川三角洲</h1><p>京都动画作品中经常出现的鸭川三角洲，《玉子爱情故事》中饼藏在这里向玉子告白<del>吓得玉子扑通掉水里</del>，《轻音少女》第一季OP中也出现过四人在这里的石头上蹦蹦跳跳的场景。</p><img src="/2024/09/12/graduation-trip-kyoto/kamogawa-delta-1.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/kamogawa-delta-2.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/kamogawa-delta-3.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/kamogawa-delta-4.jpg" class=""><p>鸭川的生态环境保持的很好，也会有人专程来观鸟，虽然我并不知道这是什么鸟，手头只有24-70焦段的镜头，好在A7RV分辨率够高可以肆意zoom in。</p><img src="/2024/09/12/graduation-trip-kyoto/kamogawa-delta-bird.jpg" class=""><p>《玉子爱情故事》中出现的场景所在的位置有不少人在戏水，外加我也没有提前仔细做好功课，所以拍照的时候没有严格按照动画分镜来。</p><img src="/2024/09/12/graduation-trip-kyoto/tamako-love-story-1.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/tamako-love-story-2.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/tamako-love-story-3.jpg" class=""><p>K-ON！的OP中也出现过鸭川三角洲的踏脚石，山田尚子永远的神。</p><img src="/2024/09/12/graduation-trip-kyoto/k-on.jpg" class=""><h1 id="伏见稻荷大社"><a href="#伏见稻荷大社" class="headerlink" title="伏见稻荷大社"></a>伏见稻荷大社</h1><p>本来以为晚上的伏见稻荷大社不仅能避开白天的热浪，应该也能避开汹涌人流，事实证明纯属想多了，太阳落山后照样遍地是人（但大概还是比白天少多了）。</p><img src="/2024/09/12/graduation-trip-kyoto/fushimi-inari-taisha-1.jpg" class=""><p>夜间灯光照明下的千本鸟居，不得不感慨现在相机防抖性能的进步，手持曝光一秒在A7RV的分辨率下放大100%都丝毫不糊。</p><img src="/2024/09/12/graduation-trip-kyoto/fushimi-inari-taisha-2.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/fushimi-inari-taisha-3.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/fushimi-inari-taisha-4.jpg" class=""><p>仰望半月的夜空。</p><img src="/2024/09/12/graduation-trip-kyoto/fushimi-inari-taisha-5.jpg" class=""><h1 id="清水寺"><a href="#清水寺" class="headerlink" title="清水寺"></a>清水寺</h1><p>白天还去清水寺逛了逛，希望以后有机会在红叶季重返这里。</p><img src="/2024/09/12/graduation-trip-kyoto/kiyomizu-dera-1.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/kiyomizu-dera-2.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/kiyomizu-dera-3.jpg" class=""><h1 id="一些吃的"><a href="#一些吃的" class="headerlink" title="一些吃的"></a>一些吃的</h1><h2 id="ぎをん藤"><a href="#ぎをん藤" class="headerlink" title="ぎをん藤"></a>ぎをん藤</h2><p>同学带我去的高级天妇罗店，可能漏掉了几张照片顺序也乱掉了不要在意。</p><div class="justified-gallery"><img src="/2024/09/12/graduation-trip-kyoto/gion-fuji-1.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/gion-fuji-2.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/gion-fuji-3.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/gion-fuji-4.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/gion-fuji-5.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/gion-fuji-6.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/gion-fuji-7.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/gion-fuji-8.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/gion-fuji-9.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/gion-fuji-10.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/gion-fuji-11.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/gion-fuji-12.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/gion-fuji-13.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/gion-fuji-14.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/gion-fuji-15.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/gion-fuji-16.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/gion-fuji-17.jpg" class=""><img src="/2024/09/12/graduation-trip-kyoto/gion-fuji-18.jpg" class=""></div><h2 id="熟成豚かわむら"><a href="#熟成豚かわむら" class="headerlink" title="熟成豚かわむら"></a>熟成豚かわむら</h2><p>专门跑去山科吃的熟成猪排，确实很顶。</p><img src="/2024/09/12/graduation-trip-kyoto/jukusei-buta-kawamura.jpg" class=""><h2 id="仙台牛たん福助"><a href="#仙台牛たん福助" class="headerlink" title="仙台牛たん福助"></a>仙台牛たん福助</h2><p>在京都站吃的仙台牛舌连锁店，感觉一般，是不是还得去仙台才能吃到正宗的。</p><img src="/2024/09/12/graduation-trip-kyoto/gyutan-fukusuke.jpg" class=""><h2 id="下鴨ごん蔵"><a href="#下鴨ごん蔵" class="headerlink" title="下鴨ごん蔵"></a>下鴨ごん蔵</h2><p>咖喱乌冬面，还可以。</p><img src="/2024/09/12/graduation-trip-kyoto/shimogamo-gonzo.jpg" class=""><h2 id="京都-鶏白湯そば純"><a href="#京都-鶏白湯そば純" class="headerlink" title="京都 鶏白湯そば純"></a>京都 鶏白湯そば純</h2><p>酒店附近的鸡汤拉面，非常美味，还顶着罪恶感抱着回国再减肥犹未晚矣的心态，试了试拉面汤泡米饭，虽然碳水爆炸，但实在是太香了。</p><img src="/2024/09/12/graduation-trip-kyoto/tori-soba.jpg" class=""><h1 id="尾声"><a href="#尾声" class="headerlink" title="尾声"></a>尾声</h1><p>下一篇post就是宇治了，本次旅行玩得最开心的一站，<del>没错，我就是粳米吹吹人</del>。</p>]]></content>
    
    
    <summary type="html">&lt;p&gt;在迷宫般的东京站找到了前往京都的新干线站台，下一站，京都！&lt;/p&gt;</summary>
    
    
    
    <category term="Life" scheme="https://blog.zzhou612.com/categories/Life/"/>
    
    <category term="Newfound Adventure" scheme="https://blog.zzhou612.com/categories/Life/Newfound-Adventure/"/>
    
    
    <category term="日本" scheme="https://blog.zzhou612.com/tags/%E6%97%A5%E6%9C%AC/"/>
    
    <category term="京都" scheme="https://blog.zzhou612.com/tags/%E4%BA%AC%E9%83%BD/"/>
    
  </entry>
  
  <entry>
    <title>毕业旅行：东京与镰仓</title>
    <link href="https://blog.zzhou612.com/2024/09/11/graduation-trip-tokyo/"/>
    <id>https://blog.zzhou612.com/2024/09/11/graduation-trip-tokyo/</id>
    <published>2024-09-11T05:30:58.000Z</published>
    <updated>2024-09-11T05:30:58.000Z</updated>
    
    <content type="html"><![CDATA[<p>完成博士答辩，等committee签完字把thesis交上去之后，成功毕业跑路。归国后旅行的第一个目的地就是阔别已久的日本，就当是久违的毕业旅行了。</p><span id="more"></span><h1 id="前言"><a href="#前言" class="headerlink" title="前言"></a>前言</h1><p>上次毕业旅行还要追溯到高中毕业，模糊的记忆中似乎是和高中同学们一起去了台湾（台北、日月潭、阿里山、高雄）。大学毕业的时候因为学院特殊的学制，八月份才毕业，火急火燎地逃离上海（甚至鸽了学院的毕业典礼），在台风来袭前赶回北京，歇了一两周就坐上了去伊萨卡的飞机。掐指一算，这次日本之行居然算得上是阔别十年之久的“毕业旅行”。</p><p>考虑到Ph.D.也算是terminal degree，这次应该是人生中最后一次毕业旅行了，还是写点流水账记录一下。上次来日本还是八年前，以很紧凑的五天行程跑完了东京➡大阪。这次准备了九天，这么多年过去了也基本失忆了，就安排了东京、镰仓、京都、宇治的行程，拉上了五年前冬天曾和我一起自驾美东的大学室友（日本语上手），在炎热的夏日开启了这次慢悠悠日本之行。</p><p><del>这次流水账大概要分3到4个post才能写完，希望不要烂尾。</del></p><h1 id="Hyatt-Regency-Tokyo"><a href="#Hyatt-Regency-Tokyo" class="headerlink" title="Hyatt Regency Tokyo"></a>Hyatt Regency Tokyo</h1><p>在东京住在Hyatt Regency Tokyo，位置很便利，淡季只要15k点数就能换一晚。房间不错很宽敞，窗外就是东京都厅和新宿中央公园，用手机随手拍了一张。</p><img src="/2024/09/11/graduation-trip-tokyo/government.jpg" class=""><h1 id="焼肉ジャンボ"><a href="#焼肉ジャンボ" class="headerlink" title="焼肉ジャンボ"></a>焼肉ジャンボ</h1><p>晚饭直奔焼肉ジャンボ（本郷店），只能说真的很爽，日式烧肉中牛五花和肥厚牛舌在烈火炙烤下散发出的充满罪恶感的脂肪燃烧的香气，真的令人无法拒绝。</p><img src="/2024/09/11/graduation-trip-tokyo/yakiniku-jambo-1.jpg" class=""><img src="/2024/09/11/graduation-trip-tokyo/yakiniku-jambo-2.jpg" class=""><img src="/2024/09/11/graduation-trip-tokyo/yakiniku-jambo-3.jpg" class=""><h1 id="神田神社-秋叶原"><a href="#神田神社-秋叶原" class="headerlink" title="神田神社 秋叶原"></a>神田神社 秋叶原</h1><p>烤肉真的很顶，饭后去秋叶原散步消消食，路过神田神社。</p><img src="/2024/09/11/graduation-trip-tokyo/kanda-shrine.jpg" class=""><p>秋叶原挂满了各种手游广告，满大街Blue Archive，甚至还在路边看到了崩坏3的广告。行人道上都是女仆店拉客的小姐姐，这么热的天还要全副武装我看了都觉得热。在A店和堂吉诃德逛了逛，还是蛮有趣的。</p><img src="/2024/09/11/graduation-trip-tokyo/akihabara.jpg" class=""><h1 id="雷门-天空树"><a href="#雷门-天空树" class="headerlink" title="雷门 天空树"></a>雷门 天空树</h1><p>晚上去天空树看东京夜景，换乘的时候路过浅草寺的雷门。</p><img src="/2024/09/11/graduation-trip-tokyo/kaminarimon.jpg" class=""><p>到天空树的时候450米的天望回廊的门票已经售罄了，但其实350米的天望甲板也够看了。找了个一堆人排队合影的角落拍照，正好帮我挡住了玻璃的反光。</p><img src="/2024/09/11/graduation-trip-tokyo/skytree.jpg" class=""><h1 id="腰越-地上电车"><a href="#腰越-地上电车" class="headerlink" title="腰越 地上电车"></a>腰越 地上电车</h1><p>第二天坐电车前往镰仓，从新宿出发大概花了一个小时的时间到达藤泽，然后转乘江之电。江之电在腰越站沿线可以看到电车在马路上行驶。</p><img src="/2024/09/11/graduation-trip-tokyo/koshigoe-train-1.jpg" class=""><img src="/2024/09/11/graduation-trip-tokyo/koshigoe-train-2.jpg" class=""><h1 id="镰仓高校前-七里滨"><a href="#镰仓高校前-七里滨" class="headerlink" title="镰仓高校前 七里滨"></a>镰仓高校前 七里滨</h1><p>在镰仓那天运气不好赶上多云，云层覆盖率超高，所以大海也显得灰蒙蒙的，希望下次能在晴天能见度高的时候看看镰仓湛蓝的海。镰仓高校前站人山人海，往回走一段路有个没啥人的低配版路口。</p><img src="/2024/09/11/graduation-trip-tokyo/kamakurakokomae-station.jpg" class=""><p>天气好的时候七里滨的海滩能看到富士山，希望下次能有机会拍到。</p><img src="/2024/09/11/graduation-trip-tokyo/shichirigahama.jpg" class=""><p>中午在灿烂的阳光下往山坡上爬，去了家叫AWANOUTA的拉面店吃了碗拉面，挺有特色的。</p><img src="/2024/09/11/graduation-trip-tokyo/awanouta.jpg" class=""><h1 id="高德院-镰仓大佛"><a href="#高德院-镰仓大佛" class="headerlink" title="高德院 镰仓大佛"></a>高德院 镰仓大佛</h1><p>还去了高德院看了眼镰仓大佛。</p><img src="/2024/09/11/graduation-trip-tokyo/kotoku-in.jpg" class=""><h1 id="六本木之丘展望台"><a href="#六本木之丘展望台" class="headerlink" title="六本木之丘展望台"></a>六本木之丘展望台</h1><p>到了傍晚一看云层覆盖率接近100%，就果断放弃了在海蜡烛看日落，直接返回了东京市内，去六本木之丘展望台看东京塔夜景。</p><p>先在附近吃一顿鳗鱼饭。</p><img src="/2024/09/11/graduation-trip-tokyo/grilled_eel.jpg" class=""><p>六本木新城森大楼顶楼的天空展望台是《天气之子》中阳菜为花火大会祈求晴天来临的取景地，似乎是因为有人跳楼，导致露天展望台于今年四月份永久关闭，错过了圣地巡礼的机会十分可惜。但52层的室内展望台还是不错的，是观赏东京铁塔🗼的好机位，就是可惜2023年完工的麻布台Hills（图左边那个傻大粗楼）立在旁边是真的有点煞风景。Tokyo City View和人山人海的天空树比起来基本没什么人，甚至可以带个迷你三脚架进行长曝光。</p><img src="/2024/09/11/graduation-trip-tokyo/roppongi-hills-1.jpg" class=""><p>我没带迷你三脚架，就拿手机和平板电脑垫了垫，长曝光试着拍了拍车流不息的城市夜景。</p><img src="/2024/09/11/graduation-trip-tokyo/roppongi-hills-2.jpg" class=""><h1 id="涩谷路口"><a href="#涩谷路口" class="headerlink" title="涩谷路口"></a>涩谷路口</h1><p>第二天去涩谷转了转，在某大楼里的一个免费NHK展会的小窗口拍了拍涩谷路口的人流，虽然因为是工作日中午，人不是很多。</p><img src="/2024/09/11/graduation-trip-tokyo/shibuya-crossing.jpg" class=""><h1 id="东京塔"><a href="#东京塔" class="headerlink" title="东京塔"></a>东京塔</h1><p>蓝天白云时的东京塔还是很不错的，希望下次去镰仓也能有这样的好天气（泪）。</p><img src="/2024/09/11/graduation-trip-tokyo/tokyo-tower-1.jpg" class=""><img src="/2024/09/11/graduation-trip-tokyo/tokyo-tower-2.jpg" class=""><h1 id="御茶之水站"><a href="#御茶之水站" class="headerlink" title="御茶之水站"></a>御茶之水站</h1><p>在御茶之水站边上的大桥，顶着大太阳拍到了三辆电车交汇，这里时铁道迷圣地，同时也是《铃芽之旅》中铃芽信仰之跃以及蚓厄钻出来的地方<del>BGM東京上空</del>。</p><img src="/2024/09/11/graduation-trip-tokyo/ochanomizu-station.jpg" class=""><h1 id="歌舞伎町"><a href="#歌舞伎町" class="headerlink" title="歌舞伎町"></a>歌舞伎町</h1><p>晚饭约在了八点半，先去歌舞伎町打发时间（并不），最后在附近一个萨莉亚先吃了点蒜香鸡排垫一垫，点了个畅饮，吹空调玩手机休整了一下。</p><img src="/2024/09/11/graduation-trip-tokyo/kabukicho.jpg" class=""><h1 id="愚直に"><a href="#愚直に" class="headerlink" title="愚直に"></a>愚直に</h1><p>晚上开始下雨，冒着瓢泼大雨前往愚直に，主厨师傅和几个徒弟在狭窄的厨房忙前忙后，准备每一道菜的时候喊着Hi来进行流水线同步。</p><div class="justified-gallery"><img src="/2024/09/11/graduation-trip-tokyo/guchokuni-1.jpg" class=""><img src="/2024/09/11/graduation-trip-tokyo/guchokuni-2.jpg" class=""><img src="/2024/09/11/graduation-trip-tokyo/guchokuni-3.jpg" class=""><img src="/2024/09/11/graduation-trip-tokyo/guchokuni-4.jpg" class=""><img src="/2024/09/11/graduation-trip-tokyo/guchokuni-5.jpg" class=""><img src="/2024/09/11/graduation-trip-tokyo/guchokuni-6.jpg" class=""><img src="/2024/09/11/graduation-trip-tokyo/guchokuni-7.jpg" class=""><img src="/2024/09/11/graduation-trip-tokyo/guchokuni-8.jpg" class=""><img src="/2024/09/11/graduation-trip-tokyo/guchokuni-9.jpg" class=""><img src="/2024/09/11/graduation-trip-tokyo/guchokuni-10.jpg" class=""><img src="/2024/09/11/graduation-trip-tokyo/guchokuni-11.jpg" class=""><img src="/2024/09/11/graduation-trip-tokyo/guchokuni-12.jpg" class=""></div><h1 id="尾声"><a href="#尾声" class="headerlink" title="尾声"></a>尾声</h1><p>东京之旅到这里就差不多结束了，第二天早上乘坐新干线前往京都。</p>]]></content>
    
    
    <summary type="html">&lt;p&gt;完成博士答辩，等committee签完字把thesis交上去之后，成功毕业跑路。归国后旅行的第一个目的地就是阔别已久的日本，就当是久违的毕业旅行了。&lt;/p&gt;</summary>
    
    
    
    <category term="Life" scheme="https://blog.zzhou612.com/categories/Life/"/>
    
    <category term="Newfound Adventure" scheme="https://blog.zzhou612.com/categories/Life/Newfound-Adventure/"/>
    
    
    <category term="日本" scheme="https://blog.zzhou612.com/tags/%E6%97%A5%E6%9C%AC/"/>
    
    <category term="东京" scheme="https://blog.zzhou612.com/tags/%E4%B8%9C%E4%BA%AC/"/>
    
    <category term="镰仓" scheme="https://blog.zzhou612.com/tags/%E9%95%B0%E4%BB%93/"/>
    
  </entry>
  
  <entry>
    <title>ASPLOS 2024@San Diego</title>
    <link href="https://blog.zzhou612.com/2024/06/09/asplos24-san-diego/"/>
    <id>https://blog.zzhou612.com/2024/06/09/asplos24-san-diego/</id>
    <published>2024-06-08T16:00:00.000Z</published>
    <updated>2024-06-08T16:00:00.000Z</updated>
    
    <content type="html"><![CDATA[<p>圣地亚哥对我而言也算是有特殊意义的城市了，六年前在申请季步入尾声之时，从大洋彼岸飞过来参加ICCAD，误打误撞开启了Ph.D.之旅。现如今在漫长旅途接近终点之时，从伊萨卡再次重返这座城市参加ASPLOS，不禁有种“君以此始，必以此终”的宿命感。</p><span id="more"></span><h1 id="故地重游"><a href="#故地重游" class="headerlink" title="故地重游"></a>故地重游</h1><p>时隔六年重返这座城市，两次都是来参加学术会议。同一个地方，不同的时间，不同的回忆，不同的身份。当年是去了趟异世界延毕的大五本科生，现如今是提桶跑路倒计时最后阶段的中老年Ph.D.。2018年来开ICCAD的时候拿着交大的奖学金，由于囊中羞涩（外加美国酒店确实贵），外加想到花完剩下的预算也是进我自己腰包，就没定当时ICCAD的会议酒店<em>Hilton San Diego Resort &amp; Spa</em>（似乎已经改名<em>San Diego Mission Bay Resort</em>），住在了附近的一小酒店（查了下地图似乎应该是现在的<em>Mission Bay Inn San Diego</em>）。当时是走路去会场，会路过海滨公园，还记得白天的时候阳光明媚景色宜人，有跑步健身遛狗的哥们还会主动打招呼，到了晚上就变成了homeless丧尸围城。那时候年轻不懂事，居然敢晚上走回酒店，现在想来实在是勇气可嘉，也可能是第一次来美国，对美利坚的风俗习惯不甚了解。</p><p>说是故地重游，其实六年前除了会场&#x2F;机场&#x2F;酒店以外也没去别的地方，这次在Ph.D.旅途终点前参加最后一次会议，租了车也逛了不少地方。在等Google报销用的virtual credit card的过程中ASPLOS的会议酒店<em>Hilton La Jolla Torrey Pines</em>订空了（提前一个多月就空了也是够离谱的），最后问了在UCSD的地头蛇同学，这似乎是个La Jolla知名高尔夫球场边上的酒店，所以很难预留足够多的房间给参会人员。最后租了车，住在了同学推荐的<em>Hotel Indigo San Diego Del Mar</em>的海景房，大概六、七分钟车程，风景很不错。</p><img src="/2024/06/09/asplos24-san-diego/SD-Hotel-Indigo.jpg" class=""><p>酒店下面走两步就能看到沿着海岸线修的铁路，还有花花。可以走下去沿着铁路一直走。</p><img src="/2024/06/09/asplos24-san-diego/SD-Coast-Rail-1.jpg" class=""><img src="/2024/06/09/asplos24-san-diego/SD-Coast-Rail-2.jpg" class=""><p>后来某天下午还专门来拍火车，可惜那天多云，大海的颜色没那么好看。</p><img src="/2024/06/09/asplos24-san-diego/SD-Coast-Rail-3.jpg" class=""><p>我没报名周末的workshop，但还是周五晚上就来了SD，周末爽玩了一把，吃了不少好吃的，可惜没留下多少美食的照片记录。</p><p>UCSD Scripps Pier，似乎是UCSD海洋学院建的观测站，也算是网红景点，落日时分很好看。后来某天落日时分带了几个没租车的同学去看，结果忘拿相机了，非常遗憾。</p><img src="/2024/06/09/asplos24-san-diego/SD-Scripps-Pier-1.jpg" class=""><img src="/2024/06/09/asplos24-san-diego/SD-Scripps-Pier-2.jpg" class=""><img src="/2024/06/09/asplos24-san-diego/SD-Scripps-Pier-3.jpg" class=""><p>每年特定的时段太阳会从柱子间落下，类似于曼哈顿悬日，落日时分会有大量老法师和游客来抢占机位，我后来落日时去的那天可谓是人山人海，甚至还有哥们拿出了无人机。可惜我当时以为没到日期，应该看不到悬日景观，就没拿相机。海浪拍在柱子上有点让我想起年轻时候看Nolan拍的<em>Inception</em>。用手机拍了下人山人海的盛况，还用了星星星的十倍镜拍了落日。</p><img src="/2024/06/09/asplos24-san-diego/SD-Scripps-Pier-Phone-1.jpg" class=""><img src="/2024/06/09/asplos24-san-diego/SD-Scripps-Pier-Phone-2.jpg" class=""><p>La Jolla Cove，看海豹、海狮的地方，我并不分得清二者就是了。确实味大，无须多言，隔着很远就能闻到。</p><img src="/2024/06/09/asplos24-san-diego/SD-La-Jolla-Cove-1.jpg" class=""><img src="/2024/06/09/asplos24-san-diego/SD-La-Jolla-Cove-2.jpg" class=""><img src="/2024/06/09/asplos24-san-diego/SD-La-Jolla-Cove-3.jpg" class=""><p>这张照片应该是在La Jolla Tide Pools边上拍的，奇怪我怎么找不到潮池的照片了，可能并没什么好拍的就没拍吧。</p><img src="/2024/06/09/asplos24-san-diego/SD-La-Jolla-Tide-Pools.jpg" class=""><p>ASPLOS会议本身没啥好说的，基本一直在social（乐）。认识了很多新朋友，也见到了许久未见的导师（笑），以及导师的导师，当时还纳闷为啥希腊帮齐聚一堂，后来周二的banquet谜底揭晓，原来Chrsitina是来领奖的。Partha还主动找我合了影，结果并没有把照片传给我，可能这就是VP吧。</p><p>周二的banquet还是值得吹一波的，虽然吃的一如既往的难以评价，只有鸡胸肉（很柴，还限量），但不得不说在USS Midway甲板上开晚宴实在太酷了。</p><img src="/2024/06/09/asplos24-san-diego/SD-USS-Midway-1.jpg" class=""><p>还能看到对面军港里的现役航母。</p><img src="/2024/06/09/asplos24-san-diego/SD-USS-Midway-2.jpg" class=""><img src="/2024/06/09/asplos24-san-diego/SD-USS-Midway-3.jpg" class=""><p>远眺Coronado Bridge。</p><img src="/2024/06/09/asplos24-san-diego/SD-USS-Midway-4.jpg" class=""><p>太阳落山之后大家入座，banquet开始。没带广角镜头，手机顺手拍了张。</p><img src="/2024/06/09/asplos24-san-diego/SD-USS-Midway-Phone.jpg" class=""><p>天黑后还是有点冷的，白天很热我还从会场跑回酒店换了薄衣服，总之就是冻的瑟瑟发抖十分后悔。</p><img src="/2024/06/09/asplos24-san-diego/SD-USS-Midway-5.jpg" class=""><img src="/2024/06/09/asplos24-san-diego/SD-USS-Midway-6.jpg" class=""><p>周三开完会，回伊萨卡的航班周四晚上起飞，于是白天还在SD转了转，中午吃了Seasurf家便宜又好吃的海鲜饭，下午去了Torrey Pines State Natural Reserve，风景确实很不错，值得一来。</p><p>Trail总体不长，但由于我背着全套装备外加阳光过于猛烈，还是出了不少汗，也一直在看着时间怕错过飞机。本来说去个Razor Point就原路返回停车场，发现风景不错之后就又去了旁边的Yucca Point Vista Point。</p><img src="/2024/06/09/asplos24-san-diego/SD-Torrey-Pines-1.jpg" class=""><img src="/2024/06/09/asplos24-san-diego/SD-Torrey-Pines-2.jpg" class=""><img src="/2024/06/09/asplos24-san-diego/SD-Torrey-Pines-3.jpg" class=""><img src="/2024/06/09/asplos24-san-diego/SD-Torrey-Pines-4.jpg" class=""><p>本来都打算赶回停车场了，毕竟时间也不早了，结果看到了一块黑色大石头。</p><img src="/2024/06/09/asplos24-san-diego/SD-Torrey-Pines-5.jpg" class=""><p>快马加鞭，在烈阳之下高速徒步沿着Beach Trail来到了Flat Rock。</p><img src="/2024/06/09/asplos24-san-diego/SD-Torrey-Pines-6.jpg" class=""><p>悬崖边有很多小黄花。</p><img src="/2024/06/09/asplos24-san-diego/SD-Torrey-Pines-7.jpg" class=""><img src="/2024/06/09/asplos24-san-diego/SD-Torrey-Pines-8.jpg" class=""><img src="/2024/06/09/asplos24-san-diego/SD-Torrey-Pines-9.jpg" class=""><p>然后沿路返回停车场，最后准时抵达机场，踏上返回伊萨卡的归途。</p><h1 id="起始与终结"><a href="#起始与终结" class="headerlink" title="起始与终结"></a>起始与终结</h1><p>在和Google实习的host开会商量投什么会议的时候，看到ASPLOS’24在圣地亚哥，当时就感受到了某种命运（笑）。本科时候其实没有想过要读博，一直想着来美国读个1.5年左右的硕士然后去湾区工作，结果一不小心差点被送去异世界。死里逃生后为了申请到较好的硕士项目，听了同学的建议，利用多出来的一年时间去做科研，运气不错很快出了成果，还申请到了奖学金，在申请季的尾巴去圣地亚哥参加学术会议。虽然人生地不熟，一个人来参会谁都不认识，但会场上还是遇到了复数交大校友，某晚颁奖典礼后其中一个学长还拉着我去和在招揽博士生的新晋教授聊天，被灌输了读Ph.D.的种种好处，于是乎我回国之后多交了几份申请，人生轨迹也就这么稀里糊涂地改变了。</p><p>人生确实是难以预料的，高中填高考志愿的时候也没怎么考虑过大学时候会发生的种种“意外”，既没想到没去成UMich，更没想到差点转生去了异世界，更更没想到最后去了和《奥德赛》中主角奥德修斯的故乡同名的美国小村伊萨卡读博。读博期间在伊萨卡痛苦挣扎之时，也想过很多次，当年要是去CMU读个MCDS的Master就去上班的IF，毕竟也是我年轻时候在闵行苦苦挣扎时候的梦想。也想过要是早几年去湾区上班我是不是就会爱上美国的生活？毕竟人生的前二十多年基本都是在为了去美国上学然后工作而努力。现在看来可谓是<em>苦海泛起爱恨，在世间难逃避命运.jpg</em>。</p><blockquote><p>Keep Ithaka always in your mind.<br>Arriving there is what you’re destined for.<br>But don’t hurry the journey at all.</p></blockquote><p>五年时间一转眼就过去了，Ph.D.漫长旅途也即将抵达终点，博士期间最后一次参加学术会议也是在圣地亚哥，我的起始与终结之地，这大概就是所谓的命运吧。最后虽然有许多感慨，但大多也都很难付诸文字。这一路走来经历了很多，走了不少弯路，渡过一个又一个难关。在这段旅途临近终点之处回首，当年很多的痛苦也不过付诸一笑，过去的就让它过去吧。</p><p>不久后就要回国开启人生的下一段旅途了，珍惜在伊萨卡的最后这段时间，然后走完这Ph.D.之旅的最后的一段路吧。</p>]]></content>
    
    
    <summary type="html">&lt;p&gt;圣地亚哥对我而言也算是有特殊意义的城市了，六年前在申请季步入尾声之时，从大洋彼岸飞过来参加ICCAD，误打误撞开启了Ph.D.之旅。现如今在漫长旅途接近终点之时，从伊萨卡再次重返这座城市参加ASPLOS，不禁有种“君以此始，必以此终”的宿命感。&lt;/p&gt;</summary>
    
    
    
    <category term="Life" scheme="https://blog.zzhou612.com/categories/Life/"/>
    
    <category term="Newfound Adventure" scheme="https://blog.zzhou612.com/categories/Life/Newfound-Adventure/"/>
    
    
    <category term="United States" scheme="https://blog.zzhou612.com/tags/United-States/"/>
    
    <category term="San Diego" scheme="https://blog.zzhou612.com/tags/San-Diego/"/>
    
    <category term="ASPLOS" scheme="https://blog.zzhou612.com/tags/ASPLOS/"/>
    
  </entry>
  
  <entry>
    <title>HPCA 2024@Edinburgh</title>
    <link href="https://blog.zzhou612.com/2024/03/12/hpca24-edinburgh/"/>
    <id>https://blog.zzhou612.com/2024/03/12/hpca24-edinburgh/</id>
    <published>2024-03-12T09:18:13.000Z</published>
    <updated>2024-03-12T09:18:13.000Z</updated>
    
    <content type="html"><![CDATA[<p>今年三月初有幸去爱丁堡参加HPCA 2024<del>公费旅游</del>，因为是和PPoPP，CGO一起举办，还是蛮热闹的。虽然我除了present论文和听了几个keynotes之外大多数时间不是在宾馆补觉就是在爱丁堡的大街小巷闲逛拍照片探店，难得出趟门，还是记录一下。</p><span id="more"></span><h1 id="逃跑路线"><a href="#逃跑路线" class="headerlink" title="逃跑路线"></a>逃跑路线</h1><p>提前订好Ithaca➡️Newark➡️Edinburgh的机票，去程行李在伊萨卡托运直达爱丁堡，返程行李在纽瓦克要取出来再次托运，但也非常方便。不得不说纽瓦克机场结构上吊打JFK，换乘&#x2F;转机方便太多，海关基本不用排队，丝滑入关，和JFK层层叠叠望不见头的队伍形成鲜明对比。</p><p>读博期间没怎么出过🇺🇸，所以过海关的时候总有些紧张，然而每次都是前面的B签大哥大姐们被细细盘问，到了我就是：</p><blockquote><p>Me: (Hand over I-20 and passport)<br>Officer: Cornell?<br>Me: Yes.<br>Officer: Have a nice day!</p></blockquote><p>祝你生活愉快，再见！秒过。只能说希望未来也能如此吧，何苦为难留学生。</p><h1 id="一些笔记"><a href="#一些笔记" class="headerlink" title="一些笔记"></a>一些笔记</h1><p>爱丁堡确实不大，交通也很方便，落地的时候没多想就打了Uber去宾馆事后发现好贵<del>虽然可以报销</del>，回程的时候一大早坐Air Express大巴去机场就非常便宜而且也很方便。会场EICC在市中心，周围的酒店也都很近，属于迈开腿走两步的距离，所以其实拖着箱子走到公交站去机场就可以了。</p><p>用Airalo上买的esim流量卡就可以愉快link start（下次记得不用买10GiB的，根本用不完）。公交车都可以直接Google Wallet进行一个touch &amp; pay非常方便，每个设备的每日扣款额度也有上限，所以没必要买一日通票。</p><p>用Google Timeline查了下某日在爱丁堡做街溜子进行布朗运动的轨迹：</p><img src="/2024/03/12/hpca24-edinburgh/Google-Timeline.png" class=""><p>城市确实不大，随便转转主要景点基本都可以踩到。</p><h1 id="照骗"><a href="#照骗" class="headerlink" title="照骗"></a>照骗</h1><div class="justified-gallery"><img src="/2024/03/12/hpca24-edinburgh/Vennel-Viewpoint.jpg" class=""><img src="/2024/03/12/hpca24-edinburgh/Vennel-Viewpoint-Night.jpg" class=""><img src="/2024/03/12/hpca24-edinburgh/Telephone-Booth.jpg" class=""><img src="/2024/03/12/hpca24-edinburgh/Victoria-Street-1.jpg" class=""><!-- <img src="/2024/03/12/hpca24-edinburgh/Victoria-Street-2.jpg" class=""> --><img src="/2024/03/12/hpca24-edinburgh/Victoria-Street-3.jpg" class=""><img src="/2024/03/12/hpca24-edinburgh/Victoria-Street-Night.jpg" class=""><img src="/2024/03/12/hpca24-edinburgh/Royal-Mile-1.jpg" class=""><img src="/2024/03/12/hpca24-edinburgh/Scottish-Bagpipes.jpg" class=""><img src="/2024/03/12/hpca24-edinburgh/Advocates-Close.jpg" class=""><img src="/2024/03/12/hpca24-edinburgh/Royal-Mile-2.jpg" class=""><img src="/2024/03/12/hpca24-edinburgh/Cockburn-Street.jpg" class=""><img src="/2024/03/12/hpca24-edinburgh/Waverley-Bridge.jpg" class=""><img src="/2024/03/12/hpca24-edinburgh/Scott-Monument.jpg" class=""><img src="/2024/03/12/hpca24-edinburgh/Calton-Hill-1.jpg" class=""><img src="/2024/03/12/hpca24-edinburgh/Calton-Hill-2.jpg" class=""><img src="/2024/03/12/hpca24-edinburgh/Calton-Hill-3.jpg" class=""><img src="/2024/03/12/hpca24-edinburgh/National-Monument-of-Scotland.jpg" class=""><img src="/2024/03/12/hpca24-edinburgh/Nelson-Monument.jpg" class=""><img src="/2024/03/12/hpca24-edinburgh/Leith-Street.jpg" class=""></div><p>闲逛时拍了不少照片，用Lightroom简单处理了一下，导出jpg的时候长边压到了3000px（a7RV的像素实在太高了），先试试Justified Gallery的照片墙效果。不得不说爱丁堡风景确实不错，欧洲的小城市就是漂亮啊。</p><p>The Vennel Viewpoint白天的样子。</p><img src="/2024/03/12/hpca24-edinburgh/Vennel-Viewpoint.jpg" class=""><p>晚上也去拍了张照片，没带三脚架，全靠防抖，凑活看看。</p><img src="/2024/03/12/hpca24-edinburgh/Vennel-Viewpoint-Night.jpg" class=""><p>路边随处可见的报废电话亭。</p><img src="/2024/03/12/hpca24-edinburgh/Telephone-Booth.jpg" class=""><p>Victoria Street and West Bow，J.K.罗琳当年在这条街上的The Elephant House咖啡馆写《哈利波特》。</p><img src="/2024/03/12/hpca24-edinburgh/Victoria-Street-1.jpg" class=""><img src="/2024/03/12/hpca24-edinburgh/Victoria-Street-2.jpg" class=""><p>后方更高的楼层在施工，不然可以爬到更高处俯瞰五颜六色的门店。</p><img src="/2024/03/12/hpca24-edinburgh/Victoria-Street-3.jpg" class=""><p>晚上的维多利亚街在灯光&#x2F;光影的点缀下也别有一番风味，HPCA的官网也用了这里的夜景照片作为banner之一。</p><img src="/2024/03/12/hpca24-edinburgh/Victoria-Street-Night.jpg" class=""><p>沿着Royal Mile皇家一英里走了走，首先映入眼帘的是St Giles’ Cathedral。</p><img src="/2024/03/12/hpca24-edinburgh/Royal-Mile-1.jpg" class=""><p>沿途有不少吹苏格兰风笛的人，我对Scottish Bagpipes的印象来源于<em>Braveheart</em>这部瞎改史实的“史诗”电影，苏格兰短裙则要上溯到小时候看春晚小沈阳的节目的久远记忆了。</p><img src="/2024/03/12/hpca24-edinburgh/Scottish-Bagpipes.jpg" class=""><p>St Giles’ Cathedral对面的Advocates Close能透过小巷看到远处的Scott Monument。</p><img src="/2024/03/12/hpca24-edinburgh/Advocates-Close.jpg" class=""><p>走啊走。</p><img src="/2024/03/12/hpca24-edinburgh/Royal-Mile-2.jpg" class=""><p>转个弯来到Cockburn Street，太阳总算是从云层里稍微出来一点。我还算运气不错，来爱丁堡开会的几天都没怎么下雨，但也基本一直多云，所以光线条件很糟糕，拍的照片大多背光&#x2F;阴影欠曝，最后全靠后期把RAW格式照片的阴影部分拉起来。</p><img src="/2024/03/12/hpca24-edinburgh/Cockburn-Street.jpg" class=""><p>Cockburn Street走出来就是Waverley Bridge，感觉这里下午不逆光的时候应该是个出片的好地方，晚上灯亮起来夜景也应该很不错，可惜我是上午去的。</p><img src="/2024/03/12/hpca24-edinburgh/Waverley-Bridge.jpg" class=""><p>过了Waverley Bridge就能看到Scott Monument，对着正对面的街上的公交站玻璃拍了张双塔<del>奇兵</del>。</p><img src="/2024/03/12/hpca24-edinburgh/Scott-Monument.jpg" class=""><p>一路走到Calton Hill俯瞰爱丁堡。</p><img src="/2024/03/12/hpca24-edinburgh/Calton-Hill-1.jpg" class=""><img src="/2024/03/12/hpca24-edinburgh/Calton-Hill-2.jpg" class=""><img src="/2024/03/12/hpca24-edinburgh/Calton-Hill-3.jpg" class=""><p>卡尔顿山上还有个National Monument of Scotland，似乎是纪念拿破仑战争中牺牲的参战的苏格兰士兵的，我想了半天也没想出来拿破仑战争中有什么希腊要素，所以为什么要山寨帕特农神庙啊？最搞笑的是还没盖多少就烂尾了。</p><img src="/2024/03/12/hpca24-edinburgh/National-Monument-of-Scotland.jpg" class=""><p>Nelson Monument本来应该能上去的，但最近似乎关闭了，话说纳尔逊是英格兰人吧（画外音：<em>England expects that every man will do his duty</em>）为啥在爱丁堡山头搞个纪念塔。远方还能看到Arthur’s Seat，似乎是个hiking的好去处，可惜我太懒了没有去爬，下次一定。以及a7RV解析力确实震撼，原图的话在原尺寸下甚至能数清亚瑟王座山头上有几个人。</p><img src="/2024/03/12/hpca24-edinburgh/Nelson-Monument.jpg" class=""><p>回程去公交站的路上随手拍了一张，似乎是在Leith Street。</p><img src="/2024/03/12/hpca24-edinburgh/Leith-Street.jpg" class=""><h1 id="最后的吐槽"><a href="#最后的吐槽" class="headerlink" title="最后的吐槽"></a>最后的吐槽</h1><p>虽然只是一点流水账，但我没咕咕而是时隔N年后重启了Blog，升级了<code>nodejs</code>和<code>hexo</code>的版本，整理并导出了照片，还写完并publish了这篇post，我觉得我已经很棒了。之后有时间的话还是整理整理照片随便记录些什么吧，就算是些没什么营养的文字和游客照，留作纪念，日后再看的时候也能回想起这段旅途。这些年的Ph.D.之旅可能有点过于摧残人心，以至于Blog停更，用<code>mdbook</code>写日记的频率也越来越低（虽然下滑到了月记，但还是持续了快五年，已经很不错了！），最近有resurrection的计划<del>堂堂复活</del>，把过去的一些爱好和习惯重新捡起来，还不算太晚。最后希望能顺利走完接下来这段路，顺利抵达漫长旅途的终点吧。</p>]]></content>
    
    
    <summary type="html">&lt;p&gt;今年三月初有幸去爱丁堡参加HPCA 2024&lt;del&gt;公费旅游&lt;/del&gt;，因为是和PPoPP，CGO一起举办，还是蛮热闹的。虽然我除了present论文和听了几个keynotes之外大多数时间不是在宾馆补觉就是在爱丁堡的大街小巷闲逛拍照片探店，难得出趟门，还是记录一下。&lt;/p&gt;</summary>
    
    
    
    <category term="Life" scheme="https://blog.zzhou612.com/categories/Life/"/>
    
    <category term="Newfound Adventure" scheme="https://blog.zzhou612.com/categories/Life/Newfound-Adventure/"/>
    
    
    <category term="United Kingdom" scheme="https://blog.zzhou612.com/tags/United-Kingdom/"/>
    
    <category term="Edinburgh" scheme="https://blog.zzhou612.com/tags/Edinburgh/"/>
    
    <category term="HPCA" scheme="https://blog.zzhou612.com/tags/HPCA/"/>
    
  </entry>
  
  <entry>
    <title>异度之刃2通关感言</title>
    <link href="https://blog.zzhou612.com/2022/07/29/xb2-review/"/>
    <id>https://blog.zzhou612.com/2022/07/29/xb2-review/</id>
    <published>2022-07-29T15:36:12.000Z</published>
    <updated>2022-07-29T15:36:12.000Z</updated>
    
    <content type="html"><![CDATA[<p>最近闲来无事通关了《异度之刃2》（一周目），随手写点感想。</p><span id="more"></span><img src="/2022/07/29/xb2-review/xb2.png" class=""><h1 id="游戏性"><a href="#游戏性" class="headerlink" title="游戏性"></a>游戏性</h1><p>先说缺点，地图引导和战斗教程做的实在是烂，烂到足以劝退玩家的级别。但地图本身设计的还是可圈可点，收集要素很多，也有足够的可探索性，在机能受限的情况下还是做出了许多能让玩家眼前一亮的绝境。而随着剧情的推进，战斗系统的全貌逐渐展现出来，不得不说“挂球破球”和“素质四连”学会之后，这个战斗系统玩起来还是有着足够深度以及相当的爽快感。游戏本身也算是量大管饱，虽然据说当时开发后期MONOLITH的人都被任天堂抽调走去做《荒野之息》了，导致后期内容略显赶工，但总的来说内容还是非常充实的。</p><h1 id="画面与音乐"><a href="#画面与音乐" class="headerlink" title="画面与音乐"></a>画面与音乐</h1><p>毕竟是Switch游戏，受限于机能，画面表现自然无法和BN的《破晓传说》之类的比，但这里还是要引用一下IGN编辑对FF14 6.0评测中的一段话：</p><blockquote><p>Good art direction and sound design sometimes outdo games that need a mythical GeForce RTX 3090 to run properly.</p></blockquote><p>优秀的艺术指导和音乐设计有时能胜过一些需要神奇的GeForce RTX 3090才能正常运行的游戏，我深以为然。虽然我还是觉得任天堂确实该更新一下Switch这个电子垃圾的配置（起码能做到稳1080P 30帧吧），但不得不说即使是在受限的机能下，带着镣铐跳舞，XB2的表现依然出彩。优秀的美术，演出和配乐使得即时演算的过场CG十分精彩，完全可以当番剧看（笑）。焰和光初次登场无比惊艳，以及“崭新的利刃”小绿觉醒，等等，不得不说确实有点水平。游戏本身美术也很出色，第一次来到英维迪亚烈腹部这张图的时候，巨神兽内部广阔空间中漫天飞舞的樱花雨确实惊艳到了我。可收集的异刃们虽然从立绘到建模质量都参差不齐，但主要角色Saitom老师的人设只能说都太香了（我永远喜欢，以下略）。配乐方面，光田康典，永远的神，《夢の中の楽園》《在りし日のふたり》《Drifting Soul》《君との未来》《One Last You》，平松建治的反击曲《Counterattack》，精英怪战斗曲《さらに名を冠する者たち》，地图BGM《グーラ領&#x2F;森林》《インヴィディア烈王国&#x2F;夜》等等等，只能说优秀的配乐确实是JRPG不可分割的一部分。</p><h1 id="剧情与Happy-Ending"><a href="#剧情与Happy-Ending" class="headerlink" title="剧情与Happy Ending"></a>剧情与Happy Ending</h1><p>关于剧情，虽然有些“桥段”也让人蚌埠住，部分反派的塑造也有点糟糕（灭是真的low穿地心），但总体上瑕不掩瑜。作为一个BMG故事，由于光焰的塑造实在太香了，确实可以让我选择性忽略很多剧情上的瑕疵。至于最后的Happy Ending，之前也看到过中文翻译的高桥哲哉关于结局的访谈，大致就是说本来想做成核心水晶开始闪烁就戛然而止的“开放式结局”，但最后想到玩家玩了这么久，经历了这么多波折，最后还是给玩家一个两个老婆都回来的完美的好结局作为奖励吧。由于并没有标出出处，我搜了好久也没搜到原文，一度以为是假新闻，最后才发现原来是<a href="https://www.nintendolife.com/news/2018/09/feature_xenoblade_chronicles_2_team_talk_torna_female_blades_and_the_ending_that_never_made_it"><code>Nintendo Life</code></a>的英文访谈。</p><blockquote><p><strong>At the end of Xenoblade Chronicles 2, Pyra and Mythra sacrifice themselves to save Rex, only to appear alive later on. Can you tell us what happened and what happens to them following the ending?</strong><br><strong>Takahashi:</strong> [Laughter] Originally we envisioned the ending sort of in an Inception-style where you would see a cutscene with Rex’s core crystal glowing, and that would be the end of the game. But, while making the final scenes of the game, I really thought we should give players a clearer sense of closure, and I really started to come around to the feeling of ending the game on a happier note. The players have been through this incredibly long, trying the experience of completing the game, so why not give them a happier note to finish on? So we thought, “Well, okay, we’ll bring back Pyra or Mythra, which one should we use? Or maybe we’ll bring back—what’s her name? The green-haired one.” In any case, we thought about ending the game with one of these female characters joining Rex again, but I decided to roll with the feeling of a happy ending of sorts and thought as a bonus why not bring both Pyra and Mythra back as a bonus for the player at the end of the game?</p></blockquote><p>相较于一些沉迷于自我陶醉与自我感动的游戏制作人（比如某“电子游戏的奇迹”），高桥哲哉无疑还是相当重视fan service的。我本身到也不排斥非HE，《最终幻想X》也一直是我最喜欢的JRPG之一，但这些年或许是遭受了不少自我陶醉式的，为了折磨观众&#x2F;读者&#x2F;玩家而强行BE作品的毒打，心态也有了些变化，XB2能玩到这么圆满的结局，真的十分满足，谢谢你高桥哥哥。经过漫长的旅途，在故事的最后，伴随着“One Last You”的旋律，于是少年遇到了少女，让人觉得这一切都是值得的。</p>]]></content>
    
    
    <summary type="html">&lt;p&gt;最近闲来无事通关了《异度之刃2》（一周目），随手写点感想。&lt;/p&gt;</summary>
    
    
    
    <category term="Life" scheme="https://blog.zzhou612.com/categories/Life/"/>
    
    <category term="No Game, No Life" scheme="https://blog.zzhou612.com/categories/Life/No-Game-No-Life/"/>
    
    
    <category term="JRPG" scheme="https://blog.zzhou612.com/tags/JRPG/"/>
    
  </entry>
  
  <entry>
    <title>Using mdBook to Keep a Personal Diary</title>
    <link href="https://blog.zzhou612.com/2019/10/20/using-mdbook-to-keep-a-personal-diary/"/>
    <id>https://blog.zzhou612.com/2019/10/20/using-mdbook-to-keep-a-personal-diary/</id>
    <published>2019-10-20T14:08:44.000Z</published>
    <updated>2019-10-20T14:08:44.000Z</updated>
    
    <content type="html"><![CDATA[<p>I have not updated my blog for a <strong>LONG</strong> time. It seems that my blog is on the edge of distinction again <del>history repeats itself</del>. The post <em>Twenty Two Plus Plus</em> in memory of my undergraduate years has been staying in the <code>_drafts</code> folder for nearly three months. I <strong>NEED</strong> to finish it before it is too late <del>24歳、学生です</del>.</p><p>The underlying reason is quite simple <del>another new excuse I made to justify my laziness</del>: I was struggling with graduation last summer semester. After I arrived at Ithaca, I found a new way to keep a personal diary&#x2F;journal. I had tried lots of tools, including paper textbooks, Word, DayOne, OneNote, etc., to help myself keep a personal diary since I was a little boy. None of these attempts lasted for more than two months. But for now, I have successfully kept a diary for two months. Thanks to <code>mdbook</code>: <em>Create book from markdown files. Like Gitbook but implemented in Rust</em>.</p><span id="more"></span><p>Third-party applications are not reliable enough to keep a personal diary. Rich-text editors are just too troublesome for maintaining the diary. So I looked for open-source tools to help me write a book in Markdown. At first, I considered using GitBook. I thought it was an open-source project backed by GitHub. But it was not. <code>gitbook-cli</code> was abandoned and GitBook no longer provides offline services. Well, that sounds like “GitBook has committed suicide” to me.</p><p>Finally, I found <code>mdBook</code>, a perfect alternative.</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br></pre></td><td class="code"><pre><span class="line">$ brew install rustup-init</span><br><span class="line">$ rustup-init</span><br><span class="line">$ rustc --version</span><br><span class="line">$ cargo install mdbook</span><br><span class="line">$ <span class="built_in">mkdir</span> 2019 &amp;&amp; <span class="built_in">cd</span> 2019</span><br><span class="line">$ mdbook init</span><br><span class="line"></span><br><span class="line">2019/</span><br><span class="line">├── book</span><br><span class="line">└── src</span><br><span class="line">    ├── chapter_1.md</span><br><span class="line">    └── SUMMARY.md</span><br><span class="line"></span><br><span class="line">$ vim SUMMARY.md</span><br></pre></td></tr></table></figure><figure class="highlight markdown"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br></pre></td><td class="code"><pre><span class="line"><span class="section"># Summary</span></span><br><span class="line"></span><br><span class="line">[<span class="string">Prefix</span>](<span class="link">Prefix.md</span>)</span><br><span class="line"></span><br><span class="line"><span class="bullet">-</span> [<span class="string">August</span>](<span class="link">August/August.md</span>)</span><br><span class="line"><span class="bullet">    *</span> [<span class="string">Thursday, August 29</span>](<span class="link">August/08-29.md</span>)</span><br><span class="line"><span class="bullet">    *</span> [<span class="string">Friday, August 30</span>](<span class="link">August/08-30.md</span>)</span><br><span class="line"><span class="bullet">    *</span> [<span class="string">Saturday, August 31</span>](<span class="link">August/08-31.md</span>)</span><br><span class="line"></span><br><span class="line"><span class="bullet">-</span> [<span class="string">September</span>](<span class="link">September/September.md</span>)</span><br><span class="line"><span class="bullet">    *</span> [<span class="string">Sunday, September 1</span>](<span class="link">September/09-01.md</span>)</span><br><span class="line"><span class="bullet">    *</span> [<span class="string">Monday, September 2</span>](<span class="link">September/09-02.md</span>)</span><br><span class="line"><span class="bullet">    *</span> [<span class="string">Tuesday, September 3</span>](<span class="link">September/09-03.md</span>)</span><br><span class="line"><span class="bullet">    *</span> [<span class="string">Wednesday, September 4</span>](<span class="link">September/09-04.md</span>)</span><br><span class="line"><span class="bullet">    *</span> [<span class="string">Thursday, September 5</span>](<span class="link">September/09-05.md</span>)</span><br><span class="line"><span class="bullet">    *</span> [<span class="string">Friday, September 6</span>](<span class="link">September/09-06.md</span>)</span><br><span class="line"><span class="bullet">    *</span> [<span class="string">Saturday, September 7</span>](<span class="link">September/09-07.md</span>)</span><br><span class="line"><span class="bullet">    *</span> [<span class="string">Sunday, September 8</span>](<span class="link">September/09-08.md</span>)</span><br><span class="line">...</span><br></pre></td></tr></table></figure><p>All set! <del>I will try to update my blog soon.</del></p>]]></content>
    
    
    <summary type="html">&lt;p&gt;I have not updated my blog for a &lt;strong&gt;LONG&lt;/strong&gt; time. It seems that my blog is on the edge of distinction again &lt;del&gt;history repeats itself&lt;/del&gt;. The post &lt;em&gt;Twenty Two Plus Plus&lt;/em&gt; in memory of my undergraduate years has been staying in the &lt;code&gt;_drafts&lt;/code&gt; folder for nearly three months. I &lt;strong&gt;NEED&lt;/strong&gt; to finish it before it is too late &lt;del&gt;24歳、学生です&lt;/del&gt;.&lt;/p&gt;
&lt;p&gt;The underlying reason is quite simple &lt;del&gt;another new excuse I made to justify my laziness&lt;/del&gt;: I was struggling with graduation last summer semester. After I arrived at Ithaca, I found a new way to keep a personal diary&amp;#x2F;journal. I had tried lots of tools, including paper textbooks, Word, DayOne, OneNote, etc., to help myself keep a personal diary since I was a little boy. None of these attempts lasted for more than two months. But for now, I have successfully kept a diary for two months. Thanks to &lt;code&gt;mdbook&lt;/code&gt;: &lt;em&gt;Create book from markdown files. Like Gitbook but implemented in Rust&lt;/em&gt;.&lt;/p&gt;</summary>
    
    
    
    <category term="Tech" scheme="https://blog.zzhou612.com/categories/Tech/"/>
    
    <category term="Nest of Coding Wisdom" scheme="https://blog.zzhou612.com/categories/Tech/Nest-of-Coding-Wisdom/"/>
    
    
    <category term="mdBook" scheme="https://blog.zzhou612.com/tags/mdBook/"/>
    
    <category term="Markdown" scheme="https://blog.zzhou612.com/tags/Markdown/"/>
    
  </entry>
  
  <entry>
    <title>MIT 6.828 Toolchains Setup on macOS</title>
    <link href="https://blog.zzhou612.com/2019/03/09/mit-6-828-toolchains-setup-on-macos/"/>
    <id>https://blog.zzhou612.com/2019/03/09/mit-6-828-toolchains-setup-on-macos/</id>
    <published>2019-03-09T07:39:32.000Z</published>
    <updated>2019-03-09T07:39:32.000Z</updated>
    
    <content type="html"><![CDATA[<p>There are many tutorials and posts introducing environment setup for the prominent operating system course MIT 6.828. However, most of them do not target at macOS. Even if some of them do, they often choose to directly compile and install the related tools without using any package management technique to keep everything clean.</p><p>After searching on the Internet for quite a while, I finally found a promising solution: By creating one’s own Homebrew tap, toolchains for 6.828 could be deployed swiftly &amp; cleanly.</p><span id="more"></span><p>In the Lab Tools guide for <a href="https://courses.cs.washington.edu/courses/cse451/18au/labs/tools.html">CSE 451: Operating System</a> in the University of Washington, <a href="https://homes.cs.washington.edu/~xi">Prof. Xi Wang</a> shows how to install the toolchains on macOS using his Homebrew tap hosted on GitHub.</p><blockquote><p>Give a man a fish, and you feed him for a day. Teach a man to fish, and you feed him for a lifetime.</p></blockquote><ul><li><a href="https://github.com/xiw/homebrew-jos">Link</a> to Wang’s Homebrew tap.</li><li>How to adds more repositories to the list of formulae that brew tracks: <a href="https://docs.brew.sh/Taps">Taps (third-party repositories)</a>.</li><li>How to create one’s own package: <a href="https://docs.brew.sh/Formula-Cookbook">Formula Cookbook</a>.</li></ul><p>I mirrored the repository, standardized the directory structure, and updated the versions of <code>gcc</code>, <code>bintuils</code>, <code>qemu</code> and <code>gdb</code>. So the up-to-date versions of the toolchains could be installed with the following command:</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">$ brew tap zzhou612/jos</span><br><span class="line">$ brew install --HEAD i386-jos-elf-qemu</span><br><span class="line">$ brew install i386-jos-elf-binutils i386-jos-elf-gcc i386-jos-elf-gdb</span><br></pre></td></tr></table></figure><p>It should be noticed that in the <code>GNUmakefile</code> of <code>jos</code>:</p><figure class="highlight makefile"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="section">gdb:</span></span><br><span class="line">    gdb -n -x .gdbinit</span><br></pre></td></tr></table></figure><p>Since we have compiled &amp; installed <code>i386-jos-elf-qemu</code>, the <code>GNUmakefile</code> needs to be modified so that <code>make gdb</code> command could work properly:</p><figure class="highlight makefile"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="section">gdb:</span></span><br><span class="line">    i386-jos-elf-qemu -n -x .gdbinit</span><br></pre></td></tr></table></figure><p>Then you could start on the lab projects straight away.</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">$ make qemu</span><br></pre></td></tr></table></figure><img src="/2019/03/09/mit-6-828-toolchains-setup-on-macos/qemu.png" class="" title="make qemu"><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">$ make qemu-nox</span><br></pre></td></tr></table></figure><img src="/2019/03/09/mit-6-828-toolchains-setup-on-macos/qemu-nox.png" class="" title="make qemu-nox">]]></content>
    
    
    <summary type="html">&lt;p&gt;There are many tutorials and posts introducing environment setup for the prominent operating system course MIT 6.828. However, most of them do not target at macOS. Even if some of them do, they often choose to directly compile and install the related tools without using any package management technique to keep everything clean.&lt;/p&gt;
&lt;p&gt;After searching on the Internet for quite a while, I finally found a promising solution: By creating one’s own Homebrew tap, toolchains for 6.828 could be deployed swiftly &amp;amp; cleanly.&lt;/p&gt;</summary>
    
    
    
    <category term="Tech" scheme="https://blog.zzhou612.com/categories/Tech/"/>
    
    <category term="Nest of Coding Wisdom" scheme="https://blog.zzhou612.com/categories/Tech/Nest-of-Coding-Wisdom/"/>
    
    
    <category term="Homebrew" scheme="https://blog.zzhou612.com/tags/Homebrew/"/>
    
  </entry>
  
  <entry>
    <title>Automatically Sign Commits Using GPG Suite on macOS</title>
    <link href="https://blog.zzhou612.com/2019/02/26/automatically-sign-commits-using-gpg-suite-on-macos/"/>
    <id>https://blog.zzhou612.com/2019/02/26/automatically-sign-commits-using-gpg-suite-on-macos/</id>
    <published>2019-02-26T06:12:45.000Z</published>
    <updated>2019-02-26T06:12:45.000Z</updated>
    
    <content type="html"><![CDATA[<p>To make my commits marked as “verified” on GitHub, I tried to sign them locally using GPG. It worked fine using the following command line command:</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">&gt; git commit -S -m your commit message</span><br></pre></td></tr></table></figure><p>But when I tried to sign commits within JetBrains IDEs, like Clion, things did not work out so easily. JetBrains IDEs do not provide native supports&#x2F;integrations for GPG. So I need to make use of GPG Suite to sign commits automatically without being prompted for password from the terminal. This post records how to do so.</p><span id="more"></span><h1 id="Installing-GPG-Suite"><a href="#Installing-GPG-Suite" class="headerlink" title="Installing GPG Suite"></a>Installing GPG Suite</h1><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">&gt; brew cask install gpg-suite</span><br><span class="line">&gt; brew cask install gpg-suite-pinentry</span><br></pre></td></tr></table></figure><h1 id="Generating-a-GPG-key"><a href="#Generating-a-GPG-key" class="headerlink" title="Generating a GPG key"></a>Generating a GPG key</h1><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">&gt; gpg --full-generate-key</span><br></pre></td></tr></table></figure><p>Choose <code>RSA and RSA</code> for encryption method, <code>4096</code> for key size.</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br></pre></td><td class="code"><pre><span class="line">&gt; gpg --list-secret-keys --keyid-format LONG</span><br><span class="line">/Users/zzhou612/.gnupg/pubring.kbx</span><br><span class="line">----------------------------------</span><br><span class="line">sec   rsa4096/B31AD9AD2B5CFABD 2019-02-22 [SC]</span><br><span class="line">      ...</span><br><span class="line">uid   [ultimate] Nathan Zhou (GitHub key) &lt;zzhou612@gmail.com&gt;</span><br><span class="line">ssb   rsa4096/... 2019-02-22 [E]</span><br><span class="line">&gt; gpg --armor --<span class="built_in">export</span> B31AD9AD2B5CFABD</span><br><span class="line"><span class="comment"># Prints the GPG key ID, in ASCII armor format</span></span><br></pre></td></tr></table></figure><p>Copy the GPG key, beginning with <code>-----BEGIN PGP PUBLIC KEY BLOCK-----</code> and ending with <code>-----END PGP PUBLIC KEY BLOCK-----</code>. Add the GPG key to  GitHub account.</p><h1 id="Configuring-Automated-Signing"><a href="#Configuring-Automated-Signing" class="headerlink" title="Configuring Automated Signing"></a>Configuring Automated Signing</h1><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br></pre></td><td class="code"><pre><span class="line">&gt; git config --global user.signingkey B31AD9AD2B5CFABD</span><br><span class="line">&gt; git config --global commit.gpgsign <span class="literal">true</span></span><br><span class="line">&gt; git config --list</span><br><span class="line">...</span><br><span class="line">user.signingkey=B31AD9AD2B5CFABD</span><br><span class="line">commit.gpgsign=<span class="literal">true</span></span><br><span class="line">&gt; vim ~/.gnupg/gpg.conf</span><br><span class="line">...</span><br><span class="line">no-tty</span><br><span class="line">use-agent</span><br></pre></td></tr></table></figure><p>Add <code>export GPG_TTY=$(tty)</code> to <code>.zshrc</code>, <code>.bashrc</code> and etc.</p><blockquote><p>When you store a password in macOS keychain, pinentry, the program used to ask for your password, will never again ask for that password. macOS will remember this password and automatically use it when needed. That means you will no longer see the pinentry dialog querying for your password. The password is protected with your macOS user password. </p></blockquote><p>Choose ‘Store in OS X Keychain’ option when the pinentry dialog asks for the password.</p><img src="/2019/02/26/automatically-sign-commits-using-gpg-suite-on-macos/pinentry.png" class="">]]></content>
    
    
    <summary type="html">&lt;p&gt;To make my commits marked as “verified” on GitHub, I tried to sign them locally using GPG. It worked fine using the following command line command:&lt;/p&gt;
&lt;figure class=&quot;highlight bash&quot;&gt;&lt;table&gt;&lt;tr&gt;&lt;td class=&quot;gutter&quot;&gt;&lt;pre&gt;&lt;span class=&quot;line&quot;&gt;1&lt;/span&gt;&lt;br&gt;&lt;/pre&gt;&lt;/td&gt;&lt;td class=&quot;code&quot;&gt;&lt;pre&gt;&lt;span class=&quot;line&quot;&gt;&amp;gt; git commit -S -m your commit message&lt;/span&gt;&lt;br&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;&lt;/figure&gt;

&lt;p&gt;But when I tried to sign commits within JetBrains IDEs, like Clion, things did not work out so easily. JetBrains IDEs do not provide native supports&amp;#x2F;integrations for GPG. So I need to make use of GPG Suite to sign commits automatically without being prompted for password from the terminal. This post records how to do so.&lt;/p&gt;</summary>
    
    
    
    <category term="Tech" scheme="https://blog.zzhou612.com/categories/Tech/"/>
    
    <category term="Nest of Coding Wisdom" scheme="https://blog.zzhou612.com/categories/Tech/Nest-of-Coding-Wisdom/"/>
    
    
    <category term="GnuPG" scheme="https://blog.zzhou612.com/tags/GnuPG/"/>
    
    <category term="Git" scheme="https://blog.zzhou612.com/tags/Git/"/>
    
  </entry>
  
  <entry>
    <title>Configure Multiple Users for Shadowsocks-libev</title>
    <link href="https://blog.zzhou612.com/2019/02/15/configure-multiple-users-for-shadowsocks-libev/"/>
    <id>https://blog.zzhou612.com/2019/02/15/configure-multiple-users-for-shadowsocks-libev/</id>
    <published>2019-02-15T12:47:07.000Z</published>
    <updated>2019-02-15T12:47:07.000Z</updated>
    
    <content type="html"><![CDATA[<p>The original Python release of shadowsocks supports multiple users through configuration, by assigning different passwords on multiple ports.</p><figure class="highlight json"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br></pre></td><td class="code"><pre><span class="line"><span class="punctuation">&#123;</span></span><br><span class="line">    <span class="attr">&quot;server&quot;</span><span class="punctuation">:</span> <span class="string">&quot;0.0.0.0&quot;</span><span class="punctuation">,</span></span><br><span class="line">    <span class="attr">&quot;port_password&quot;</span><span class="punctuation">:</span> <span class="punctuation">&#123;</span></span><br><span class="line">        <span class="attr">&quot;8381&quot;</span><span class="punctuation">:</span> <span class="string">&quot;foobar1&quot;</span><span class="punctuation">,</span></span><br><span class="line">        <span class="attr">&quot;8382&quot;</span><span class="punctuation">:</span> <span class="string">&quot;foobar2&quot;</span><span class="punctuation">,</span></span><br><span class="line">        <span class="attr">&quot;8383&quot;</span><span class="punctuation">:</span> <span class="string">&quot;foobar3&quot;</span><span class="punctuation">,</span></span><br><span class="line">        <span class="attr">&quot;8384&quot;</span><span class="punctuation">:</span> <span class="string">&quot;foobar4&quot;</span></span><br><span class="line">    <span class="punctuation">&#125;</span><span class="punctuation">,</span></span><br><span class="line">    <span class="attr">&quot;timeout&quot;</span><span class="punctuation">:</span> <span class="number">300</span><span class="punctuation">,</span></span><br><span class="line">    <span class="attr">&quot;method&quot;</span><span class="punctuation">:</span> <span class="string">&quot;aes-256-cfb&quot;</span></span><br><span class="line"><span class="punctuation">&#125;</span></span><br></pre></td></tr></table></figure><p>Currently I am using <code>shadowsocks-libev</code>, which is the libev port of shadowsocks. And I also need to support the usage of multiple users. <span id="more"></span> According to Madeye’s reply to the GitHub <a href="https://github.com/shadowsocks/shadowsocks-libev/issues/5">Issue</a>, shadowsocks-libev does not support multi-port configuration:</p><blockquote><p>Sorry, we have no plan to support multi port configuration. Actually you can use multiple instances instead. For example:</p></blockquote><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">ss-server -c config1.json -f pid1</span><br><span class="line">ss-server -c config2.json -f pid2</span><br><span class="line">ss-server -c config3.json -f pid3</span><br></pre></td></tr></table></figure><blockquote><p>As the best practice we recommend for <code>shadowsocks-libev</code>, it helps to isolate each user in different processes and reconfigure each user’s port&#x2F;password&#x2F;encryption&#x2F;timeout without reload&#x2F;restart the whole service. Furthermore, this approach enables us to manage users with legacy control panels, for example old SSH &#x2F; VHOST panels with each user’s <code>ss-server</code> running in its own space.</p><p>Compared to other implementations, <code>shadowsocks-libev</code> uses much fewer resources (about 1MB memory and hundreds of file descriptors in a typical usage) . As a result, this kind of multi processes should only introduce slight overhead and even works well for low end boxes.</p></blockquote><p>I choose to use <code>systemctl</code> to manage the <code>systemd</code> instances of <code>shadowsocks-libev</code>. The following template unit files are installed in the <code>/lib/systemd/system</code> directory:</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">shadowsocks-libev-local@.service</span><br><span class="line">shadowsocks-libev-redir@.service</span><br><span class="line">shadowsocks-libev-server@.service</span><br><span class="line">shadowsocks-libev-tunnel@.service</span><br></pre></td></tr></table></figure><p>Take a look at the template unit file <code>shadowsocks-libev-server@.service</code>:</p><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br></pre></td><td class="code"><pre><span class="line">[Unit]</span><br><span class="line">Description=Shadowsocks-Libev Custom Server Service for %I</span><br><span class="line">Documentation=man:ss-server(1)</span><br><span class="line">After=network.target</span><br><span class="line"></span><br><span class="line">[Service]</span><br><span class="line">Type=simple</span><br><span class="line">CapabilityBoundingSet=CAP_NET_BIND_SERVICE</span><br><span class="line">ExecStart=/usr/bin/ss-server -c /etc/shadowsocks-libev/%i.json</span><br><span class="line">User=nobody</span><br><span class="line">Group=nobody</span><br><span class="line">LimitNOFILE=32768</span><br><span class="line"></span><br><span class="line">[Install]</span><br><span class="line">WantedBy=multi-user.target</span><br></pre></td></tr></table></figure><p>With the help of template unit files, service instances could be deployed and managed easily. For example, Cloud and Tifa, two AVALANCHE members, are planning to deploy <code>shadowsocks-libev</code> services on the same VPS to bypass the firewall of Shinra Inc. In this case, they could simply create <code>cloud.json</code> and <code>tifa.json</code> configurations with different ports, passwords and encryption methods in <code>/etc/shadowsocks-libev</code> directory. Then enable and start the <code>systemd</code> services using the following commands: </p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">sudo systemctl <span class="built_in">enable</span> shadowsocks-libev-server@cloud.service --now</span><br><span class="line">sudo systemctl <span class="built_in">enable</span> shadowsocks-libev-server@tifa.service --now</span><br></pre></td></tr></table></figure><p>The status of <code>shadowsocks-libev</code> instances could be checked with the following commands:</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">sudo systemctl status shadowsocks-libev-server@cloud.service</span><br><span class="line">sudo systemctl status shadowsocks-libev-server@tifa.service</span><br></pre></td></tr></table></figure><p>That’s all done. Enjoy! </p>]]></content>
    
    
    <summary type="html">&lt;p&gt;The original Python release of shadowsocks supports multiple users through configuration, by assigning different passwords on multiple ports.&lt;/p&gt;
&lt;figure class=&quot;highlight json&quot;&gt;&lt;table&gt;&lt;tr&gt;&lt;td class=&quot;gutter&quot;&gt;&lt;pre&gt;&lt;span class=&quot;line&quot;&gt;1&lt;/span&gt;&lt;br&gt;&lt;span class=&quot;line&quot;&gt;2&lt;/span&gt;&lt;br&gt;&lt;span class=&quot;line&quot;&gt;3&lt;/span&gt;&lt;br&gt;&lt;span class=&quot;line&quot;&gt;4&lt;/span&gt;&lt;br&gt;&lt;span class=&quot;line&quot;&gt;5&lt;/span&gt;&lt;br&gt;&lt;span class=&quot;line&quot;&gt;6&lt;/span&gt;&lt;br&gt;&lt;span class=&quot;line&quot;&gt;7&lt;/span&gt;&lt;br&gt;&lt;span class=&quot;line&quot;&gt;8&lt;/span&gt;&lt;br&gt;&lt;span class=&quot;line&quot;&gt;9&lt;/span&gt;&lt;br&gt;&lt;span class=&quot;line&quot;&gt;10&lt;/span&gt;&lt;br&gt;&lt;span class=&quot;line&quot;&gt;11&lt;/span&gt;&lt;br&gt;&lt;/pre&gt;&lt;/td&gt;&lt;td class=&quot;code&quot;&gt;&lt;pre&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;punctuation&quot;&gt;&amp;#123;&lt;/span&gt;&lt;/span&gt;&lt;br&gt;&lt;span class=&quot;line&quot;&gt;    &lt;span class=&quot;attr&quot;&gt;&amp;quot;server&amp;quot;&lt;/span&gt;&lt;span class=&quot;punctuation&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;string&quot;&gt;&amp;quot;0.0.0.0&amp;quot;&lt;/span&gt;&lt;span class=&quot;punctuation&quot;&gt;,&lt;/span&gt;&lt;/span&gt;&lt;br&gt;&lt;span class=&quot;line&quot;&gt;    &lt;span class=&quot;attr&quot;&gt;&amp;quot;port_password&amp;quot;&lt;/span&gt;&lt;span class=&quot;punctuation&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;punctuation&quot;&gt;&amp;#123;&lt;/span&gt;&lt;/span&gt;&lt;br&gt;&lt;span class=&quot;line&quot;&gt;        &lt;span class=&quot;attr&quot;&gt;&amp;quot;8381&amp;quot;&lt;/span&gt;&lt;span class=&quot;punctuation&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;string&quot;&gt;&amp;quot;foobar1&amp;quot;&lt;/span&gt;&lt;span class=&quot;punctuation&quot;&gt;,&lt;/span&gt;&lt;/span&gt;&lt;br&gt;&lt;span class=&quot;line&quot;&gt;        &lt;span class=&quot;attr&quot;&gt;&amp;quot;8382&amp;quot;&lt;/span&gt;&lt;span class=&quot;punctuation&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;string&quot;&gt;&amp;quot;foobar2&amp;quot;&lt;/span&gt;&lt;span class=&quot;punctuation&quot;&gt;,&lt;/span&gt;&lt;/span&gt;&lt;br&gt;&lt;span class=&quot;line&quot;&gt;        &lt;span class=&quot;attr&quot;&gt;&amp;quot;8383&amp;quot;&lt;/span&gt;&lt;span class=&quot;punctuation&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;string&quot;&gt;&amp;quot;foobar3&amp;quot;&lt;/span&gt;&lt;span class=&quot;punctuation&quot;&gt;,&lt;/span&gt;&lt;/span&gt;&lt;br&gt;&lt;span class=&quot;line&quot;&gt;        &lt;span class=&quot;attr&quot;&gt;&amp;quot;8384&amp;quot;&lt;/span&gt;&lt;span class=&quot;punctuation&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;string&quot;&gt;&amp;quot;foobar4&amp;quot;&lt;/span&gt;&lt;/span&gt;&lt;br&gt;&lt;span class=&quot;line&quot;&gt;    &lt;span class=&quot;punctuation&quot;&gt;&amp;#125;&lt;/span&gt;&lt;span class=&quot;punctuation&quot;&gt;,&lt;/span&gt;&lt;/span&gt;&lt;br&gt;&lt;span class=&quot;line&quot;&gt;    &lt;span class=&quot;attr&quot;&gt;&amp;quot;timeout&amp;quot;&lt;/span&gt;&lt;span class=&quot;punctuation&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;number&quot;&gt;300&lt;/span&gt;&lt;span class=&quot;punctuation&quot;&gt;,&lt;/span&gt;&lt;/span&gt;&lt;br&gt;&lt;span class=&quot;line&quot;&gt;    &lt;span class=&quot;attr&quot;&gt;&amp;quot;method&amp;quot;&lt;/span&gt;&lt;span class=&quot;punctuation&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;string&quot;&gt;&amp;quot;aes-256-cfb&amp;quot;&lt;/span&gt;&lt;/span&gt;&lt;br&gt;&lt;span class=&quot;line&quot;&gt;&lt;span class=&quot;punctuation&quot;&gt;&amp;#125;&lt;/span&gt;&lt;/span&gt;&lt;br&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;&lt;/figure&gt;

&lt;p&gt;Currently I am using &lt;code&gt;shadowsocks-libev&lt;/code&gt;, which is the libev port of shadowsocks. And I also need to support the usage of multiple users.</summary>
    
    
    
    <category term="Tech" scheme="https://blog.zzhou612.com/categories/Tech/"/>
    
    <category term="Nest of Coding Wisdom" scheme="https://blog.zzhou612.com/categories/Tech/Nest-of-Coding-Wisdom/"/>
    
    
    <category term="Shadowsocks" scheme="https://blog.zzhou612.com/tags/Shadowsocks/"/>
    
    <category term="Systemctl" scheme="https://blog.zzhou612.com/tags/Systemctl/"/>
    
  </entry>
  
  <entry>
    <title>Statement of Ostrich</title>
    <link href="https://blog.zzhou612.com/2018/12/06/statement-of-ostrich/"/>
    <id>https://blog.zzhou612.com/2018/12/06/statement-of-ostrich/</id>
    <published>2018-12-06T10:12:44.000Z</published>
    <updated>2018-12-06T10:12:44.000Z</updated>
    
    <content type="html"><![CDATA[<p>Blog又又又很久没有更新了，真的感到十分惭愧。申请季快进入尾声了，SOP也都写的差不多了，还是赶紧补一篇Statement of Ostrich来记录一下最近的”一点人生的经验“和“变化”吧，毕竟这半年对我而言确实可以说是天翻地覆。</p><span id="more"></span><p>之前的大学生活过于坎坷。Duel Degree项目申请失败，没有压倒性的绩点，又不愿意”曲线救国”，在PS里大谈自己想学CS之外的专业的鬼话，被UMich干脆拒绝，成为了密院的留守儿童，然后在港大交换期间去柬埔寨游玩又被酒驾的司机撞回了北京，坦率来说我已经不敢对生活中任何美好的事物抱有期望了。然而随着论文成功被ICCAD 2018接受，生活又渐渐有了点“盼头”，夏季学期成功生还，最后一年的绩点也算是圆满，如果还是抱着过去那种申个Master of Science in Computer Science项目然后再美国找工作的心态的话，手中的牌也算充足，我现在应该已经很满足了吧。</p><h1 id="围城"><a href="#围城" class="headerlink" title="围城"></a>围城</h1><p>然而参加了International Conference on Computer-Aided Design 2018之后，我才意识到之前的自己的视野是多么的狭隘。万分幸运，在SIGDA Dinner上遇到了愿意给我这个“井底之蛙”扫盲的交大学长和教授，才意识到过去对自己而言有些畏惧的Ph.D.其实也没那么遥不可及，真的有一种“eyes wide open”的感觉。</p><p>于是从洛杉矶和老同学吃完饭，转机飞回北京后，我立马化身Ph.D. (Systems Track) Bot开始一个一个实验室的网页进行爬虫式检索：Research Interests, Publication, Current Students, Alumni…一条一条爬过去，看了无数Ph.D. Candidate的Resume之后，为自己感到了深深的悲哀。如果我能早些看到这些“人生轨迹”该多好呢？至少也能知道一些别的“活法”，而不是在突围失败之后，困守在密院这样一座围城里面，终日重复着西西弗斯式的徒劳努力。</p><p>虽然我也深知人生没有如果的道理，但还是不免有些情绪低落，这大概也是申请季必不可少的一环吧。从积极的方向想，看着过去自己的狭隘与愚蠢而感到悲哀，也正是自己有所长进的证明吧。</p><h1 id="连通图"><a href="#连通图" class="headerlink" title="连通图"></a>连通图</h1><p>最近一直担忧着“失学”，“全聚德”的情况，处于一种“等待与绝望”的状态中，所以这短短Blog的记录也不免弥漫着负面情绪。大概正是因为在这因车祸延毕的一年来，切实奋战过了，才更加担心这所有的努力会不会只是竹篮打水一场空。</p><blockquote><p>人生如此复杂，机会多得像稠密图，我们没理由认输。尽管我们走不了最短路，但图仍是连通图，TLE之前，没有一个节点叫失败。</p></blockquote><p>NOI贴吧某不知名网友的这段话我一直珍藏于心，不论身处怎样的逆境，这段话总能给我继续走下去的勇气。希望到时候不论结果如何，我都能接着保持这一年来的状态，继续前进吧。</p>]]></content>
    
    
    <summary type="html">&lt;p&gt;Blog又又又很久没有更新了，真的感到十分惭愧。申请季快进入尾声了，SOP也都写的差不多了，还是赶紧补一篇Statement of Ostrich来记录一下最近的”一点人生的经验“和“变化”吧，毕竟这半年对我而言确实可以说是天翻地覆。&lt;/p&gt;</summary>
    
    
    
    <category term="Life" scheme="https://blog.zzhou612.com/categories/Life/"/>
    
    <category term="Pigeonhole" scheme="https://blog.zzhou612.com/categories/Life/Pigeonhole/"/>
    
    
    <category term="碎碎念" scheme="https://blog.zzhou612.com/tags/%E7%A2%8E%E7%A2%8E%E5%BF%B5/"/>
    
  </entry>
  
  <entry>
    <title>CHANGE!!!!</title>
    <link href="https://blog.zzhou612.com/2018/06/11/change/"/>
    <id>https://blog.zzhou612.com/2018/06/11/change/</id>
    <published>2018-06-11T12:03:39.000Z</published>
    <updated>2018-06-11T12:03:39.000Z</updated>
    
    <content type="html"><![CDATA[<p>春季丰富了不少人生的经历，也增添了些许不成熟的想法。虽然早就有诉诸笔端的冲动，只不过由于自身“鸵鸽”的本性一拖再拖，不知不觉中春假都已悄然结束。就连夏季学期都开始了一个星期，掐指一算距离我的上一篇文章过去将近过去了四个月，我才终于为了不让这个Blog像它的前辈们一样僵尸化，下定决心坐下来随便写点什么来填补这段漫长的空白。</p><span id="more"></span><h1 id="春-小结"><a href="#春-小结" class="headerlink" title="春 小结"></a>春 小结</h1><p>春季学期没有课业烦恼，在Cisco实习了四个月，捞了点小钱。Research也算尽了人事，能不能中大概也只能听天命了。GRE还算比较开心，也算是一次性拿到了“够用”的分数，让夏季学期免去了被GRE折磨的烦恼，但如果Paper能侥幸被接收的话<del>现在想想感觉是在期待百万动画化一样</del>可能会为了一些不切实际的目标再冲击一次吧。<del>结果AW挂了，回北京后还要再重考一次，痛哭</del></p><p>总的来说虽然春季摸了不少鱼，也遇到了不少坎坷，但该做的事情也算是做完了，虽然现在想想还有不少可以改进的空间，但木已成舟，剩下的也只能听之任之了。</p><h1 id="CHANGE"><a href="#CHANGE" class="headerlink" title="CHANGE!!!!"></a>CHANGE!!!!</h1><p>之前一段时间各种大新闻，世界局势波谲云诡，各位演员翻脸比翻书还快，演得人一愣一愣的，让人特别好奇今年谁才能拿下奥斯卡金像奖的最佳主角。像什么“三年又三年”这样原来不太敢想的事情都确实发生了，让人不禁感慨万千：活得久点确实能看到不少稀奇事物，人生真是如梦又似幻。</p><p>撇开离自己生活较远的大事不谈，就我自己个人的经历也让我切实感受到了世界在不断变化这一奇妙的常识。去年九月份休学了大半年重返学校时所感受到的那种“割裂感”依然记忆犹新，一年不到的时间里身边的同学就发生了各种各样的变化，确实也带给了我一点不小的冲击。</p><p>虽然现在我只是一条咸鱼，但狡兔三窟，未雨绸缪的道理我还是懂的，过去不断向上爬的那种心境虽然早已随着人生境遇的变化灰飞烟灭，但多少还有几分余烬，摸鱼滑水之余也终归是想着能有个“光辉的未来”的，至少想办法让自己过得充实一点吧，还是不要太浑浑噩噩为好。</p><h1 id="空種"><a href="#空種" class="headerlink" title="空種"></a>空種</h1><blockquote><p>时々不安になる 私に何ができるのだろう</p><p>时间は无限じゃない そんな中で</p><p>生きできた时间の中には 忘れたいこともあるけど</p><p>谁かとは立ち会えるのなら 记忆は 辉き始める</p></blockquote><p>之前四月份的时候偶然听到了南条爱乃在穢翼のユースティア特典里的角色歌，很好听，很喜欢，但也很忧伤。不由得想起现在已经不在了的初高中老同学，原来还在附中上学的时候天天跟我安利这个GalGame。世界在不断变化，时间在不断流逝，但他的时间却永远地停留在了2017年的四月。当年踏进同一个班的同桌，又几乎同时在世界的两端出了车祸，我大难不死捡回一条命，他却没有那么幸运。等繁忙的学期结束之后补一下穢翼吧，虽然再没有机会和他在新中关一边吃着烤肉一边谈天说地了，但还是可以去凤凰岭一趟和他聊聊，怀念过往。</p><p>人生无常的道理谁都知道，但大概也只有真出过事才能真正懂得活着是多么幸运幸福的一件事。总的来说，经历了这么多，我现在心态大概就是活得开心就好。虽然有时候还会“心态爆炸”，但总的来说已经比前几年的痛苦挣扎好很多了，希望这种平和一点的心态能延续下去吧。</p><h1 id="Summer-Flowers"><a href="#Summer-Flowers" class="headerlink" title="Summer Flowers"></a>Summer Flowers</h1><blockquote><p>Let life be beautiful like summer flowers</p></blockquote><p>其实这篇文章五月中旬就开始写了，然后又一路拖到现在，实在不能再拖下去了才决定填填补补一下就这么草草Publish了。就先写这么多吧，以后有机会再补上内容<del>咕咕咕</del>。</p><p>最后希望能够顺利度过这个神奇的夏季学期。</p>]]></content>
    
    
    <summary type="html">&lt;p&gt;春季丰富了不少人生的经历，也增添了些许不成熟的想法。虽然早就有诉诸笔端的冲动，只不过由于自身“鸵鸽”的本性一拖再拖，不知不觉中春假都已悄然结束。就连夏季学期都开始了一个星期，掐指一算距离我的上一篇文章过去将近过去了四个月，我才终于为了不让这个Blog像它的前辈们一样僵尸化，下定决心坐下来随便写点什么来填补这段漫长的空白。&lt;/p&gt;</summary>
    
    
    
    <category term="Life" scheme="https://blog.zzhou612.com/categories/Life/"/>
    
    <category term="Pigeonhole" scheme="https://blog.zzhou612.com/categories/Life/Pigeonhole/"/>
    
    
    <category term="碎碎念" scheme="https://blog.zzhou612.com/tags/%E7%A2%8E%E7%A2%8E%E5%BF%B5/"/>
    
  </entry>
  
  <entry>
    <title>Build My Own Nest</title>
    <link href="https://blog.zzhou612.com/2018/02/24/build-my-own-nest/"/>
    <id>https://blog.zzhou612.com/2018/02/24/build-my-own-nest/</id>
    <published>2018-02-24T11:21:57.000Z</published>
    <updated>2018-02-24T11:21:57.000Z</updated>
    
    <content type="html"><![CDATA[<p>Every ostrich needs a nest. So do I.</p><p>There are many posts that illustrate how to create a Hexo-driven blog hosted on Github. However, when it comes to personal VPS, such step-to-step tutorial vanishes. Since I need to use <code>shadowsocks</code> to access the outside world beyond the wall, I happen to own a VPS provided by Bandwagon. So I do not need to(also not willing to) use Github to store the static webpages. As a result, this website is deployed on my personal VPS(Ubuntu 16.04). And here are some of the crucial procedures I have taken to build this website(my own nest):</p><span id="more"></span><h1 id="Deployment-Workflow"><a href="#Deployment-Workflow" class="headerlink" title="Deployment Workflow"></a>Deployment Workflow</h1><p>Hexo provides multiple deployment strategies. And I choose to use git together with post-receive hook to deploy my website to the remote server.</p><p>The general workflow of my blog is pretty simple. After the static webpages are generated on my local machine, they will go through the following procedures to reach the working directory of the remote Nginx web server:</p><ul><li>local computer → push → git repository on remote server</li><li>post-receive git hook script → copy → Nginx directory</li></ul><h1 id="Hexo-Local-Configuration"><a href="#Hexo-Local-Configuration" class="headerlink" title="Hexo Local Configuration"></a>Hexo Local Configuration</h1><p>First of all, I need to edit the deployment settings in <code>_config.yml</code> on my local machine.  </p><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">deploy:</span><br><span class="line">  type: git</span><br><span class="line">  repo: ssh://git@my.server&#x27;s.ip.address:ssh_port/home/git/hexo.git</span><br><span class="line">  branch: master</span><br></pre></td></tr></table></figure><h1 id="Create-Remote-Git-Repository"><a href="#Create-Remote-Git-Repository" class="headerlink" title="Create Remote Git Repository"></a>Create Remote Git Repository</h1><p>Then I need to add the corresponding <code>git</code> user on the remote server.</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">adduser git</span><br></pre></td></tr></table></figure><p>Copy the SSH key to the server.</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">ssh-copy-id -p ssh_port git@my.server<span class="string">&#x27;s.ip.address</span></span><br></pre></td></tr></table></figure><p>Create a git repository named <code>hexo-git</code>.</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># login with git user</span></span><br><span class="line"><span class="built_in">cd</span> ~</span><br><span class="line"><span class="built_in">mkdir</span> hexo-git</span><br><span class="line"><span class="built_in">cd</span> hexo-git</span><br><span class="line">git init --bare</span><br></pre></td></tr></table></figure><h1 id="Add-Post-receive-Git-Hook"><a href="#Add-Post-receive-Git-Hook" class="headerlink" title="Add Post-receive Git Hook"></a>Add Post-receive Git Hook</h1><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">cd</span> ~/hexo-git/hooks</span><br><span class="line"><span class="built_in">touch</span> post-receive</span><br><span class="line">vim post-receive</span><br><span class="line"><span class="built_in">chmod</span> +x post-receive</span><br></pre></td></tr></table></figure><p>Edit the post-receive git hook script.</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line"><span class="meta">#!/bin/bash</span></span><br><span class="line">GIT_REPO=/home/git/hexo-git</span><br><span class="line">TMP_GIT_CLONE=/home/git/tmp/hexo</span><br><span class="line">PUBLIC_WWW=/var/www/blog</span><br><span class="line"><span class="built_in">rm</span> -rf <span class="variable">$&#123;TMP_GIT_CLONE&#125;</span></span><br><span class="line">git <span class="built_in">clone</span> <span class="variable">$GIT_REPO</span> <span class="variable">$TMP_GIT_CLONE</span></span><br><span class="line"><span class="built_in">rm</span> -rf <span class="variable">$&#123;PUBLIC_WWW&#125;</span>/*</span><br><span class="line"><span class="built_in">cp</span> -rf <span class="variable">$&#123;TMP_GIT_CLONE&#125;</span>/* <span class="variable">$&#123;PUBLIC_WWW&#125;</span></span><br></pre></td></tr></table></figure><h1 id="Set-Permissions"><a href="#Set-Permissions" class="headerlink" title="Set Permissions"></a>Set Permissions</h1><p>To ensure that the <code>git</code> user holds sufficient permissions to perform write operations in the web server directory, I decided to add <code>git</code> user to <code>www-data</code> group.</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">sudo usermod git -aG www-data</span><br></pre></td></tr></table></figure><p>Then I set the permissions to make sure that all the members in the <code>www-data</code> group can read and write all files in <code>/var/www</code> directory.</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">sudo <span class="built_in">chown</span> -R www-data:www-data /var/www</span><br><span class="line">sudo <span class="built_in">chmod</span> g+s /var/www</span><br><span class="line">sudo <span class="built_in">chmod</span> -R g+rwx,o-rwx /var/www</span><br></pre></td></tr></table></figure><h1 id="Create-Subdomains-with-Nginx"><a href="#Create-Subdomains-with-Nginx" class="headerlink" title="Create Subdomains with Nginx"></a>Create Subdomains with Nginx</h1><p>Maintaining subdomains using Nginx is pretty simple. Just create&#x2F;edit the configuration files in <code>sites-available</code> folder. Each subdomain should be assigned an independent root directory. Then, create the corresponding symlinks of configuration files in the <code>sites-enabled</code> folder to enable the subdomains.</p><p>Since I only have a homepage <code>zzhou612.com</code> and a subdomain <code>blog.zzhou612.com</code>, the structure of my web server directory looks like this:</p><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">/var/www</span><br><span class="line">├── blog</span><br><span class="line">└── html</span><br></pre></td></tr></table></figure><h1 id="Secure-Nginx-with-Let’s-Encrypt"><a href="#Secure-Nginx-with-Let’s-Encrypt" class="headerlink" title="Secure Nginx with Let’s Encrypt"></a>Secure Nginx with Let’s Encrypt</h1><p>Just use <code>certbot</code>, which can “automatically enable HTTPS on your website, deploying Let’s Encrypt certificates”.</p><p>Detailed instructions can be checked on the <a href="https://certbot.eff.org/#ubuntuxenial-nginx">official website</a> of <code>certbot</code>.</p>]]></content>
    
    
    <summary type="html">&lt;p&gt;Every ostrich needs a nest. So do I.&lt;/p&gt;
&lt;p&gt;There are many posts that illustrate how to create a Hexo-driven blog hosted on Github. However, when it comes to personal VPS, such step-to-step tutorial vanishes. Since I need to use &lt;code&gt;shadowsocks&lt;/code&gt; to access the outside world beyond the wall, I happen to own a VPS provided by Bandwagon. So I do not need to(also not willing to) use Github to store the static webpages. As a result, this website is deployed on my personal VPS(Ubuntu 16.04). And here are some of the crucial procedures I have taken to build this website(my own nest):&lt;/p&gt;</summary>
    
    
    
    <category term="Tech" scheme="https://blog.zzhou612.com/categories/Tech/"/>
    
    <category term="Nest of Coding Wisdom" scheme="https://blog.zzhou612.com/categories/Tech/Nest-of-Coding-Wisdom/"/>
    
    
    <category term="Git" scheme="https://blog.zzhou612.com/tags/Git/"/>
    
    <category term="Hexo" scheme="https://blog.zzhou612.com/tags/Hexo/"/>
    
    <category term="Nginx" scheme="https://blog.zzhou612.com/tags/Nginx/"/>
    
  </entry>
  
  <entry>
    <title>Hello, World!</title>
    <link href="https://blog.zzhou612.com/2018/02/06/hello-world/"/>
    <id>https://blog.zzhou612.com/2018/02/06/hello-world/</id>
    <published>2018-02-06T06:31:12.000Z</published>
    <updated>2018-02-06T06:31:12.000Z</updated>
    
    <content type="html"><![CDATA[<p>年轻的时候还在搞OI，也算是看着Matrix67，Byvoid这样的大牛的个人博客一步步走过来的。羡慕着大牛们的人生轨迹的同时，也想着自己也要搭个博客，让自己这个鶸也能在世界上留下一点微小的痕迹。但网站搭好了，却每次都和我那拿完省一就“激流勇退”的OI生涯一样，“创业未半而中道崩殂”：搭好之后一共没写过几篇文章，却往往由于“众所周知的原因”更换了连接更加顺畅的VPS做梯子，最后又懒得做迁移，一切便烟消云散。一次又一次重启，仿佛之前的一切从未存在过。</p><blockquote><p>So we beat on, boats against the current, borne back ceaselessly into the past.</p></blockquote><span id="more"></span><p>希望这是我最后一次干这种事情。</p><p>好好反省了一下之前没坚持下来的原因，大抵是因为之前一直用的是Wordpress框架搭博客。然而我既不懂php，也不愿意去学。对我而言Wordpress是个彻底的黑箱，我只能用别人写好的Theme和Plugins，自己既看不懂也改不动。这次换了Hexo，Node.js对我而言友好太多了，归根结底Wordpress提供的后端管理与文章编辑界面我根本用不上，比起WP看似功能强大的在线编辑器还是Markdown写起来更加舒爽。而Hexo这种生成静态页面并部署上传的框架，起码整个流程我都略知一二，出了问题也能自己解决，部署迁移也十分方便。</p><p>依稀上次重启博客还是在香港，一年过去了，期间发生了各种各样神奇的事情，也算是经历了人生的大起大落，解锁了不少人生成就。第一次在异国他乡遭遇车祸，第一次去浅水湾看Live。曾经也做过一些微小的记录，虽然Wordpress迁移到Hexo有现成的Plugin可以用也很方便，但也懒得做这些微小的工作了，过去的就让它过去吧。</p><p>希望接下来的一年能活得更加自由自在，做自己想做的事，去自己想去的地方。即使形势所迫不得处理一些不得不应付的差事，也能保持健康积极的心态。人活得开心最重要。</p><p>最后希望这次能坚持下来，记录平日生活的点滴，等多年之后回首往事，便能看到那万千思绪汇聚成的静态网页文档。</p><p>不也挺好吗。</p>]]></content>
    
    
    <summary type="html">&lt;p&gt;年轻的时候还在搞OI，也算是看着Matrix67，Byvoid这样的大牛的个人博客一步步走过来的。羡慕着大牛们的人生轨迹的同时，也想着自己也要搭个博客，让自己这个鶸也能在世界上留下一点微小的痕迹。但网站搭好了，却每次都和我那拿完省一就“激流勇退”的OI生涯一样，“创业未半而中道崩殂”：搭好之后一共没写过几篇文章，却往往由于“众所周知的原因”更换了连接更加顺畅的VPS做梯子，最后又懒得做迁移，一切便烟消云散。一次又一次重启，仿佛之前的一切从未存在过。&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;So we beat on, boats against the current, borne back ceaselessly into the past.&lt;/p&gt;
&lt;/blockquote&gt;</summary>
    
    
    
    <category term="Life" scheme="https://blog.zzhou612.com/categories/Life/"/>
    
    <category term="Pigeonhole" scheme="https://blog.zzhou612.com/categories/Life/Pigeonhole/"/>
    
    
    <category term="碎碎念" scheme="https://blog.zzhou612.com/tags/%E7%A2%8E%E7%A2%8E%E5%BF%B5/"/>
    
  </entry>
  
</feed>
