<?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 jamilxt on Medium]]></title>
        <description><![CDATA[Stories by jamilxt on Medium]]></description>
        <link>https://medium.com/@jamilxt?source=rss-cbc015683892------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*SAERlm0RRbVMz_9bfDctfA.png</url>
            <title>Stories by jamilxt on Medium</title>
            <link>https://medium.com/@jamilxt?source=rss-cbc015683892------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 03:52:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jamilxt/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[Medium’s Paywall Enforcement Is My Last Straw as a Writer]]></title>
            <link>https://medium.com/@jamilxt/mediums-paywall-enforcement-is-my-last-straw-as-a-writer-9f3f1aa8e035?source=rss-cbc015683892------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f3f1aa8e035</guid>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[content-writing]]></category>
            <dc:creator><![CDATA[jamilxt]]></dc:creator>
            <pubDate>Wed, 28 Oct 2026 13:11:30 GMT</pubDate>
            <atom:updated>2026-10-28T13:11:30.177Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*gBfR4VXv1SF5bXsR.png" /></figure><p>I am disappointed with Medium.</p><p>Not because a platform has rules. Every publishing platform has rules, and writers should read them. My disappointment is about the experience of discovering that a rule is being enforced against writers who believed they could continue using a feature, and about what that says about the relationship between a publishing platform and the people who create for it.</p><p>A writer shared a Medium notice on October 27 saying that a Medium membership was required to put new stories behind the paywall, with enforcement starting that day.[3] That is a report from an individual writer, not a platform-wide rollout schedule published by Medium. The distinction matters. I have not found an official Medium announcement confirming that every writer received the notice on the same date.</p><p>There is another important detail: the membership requirement itself does not appear to be new. Medium’s Partner Program eligibility guidance requires an active Medium membership, and the current Partner Program terms say writers who were already participants on August 1, 2024 had until December 31, 2024 to meet the eligibility requirements.[1][2] So this looks less like a brand-new rule and more like enforcement reaching writers who had not previously encountered it in this way.</p><p>That does not make the frustration disappear. Medium’s current terms reserve the right to modify or discontinue the Partner Program without advance notice. They also say Medium will use reasonable efforts to contact existing participants before removing them for failing to meet eligibility requirements.[2] We do not know the writer’s account history, so we cannot tell whether this was a new application of the rule to that account or a delayed enforcement of an older requirement. The fair criticism is narrower: even if the terms allow the change without advance notice, a notice saying “starting today” gives a writer little time to understand the change and decide what to do next.</p><h3>Membership is not the same as permission to publish</h3><p>To be precise, Medium is not saying that writers must pay simply to post a public story. Its own help center says memberships are not required to read and write on Medium.[4] The Partner Program requirements concern eligibility to earn through the program and to use the paywall. The distinction is important, and it would be misleading to describe this as Medium charging every writer just to publish. The issue is narrower: a writer who wants to put a new story behind Medium’s paywall needs to satisfy the membership requirement for the Partner Program.[1]</p><p>That narrower issue still has real consequences. A paywall is not just a decorative setting. It shapes how a writer chooses to distribute work, who can read it, and whether the writer can participate in the platform’s monetization system. Medium’s enrollment guidance says an active membership is one of the requirements, and that enrollment takes effect once the eligibility requirements are met.[1] This makes membership part of the product’s earning workflow, not merely an optional way to support other writers.</p><p>If a writer’s eligibility changes, the next questions are practical: can existing locked stories remain locked, what happens to future stories, and where can the writer find an explanation? Medium’s Partner Program terms say that if a participant is removed, their locked stories will be removed from behind the paywall.[2] That is a material consequence. It deserves an explanation that is easy to find and hard to misunderstand.</p><h3>A rule can be old and the rollout can still feel abrupt</h3><p>I do not want to pretend that the requirement was invented yesterday. The official terms show that Medium had already set an eligibility deadline for existing Partner Program participants in 2024.[2] That is part of the story, and leaving it out would make the criticism weaker, not stronger.</p><p>Still, a rule’s existence in a terms page is not the same as every affected writer understanding how it applies to them. Terms pages are important, but most writers do not revisit them every time they open the editor. If a creator can access a paywall control and later finds that new stories can no longer use it without a membership, the platform should communicate the transition directly, explain the reason, and state what the writer can still do.</p><p>The report shared on October 27 says the enforcement began that day for at least one writer.[3] That is enough to raise a reasonable question, but not enough to claim that Medium changed the rule for everyone overnight. I want to keep those facts separate. The requirement is documented. The timing and reach of the enforcement are less clear from the public information I could verify.</p><p>That uncertainty is itself part of the problem. Writers should not have to piece together a platform policy from individual screenshots, help pages, and community posts. If a rule is changing in practice, the platform should say who is affected, when it applies, whether there is a grace period, and where writers can find the official explanation.</p><p>A useful notice should let the recipient answer a few basic questions without searching through community threads. Does the requirement apply to every Partner Program writer, or only to accounts that were previously allowed to use the paywall without meeting the membership condition? Does it affect only new stories, or also stories that are already locked? What action can the writer take, and by what date? Medium’s terms address some of these consequences, including removal of locked stories if a participant is removed from the program.[2] The reported email also says enforcement begins immediately, but the public post does not establish how broadly that message was sent or whether every account was treated alike.[3]</p><p>I would find this easier to accept if the communication made the situation unambiguous. A link to the relevant eligibility page, a plain explanation of the account’s status, and reasonable time to decide would not remove the membership requirement. They would make the enforcement easier to understand and give writers a fair chance to choose whether the program still works for them. That is a modest expectation, not a demand that Medium change its business model.</p><h3>Why this disappoints me as a writer</h3><p>A publishing platform asks writers to invest more than words. We invest time in shaping stories, formatting them for the editor, learning the platform’s distribution habits, and building a relationship with readers there. In return, we expect the platform to make its rules understandable and its product behavior predictable.</p><p>That expectation is not a demand for guaranteed reach or income. No platform can promise that every story will find an audience. It is a basic expectation that important eligibility changes will be communicated in a way that respects the people who rely on the service.</p><p>When writers discover a restriction only after they try to use a feature, trust takes a hit. Even if the restriction is technically documented, the experience can still feel like the ground moved beneath them. Clear communication cannot make every policy popular, but it can prevent avoidable surprise and let writers make an informed decision.</p><p>Medium may reasonably decide that its Partner Program requires membership. A company can set eligibility criteria for a monetization program. But writers can also reasonably decide that the combination of a membership requirement, unclear enforcement timing, and uncertainty about future access is not a publishing arrangement they want to continue with.</p><p>That is where I have landed. I am not claiming Medium has banned public writing, and I am not claiming that a membership requirement appeared for the first time this week. I am saying that this experience has changed how much confidence I have in the platform as a place to keep publishing.</p><h3>This will be my last article on Medium</h3><p>I have decided that this will be my last article on Medium. I am sharing it on DEV because I want the point to be readable outside the platform I am criticizing.</p><p>This is not a call for writers to leave Medium, and it is not a claim that every writer will have the same experience. Some writers may find the membership worthwhile. Others may be comfortable publishing public stories without using the Partner Program. Those are valid choices.</p><p>For me, the issue is trust. I want to publish somewhere I can understand the rules, make a plan around them, and feel that important changes will be communicated clearly. I do not want to keep investing in a platform when I am uncertain about how its monetization controls will work for me or when I will learn about a change in practice.</p><p>Medium still lets writers publish public stories without paying for membership.[4] That fact deserves to be stated plainly. So does the other fact: access to the Partner Program and its paywall is tied to membership eligibility.[1] Writers should be able to weigh both points without exaggeration or confusion.</p><p>My disappointment is not that Medium has a business model. It is that the experience has left me less confident in the platform and more convinced that I should put my future writing elsewhere. I would have preferred a clear explanation before a restriction appeared in the workflow. Instead, I am making my decision now.</p><p>This is my final article on Medium. I will keep writing, but I will do it elsewhere.</p><h3>Sources</h3><p>[1] <a href="https://help.medium.com/hc/en-us/articles/39121627791639-Medium-Partner-Program-eligibility">Medium Partner Program eligibility</a><br>[2] <a href="https://help.medium.com/hc/en-us/articles/115011927148-Medium-Partner-Program-Terms">Medium Partner Program Terms</a><br>[3] <a href="https://www.reddit.com/r/Medium/comments/1xgxpnr/did_anyone_else_get_the_you_need_a_membership_to/">A writer’s report of a Medium enforcement notice on October 27, 2026</a><br>[4] <a href="https://help.medium.com/hc/en-us/articles/225168028-Using-Medium">Using Medium</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f3f1aa8e035" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Discord Server Chats May Appear on the Web. Check These Settings]]></title>
            <link>https://medium.com/@jamilxt/discord-server-chats-may-appear-on-the-web-check-these-settings-e687146958f9?source=rss-cbc015683892------2</link>
            <guid isPermaLink="false">https://medium.com/p/e687146958f9</guid>
            <category><![CDATA[web]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[discord]]></category>
            <category><![CDATA[privacy]]></category>
            <dc:creator><![CDATA[jamilxt]]></dc:creator>
            <pubDate>Wed, 28 Oct 2026 12:45:05 GMT</pubDate>
            <atom:updated>2026-10-28T12:45:05.798Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*pO9PHxjTx6gvjXT7.png" /></figure><p>A Discord setting can look like a simple yes-or-no choice, but web visibility depends on more than one switch. The server must be Discoverable, an administrator chooses which public channels can contribute, and each member has a separate control over their own messages.[1][2]</p><p>Discord began gradually rolling out its Web Presence controls on October 27, 2026.[1] Its current guidance says public-channel summaries may start appearing on server web pages from November 16, while individual messages may become searchable from mid-December.[1][2] The exact timing can vary during rollout.[1]</p><p>If you manage a server, or simply post in one, check both the server settings and your personal setting. They answer different questions.[1][2]</p><h3>First, distinguish a server page from searchable messages</h3><p>Discord’s <strong>Server Web Page</strong> is a public page for a Discoverable server.[1] Discord says search engines such as Google can show these pages.[1] The page can also display content drawn from eligible public channels.[1]</p><p>There are two kinds of channel content in the current Web Presence controls:[1]</p><ul><li><strong>Channel Summaries</strong> are short summaries of activity, shown on the server’s web page. Discord says these may cover discussions from November 16, 2026 onward.[1]</li><li><strong>Channel Messages</strong> are eligible answers from public channels that may appear in web search, in members’ own words. Discord says this feature is expected to roll out from mid-December 2026.[1][2]</li></ul><p>These are separate features.[1] Each has its own switch and its own channel selection.[1] A server can allow summaries for one channel and messages for another, or turn either feature off.[1]</p><p>That distinction matters when someone says, “I turned off the web setting.” Which one? A member’s personal message setting does not remove the server’s web page.[1][2] Disabling summaries does not automatically disable individual messages.[1] And a server setting does not replace each member’s control.[1][2]</p><h3>Check whether the server is Discoverable</h3><p>An administrator can check <strong>Server Settings → Access → Discoverable</strong>.[1] Discord says the server is Discoverable when it meets the requirements and Server Discovery is turned on.[1] If the Discoverable settings are unavailable or the server does not meet those requirements, it is not currently Discoverable.[1]</p><p>This is the first check because the web-page and channel-content controls apply to Discoverable servers. A personal preference switch by itself cannot make a non-Discoverable server public through this feature.[1][2]</p><h3>Review the server’s Web Presence controls</h3><p>For a Discoverable server, an owner or administrator can open <strong>Server Settings → Community → Web Presence</strong> on desktop or in a browser.[1] Discord says bots cannot change these settings.[1]</p><p>Review both sections, not just the first toggle you see:</p><ol><li>Check <strong>Channel Summaries on the web</strong>. Decide whether summaries should be enabled, and which public channels may contribute.</li><li>Check <strong>Channel Messages on the web</strong> separately. Choose the eligible channels or turn the feature off.</li><li>Save changes, then revisit the page to confirm the selected channels and switches.</li></ol><p>Discord says public channels in Discoverable servers are included by default, and the controls are rolling out gradually.[1] So do not assume the settings are off just because nobody on the team deliberately enabled them. Check the actual controls in the server.[1]</p><p>Channels that participate are labeled with an icon in the channel header. Discord says private channels, including role-restricted channels, are not eligible. Public threads or forums may be eligible when their parent channel and the relevant feature are enabled; private threads and private forums are excluded.[1][2]</p><h3>Members have a separate control</h3><p>Each member can find the personal switch under <strong>User Settings → Data &amp; Privacy → Show my message content from Discoverable channels on web pages</strong>.[2] Discord says this setting applies to the member’s account across servers, not to just one server.[2]</p><p>Discord’s current guidance says the setting is on by default in most regions and off by default in the EU/EEA, UK, Canada, Brazil, Australia, and South Korea.[2] Teen accounts are not eligible to have messages appear through this feature.[2] Regional rules and account eligibility matter, so check the account itself rather than inferring its state from another member’s screen.[2]</p><p>The personal switch affects messages sent while it has a particular value.[2] Messages sent while the setting is off will not appear as Channel Messages on the web.[2] Turning it off later does not automatically remove messages sent while it was on.[2] Those may still appear on Discord’s web pages.[2]</p><h3>Turning a switch off is not always removal</h3><p>If a server disables Channel Summaries or Channel Messages, Discord says that stops new content from being generated or shown going forward.[1] Content already published may remain visible until it is individually removed.[1]</p><p>For a specific message, Discord’s guidance is to delete the original message. That removes its visibility from Discord’s app and web pages. But search engines may retain cached or indexed copies for a while, and Discord does not control those copies. Search-result removal may take additional time or require a separate request to the search engine.[1][2]</p><p>If the goal is to remove the server’s page entirely, turning off both content features is not enough. Discord says the page remains live while the server is Discoverable. Turning off Discoverability takes down the page and changes the server back to a Community Server. Previously published content may still need separate removal, and search engines may retain cached results.[1]</p><h3>A practical privacy check</h3><p>Use this sequence when reviewing a server:</p><ul><li><strong>Server status:</strong> Is Server Discovery on under <strong>Server Settings → Access → Discoverable</strong>?</li><li><strong>Summaries:</strong> Which public channels are selected for Channel Summaries? Is the feature needed at all?</li><li><strong>Messages:</strong> Which public channels are selected for Channel Messages? Is this feature needed at all?</li><li><strong>Member setting:</strong> Is your own account’s “Show my message content…” switch on or off?</li><li><strong>Existing content:</strong> If something has already appeared, disable future inclusion, delete the original message if appropriate, and check whether a search engine still shows a cached result.</li></ul><p>The useful takeaway is not “Discord is exposing every server.”[1] The feature applies to Discoverable servers and eligible public channels, with separate controls for administrators and members.[1][2] The safer habit is to inspect those controls directly, especially during a gradual rollout, instead of treating one screenshot or one toggle as a complete privacy audit.</p><h3>Sources</h3><p>[1] <a href="https://support.discord.com/hc/en-us/articles/44049845164823-Discoverable-Server-Web-Presence">Discoverable Server Web Presence</a><br>[2] <a href="https://support.discord.com/hc/en-us/articles/44302319454359-Discoverable-Content-on-the-Web">Discoverable Content on the Web</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e687146958f9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stop Coding Agents From Trusting Downloads: Build a Workspace Preflight]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@jamilxt/stop-coding-agents-from-trusting-downloads-build-a-workspace-preflight-ead57ef3d361?source=rss-cbc015683892------2"><img src="https://cdn-images-1.medium.com/max/1000/0*GhFBd7lKkFeFrzLR.png" width="1000"></a></p><p class="medium-feed-snippet">A downloaded text file cannot normally execute itself. But an AI coding agent may read it, interpret it as an instruction, and run the&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@jamilxt/stop-coding-agents-from-trusting-downloads-build-a-workspace-preflight-ead57ef3d361?source=rss-cbc015683892------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@jamilxt/stop-coding-agents-from-trusting-downloads-build-a-workspace-preflight-ead57ef3d361?source=rss-cbc015683892------2</link>
            <guid isPermaLink="false">https://medium.com/p/ead57ef3d361</guid>
            <category><![CDATA[python]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ai-agent]]></category>
            <dc:creator><![CDATA[jamilxt]]></dc:creator>
            <pubDate>Tue, 27 Oct 2026 09:41:03 GMT</pubDate>
            <atom:updated>2026-10-27T09:41:03.140Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Flint Is a Coding Model. The Bigger Test Is Whether AI Can Build the Next One]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@jamilxt/flint-is-a-coding-model-the-bigger-test-is-whether-ai-can-build-the-next-one-165093f7cc5d?source=rss-cbc015683892------2"><img src="https://cdn-images-1.medium.com/max/1000/0*EiRDGixsfl3ZujMU.png" width="1000"></a></p><p class="medium-feed-snippet">A coding model that runs locally is useful. A coding model whose development was substantially automated by another AI system is a much&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@jamilxt/flint-is-a-coding-model-the-bigger-test-is-whether-ai-can-build-the-next-one-165093f7cc5d?source=rss-cbc015683892------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@jamilxt/flint-is-a-coding-model-the-bigger-test-is-whether-ai-can-build-the-next-one-165093f7cc5d?source=rss-cbc015683892------2</link>
            <guid isPermaLink="false">https://medium.com/p/165093f7cc5d</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[jamilxt]]></dc:creator>
            <pubDate>Tue, 27 Oct 2026 08:38:46 GMT</pubDate>
            <atom:updated>2026-10-27T08:38:46.203Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[OpenShell vs Docker Sandboxes: Which AI Agent Runtime Should You Choose?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@jamilxt/openshell-vs-docker-sandboxes-which-ai-agent-runtime-should-you-choose-de0f922e416e?source=rss-cbc015683892------2"><img src="https://cdn-images-1.medium.com/max/1000/0*NK8ir68Y38jmOsjD.png" width="1000"></a></p><p class="medium-feed-snippet">An AI coding agent can read a repository, run shell commands, install packages, and send network requests.</p><p class="medium-feed-link"><a href="https://medium.com/@jamilxt/openshell-vs-docker-sandboxes-which-ai-agent-runtime-should-you-choose-de0f922e416e?source=rss-cbc015683892------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@jamilxt/openshell-vs-docker-sandboxes-which-ai-agent-runtime-should-you-choose-de0f922e416e?source=rss-cbc015683892------2</link>
            <guid isPermaLink="false">https://medium.com/p/de0f922e416e</guid>
            <category><![CDATA[devtools]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[jamilxt]]></dc:creator>
            <pubDate>Tue, 27 Oct 2026 08:34:28 GMT</pubDate>
            <atom:updated>2026-10-27T08:34:28.314Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Goose vs Rust: Can a New Language Beat Rust at Memory-Safe Performance?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@jamilxt/goose-vs-rust-can-a-new-language-beat-rust-at-memory-safe-performance-cdc399321428?source=rss-cbc015683892------2"><img src="https://cdn-images-1.medium.com/max/1000/0*hqlRCcgwClJVS3VU.png" width="1000"></a></p><p class="medium-feed-snippet">A new programming language can attract attention by promising to be faster than Rust. That claim is easy to make and hard to evaluate. The&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@jamilxt/goose-vs-rust-can-a-new-language-beat-rust-at-memory-safe-performance-cdc399321428?source=rss-cbc015683892------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@jamilxt/goose-vs-rust-can-a-new-language-beat-rust-at-memory-safe-performance-cdc399321428?source=rss-cbc015683892------2</link>
            <guid isPermaLink="false">https://medium.com/p/cdc399321428</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[performance]]></category>
            <category><![CDATA[compilers]]></category>
            <category><![CDATA[rust]]></category>
            <dc:creator><![CDATA[jamilxt]]></dc:creator>
            <pubDate>Tue, 27 Oct 2026 08:32:02 GMT</pubDate>
            <atom:updated>2026-10-27T08:32:02.764Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Two Critical PHP Vulnerabilities: What to Do Before the Emergency Release]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@jamilxt/two-critical-php-vulnerabilities-what-to-do-before-the-emergency-release-f75415a482f4?source=rss-cbc015683892------2"><img src="https://cdn-images-1.medium.com/max/1000/0*BW96gnQWYbBt7GXF.png" width="1000"></a></p><p class="medium-feed-snippet">The PHP security team has scheduled an emergency security release for October 21, 2026, at 14:00 UTC. Its advance notice says the release&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@jamilxt/two-critical-php-vulnerabilities-what-to-do-before-the-emergency-release-f75415a482f4?source=rss-cbc015683892------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@jamilxt/two-critical-php-vulnerabilities-what-to-do-before-the-emergency-release-f75415a482f4?source=rss-cbc015683892------2</link>
            <guid isPermaLink="false">https://medium.com/p/f75415a482f4</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[php]]></category>
            <dc:creator><![CDATA[jamilxt]]></dc:creator>
            <pubDate>Wed, 21 Oct 2026 15:21:51 GMT</pubDate>
            <atom:updated>2026-10-21T15:21:51.240Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[PHP Patched the Two Critical RCE Flaws: Versions, Risk by SAPI, and Stopgaps]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@jamilxt/php-patched-the-two-critical-rce-flaws-versions-risk-by-sapi-and-stopgaps-e69fea104b8f?source=rss-cbc015683892------2"><img src="https://cdn-images-1.medium.com/max/1000/0*1pyeUOMDwQvGWW9I.png" width="1000"></a></p><p class="medium-feed-snippet">Earlier today, a preparation checklist on this blog covered PHP&#x2019;s upcoming emergency security release.</p><p class="medium-feed-link"><a href="https://medium.com/@jamilxt/php-patched-the-two-critical-rce-flaws-versions-risk-by-sapi-and-stopgaps-e69fea104b8f?source=rss-cbc015683892------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@jamilxt/php-patched-the-two-critical-rce-flaws-versions-risk-by-sapi-and-stopgaps-e69fea104b8f?source=rss-cbc015683892------2</link>
            <guid isPermaLink="false">https://medium.com/p/e69fea104b8f</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[php]]></category>
            <dc:creator><![CDATA[jamilxt]]></dc:creator>
            <pubDate>Wed, 21 Oct 2026 15:19:50 GMT</pubDate>
            <atom:updated>2026-10-21T15:22:31.929Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[PEG XL vs AVIF: Which Image Format Should You Actually Ship?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@jamilxt/peg-xl-vs-avif-which-image-format-should-you-actually-ship-645b62985d32?source=rss-cbc015683892------2"><img src="https://cdn-images-1.medium.com/max/1000/0*4fdXZrPRcrldf1sY.png" width="1000"></a></p><p class="medium-feed-snippet">For years the answer to &#x201C;which modern image format should I use?&#x201D; was easy. AVIF, full stop. JPEG XL was the promising codec Google helped&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@jamilxt/peg-xl-vs-avif-which-image-format-should-you-actually-ship-645b62985d32?source=rss-cbc015683892------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@jamilxt/peg-xl-vs-avif-which-image-format-should-you-actually-ship-645b62985d32?source=rss-cbc015683892------2</link>
            <guid isPermaLink="false">https://medium.com/p/645b62985d32</guid>
            <category><![CDATA[webdev]]></category>
            <category><![CDATA[performance]]></category>
            <category><![CDATA[image]]></category>
            <category><![CDATA[jpeg-xl]]></category>
            <dc:creator><![CDATA[jamilxt]]></dc:creator>
            <pubDate>Sun, 18 Oct 2026 08:49:13 GMT</pubDate>
            <atom:updated>2026-10-18T08:49:13.010Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The Bug Is on Every Android 17 Phone, but Not in the Source Code Anyone Can See]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@jamilxt/the-bug-is-on-every-android-17-phone-but-not-in-the-source-code-anyone-can-see-8e85318bb0b0?source=rss-cbc015683892------2"><img src="https://cdn-images-1.medium.com/max/1000/0*Cr6sMw8aiwIIXWNs.png" width="1000"></a></p><p class="medium-feed-snippet">Last weekend, Visual Pinball on Android stopped loading pinball tables out of nowhere. Not all of them. Only the tables whose VBScript&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@jamilxt/the-bug-is-on-every-android-17-phone-but-not-in-the-source-code-anyone-can-see-8e85318bb0b0?source=rss-cbc015683892------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@jamilxt/the-bug-is-on-every-android-17-phone-but-not-in-the-source-code-anyone-can-see-8e85318bb0b0?source=rss-cbc015683892------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e85318bb0b0</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[debugging]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[jamilxt]]></dc:creator>
            <pubDate>Sat, 17 Oct 2026 08:05:14 GMT</pubDate>
            <atom:updated>2026-10-17T08:05:14.841Z</atom:updated>
        </item>
    </channel>
</rss>