<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title>Joshua Rogers&apos; Scribbles</title>
		<description></description>
		<link>https://joshua.hu</link>
		<atom:link href="https://joshua.hu/rss-feed.xml" rel="self" type="application/rss+xml" />
		
			<item>
				<title>Video Games Around The World: South Africa</title>
				
				
					<description>&lt;p&gt;&lt;em&gt;This was originally written on April 16, 2020 and published on LinkedIn. I’ve decided to move the posts here for better searchability. Those that know me well, know that I am a video game history researcher, and this is just some of my random published articles.&lt;/em&gt;&lt;/p&gt;

</description>
				
				<pubDate>Thu, 14 May 2026 00:00:00 +0000</pubDate>
				<link>https://joshua.hu/video-games-around-the-world-south-africa</link>
				<guid isPermaLink="true">https://joshua.hu/video-games-around-the-world-south-africa</guid>
			</item>
		
			<item>
				<title>Video Game History Around The World: An Essay.</title>
				
				
					<description>&lt;p&gt;&lt;em&gt;This was originally written on June 12, 2020 and published on LinkedIn. I’ve decided to move the posts here for better searchability. Those that know me well, know that I am a video game history researcher, and this is just some of my random published articles.&lt;/em&gt;&lt;/p&gt;

</description>
				
				<pubDate>Thu, 14 May 2026 00:00:00 +0000</pubDate>
				<link>https://joshua.hu/video-game-history-around-the-world-essay</link>
				<guid isPermaLink="true">https://joshua.hu/video-game-history-around-the-world-essay</guid>
			</item>
		
			<item>
				<title>Some Thoughts on Cross-Cultural Video Game and Music</title>
				
				
					<description>&lt;p&gt;&lt;em&gt;This was originally written on September 15, 2020 and published on LinkedIn. I’ve decided to move the posts here for better searchability. Those that know me well, know that I am a video game history researcher, and this is just some of my random published articles.&lt;/em&gt;&lt;/p&gt;

</description>
				
				<pubDate>Thu, 14 May 2026 00:00:00 +0000</pubDate>
				<link>https://joshua.hu/some-thoughts-on-cross-cultural-video-game-and-music</link>
				<guid isPermaLink="true">https://joshua.hu/some-thoughts-on-cross-cultural-video-game-and-music</guid>
			</item>
		
			<item>
				<title>Exploring &quot;Bus Tours&quot; of Nintendo and Sega: The Nintendo Challenger, Campus Challenge, and More.</title>
				
				
					<description>&lt;p&gt;&lt;em&gt;This was originally written on July 10, 2020 and published on LinkedIn. I’ve decided to move the posts here for better searchability. Those that know me well, know that I am a video game history researcher, and this is just some of my random published articles.&lt;/em&gt;&lt;/p&gt;

</description>
				
				<pubDate>Thu, 14 May 2026 00:00:00 +0000</pubDate>
				<link>https://joshua.hu/exploring-bus-tours-of-nintendo-and-sega</link>
				<guid isPermaLink="true">https://joshua.hu/exploring-bus-tours-of-nintendo-and-sega</guid>
			</item>
		
			<item>
				<title>Always &apos;Copy Clean Link&apos; when possible on Firefox, with userChrome.css</title>
				
				
					<description>&lt;p&gt;In my &lt;a href=&quot;https://joshua.hu/firefox-making-right-click-not-suck&quot;&gt;last&lt;/a&gt; two &lt;a href=&quot;https://joshua.hu/firefox-making-right-click-not-suck-even-more-with-userchrome&quot;&gt;posts&lt;/a&gt;, I outlined how to clean up the right-click menu in Firefox to remove useless buttons, using either &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;about:config&lt;/code&gt; or &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;userChrome.css&lt;/code&gt;, respectively. One of my major complaints was that when right-clicking a link, I was presented with two buttons: one for ‘Copy Link’, and one for ‘Copy Clean Link’ – with the latter 99.99% of the time being greyed out due to the link already being ‘clean’. I found the greyed out link annoying since it simply cluttered up the menu as an unclickable button; and even if it were clickable, I wouldn’t deliberately use it – I’m so used to clicking ‘Copy Link’ that I just always want to click that; I don’t want to make the split-second decision of copying a link based on two different buttons. In my ideal world, the ‘Copy Link’ button would &lt;em&gt;always&lt;/em&gt; clean the link, if possible; but this is not an option in Firefox.&lt;/p&gt;

</description>
				
				<pubDate>Tue, 17 Mar 2026 00:00:00 +0000</pubDate>
				<link>https://joshua.hu/firefox-always-copy-clean-link-url-userchrome-css</link>
				<guid isPermaLink="true">https://joshua.hu/firefox-always-copy-clean-link-url-userchrome-css</guid>
			</item>
		
			<item>
				<title>Making Firefox&apos;s right-click not suck, even more, with userChrome.css</title>
				
				
					<description>&lt;h2 id=&quot;cleaning-up-right-click-with-userchromecss&quot;&gt;Cleaning up right-click with userChrome.css&lt;/h2&gt;

</description>
				
				<pubDate>Sat, 07 Mar 2026 00:00:00 +0000</pubDate>
				<link>https://joshua.hu/firefox-making-right-click-not-suck-even-more-with-userchrome</link>
				<guid isPermaLink="true">https://joshua.hu/firefox-making-right-click-not-suck-even-more-with-userchrome</guid>
			</item>
		
			<item>
				<title>Making Firefox&apos;s right-click not suck with about:config</title>
				
				
					<description>&lt;p&gt;On a fresh installation of Firefox on MacOS, right-clicking an image while some text on the page is highlighted (to show as many buttons as possible) looks like so:&lt;/p&gt;

</description>
				
				<pubDate>Wed, 04 Mar 2026 00:00:00 +0000</pubDate>
				<link>https://joshua.hu/firefox-making-right-click-not-suck</link>
				<guid isPermaLink="true">https://joshua.hu/firefox-making-right-click-not-suck</guid>
			</item>
		
			<item>
				<title>wtf is NS_ERROR_INVALID_CONTENT_ENCODING? investigating shared dictionaries and ChatGPT breakage in Firefox</title>
				
				
					<description>&lt;p&gt;Today I learnt about the &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;NS_ERROR_INVALID_CONTENT_ENCODING&lt;/code&gt; error (or “Content Encoding Error”) in Firefox, which started popping up in my Network tab while trying to access ChatGPT. Indeed, while having access to ChatGPT has allowed me to keep up the charade that I actually know what I’m doing in (life|work|security|etc), the service became completely inoperable in Firefox a few days ago. I couldn’t find any analysis online, so I dug into it myself.&lt;/p&gt;

</description>
				
				<pubDate>Fri, 16 Jan 2026 00:00:00 +0000</pubDate>
				<link>https://joshua.hu/chatgpt-fail-loading-firefox</link>
				<guid isPermaLink="true">https://joshua.hu/chatgpt-fail-loading-firefox</guid>
			</item>
		
			<item>
				<title>From gixy-ng to Gixy-Next: rescuing the nginx security scanner, Gixy, from AI slop</title>
				
				
					<description>&lt;p&gt;I recently decided to fork and maintain a new version of the Gixy nginx security tooling, calling my fork &lt;em&gt;Gixy-Next&lt;/em&gt;. The official website is &lt;a href=&quot;https://gixy.io/&quot;&gt;https://gixy.io/&lt;/a&gt;, and the source code is available on GitHub at &lt;a href=&quot;https://github.com/megamansec/gixy-next&quot;&gt;MegaManSec/Gixy-Next&lt;/a&gt;. The Python package is available on &lt;a href=&quot;https://pypi.org/project/gixy-next&quot;&gt;PyPi&lt;/a&gt;, but there’s also an &lt;a href=&quot;https://gixy.io/scanner/&quot;&gt;online scanner&lt;/a&gt; which can be run in your browser (locally; with WASM).&lt;/p&gt;

</description>
				
				<pubDate>Sat, 10 Jan 2026 00:00:00 +0000</pubDate>
				<link>https://joshua.hu/gixy-ng-ai-slop-gixy-next-maintained</link>
				<guid isPermaLink="true">https://joshua.hu/gixy-ng-ai-slop-gixy-next-maintained</guid>
			</item>
		
			<item>
				<title>My 2025 Bug Bounty Stories</title>
				
				
					<description>&lt;p&gt;This year, I’ve reported more issues via bug bounties than perhaps the past 10 years combined. The issues were all in completely random places, and the only reason they were reported via bug bounty programs is because it is generally impossible to get a human response &lt;a href=&quot;/slack-is-broken-with-noscript&quot;&gt;any other way&lt;/a&gt; from tech companies (even when you have a full &lt;a href=&quot;/death-of-a-tech-support-github-edition&quot;&gt;technical analysis of the issue&lt;/a&gt;).&lt;/p&gt;

</description>
				
				<pubDate>Mon, 22 Dec 2025 00:00:00 +0000</pubDate>
				<link>https://joshua.hu/2025-bug-bounty-stories-fail</link>
				<guid isPermaLink="true">https://joshua.hu/2025-bug-bounty-stories-fail</guid>
			</item>
		
	</channel>
</rss>
