<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Elim Kwan on Medium]]></title>
        <description><![CDATA[Stories by Elim Kwan on Medium]]></description>
        <link>https://medium.com/@elimkwan?source=rss-879db300e5cf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*estsQFP3KYHp67s3uBjGoA@2x.jpeg</url>
            <title>Stories by Elim Kwan on Medium</title>
            <link>https://medium.com/@elimkwan?source=rss-879db300e5cf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 03:22:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@elimkwan/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Foray into the Realm of Quadruped Robots — from winners of the SoTA26 Trust Everything Hackathon]]></title>
            <link>https://medium.com/@elimkwan/foray-into-the-realm-of-quadruped-robots-from-winners-of-the-sota26-trust-everything-hackathon-84b897aa5c00?source=rss-879db300e5cf------2</link>
            <guid isPermaLink="false">https://medium.com/p/84b897aa5c00</guid>
            <category><![CDATA[unitree]]></category>
            <category><![CDATA[quadruped-robot]]></category>
            <category><![CDATA[unitree-go1-pro]]></category>
            <category><![CDATA[robotics]]></category>
            <category><![CDATA[ai-trust-and-safety]]></category>
            <dc:creator><![CDATA[Elim Kwan]]></dc:creator>
            <pubDate>Fri, 20 Mar 2026 17:13:37 GMT</pubDate>
            <atom:updated>2026-03-20T17:13:37.742Z</atom:updated>
            <content:encoded><![CDATA[<h3>Foray into the Realm of Quadruped Robots — from the team that won the SoTA26 Trust Everything Hackathon Grand Prize</h3><p>How it started: <a href="https://youtube.com/shorts/XNQkx1yv_iQ">https://youtube.com/shorts/XNQkx1yv_iQ</a></p><p>How it ended:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MvGUPIbtbcdnksmaRwnUzg.jpeg" /></figure><p>Just kidding! But as a team curious about robotics, what could be more exciting than trying to program a robot dog? Quadruped robots offer unique advantages in their ability to traverse complex terrain and to carry heavy sensing payloads, essential for mine inspection and clearing tasks. Our immediate goal was simple: instead of relying on a remote controller, we wanted to command the robot directly from our laptops. Achieving this would open the door to many downstream possibilities, from autonomous navigation to integrating advanced security and verification mechanisms.</p><p>I began by exploring the basics using the tools I had available — Mac laptops. While perhaps not the most conventional platform for robotics development, it was the environment I was working in. I experimented with several approaches, including RoboStack and Docker-based setups. Initially, I tried running Docker images with the Unitree SDK and ROS, but compiling the full stack proved challenging on macOS. I then shifted to a lighter setup using Docker with just the Unitree SDK, which brought me closer to controlling the robot.</p><p>However, connectivity soon became the biggest hurdle. In theory, connecting to the robot dog’s WiFi hotspot should have made communication straightforward. In practice, the connection dropped frequently. I even attempted to use the Unitree mobile app, only to discover that it no longer supports the GO1 series. Another option, DroneBlocks — offering MIT Scratch-style programming for the GO1 Pro — also turned out to be incompatible with my setup.</p><p>Undeterred, my team tried running the Docker environment inside a virtual machine, hoping the network stack would behave more reliably. Unfortunately, the wireless connections continued to drop. On the second day of the hackathon, I brought LAN cables and adapters, planning to bypass WiFi entirely with a wired connection. Yet, that plan ended when I discovered the robot’s Ethernet port was covered by a screwed-in plate requiring a very specific screwdriver. With limited time remaining, the team ultimately switched to another mobile robot platform that allowed us to demonstrate the concept.</p><p>Despite the setbacks, the experience was incredibly valuable. Along the way, I learned a great deal about working with quadruped robots:</p><ul><li>“Can stand even when kicked” — Their motion control systems are remarkably sophisticated and stable</li><li>“It cuts my hand” — They are impressive but heavy machines, and can hurt when mishandled!</li><li>“Drop dead happens” — Battery life can be surprisingly short, and when it runs out, the robot literally drops to the floor with no warning.</li><li>“It can climb mountains, but flat is needed for initialisation” — Each startup requires at least 2 min calibration phase on the flat before the robot is ready to move.</li></ul><p>In many ways, the experience mirrored the spirit of the Trust Everything, Everywhere hackathon itself. Building trustworthy systems requires not only clever algorithms but also reliable connections between hardware, software, and people. While we ultimately demonstrated our idea on a different robot platform, experimenting with the quadruped reminded us that trust in robotics begins with understanding the full system, from networks and batteries to control software and safety.</p><p>And of course, getting to work with a robot dog was still a highlight of the weekend.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d71tVc3uziEhIMGlFQN9Jg.jpeg" /></figure><p><strong>Link to the full newsletter:</strong> <a href="https://sotaletters.substack.com/p/minetrust-the-future-of-trustworthy">https://sotaletters.substack.com/p/minetrust-the-future-of-trustworthy</a><br><strong>Presentation and live demo:</strong> <a href="https://lnkd.in/exvSEgtR">https://lnkd.in/exvSEgtR</a><br><strong>Twitter post:</strong> <a href="https://lnkd.in/eHkNDnDk">https://lnkd.in/eHkNDnDk</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84b897aa5c00" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Linux with GUI on Windows 11 (WSL, SSH, Remote Desktop …)]]></title>
            <link>https://medium.com/@elimkwan/using-linux-with-gui-on-windows-11-wsl-ssh-remote-desktop-bb1959e8f2dc?source=rss-879db300e5cf------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb1959e8f2dc</guid>
            <category><![CDATA[ssh-tunnel]]></category>
            <category><![CDATA[wsl]]></category>
            <category><![CDATA[ubuntu]]></category>
            <category><![CDATA[windows-11]]></category>
            <category><![CDATA[remote-desktop]]></category>
            <dc:creator><![CDATA[Elim Kwan]]></dc:creator>
            <pubDate>Fri, 29 Oct 2021 06:37:57 GMT</pubDate>
            <atom:updated>2021-10-29T18:28:54.576Z</atom:updated>
            <content:encoded><![CDATA[<h3>Using Linux with GUI on Windows 11 (WSL, SSH, Remote Desktop …)</h3><p>What’s the easiest way of accessing a remote server with Ubuntu OS from a Windows 11 laptop + some graphic interface? Or just some nice GUI for any local Linux distribution? We will introduce four methods that <strong>do not involve dual-booting:</strong></p><ol><li>WSL2 + XLaunch (GUI for local WSL Ubuntu instance only)</li><li>WSL2 + Remote Desktop (GUI for local WSL Ubuntu instance only)</li><li>Window SSH + XLaunch (GUI for Ubuntu on the remote server!)</li><li>Window SSH + Remote Desktop (GUI for Ubuntu on the remote server!)</li></ol><p>The following tutorial assumed that you have installed <a href="https://www.omgubuntu.co.uk/how-to-install-wsl2-on-windows-10">windows linux subsystem 2 (WSL2)</a>, a <a href="https://ubuntu.com/wsl">Ubuntu distribution</a> and <a href="https://sourceforge.net/projects/vcxsrv/">XLaunch(VcXsrv)</a>.</p><p>The author also recommends installing the <a href="https://www.microsoft.com/en-us/p/windows-terminal/9n0dx20hk701#activetab=pivot:overviewtab">Windows Terminal</a> for easy access to WSL and Window PowerShell terminals. I mean who wouldn’t like the colouring of this!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V74WBc-Kl3k4Ayio0_0V5g.jpeg" /><figcaption>Custom Windows Terminal colour scheme from <a href="https://www.thomasmaurer.ch/2020/06/my-windows-terminal-color-schemes/">Thomas Maurer</a></figcaption></figure><h3>Method 1 — WSL2 with XLaunch:</h3><p>Open Windows Terminal and open a tab for your Ubuntu instance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P2527GuCRFZEatw2HT7xvA.jpeg" /></figure><p>Use a command-line editor (e.g. vi) to edit the .bashrc file.</p><pre>vi $HOME/.bashrc</pre><p>Insert the following two lines at the end of the .bashrc file.</p><pre>export DISPLAY=$(awk &#39;/nameserver / {print $2; exit}&#39; /etc/resolv.conf 2&gt;/dev/null):0<br>export LIBGL_ALWAYS_INDIRECT=1</pre><p>Launch XLaunch from the startup menu. Change display number to 0, click next, click next, tick the box for “Disable access control”, click next, click finish.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/754/1*c3C8WkyvWMPwDk76pqOocQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/754/1*taYA-Z4zhaNb5g_ImHNSHg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/759/1*IQ3GVi_7-AEbCrmop6i-3g.jpeg" /></figure><p>Test the GUI by typing gedit in the wsl ubuntu terminal, you should see gedit editor window popping up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qIprV9G9GFeLjZW52cPWNg.jpeg" /></figure><h3>Method 2 — WSL2 with Remote Desktop:</h3><p>Ensure the application Remote Desktop Connection is on your laptop.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/780/1*KRVEfaOMmrD8dXPFV6_QPg.png" /></figure><p>On the wsl ubuntu terminal, install packages and validate packages with the following commands:</p><pre>sudo apt-get update<br>sudo apt install xrdp<br>sudo service xrdp start<br>sudo ufw allow from any to any port 3389 proto tcp<br>sudo apt-get install xfce4<br>echo xfce4-session &gt;~/.xsession<br>sudo service xrdp restart</pre><p>Then get the hostname of the wsl ubuntu instances with the following command:</p><pre>hostname -I</pre><p>For my laptop, the output is something like this:</p><pre>172.25.157.246</pre><p>Copy the hostname to the Remote Desktop Connection, and enter your wsl ubuntu credential.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qJ_03Yfo9XB8QRgoCaBqHA.jpeg" /></figure><p>Click Yes for the pop-up warnings and log in, afterwards, you will get a ubuntu desktop interface (even with a terminal emulator)!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MMv6o-vfMrLCGNybmbiTuA.jpeg" /></figure><p>Note that after rebooting the laptop, the hostname of the wsl ubuntu will change, we will have to restart the xrdp and check the hostname again</p><pre>sudo service xrdp restart<br>hostname -I</pre><p>It is also possible to set up ssh from the wsl ubuntu to our remote server ubuntu, the process is fairly straightforward, hence, we will move on to discuss how to set up ssh directly from the windows machine and provide a graphic interface for it.</p><h3>Method 3 — Window SSH + XLaunch:</h3><p>Install <a href="https://docs.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstuse">OpenSSH</a> on the Window Machines. Then, in the Window PowerShell Terminal view the ssh config file, if it doesn’t exist, create one at $HOME/.ssh/config . Also, please ensure the encoding of the file is UTF-8 , else it will run into errors.</p><pre>notepad.exe $HOME/.ssh/config</pre><p>In the file, copy and paste the following, change [machine-name], [user-name], [port-number], [host-name] to your own one:</p><pre>Host *<br>    ForwardX11 yes<br>    ForwardX11Trusted yes<br>    PreferredAuthentications hostbased,publickey,keyboard-interactive,password</pre><pre>Host [machine-name]<br>    User [user-name]<br>    Port [port-number]<br>    HostName [host-name]</pre><p>On the server side, enable X11forwarding. One can do so by ssh into the remote server from the Window PowerShell terminal or ssh from the wsl ubuntu instance.</p><pre>ssh [machine-name]</pre><p>View the ssh config file.</p><pre>vi /etc/ssh/ssh_config</pre><p>Make sure you see something like this uncommented:</p><pre>Host *<br>   ForwardAgent yes<br>   ForwardX11 yes</pre><p>Then, head back to the window machine, launch XLaunch(follow what we discussed in Method 1). And finally, enter the following command in the Window Powershell terminal:</p><pre>ssh -X [machine-name]</pre><p>Finally, test it by typing gedit, you should see a gedit editor window popping up.</p><h3>Method 4 — Window SSH + Remote Desktop:</h3><p>Assuming you have set up OpenSSH on the window Machine (see the first part of Method 3). From the Window PowerShell Terminal, ssh into the server:</p><pre>ssh [machine-name]</pre><p>Then, on the remote server, set up xrdp .</p><pre>sudo apt install xrdp<br>sudo service xrdp start<br>sudo ufw allow from any to any port 3389 proto tcp</pre><p>Also, check the hostname of the remote server with</p><pre>hostname -I</pre><p>We will obtain an ip address that look like thisxxx.xxx.xxx.xxx . Save the number somewhere.</p><p>Then, on the Window Powershell, use the following command to set up SSH port forwarding.</p><pre>ssh -L 5901:[ip-address-obtained]:3389 [machine-name]</pre><p>Note that the general format of the command is</p><pre>ssh -L local_port:destination_server_ip:remote_port ssh_server_hostname</pre><p>Finally, enter the following hostname localhost:5901 to the Remote Desktop Connection, and enter your user credential for the remote server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/619/1*9qEqPoS3GBNsBk5jGEYYuA.jpeg" /></figure><p>You should be able to produce similar results to Method 2, except this ubuntu is the remote server one. And rebooting the window laptop will not change the hostname.</p><p>Voila! Here’s the final result</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FQdQJ2_SjaqQ%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DQdQJ2_SjaqQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FQdQJ2_SjaqQ%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/95a05761bdafa1b493ddb1352c0cc110/href">https://medium.com/media/95a05761bdafa1b493ddb1352c0cc110/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb1959e8f2dc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>