<?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>DEV Community: MaxHex</title>
    <description>The latest articles on DEV Community by MaxHex (@maxhex).</description>
    <link>https://dev.to/maxhex</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4216522%2Fe3ae0ca5-43df-4b5c-975b-65df6093b11e.jpg</url>
      <title>DEV Community: MaxHex</title>
      <link>https://dev.to/maxhex</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/maxhex"/>
    <language>en</language>
    <item>
      <title>Chrome Zero-Day CVE-2026-125350: How to Update Chrome and 6 Checks for Extension Developers</title>
      <dc:creator>MaxHex</dc:creator>
      <pubDate>Sun, 15 Nov 2026 18:28:27 +0000</pubDate>
      <link>https://dev.to/maxhex/chrome-zero-day-cve-2026-125350-how-to-update-chrome-and-6-checks-for-extension-developers-51l</link>
      <guid>https://dev.to/maxhex/chrome-zero-day-cve-2026-125350-how-to-update-chrome-and-6-checks-for-extension-developers-51l</guid>
      <description>&lt;p&gt;&lt;em&gt;Updating your own Chrome takes a minute. The part that takes longer is every other Chrome you forgot you have. None of this is a reason to ship anything in a hurry.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;You read the headline between two tasks. Another Google Chrome zero-day, already used in attacks. You open the menu, see a small "Relaunch" button, think "later", and go back to your code. The laptop stays open for the rest of the week.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fktu7p2xk7lzsbaia6ene.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fktu7p2xk7lzsbaia6ene.jpeg" alt="Chrome Zero-Day CVE-2026-125350: How to Update Chrome" width="800" height="447"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;CVE-2026-125350 is a high-severity Chrome vulnerability: a memory bug (a "use-after-free") in the part of Chrome that reads XML. Google fixed it with a Chrome security update on 9 November 2026, in Chrome 157.0.8103.50 for Linux and 157.0.8103.50/.51 for Windows and Mac, and wrote one short line about it: an exploit for this bug exists in the wild. The security press counts it as the eighth Chrome zero-day used in attacks this year.&lt;/p&gt;

&lt;p&gt;A smaller question helps more than the headline: how many copies of Chrome do you really run? For an extension developer the answer is rarely one. Go through the list in order. The first four are checks for today; the last two are for the rest of the week.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Check your Chrome version
&lt;/h2&gt;

&lt;p&gt;"I have auto-update" is a setting, not a version number. If you are asking "what version of Chrome do I have?", open this page and read the number:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;chrome://settings/help
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;On Linux the terminal shows the installed build (the running one may still be older until you restart):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;google-chrome --version
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;There is one more detail. On 11 November Google shipped a second update, 157.0.8103.78 (.79 on some Windows and Mac machines), with 83 more security fixes, five of them rated Critical. So the fix for the zero-day is in .50, but the latest Chrome version at the time of writing is .78, and that is the number you want to see.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Update Chrome, then relaunch it
&lt;/h2&gt;

&lt;p&gt;How to update Chrome: open Help → About Google Chrome and wait for the download to finish. On Windows and Mac, Chrome usually does this by itself in the background; on Linux the update arrives with your system updates. It starts using it only after a restart. A downloaded update protects nobody while the old browser is still running.&lt;/p&gt;

&lt;p&gt;Developers are a bad case here. We keep one window open for days, with forty tabs. Picture a freelance developer whose Chrome downloaded the update on Monday. They never closed the window, so on Friday they are still on the old build. Click "Relaunch".&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Count the other Chromes on your machine
&lt;/h2&gt;

&lt;p&gt;This is the step that took me the longest. On my work machine I found more browsers than I expected:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Chrome Beta and Canary, which I use to test upcoming changes&lt;/li&gt;
&lt;li&gt;an old portable copy in a folder for reproducing bug reports&lt;/li&gt;
&lt;li&gt;the browser that my test tool downloaded for itself&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The last one is easy to forget. Automation tools such as Playwright and Puppeteer download their own browser build. It does not update with your Chrome. It changes only when you update the tool.&lt;/p&gt;

&lt;p&gt;This part is a guess: I have not seen an official statement about these builds and this bug. They are built from the same code, so I treat an old one as unpatched. Check which browser version the tool ships, update the tool when a release with 157.0.8103.50 or later is out, and until then do not use that browser to open pages you do not control.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Check the other browsers your extension lives in
&lt;/h2&gt;

&lt;p&gt;If you publish in more than one store, you also run more than one browser. Each of them ships the fix on its own schedule.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Edge.&lt;/strong&gt; Microsoft's release notes say Edge 157.0.4341.46, released on 9 November, contains the fix.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Brave, Opera, Vivaldi.&lt;/strong&gt; I did not find a clear statement for each of them, so I give no version numbers here. Open the "About" page in each browser and read the vendor's release notes.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Firefox uses a different engine. I found no report that it is affected.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Watch your store numbers for a week, and do not ship in a panic
&lt;/h2&gt;

&lt;p&gt;Google describes it as a bug in the browser itself. Nothing I read says extension code needs to change because of it. An emergency release "just in case" brings more risk than it removes.&lt;/p&gt;

&lt;p&gt;What I do instead is boring. Three Chrome builds shipped in just over a week, and any browser update can change how an extension behaves. The first sign is rarely a bug report. It is a new one-star review or a rating that starts to slip. I open my extensions in &lt;a href="https://cwspy.com" rel="noopener noreferrer"&gt;cwspy.com&lt;/a&gt; every morning anyway; this week I read the rating and review lines more carefully. Each release and listing edit is marked on the same line, so if something bends, I can see whether it sits next to my change or next to nothing of mine.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Tell your users one calm sentence
&lt;/h2&gt;

&lt;p&gt;If you have a newsletter, a changelog or a support inbox, one sentence is enough: "Chrome has an important security update, please open Help → About Google Chrome and relaunch." No drama, no promise that your extension protects anyone. An extension cannot fix a browser bug.&lt;/p&gt;

&lt;h2&gt;
  
  
  What we know about the Chrome zero-day, and what we do not
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Fixed in:&lt;/strong&gt; Chrome 157.0.8103.50 (Linux) and .50/.51 (Windows, Mac), released 9 November 2026. A second update, 157.0.8103.78/.79, followed on 11 November.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reported:&lt;/strong&gt; first on 12 October and again on 6 November, according to Google's release note.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Exploited:&lt;/strong&gt; Google says an exploit exists in the wild. According to press reports, CISA added the bug to its list of known exploited vulnerabilities on 10 November, with a 24 November deadline for US federal agencies.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Not public:&lt;/strong&gt; who uses it, against whom, and how. Google usually keeps the details restricted until most users have updated.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Extensions:&lt;/strong&gt; nothing I read connects this bug to extensions.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The short version
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Check your Chrome version. You want 157.0.8103.78 or later.&lt;/li&gt;
&lt;li&gt;Update Chrome and relaunch it.&lt;/li&gt;
&lt;li&gt;Update Beta, Canary and portable copies, and check the browser inside your test tools.&lt;/li&gt;
&lt;li&gt;Check Edge and the other browsers you publish for.&lt;/li&gt;
&lt;li&gt;Do not ship an emergency release; watch your rating and reviews for a week.&lt;/li&gt;
&lt;li&gt;Tell users to update, in one sentence.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A security headline asks you to be worried. A version number asks you to check. The second one takes a minute.&lt;/p&gt;




&lt;p&gt;Sources:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_018223192.html" rel="noopener noreferrer"&gt;Chrome Releases: Stable Channel Update for Desktop, 9 November 2026&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_01744469280.html" rel="noopener noreferrer"&gt;Chrome Releases: Stable Channel Update for Desktop, 11 November 2026&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://learn.microsoft.com/en-us/deployedge/microsoft-edge-relnotes-security" rel="noopener noreferrer"&gt;Microsoft Edge security release notes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.malwarebytes.com/blog/bugs/2026/11/update-chrome-now-to-fix-a-flaw-attackers-are-exploiting" rel="noopener noreferrer"&gt;Malwarebytes: Update Chrome now to fix a flaw attackers are exploiting&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://thehackernews.com/2026/11/google-issues-chrome-security-update.html" rel="noopener noreferrer"&gt;The Hacker News: Google Issues Chrome Security Update for Eighth Actively Exploited Zero-Day of 2026&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>cybersecurity</category>
      <category>news</category>
      <category>security</category>
    </item>
    <item>
      <title>Which Chrome Extension Analytics Tool Is Worth Keeping? I Tested the Ones I Could Find</title>
      <dc:creator>MaxHex</dc:creator>
      <pubDate>Sat, 07 Nov 2026 07:26:34 +0000</pubDate>
      <link>https://dev.to/maxhex/which-chrome-extension-analytics-tool-is-worth-keeping-i-tested-the-ones-i-could-find-5gm6</link>
      <guid>https://dev.to/maxhex/which-chrome-extension-analytics-tool-is-worth-keeping-i-tested-the-ones-i-could-find-5gm6</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;The store shows you one number for today. The right tool shows you what moved it, and when — none of them replaces the official dashboard, and I say where each one stops.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;I have been shipping Chrome extensions for about eight years, a few of my own and a couple for clients. The routine never changes: you push an update on Tuesday, and on Friday the user count in the Chrome Web Store is lower than it was. Was it the update? A competitor? A ranking change for the main keyword? The store gives you one figure for today and no history, so for years I answered that question with a guess and a shrug.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Foejviu3r524bfl62s14x.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Foejviu3r524bfl62s14x.png" alt="One number in the store vs the full history in cwspy.com. Illustrative numbers from one of my extensions." width="800" height="336"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Chrome extension analytics is the category of tools that keep the daily history of a store listing — users, ratings, reviews, versions and keyword positions — so a change has a date and a reason. A smaller question helps when choosing one: if your analytics tool vanished tomorrow, which number would you miss first? Read the list below with that number in mind. It covers what exists, how I tested them, and which one I kept.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Start with the question you actually need answered
&lt;/h2&gt;

&lt;p&gt;Before comparing dashboards, write down the one question you ask most often. Mine, after eight years, is still: &lt;em&gt;when a number moves, what moved it?&lt;/em&gt; That ruled out anything that shows a snapshot without history, and it made "nice charts" a secondary concern. Your question may be different: keyword positions, competitor growth, or why people uninstall. Pick the tool for that question, not for the longest feature list.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. The tools that exist
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Chrome Web Store Developer Dashboard.&lt;/strong&gt; The official Chrome Web Store analytics, free and accurate: installs, weekly users and ratings for your own extensions, within the dashboard's own date ranges. It is the ground truth every other tool is checked against, and I still open it first thing on release day.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;ChromeStats (chrome-stats.com).&lt;/strong&gt; As far as I used it: a large catalogue of extensions with user counts, ratings and version history, and side-by-side comparison. Good for sizing up a category before you enter it; I used it that way before my last launch, and a solo developer with one idea could start here to see who already owns the niche.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Exstats.&lt;/strong&gt; Tracks listings in several stores. I only looked at it and did not keep it running; it may suit you if you publish in more than one store and want the numbers in one place.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Do it yourself: GA4 inside the extension plus a spreadsheet.&lt;/strong&gt; Google Analytics answers in-extension questions, which no store tool can. Store history is a separate job, and a hand-kept spreadsheet is the honest way to start it: one row a day, user count and version, for a month. I ran one for a few months and gave up. It taught me what I wanted from a real tool.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;cwspy.com.&lt;/strong&gt; Keeps the daily history of a listing (users, rating, reviews, version) for Chrome, Edge, Firefox and Opera, plus keyword position tracking (the part of Chrome Web Store SEO you can actually measure), a competitor list, traffic analytics through a GA connection (Chrome Web Store only), and an uninstall feedback page that collects the reason when someone removes the extension.&lt;/p&gt;

&lt;p&gt;There are a few other names in this space, mostly single-purpose checkers or abandoned projects. None of them was significant enough to change the picture, so they were left out of the test.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. How I tested them
&lt;/h2&gt;

&lt;p&gt;I did not read feature lists. I tracked the same three extensions, one of mine and two rivals, in every tool that could see them (the Dashboard only sees mine) for about three months, and checked four things each week: whether the extension stats matched the store, whether a change I knew about (a release, a listing edit) showed up with the right date, whether and how often a tool recorded keyword positions, and how long it took to answer my question from the dashboard. I also wrote down where each tool stops.&lt;/p&gt;

&lt;p&gt;That last column turned out to be the useful one. Most tools agree on the numbers. They differ in what they keep and in what sits next to the chart.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Where cwspy.com pulled ahead
&lt;/h2&gt;

&lt;p&gt;By the end cwspy.com was the tab I opened first. The advantages were clear enough that I did not need a scoring table. The numbers below are rounded and only illustrative:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Full history, not a snapshot.&lt;/strong&gt; Every user count, rating, review count and version is stored daily. When my count slipped from about 12.4k to 10.9k over six weeks, I scrolled back to the exact day it turned and found the release that went out that morning. Eight years in, that was the first time it took one scroll instead of a spreadsheet hunt. Listings from Chrome, Edge, Firefox and Opera sit in one account with the same charts for each.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keyword positions and rivals on the same timeline.&lt;/strong&gt; My position for the main keyword moved from 14 to 6 after a listing edit, and the keyword list showed which rival I passed.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Uninstall feedback next to the numbers.&lt;/strong&gt; The built-in uninstall page asks one question, stores the answer with the version and date, and shows the most common reason first. About a quarter of my answers named one unrelated permission, the one that release had added; I removed it and the count turned back up.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The cause is on the chart.&lt;/strong&gt; Releases and listing edits are marked on the same line as the user count, so "what moved this number?" is answered where the number is.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It is not a replacement for GA4 inside the extension; nothing on this list is. For everything that happens in the store, it is the tool I open every morning.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. What I would do in your place
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Keep the Developer Dashboard. It is the official Chrome Web Store analytics, it is the ground truth, and it is free.&lt;/li&gt;
&lt;li&gt;Add the extension to cwspy.com. It shows the current figures, the full history, and how the numbers moved after each update, which the Developer Dashboard does not keep. The first chart showed up the day I added the extension. I would recommend it to any developer who keeps an eye on their extensions.&lt;/li&gt;
&lt;li&gt;For sizing up a category, ChromeStats does the job.&lt;/li&gt;
&lt;li&gt;Whatever you pick, run it for a month before deciding. A good analytics tool proves itself on the first number you cannot explain.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The store will keep showing you one number. After eight years I prefer the tool that shows me the story behind it.&lt;/p&gt;




&lt;p&gt;Tools mentioned:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://cwspy.com" rel="noopener noreferrer"&gt;cwspy.com&lt;/a&gt; — Chrome extension analytics: daily history, keyword positions, uninstall feedback. The winner of this comparison&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://chrome.google.com/webstore/devconsole/" rel="noopener noreferrer"&gt;Chrome Web Store Developer Dashboard&lt;/a&gt; — official figures for your own extensions&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://chrome-stats.com" rel="noopener noreferrer"&gt;ChromeStats&lt;/a&gt; — catalogue and side-by-side comparison&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://exstats.com" rel="noopener noreferrer"&gt;Exstats&lt;/a&gt; — multi-store tracking&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>analytics</category>
      <category>chrome</category>
      <category>extensions</category>
    </item>
    <item>
      <title>The VCR never worked again. Hi, I'm Max Hex</title>
      <dc:creator>MaxHex</dc:creator>
      <pubDate>Fri, 30 Oct 2026 06:09:11 +0000</pubDate>
      <link>https://dev.to/maxhex/the-vcr-never-worked-again-hi-im-max-hex-49h0</link>
      <guid>https://dev.to/maxhex/the-vcr-never-worked-again-hi-im-max-hex-49h0</guid>
      <description>&lt;p&gt;Quick intro, because I'm new here and I'd rather you know who's talking before I start posting.&lt;/p&gt;

&lt;p&gt;I'm Max Hex. I write software. And I have exactly one personality trait that matters: &lt;strong&gt;if something is closed, I want to know what's inside.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Patient zero: a VCR
&lt;/h2&gt;

&lt;p&gt;I was nine. The family VCR had a problem. I had a screwdriver. The VCR was never seen working again — but I could draw you its insides from memory, and I still can.&lt;/p&gt;

&lt;p&gt;Thirty-odd years later the job is the same, just with worse screwdrivers. I spend my days reading systems nobody meant to be read: undocumented endpoints, pages that change shape overnight, data that quietly lies. I find out what they &lt;em&gt;actually&lt;/em&gt; do, as opposed to what the README claims.&lt;/p&gt;

&lt;h2&gt;
  
  
  Same trait, weekends edition
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Dead laptops.&lt;/strong&gt; A 1989 machine with a leaking capacitor is my favourite kind of bug. No search results, no patch notes, no "did you try updating" — just a schematic and a soldering iron. The first boot after a repair beats every green pipeline I've ever seen.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Very long bike rides.&lt;/strong&gt; 200 km, one day, no headphones. Somewhere past kilometre 140 the inner compiler finally shuts up, and that's where most of my good design decisions come from. I don't fully understand why. I've stopped fighting it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Board games, adversarially.&lt;/strong&gt; I don't play to win. I play to find the strategy the designer didn't see — the exploit. A game is a tiny system with at least one bug, and I like being the person who files the report.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Coffee, with logging.&lt;/strong&gt; Scale, timer, a notebook. The coffee is bad. The data about the coffee is beautiful.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'll post here
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;How systems behave when you watch them long enough (and why "watch long enough" is the whole trick)&lt;/li&gt;
&lt;li&gt;Why data lies, and how to catch it in the act&lt;/li&gt;
&lt;li&gt;Occasional notes on running a one-person product without losing your mind&lt;/li&gt;
&lt;li&gt;What a bicycle has to do with debugging. More than you'd think.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Short posts. Plain words. Real numbers. When I'm guessing, I'll say it's a guess.&lt;/p&gt;

&lt;h2&gt;
  
  
  Your turn
&lt;/h2&gt;

&lt;p&gt;If you've ever broken something just to see how it worked — I want to hear about it. &lt;strong&gt;What was the first thing you took apart, and did it survive?&lt;/strong&gt; 👇&lt;/p&gt;

</description>
      <category>hobby</category>
      <category>mylife</category>
      <category>aboutme</category>
    </item>
  </channel>
</rss>
