<?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: ahmed isam</title>
    <description>The latest articles on DEV Community by ahmed isam (@ahmed_isam_752b775a50fd90).</description>
    <link>https://dev.to/ahmed_isam_752b775a50fd90</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%2F4039609%2Fdbf219b9-4d68-415d-b462-ad4a379a5937.jpg</url>
      <title>DEV Community: ahmed isam</title>
      <link>https://dev.to/ahmed_isam_752b775a50fd90</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ahmed_isam_752b775a50fd90"/>
    <language>en</language>
    <item>
      <title>Who owns a digital person?</title>
      <dc:creator>ahmed isam</dc:creator>
      <pubDate>Sun, 11 Oct 2026 23:16:07 +0000</pubDate>
      <link>https://dev.to/ahmed_isam_752b775a50fd90/who-owns-a-digital-person-3530</link>
      <guid>https://dev.to/ahmed_isam_752b775a50fd90/who-owns-a-digital-person-3530</guid>
      <description>&lt;p&gt;--&lt;br&gt;
title: "Who owns a digital person?"&lt;br&gt;
description: "Every sentence in your capsule came from you."&lt;br&gt;
tags: ["owns", "digital", "person"]&lt;/p&gt;

&lt;h2&gt;
  
  
  canonical_url: &lt;a href="https://stillherememory.com/blog/who-owns-a-digital-person" rel="noopener noreferrer"&gt;https://stillherememory.com/blog/who-owns-a-digital-person&lt;/a&gt;
&lt;/h2&gt;

&lt;p&gt;Every sentence in your capsule came from you. It is stored encrypted so that our own team cannot open it and read it, and it is never used to train a model.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;H2 · What belongs to us.&lt;/strong&gt; The parts you did not write belong to us: the interface, the models that arrange a reply, the servers and the backups. That is the ordinary sense in which a tool belongs to the people who made it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;H2 · What was never available to own.&lt;/strong&gt; This is the piece most arguments skip past. Your mother, your partner, your child: a person is not an asset with a title attached, and nothing built from your writing changes that.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;H2 · Three questions that settle most disputes.&lt;/strong&gt; | Question | Our answer |&lt;br&gt;
|---|---|&lt;br&gt;
| Who can read what I wrote? | You, and whoever you choose to share it with. Not our staff, and not an advertiser.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;H2 · Where the line gets genuinely hard.&lt;/strong&gt; Two cases have no tidy answer, and we would rather say so than pretend otherwise. The first is family.&lt;/p&gt;

&lt;p&gt;The part worth keeping: In practice, ownership comes down to what happens on an ordinary Tuesday. Full write-up is on the source blog.&lt;/p&gt;

</description>
      <category>owns</category>
      <category>digital</category>
      <category>person</category>
    </item>
    <item>
      <title>Best Codex Skins by Color: Blue, Purple, Green</title>
      <dc:creator>ahmed isam</dc:creator>
      <pubDate>Sun, 11 Oct 2026 23:08:01 +0000</pubDate>
      <link>https://dev.to/ahmed_isam_752b775a50fd90/best-codex-skins-by-color-blue-purple-green-4fa6</link>
      <guid>https://dev.to/ahmed_isam_752b775a50fd90/best-codex-skins-by-color-blue-purple-green-4fa6</guid>
      <description>&lt;p&gt;--&lt;br&gt;
title: "Best Codex Skins by Color: Blue, Purple, Green"&lt;br&gt;
description: "Title: Best Codex Skins by Color: Blue, Purple, Green  Excerpt: Picking a Codex skin by color beats reading hex tables."&lt;br&gt;
tags: ["best", "codex", "skins", "color"]&lt;/p&gt;

&lt;h2&gt;
  
  
  canonical_url: &lt;a href="https://awesomecodexskin.com/blog/best-codex-skins-by-color-blue-purple-green/" rel="noopener noreferrer"&gt;https://awesomecodexskin.com/blog/best-codex-skins-by-color-blue-purple-green/&lt;/a&gt;
&lt;/h2&gt;

&lt;p&gt;Title: Best Codex Skins by Color: Blue, Purple, Green&lt;/p&gt;

&lt;p&gt;Excerpt: Picking a Codex skin by color beats reading hex tables. The best blue codex skin entries, the purple codex theme options worth installing, and the green editor skin picks that stay readable in a long session.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Full article (as published to &lt;code&gt;src/content/blog/best-codex-skins-by-color-blue-purple-green.md&lt;/code&gt;).&lt;/strong&gt; Color narrows a Codex skin faster than any spec sheet. You usually know whether you want a cool blue, something purple, or a muted green long before you care about hex values or install formats.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Blue: two entries, two install paths.&lt;/strong&gt; &lt;a href="https://dev.to/skins/blue-enchantress/"&gt;Blue Enchantress&lt;/a&gt; is the blue most people mean when they ask for one. It comes from codexthemes.ai, targets &lt;code&gt;codex-desktop&lt;/code&gt;, and runs on an electric blue accent at &lt;code&gt;#2D7DF6&lt;/code&gt; filed under neon-cyberpunk.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Purple: saturated and CLI-first.&lt;/strong&gt; &lt;a href="https://dev.to/skins/vivid-purple/"&gt;Vivid Purple (CLI)&lt;/a&gt; is the purple codex theme entry with real usage behind it. vufly ported it through Bearded Theme Ports, so it arrives as a &lt;code&gt;.tmTheme&lt;/code&gt; file rather than a prompt, and it targets &lt;code&gt;codex-cli&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Green: the quiet end of the palette.&lt;/strong&gt; &lt;a href="https://dev.to/skins/forest-mist/"&gt;Forest Mist&lt;/a&gt; is the green editor skin worth starting with, and it is the most-installed of the four here at 880 installs and 167 likes. It comes from the Cidala Tiger Skin project under an MIT license, targets &lt;code&gt;codex-desktop&lt;/code&gt;, and installs by prompt.&lt;/p&gt;

&lt;p&gt;The part worth keeping: Start with &lt;a href="https://dev.to/skins/forest-mist/"&gt;Forest Mist&lt;/a&gt; if you work long sessions, &lt;a href="https://dev.to/skins/blue-enchantress/"&gt;Blue Enchantress&lt;/a&gt; if you want a blue in one paste, or &lt;a href="https://dev.to/skins/vivid-purple/"&gt;Vivid Purple (CLI)&lt;/a&gt; if you are on Codex CLI and want something loud. Full write-up is on the source blog.&lt;/p&gt;

</description>
      <category>best</category>
      <category>codex</category>
      <category>skins</category>
      <category>color</category>
    </item>
    <item>
      <title>Personal Page Anti-Patterns: 5 Common Mistakes</title>
      <dc:creator>ahmed isam</dc:creator>
      <pubDate>Sun, 11 Oct 2026 00:26:52 +0000</pubDate>
      <link>https://dev.to/ahmed_isam_752b775a50fd90/personal-page-anti-patterns-5-common-mistakes-1anb</link>
      <guid>https://dev.to/ahmed_isam_752b775a50fd90/personal-page-anti-patterns-5-common-mistakes-1anb</guid>
      <description>&lt;p&gt;--&lt;br&gt;
title: "Personal Page Anti-Patterns: 5 Common Mistakes"&lt;br&gt;
description: "- slug：&lt;code&gt;homepage-mistakes-anti-patterns&lt;/code&gt; - canonical：&lt;code&gt;/blog/homepage-mistakes-anti-patterns&lt;/code&gt;  ---  |---|---|---|  ---  &lt;strong&gt;English Version.&lt;/strong&gt; Most homepage mistakes are not aesthetic."&lt;br&gt;
tags: ["personal", "page", "anti", "patterns"]&lt;/p&gt;

&lt;h2&gt;
  
  
  canonical_url: &lt;a href="https://dynamic-profile.shop/blog/homepage-mistakes-anti-patterns" rel="noopener noreferrer"&gt;https://dynamic-profile.shop/blog/homepage-mistakes-anti-patterns&lt;/a&gt;
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;slug：&lt;code&gt;homepage-mistakes-anti-patterns&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;canonical：&lt;code&gt;/blog/homepage-mistakes-anti-patterns&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;|---|---|---|&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;English Version.&lt;/strong&gt; Most homepage mistakes are not aesthetic. They sit in the order things appear, in whether there is any evidence, and in how much upkeep the layout demands.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Anti-pattern 1: the positioning line in paragraph three.&lt;/strong&gt; A large image takes the first screen. A greeting takes the second.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Anti-pattern 2: work shown without outcomes.&lt;/strong&gt; Six attractive screenshots and, underneath, "built in Figma". This is the most common of the portfolio mistakes: everything visible made it onto the page, and everything persuasive stayed off it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Anti-pattern 3: a contact path that costs too much.&lt;/strong&gt; The most expensive of the personal site errors turns contact into an obstacle. Three versions turn up repeatedly: an email address only, so the visitor composes a message from scratch; a direct message only, so they have to follow you first; or a form asking for five fields before it submits.&lt;/p&gt;

&lt;p&gt;The part worth keeping: Move the positioning line to the top. Full write-up is on the source blog.&lt;/p&gt;

</description>
      <category>personal</category>
      <category>page</category>
      <category>anti</category>
      <category>patterns</category>
    </item>
    <item>
      <title>Why Your Plugin List Is a Security Asset</title>
      <dc:creator>ahmed isam</dc:creator>
      <pubDate>Sun, 11 Oct 2026 00:21:38 +0000</pubDate>
      <link>https://dev.to/ahmed_isam_752b775a50fd90/why-your-plugin-list-is-a-security-asset-46fd</link>
      <guid>https://dev.to/ahmed_isam_752b775a50fd90/why-your-plugin-list-is-a-security-asset-46fd</guid>
      <description>&lt;p&gt;--&lt;br&gt;
title: "Why Your Plugin List Is a Security Asset"&lt;br&gt;
description: "Most teams cannot answer the question that decides whether a security advisory costs an afternoon or a week: which projects actually run the affected plugin."&lt;br&gt;
tags: ["plugin", "list", "security", "asset"]&lt;/p&gt;

&lt;h2&gt;
  
  
  canonical_url: &lt;a href="https://dshquality.com/blog/why-your-plugin-list-is-a-security-asset" rel="noopener noreferrer"&gt;https://dshquality.com/blog/why-your-plugin-list-is-a-security-asset&lt;/a&gt;
&lt;/h2&gt;

&lt;p&gt;Most teams cannot answer the question that decides whether a security advisory costs an afternoon or a week: which projects actually run the affected plugin. That gap is where the plugin inventory value lives, and it is also why your plugin list is a security asset rather than housekeeping.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What a plugin inventory is worth.&lt;/strong&gt; The list itself carries almost no value on a quiet Tuesday. Its worth shows up under pressure, in four specific situations.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The three days the list pays for itself.&lt;/strong&gt; Every team that keeps one hits these eventually, usually within a year. - The advisory day.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Building one in an afternoon.&lt;/strong&gt; This is a spreadsheet job. Do not wait for a platform decision.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Keeping it current without adding process.&lt;/strong&gt; Inventories fail for the same reason most checklists fail: they ask people to remember. Attach the update to something that already happens.&lt;/p&gt;

&lt;p&gt;The part worth keeping: Inventories fail for the same reason most checklists fail: they ask people to remember. Full write-up is on the source blog.&lt;/p&gt;

</description>
      <category>plugin</category>
      <category>list</category>
      <category>security</category>
      <category>asset</category>
    </item>
    <item>
      <title>Old Photo Identification: Reading the Clues in an Unknown Print</title>
      <dc:creator>ahmed isam</dc:creator>
      <pubDate>Sun, 11 Oct 2026 00:16:10 +0000</pubDate>
      <link>https://dev.to/ahmed_isam_752b775a50fd90/old-photo-identification-reading-the-clues-in-an-unknown-print-587n</link>
      <guid>https://dev.to/ahmed_isam_752b775a50fd90/old-photo-identification-reading-the-clues-in-an-unknown-print-587n</guid>
      <description>&lt;p&gt;--&lt;br&gt;
title: "Old Photo Identification: Reading the Clues in an Unknown Print"&lt;br&gt;
description: "---  &lt;strong&gt;English / EN.&lt;/strong&gt; Most unknown photographs are dated within ten minutes by something printed on the back, not by the clothes."&lt;br&gt;
tags: ["photo", "identification", "reading", "clues"]&lt;/p&gt;

&lt;h2&gt;
  
  
  canonical_url: &lt;a href="https://old-photo-restoration-saas.shop/blog/old-photo-identification-guide" rel="noopener noreferrer"&gt;https://old-photo-restoration-saas.shop/blog/old-photo-identification-guide&lt;/a&gt;
&lt;/h2&gt;




&lt;p&gt;&lt;strong&gt;English / EN.&lt;/strong&gt; Most unknown photographs are dated within ten minutes by something printed on the back, not by the clothes. Start with the paper, then use the frame to narrow the range, and write the answer on the print before it goes back in the box.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Start with the object you are holding.&lt;/strong&gt; Before squinting at collars and hemlines, look at what the photograph is printed on. The physical support narrows the range faster than anything inside the frame, and it is the one set of clues nobody in the family can argue about.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Clues inside the frame.&lt;/strong&gt; Clothing dates a photograph to a range rather than to a year, and that range is usually ten years wide. Establish the range first, then use the remaining clues to pull it tighter.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Studio imprints are the fastest shortcut.&lt;/strong&gt; A printed photographer name turns a guessing game into a look-up, because most studios occupied a given address for a short stretch. Once you have the address history, the print has a hard bracket around it.&lt;/p&gt;

&lt;p&gt;The part worth keeping: Log what is printed on the back first, then use /restore on old-photo-restoration-saas.shop to recover a street sign, a house number or a studio imprint that has faded past reading. Full write-up is on the source blog.&lt;/p&gt;

</description>
      <category>photo</category>
      <category>identification</category>
      <category>reading</category>
      <category>clues</category>
    </item>
    <item>
      <title>Who Can Delete a Minor Tweets</title>
      <dc:creator>ahmed isam</dc:creator>
      <pubDate>Sun, 11 Oct 2026 00:09:04 +0000</pubDate>
      <link>https://dev.to/ahmed_isam_752b775a50fd90/who-can-delete-a-minor-tweets-42af</link>
      <guid>https://dev.to/ahmed_isam_752b775a50fd90/who-can-delete-a-minor-tweets-42af</guid>
      <description>&lt;p&gt;--&lt;br&gt;
title: "Who Can Delete a Minor Tweets"&lt;br&gt;
description: "Children and teens data is treated as highly sensitive."&lt;br&gt;
tags: ["delete", "minor", "tweets"]&lt;/p&gt;

&lt;h2&gt;
  
  
  canonical_url: &lt;a href="https://digital-footprint-health.shop/blog/minor-tweets-deletion-rights" rel="noopener noreferrer"&gt;https://digital-footprint-health.shop/blog/minor-tweets-deletion-rights&lt;/a&gt;
&lt;/h2&gt;

&lt;p&gt;Children and teens data is treated as highly sensitive. They may not grasp the long-tail consequences of what they post, and that information can later feed profiling they never wanted as adults.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can a parent delete on their behalf?.&lt;/strong&gt; It depends on platform policy and local law. Most platforms let a guardian request deletion or restriction for their own minor child account, but usually require proof of guardianship, and the scope is limited to content under that account.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Where does the platform duty end.&lt;/strong&gt; Platforms generally must provide a request deletion entry point and apply stricter default privacy settings plus age verification for minor accounts. But they are not obligated to scrub the entire web, third-party reposts, search caches, and screenshots sit outside their deletion radius.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How to prepare guardianship proof.&lt;/strong&gt; Platforms differ slightly on materials, but the core is proving you are the account user legal guardian. Commonly accepted items include the household register page showing the relationship, the birth certificate, a court guardianship order, and the platform own appeal form.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Three things parents can actually do.&lt;/strong&gt; - First submit the minor deletion or restriction request on the platform;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;At the same time, set the account privacy to maximum and turn on login protection;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;For search caches, use each engine removal request flow and follow up patiently.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The part worth keeping: The line between child and adult is not the same everywhere. Full write-up is on the source blog.&lt;/p&gt;

</description>
      <category>delete</category>
      <category>minor</category>
      <category>tweets</category>
    </item>
    <item>
      <title>PDF Merge vs Split: When to Use Each One</title>
      <dc:creator>ahmed isam</dc:creator>
      <pubDate>Sun, 11 Oct 2026 00:03:23 +0000</pubDate>
      <link>https://dev.to/ahmed_isam_752b775a50fd90/pdf-merge-vs-split-when-to-use-each-one-1b16</link>
      <guid>https://dev.to/ahmed_isam_752b775a50fd90/pdf-merge-vs-split-when-to-use-each-one-1b16</guid>
      <description>&lt;p&gt;--&lt;br&gt;
title: "PDF Merge vs Split: When to Use Each One"&lt;br&gt;
description: "Choosing between merging and splitting comes down to one question: are you changing the number of files, or the range of pages? Merging collapses several files into one and solves delivery, archiving and continuous page numbering."&lt;br&gt;
tags: ["merge", "split", "when", "each"]&lt;/p&gt;

&lt;h2&gt;
  
  
  canonical_url: &lt;a href="https://pdfmergenext.shop/blog/pdf-merge-vs-split-when-to-use" rel="noopener noreferrer"&gt;https://pdfmergenext.shop/blog/pdf-merge-vs-split-when-to-use&lt;/a&gt;
&lt;/h2&gt;

&lt;p&gt;Choosing between merging and splitting comes down to one question: are you changing the number of files, or the range of pages? Merging collapses several files into one and solves delivery, archiving and continuous page numbering. Splitting cuts one file at page boundaries and solves size caps, recipients who should not see everything, and requests for a handful of pages.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What each one actually changes.&lt;/strong&gt; Merging changes the container. You put files A, B and C into final reading order and the tool copies their page objects into a new file in that sequence.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Side-by-side.&lt;/strong&gt; |---|---|---|&lt;/p&gt;

&lt;p&gt;The part worth keeping: |---|---|---| Full write-up is on the source blog.&lt;/p&gt;

</description>
      <category>merge</category>
      <category>split</category>
      <category>when</category>
      <category>each</category>
    </item>
    <item>
      <title>A Privacy Checklist for Chinese Students Abroad on X</title>
      <dc:creator>ahmed isam</dc:creator>
      <pubDate>Sat, 10 Oct 2026 23:57:30 +0000</pubDate>
      <link>https://dev.to/ahmed_isam_752b775a50fd90/a-privacy-checklist-for-chinese-students-abroad-on-x-2lnm</link>
      <guid>https://dev.to/ahmed_isam_752b775a50fd90/a-privacy-checklist-for-chinese-students-abroad-on-x-2lnm</guid>
      <description>&lt;p&gt;--&lt;br&gt;
title: "A Privacy Checklist for Chinese Students Abroad on X"&lt;br&gt;
description: "Passport numbers, study-visa IDs, dorm room numbers, class schedules, things you might post casually, are just as dangerous abroad."&lt;br&gt;
tags: ["privacy", "checklist", "chinese", "students"]&lt;/p&gt;

&lt;h2&gt;
  
  
  canonical_url: &lt;a href="https://digital-footprint-health.shop/blog/chinese-students-abroad-x-privacy-checklist" rel="noopener noreferrer"&gt;https://digital-footprint-health.shop/blog/chinese-students-abroad-x-privacy-checklist&lt;/a&gt;
&lt;/h2&gt;

&lt;p&gt;Passport numbers, study-visa IDs, dorm room numbers, class schedules, things you might post casually, are just as dangerous abroad. They piece together who you are, where you live, when you are where, and once misused, range from harassment to identity theft.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Location and itinerary are the first to lock down.&lt;/strong&gt; Flying to X today or weekend in this city broadcasts your empty window in real time. Post trip content after it ends, or share the feeling without exact time and place.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Politics and sensitive topics: handle by context.&lt;/strong&gt; Discussing local politics and social issues abroad is normal, but on highly sensitive topics, home-country stance, ethnicity, religion, use more restrained wording to avoid screenshots taken out of context. Remember: screenshots outlive the original, and context is lost in sharing.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A checklist you can follow.&lt;/strong&gt; - Passport, visa, address, schedule, never public;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Real-time location and unfinished trips, strip exact time and place before posting;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Highly sensitive topics, restrained wording, fewer emotional hashtags;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;If old posts already hold hard-private facts, clean them before posting more;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Set the account to followers only or stricter to reduce being found.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;What each of the three scenarios must guard against.&lt;/strong&gt; ScenarioMain riskResponse&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Visa applicationSensitive stance resurfacedClean old posts early, avoid extreme wording

Return screeningScreenshot taken out of contextRestrained wording, periodic self-check

Domestic job huntBackground check on old postsSecure hard-private facts first, tighten account
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;The part worth keeping: Treat the start of each term as a privacy checkpoint. Full write-up is on the source blog.&lt;/p&gt;

</description>
      <category>privacy</category>
      <category>checklist</category>
      <category>chinese</category>
      <category>students</category>
    </item>
    <item>
      <title>Hiding Your Pet During Screen Sharing: How to Hide Codex Pet Overlays Fast</title>
      <dc:creator>ahmed isam</dc:creator>
      <pubDate>Sat, 10 Oct 2026 23:48:44 +0000</pubDate>
      <link>https://dev.to/ahmed_isam_752b775a50fd90/hiding-your-pet-during-screen-sharing-how-to-hide-codex-pet-overlays-fast-3079</link>
      <guid>https://dev.to/ahmed_isam_752b775a50fd90/hiding-your-pet-during-screen-sharing-how-to-hide-codex-pet-overlays-fast-3079</guid>
      <description>&lt;p&gt;--&lt;br&gt;
title: "Hiding Your Pet During Screen Sharing: How to Hide Codex Pet Overlays Fast"&lt;br&gt;
description: "A pet placed so it sits in the corner of your eye all day ends up in every recording you make."&lt;br&gt;
tags: ["hiding", "during", "screen", "sharing"]&lt;/p&gt;

&lt;h2&gt;
  
  
  canonical_url: &lt;a href="https://codexpetgenerator.com/blog/hide-codex-pet-screen-share" rel="noopener noreferrer"&gt;https://codexpetgenerator.com/blog/hide-codex-pet-screen-share&lt;/a&gt;
&lt;/h2&gt;

&lt;p&gt;A pet placed so it sits in the corner of your eye all day ends up in every recording you make. Most people find out during playback, usually four minutes into a client demo they have already sent.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What screen sharing tools actually capture.&lt;/strong&gt; Here is the part people get wrong. A pet during screenshare behaves differently depending on what you hand over: pick one window and the pet usually falls outside the frame, pick a whole display and it rides along every time.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Four ways to pause codex pet motion.&lt;/strong&gt; These are ordered by how much they cost you. Start at the top and stop as soon as one of them solves it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Hide pixel pet overlays for one app instead of quitting everything.&lt;/strong&gt; Quitting Codex to sit through a fifteen-minute call costs more than it saves, especially with a long task still running in the background. Two options sit between doing nothing and killing the app.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Ninety seconds before the call.&lt;/strong&gt; This is the whole check, and it catches nearly everything that goes wrong:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Start the recording tool and read the preview thumbnail, not the meeting window&lt;/li&gt;
&lt;li&gt;Open the window you plan to share and look at all four corners&lt;/li&gt;
&lt;li&gt;Record five seconds, stop, and watch it back&lt;/li&gt;
&lt;li&gt;If you are sharing a whole display, hide the pet first&lt;/li&gt;
&lt;li&gt;Ask whoever else is on the call. They notice things you stopped seeing months ago&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The part worth keeping: |------|-----|&lt;br&gt;
| slug (en) | &lt;code&gt;hide-codex-pet-screen-share&lt;/code&gt; |&lt;br&gt;
| slug (zh) | &lt;code&gt;hide-codex-pet-screen-share-zh&lt;/code&gt; |&lt;br&gt;
| author | PetGen |&lt;br&gt;
| date | 2026-10-11 |&lt;br&gt;
| related | codex-pet-not-showing-fixes, dual-monitor-pet-placement, codex-pet-9-animation-states, install-codex-pet-terminal | Full write-up is on the source blog.&lt;/p&gt;

</description>
      <category>hiding</category>
      <category>during</category>
      <category>screen</category>
      <category>sharing</category>
    </item>
    <item>
      <title>Does Compressing an Image Reduce Quality? Six Myths Checked</title>
      <dc:creator>ahmed isam</dc:creator>
      <pubDate>Sat, 10 Oct 2026 23:42:24 +0000</pubDate>
      <link>https://dev.to/ahmed_isam_752b775a50fd90/does-compressing-an-image-reduce-quality-six-myths-checked-4p9n</link>
      <guid>https://dev.to/ahmed_isam_752b775a50fd90/does-compressing-an-image-reduce-quality-six-myths-checked-4p9n</guid>
      <description>&lt;p&gt;--&lt;br&gt;
title: "Does Compressing an Image Reduce Quality? Six Myths Checked"&lt;br&gt;
description: "---  &lt;strong&gt;English / EN.&lt;/strong&gt; Does compressing an image reduce quality? Sometimes it does and sometimes it does not, and the difference comes down to which kind ran."&lt;br&gt;
tags: ["compressing", "image", "reduce", "quality"]&lt;/p&gt;

&lt;h2&gt;
  
  
  canonical_url: &lt;a href="https://image-compressor-saas.shop/blog/does-compressing-image-reduce-quality" rel="noopener noreferrer"&gt;https://image-compressor-saas.shop/blog/does-compressing-image-reduce-quality&lt;/a&gt;
&lt;/h2&gt;




&lt;p&gt;&lt;strong&gt;English / EN.&lt;/strong&gt; Does compressing an image reduce quality? Sometimes it does and sometimes it does not, and the difference comes down to which kind ran. Lossy compression discards high frequency detail for good.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Lossy and lossless discard different things.&lt;/strong&gt; - Lossy compression drops detail the eye struggles to notice, including the colour information that chroma subsampling halves or quarters&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Lossless compression changes nothing but the encoding, so PNG, ZIP and lossless WebP restore every pixel exactly&lt;/li&gt;
&lt;li&gt;The quality slider on a JPEG export controls how aggressive the quantisation table is, and even 100 stays lossy&lt;/li&gt;
&lt;li&gt;Lossy WebP and AVIF discard data too, they just hide the damage better at the same file size&lt;/li&gt;
&lt;li&gt;HEIC borrows video compression machinery and pays for its small files the same way&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;One question settles it: can the pixels be restored exactly? If yes, the route was lossless. If no, data left the building.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What one pass actually costs.&lt;/strong&gt; Take a JPEG straight out of a camera down to 60 or 75 percent quality, zoom to actual pixels and inspect a flat area. Faint banding shows up in a sky or a painted wall.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Six claims, checked one at a time.&lt;/strong&gt; - Every kind of compression costs quality. Wrong.&lt;/p&gt;

&lt;p&gt;The part worth keeping: Compress once on image-compressor-saas.shop and keep the master file separate, with nothing leaving your machine. Full write-up is on the source blog.&lt;/p&gt;

</description>
      <category>compressing</category>
      <category>image</category>
      <category>reduce</category>
      <category>codequality</category>
    </item>
    <item>
      <title>Your Old Tweets May Be Feeding AI Training Data</title>
      <dc:creator>ahmed isam</dc:creator>
      <pubDate>Sat, 10 Oct 2026 23:32:35 +0000</pubDate>
      <link>https://dev.to/ahmed_isam_752b775a50fd90/your-old-tweets-may-be-feeding-ai-training-data-2iek</link>
      <guid>https://dev.to/ahmed_isam_752b775a50fd90/your-old-tweets-may-be-feeding-ai-training-data-2iek</guid>
      <description>&lt;p&gt;--&lt;br&gt;
title: "Your Old Tweets May Be Feeding AI Training Data"&lt;br&gt;
description: "Large models need astronomical amounts of text."&lt;br&gt;
tags: ["tweets", "feeding", "training", "data"]&lt;/p&gt;

&lt;h2&gt;
  
  
  canonical_url: &lt;a href="https://digital-footprint-health.shop/blog/ai-scraping-old-tweets-training-data" rel="noopener noreferrer"&gt;https://digital-footprint-health.shop/blog/ai-scraping-old-tweets-training-data&lt;/a&gt;
&lt;/h2&gt;

&lt;p&gt;Large models need astronomical amounts of text. Public web pages, books, forums, and open datasets are all sources, and public social posts are high-value corpus because of their volume and real conversational context.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Where your old tweets may land.&lt;/strong&gt; - The public posts themselves. If set to public, the odds of being scraped are high, often without separate consent.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can ordinary users retract.&lt;/strong&gt; What you can do first is reduce the source: set old tweets private or delete them to lower the chance of future scraping; for what platforms already grabbed, watch for objection, deletion, or opt-out mechanisms they and regulators provide, though effectiveness varies by jurisdiction. The more practical move is to clear the truly dangerous hard-private facts first, those matter more than being read by a model.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A often-ignored angle: training data also shapes model bias.&lt;/strong&gt; The emotional and extreme expressions in public tweets subtly enter the model tone. A heated line you posted years ago may reappear, in another form, inside some AI answer.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;If you want to actively opt out of training sets.&lt;/strong&gt; There is no one-click opt-out yet, but you can stack a few moves: batch-privatize or delete historical public posts to lower future scrape odds; watch platform-published objection and deletion channels and object to clearly violating scrapes; for already-trained models, influence is limited, so focus on source control. Treat it as a long-term action like cleaning hard-private facts, more practical than hoping for a magic switch someday.&lt;/p&gt;

&lt;p&gt;The part worth keeping: Since public scraping became a flashpoint, several platforms updated terms, added opt-out or objection forms, or restricted bulk access through their APIs. Full write-up is on the source blog.&lt;/p&gt;

</description>
      <category>tweets</category>
      <category>feeding</category>
      <category>training</category>
      <category>data</category>
    </item>
    <item>
      <title>Why Your X Archive Often Misses the Last Month of Tweets</title>
      <dc:creator>ahmed isam</dc:creator>
      <pubDate>Sat, 10 Oct 2026 23:24:34 +0000</pubDate>
      <link>https://dev.to/ahmed_isam_752b775a50fd90/why-your-x-archive-often-misses-the-last-month-of-tweets-1d2</link>
      <guid>https://dev.to/ahmed_isam_752b775a50fd90/why-your-x-archive-often-misses-the-last-month-of-tweets-1d2</guid>
      <description>&lt;p&gt;--&lt;br&gt;
title: "Why Your X Archive Often Misses the Last Month of Tweets"&lt;br&gt;
description: "The X archive is essentially a periodically generated data package."&lt;br&gt;
tags: ["archive", "often", "misses", "last"]&lt;/p&gt;

&lt;h2&gt;
  
  
  canonical_url: &lt;a href="https://digital-footprint-health.shop/blog/x-archive-missing-recent-tweets" rel="noopener noreferrer"&gt;https://digital-footprint-health.shop/blog/x-archive-missing-recent-tweets&lt;/a&gt;
&lt;/h2&gt;

&lt;p&gt;The X archive is essentially a periodically generated data package. After you request it, the system needs time to bundle it, and what you can download is often the state from some point before your request, not a real-time full copy at the exact second you clicked.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why the last 30 days are often missing.&lt;/strong&gt; Several causes stack up: the packaging queue has latency; very active accounts generate larger files and slower bundles; and some real-time interactions, a just-made retweet, a just-tapped like, are not in the main archive structure at all. The result: the more active you are, the more visible the recent gap becomes.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Coverage by download method.&lt;/strong&gt; MethodRecent tweetsSpeedBest for&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Web full archive requestOften weeks of gapSlow, queueOne-off full backup

API incremental pullMore completeFastTechnical users, periodic sync

Third-party exporterDepends on API scopeMediumStructured analysis
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;Archive versus real-time API trade-off.&lt;/strong&gt; If you only want a privacy check, the web archive is usually enough, as long as you fill the recent gap. If you run long-term analytics and need day-by-day comparison, a real-time API or incremental pull fits better, at the cost of some technical setup.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How to close the gap.&lt;/strong&gt; - Wait a few days and re-request. Under the snapshot model, requesting again later usually backfills recent content.&lt;/p&gt;

&lt;p&gt;The part worth keeping: The simplest version of this is a recurring reminder: request, download, scan, repeat. Full write-up is on the source blog.&lt;/p&gt;

</description>
      <category>archive</category>
      <category>often</category>
      <category>misses</category>
      <category>last</category>
    </item>
  </channel>
</rss>
