<?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: dylan yu</title>
    <description>The latest articles on DEV Community by dylan yu (@dylan_yu_7ffff00b5355942d).</description>
    <link>https://dev.to/dylan_yu_7ffff00b5355942d</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%2F4028400%2Fdac3210c-01da-48e4-93e3-fba394abe9e2.png</url>
      <title>DEV Community: dylan yu</title>
      <link>https://dev.to/dylan_yu_7ffff00b5355942d</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/dylan_yu_7ffff00b5355942d"/>
    <language>en</language>
    <item>
      <title>Camera Shutter Count on Used Bodies: What the Number Means and What a Sample File Can Leak</title>
      <dc:creator>dylan yu</dc:creator>
      <pubDate>Thu, 05 Nov 2026 11:22:29 +0000</pubDate>
      <link>https://dev.to/dylan_yu_7ffff00b5355942d/camera-shutter-count-on-used-bodies-what-the-number-means-and-what-a-sample-file-can-leak-23d</link>
      <guid>https://dev.to/dylan_yu_7ffff00b5355942d/camera-shutter-count-on-used-bodies-what-the-number-means-and-what-a-sample-file-can-leak-23d</guid>
      <description>&lt;p&gt;When you buy a used camera, the shutter count is one of the first numbers people ask for. It is a wear signal, not a certificate. This post explains what the count actually measures, why two bodies with the same number can have very different lives, and what to watch for when a seller sends you a sample image to "prove" the count.&lt;/p&gt;

&lt;h2&gt;
  
  
  What shutter count measures
&lt;/h2&gt;

&lt;p&gt;On bodies with a mechanical shutter, the count is a running total of how many times that shutter has fired. Dealers treat it like mileage. Manufacturers publish rated lifespans for many shutters; a count far below the rating on an older body can look attractive, and a count near the rating can push the price down.&lt;/p&gt;

&lt;p&gt;Electronic-shutter frames on hybrid bodies may never bump the mechanical counter. A camera used mostly for silent shooting can look "low mileage" while the sensor, buttons, and mounts have seen heavy use. Always ask how the owner shot, not only what the counter says.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where the number lives
&lt;/h2&gt;

&lt;p&gt;The count is often buried in maker notes inside a JPEG or RAW, not in a friendly, portable EXIF label every viewer shows. Tools differ by brand. Some bodies expose the count only through a menu or a tethered utility. A single sample file is useful when the maker notes are present; it is useless when the body never wrote them into that file.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a "proof" file can leak
&lt;/h2&gt;

&lt;p&gt;Sellers often email or upload a JPEG from the body to prove the count. That file can also carry:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;GPS if location tagging was on&lt;/li&gt;
&lt;li&gt;serial number and lens identifiers&lt;/li&gt;
&lt;li&gt;exact capture time and timezone&lt;/li&gt;
&lt;li&gt;other private fields you never meant to publish with a marketplace listing&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you are the seller, send a screenshot of the count UI, or a cleaned image that still shows the maker-note field your buyer cares about. If you are the buyer, treat an uncleaned sample as a privacy risk for the seller — and as a reminder that metadata travels farther than the one number you asked for.&lt;/p&gt;

&lt;h2&gt;
  
  
  A short routine before you share a sample
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Confirm the count with a viewer that can read the maker notes for that brand.&lt;/li&gt;
&lt;li&gt;Decide whether the buyer needs the raw file or only a cropped screenshot of the count.&lt;/li&gt;
&lt;li&gt;If you share an image file, strip location and other personal fields from the copy. A practical option is to &lt;a href="https://removeaimeta.com/remove-exif" rel="noopener noreferrer"&gt;delete EXIF data&lt;/a&gt; on the shared copy while you keep the archive original.&lt;/li&gt;
&lt;li&gt;Do not overwrite your original. Keep the untouched file for your own records.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Buying checklist (short)
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Ask for count, service history, and whether the shutter was replaced (a replacement can reset the story the number tells).&lt;/li&gt;
&lt;li&gt;Prefer a live video of the menu or a tethered readout when the brand does not write the count into files.&lt;/li&gt;
&lt;li&gt;Price the body against rated shutter life and actual condition of seals, sensor dust, and mounts — not the counter alone.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Shutter count is a useful clue. It is not the whole condition report, and the file you use to prove it should not become an accidental dump of location and serial data.&lt;/p&gt;

</description>
      <category>photography</category>
      <category>privacy</category>
      <category>beginners</category>
      <category>tooling</category>
    </item>
    <item>
      <title>How to Check and Remove GPS Location From Your Phone Photos</title>
      <dc:creator>dylan yu</dc:creator>
      <pubDate>Tue, 03 Nov 2026 11:33:41 +0000</pubDate>
      <link>https://dev.to/dylan_yu_7ffff00b5355942d/how-to-check-and-remove-gps-location-from-your-phone-photos-2poi</link>
      <guid>https://dev.to/dylan_yu_7ffff00b5355942d/how-to-check-and-remove-gps-location-from-your-phone-photos-2poi</guid>
      <description>&lt;p&gt;Every time you take a photo with your phone, there is a good chance the exact spot where you stood was saved inside the file. Not in the picture itself, but in a hidden block of data that travels with the image when you email it, upload it to a marketplace, or drop it into a shared folder.&lt;/p&gt;

&lt;p&gt;This post walks through how to see whether a photo carries location data, and how to strip it before you share.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where the location lives
&lt;/h2&gt;

&lt;p&gt;Phone cameras write GPS coordinates into the photo's metadata. Most of it sits in EXIF fields such as latitude, longitude and altitude, and some apps copy the same information into XMP or IPTC blocks. Newer editing and AI tools may also add C2PA Content Credentials, which record how the image was made or edited.&lt;/p&gt;

&lt;p&gt;None of this is visible when you look at the photo. It only shows up when someone opens the file details or runs it through a metadata viewer.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to check a photo on iPhone
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Open the photo in the Photos app.&lt;/li&gt;
&lt;li&gt;Swipe up, or tap the info button.&lt;/li&gt;
&lt;li&gt;If a map appears under the photo, the file has GPS coordinates.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You can tap &lt;strong&gt;Adjust&lt;/strong&gt; next to the location to change it, or remove it for that copy when sharing by tapping &lt;strong&gt;Options&lt;/strong&gt; on the share sheet and turning off &lt;strong&gt;Location&lt;/strong&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to check a photo on Android
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Open the photo in Google Photos.&lt;/li&gt;
&lt;li&gt;Swipe up to see the details panel.&lt;/li&gt;
&lt;li&gt;Look for a map or a place name.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Google Photos lets you remove an estimated location, but a location saved by the camera can still be inside the original file depending on how you export it. Turning off location tags in the camera app stops new photos from being tagged, but it does not clean the ones you already have.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to check on a computer
&lt;/h2&gt;

&lt;p&gt;On Windows, right-click the file, choose &lt;strong&gt;Properties&lt;/strong&gt;, then &lt;strong&gt;Details&lt;/strong&gt;, and scroll to the GPS section. On macOS, open the image in Preview and choose &lt;strong&gt;Tools &amp;gt; Show Inspector&lt;/strong&gt;, then look for a GPS tab.&lt;/p&gt;

&lt;p&gt;If you see coordinates there, anyone you send the original file to can see them too.&lt;/p&gt;

&lt;h2&gt;
  
  
  Removing GPS before you share
&lt;/h2&gt;

&lt;p&gt;There are a few ways to do it:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Share sheet options.&lt;/strong&gt; iPhone can drop location for a single share. This is quick, but easy to forget, and it only covers that one send.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Windows "Remove Properties and Personal Information".&lt;/strong&gt; In the Details tab there is a link that can create a copy without most properties. It works, but it is clunky for more than a couple of files.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A browser tool.&lt;/strong&gt; If you want to clean a file without installing anything, you can &lt;a href="https://removeaimeta.com/remove-exif" rel="noopener noreferrer"&gt;delete EXIF data&lt;/a&gt; right in your browser. Remove AI Meta strips embedded XMP, C2PA, IPTC and GPS metadata from the image locally, so the file is not uploaded anywhere. It is free for 1 image, and $9.99 one-time if you need more.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Command line.&lt;/strong&gt; If you are comfortable in a terminal, ExifTool can remove every tag in one command and handle whole folders.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Whichever route you pick, open the cleaned copy afterwards and check the details panel again. If the map is gone, the location is gone.&lt;/p&gt;

&lt;h2&gt;
  
  
  A quick habit that helps
&lt;/h2&gt;

&lt;p&gt;Before posting a photo of your home, your car, or your kids anywhere public, run it through a metadata check. It takes a few seconds and closes one of the easiest ways for strangers to work out where a picture was taken.&lt;/p&gt;

&lt;p&gt;Some platforms strip location on upload, but many file-sharing services, email attachments and messaging apps that send "original quality" files do not. Cleaning the file yourself means you do not have to guess.&lt;/p&gt;

</description>
      <category>privacy</category>
      <category>photography</category>
      <category>security</category>
      <category>beginners</category>
    </item>
    <item>
      <title>What Your Photos Reveal Before You Hit Share: EXIF, XMP, IPTC and C2PA Explained</title>
      <dc:creator>dylan yu</dc:creator>
      <pubDate>Tue, 03 Nov 2026 10:50:53 +0000</pubDate>
      <link>https://dev.to/dylan_yu_7ffff00b5355942d/what-your-photos-reveal-before-you-hit-share-exif-xmp-iptc-and-c2pa-explained-d0b</link>
      <guid>https://dev.to/dylan_yu_7ffff00b5355942d/what-your-photos-reveal-before-you-hit-share-exif-xmp-iptc-and-c2pa-explained-d0b</guid>
      <description>&lt;p&gt;A photo file carries more than the picture. Open the properties of almost any JPEG straight off a phone and you will find the camera model, the lens, the exposure settings, sometimes a serial number, and very often a pair of GPS coordinates accurate enough to find a front door. Images that came out of a generator or an editing app can carry a different set of records: an XMP block naming the software, an IPTC field describing how the image was made, or a C2PA manifest that records its edit history.&lt;/p&gt;

&lt;p&gt;None of this is visible when you look at the image. All of it travels with the file when you email it, drop it in a shared folder, or upload it somewhere that keeps the original.&lt;/p&gt;

&lt;p&gt;This post walks through what those layers actually are, what to expect when you post to the big platforms, and a simple routine for cleaning files before they leave your machine.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is actually hiding inside an image file
&lt;/h2&gt;

&lt;p&gt;It helps to think of metadata as several separate layers rather than one blob. Different tools write different layers, and a cleaner that handles one may leave another untouched.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;EXIF.&lt;/strong&gt; This is the oldest and most familiar layer. Cameras and phones write it at capture time: make and model, lens, focal length, shutter speed, ISO, the time the shot was taken, orientation, and, if location services were on, GPS latitude and longitude. Some cameras also store a body serial number and a shutter count. For most people, the GPS fields are the real privacy concern. A photo of a new couch posted to a marketplace listing can quietly point at your home.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;XMP.&lt;/strong&gt; Adobe's Extensible Metadata Platform is a flexible, XML-based layer. Editing apps use it to record the software that touched a file, edit settings, ratings, and keywords. Image generators and AI-assisted editors often write XMP fields that name the tool or describe how the image was produced.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;IPTC.&lt;/strong&gt; Originally built for news photography, IPTC fields hold captions, credits, copyright notices, and keywords. One field matters more than it used to: DigitalSourceType, which can state that an image was created or altered by a generative model. Several platforms read it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;C2PA / Content Credentials.&lt;/strong&gt; This is the newest layer. A C2PA manifest is a signed record attached to a file that describes where it came from and what was done to it. Some cameras, editing suites, and AI image tools write one. It is designed to be verifiable, which is exactly why some people want to keep it and others need to remove it before sharing a draft, a client file, or a personal photo.&lt;/p&gt;

&lt;p&gt;There is one more category worth naming because people often confuse it with metadata: &lt;strong&gt;pixel-level watermarks&lt;/strong&gt;. Some generators embed an invisible signal into the image itself rather than into a tag. Removing metadata does not touch those. If a tool tells you otherwise, be sceptical. A metadata cleaner rewrites the file's tags; it does not alter the picture, and it cannot promise that no system will ever classify an image.&lt;/p&gt;

&lt;p&gt;So when someone says they want to "strip metadata," it is worth asking which layer they mean. Location privacy is an EXIF problem. A stray generator tag is usually XMP, IPTC, or C2PA. Each needs to be checked separately.&lt;/p&gt;

&lt;h2&gt;
  
  
  What platforms keep, strip, or read
&lt;/h2&gt;

&lt;p&gt;Here is where a lot of confusion starts. People assume that because a big platform "strips metadata," their file is clean. In practice, platforms re-encode uploads in different ways, change their pipelines without much notice, and may read certain fields (especially AI-related ones) before discarding them. The table below is a cautious summary of what is widely reported. Treat it as a starting point, not a guarantee, and test with your own files.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Platform&lt;/th&gt;
&lt;th&gt;EXIF / GPS on the public copy&lt;/th&gt;
&lt;th&gt;AI-related fields (IPTC / C2PA)&lt;/th&gt;
&lt;th&gt;What to keep in mind&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Instagram&lt;/td&gt;
&lt;td&gt;Generally removed from the image people download&lt;/td&gt;
&lt;td&gt;May be read at upload and used for an AI label&lt;/td&gt;
&lt;td&gt;A label is applied to the post; cleaning the file later does not remove it from a live post&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Facebook&lt;/td&gt;
&lt;td&gt;Generally removed from the public copy&lt;/td&gt;
&lt;td&gt;May be read at upload, similar to Instagram&lt;/td&gt;
&lt;td&gt;The original file may still be stored on the platform's side&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;X (Twitter)&lt;/td&gt;
&lt;td&gt;Generally removed from photos&lt;/td&gt;
&lt;td&gt;Handling of C2PA is not clearly documented&lt;/td&gt;
&lt;td&gt;Files sent another way, such as attachments, may not be re-encoded&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;LinkedIn&lt;/td&gt;
&lt;td&gt;Behaviour varies by upload type&lt;/td&gt;
&lt;td&gt;Some posts show Content Credentials information&lt;/td&gt;
&lt;td&gt;Documents and native images may be handled differently&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Pinterest&lt;/td&gt;
&lt;td&gt;Generally re-encoded&lt;/td&gt;
&lt;td&gt;May read AI-related fields for labelling&lt;/td&gt;
&lt;td&gt;Pins saved from elsewhere carry whatever the source kept&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Email, cloud drives, chat file transfers&lt;/td&gt;
&lt;td&gt;Usually preserved exactly&lt;/td&gt;
&lt;td&gt;Usually preserved exactly&lt;/td&gt;
&lt;td&gt;This is where most accidental location leaks happen&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The last row matters most. Social feeds tend to re-encode, which removes a lot of EXIF as a side effect. Email attachments, shared drive links, messaging apps sending "as file," and marketplace or forum uploads frequently hand over the original bytes untouched. If you only clean files "before social media," you are protecting the channel that needed it least.&lt;/p&gt;

&lt;p&gt;Two other points are worth keeping in mind. First, a platform reading an AI field at upload means the label decision happens then. If a post already has a label, editing the file you have on your laptop changes nothing about the live post; you would need to delete it and upload a cleaned file. Second, platforms do not only look at tags. A clean file can still be labelled if a platform detects a pixel watermark or the uploader self-discloses. Honest expectations save a lot of frustration.&lt;/p&gt;

&lt;h2&gt;
  
  
  A simple cleaning routine before you share
&lt;/h2&gt;

&lt;p&gt;The good news is that cleaning a file properly takes less than a minute once it is a habit. Here is the routine I use.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Inspect before you strip.&lt;/strong&gt; Open the file in a metadata viewer and see what is actually there. You may find GPS on a photo you assumed was clean, or a generator tag on an image you only lightly edited. Knowing what is present tells you which mode you need.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Pick the right scope.&lt;/strong&gt; If you are sharing a personal photo and only care about location and camera details, you want to &lt;a href="https://removeaimeta.com/remove-exif" rel="noopener noreferrer"&gt;delete EXIF data&lt;/a&gt;, specifically GPS and device fields, while leaving everything else as it is. If you are working with generated or AI-edited images and need the provenance records gone before a draft goes to a client, you want to &lt;a href="https://removeaimeta.com/remove-ai-info" rel="noopener noreferrer"&gt;remove AI metadata&lt;/a&gt;: the C2PA manifest, the IPTC DigitalSourceType value, and generator XMP. If you want a fully bare file, strip everything.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Clean locally where you can.&lt;/strong&gt; A browser-based cleaner that processes the file on your own device means the photo never has to be uploaded to someone else's server. That is worth checking for any tool you use, especially with personal photos. Command-line tools such as ExifTool are excellent if you are comfortable in a terminal; they give fine control, though C2PA manifests and some XMP blocks need the right flags.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Verify after cleaning.&lt;/strong&gt; This step is the one most people skip. Reopen the cleaned file and confirm the fields you cared about are gone. A good cleaner shows you a before-and-after list. If the GPS row is still there, the job is not done.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5. Keep your originals.&lt;/strong&gt; Cleaning should produce a new file, not overwrite your archive. You may want the original capture date and camera data later for your own records. Only the shared copy needs to be bare.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;6. Re-upload rather than edit, if a post already exists.&lt;/strong&gt; If a platform has already labelled or stored a file, the clean version only helps when it replaces the original upload.&lt;/p&gt;

&lt;p&gt;For my own workflow I use &lt;a href="https://removeaimeta.com/ai-metadata-cleaner" rel="noopener noreferrer"&gt;this metadata remover&lt;/a&gt;, which runs in the browser tab, shows the before-and-after field report, and lets me choose between EXIF/GPS only, AI provenance only, or everything. It clears embedded XMP, C2PA, IPTC, and GPS metadata from JPEG, PNG, and WebP files, and it leaves the pixels alone. One file is free to try; unlimited files and batch ZIP downloads are a one-time $9.99 rather than a subscription. Other tools work too. What matters is that you inspect, clean the right layer, and verify.&lt;/p&gt;

&lt;p&gt;A few practical habits round this out:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Turn off location tagging in your phone's camera app if you rarely need it. Prevention is easier than cleanup.&lt;/li&gt;
&lt;li&gt;Be careful with "send as file" or "original quality" options in chat apps. They usually keep everything.&lt;/li&gt;
&lt;li&gt;Remember that screenshots carry their own metadata, often the device model and time, even if they drop the original photo's GPS.&lt;/li&gt;
&lt;li&gt;For batches, such as a product shoot or a set of carousel slides, clean them together so none slips through.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Metadata is not sinister on its own. It is useful for organising your library, proving authorship, and documenting edits. The problem is only that it travels further than most people expect. A short inspect, clean, and verify routine keeps the useful parts in your archive and the private parts out of other people's hands.&lt;/p&gt;

</description>
      <category>privacy</category>
      <category>photography</category>
      <category>webdev</category>
      <category>ai</category>
    </item>
    <item>
      <title>Birth Time Uncertainty Breaks House Placements First</title>
      <dc:creator>dylan yu</dc:creator>
      <pubDate>Wed, 28 Oct 2026 10:40:19 +0000</pubDate>
      <link>https://dev.to/dylan_yu_7ffff00b5355942d/birth-time-uncertainty-breaks-house-placements-first-463b</link>
      <guid>https://dev.to/dylan_yu_7ffff00b5355942d/birth-time-uncertainty-breaks-house-placements-first-463b</guid>
      <description>&lt;p&gt;If you compute a natal chart in the browser, the first accuracy problem is usually not the ephemeris — it is the birth time.&lt;/p&gt;

&lt;p&gt;An hour of error moves the Ascendant and rearranges houses. Planet-in-sign labels can look stable while house stories become fiction. Treat unknown times as unknown: do not invent noon and then argue about the 10th house.&lt;/p&gt;

&lt;h2&gt;
  
  
  A minimal pipeline
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Collect date, time (or "unknown"), and place&lt;/li&gt;
&lt;li&gt;Convert to a UTC instant carefully around DST edges&lt;/li&gt;
&lt;li&gt;Compute positions&lt;/li&gt;
&lt;li&gt;Render only what the data supports&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You can try a browser chart at &lt;a href="https://astralhoro.com/natal-chart" rel="noopener noreferrer"&gt;AstralHoro natal chart&lt;/a&gt; when you want positions without installing desktop software.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to show users
&lt;/h2&gt;

&lt;p&gt;When time is missing, hide or clearly label house-dependent claims. Sun/Moon by sign can still be useful; angles cannot.&lt;/p&gt;

&lt;p&gt;Link: &lt;a href="https://astralhoro.com/natal-chart" rel="noopener noreferrer"&gt;https://astralhoro.com/natal-chart&lt;/a&gt;&lt;/p&gt;

</description>
      <category>javascript</category>
      <category>astronomy</category>
      <category>webdev</category>
      <category>opensource</category>
    </item>
    <item>
      <title>Price a MonaReel Render Before You Hit Send</title>
      <dc:creator>dylan yu</dc:creator>
      <pubDate>Wed, 28 Oct 2026 10:39:49 +0000</pubDate>
      <link>https://dev.to/dylan_yu_7ffff00b5355942d/price-a-monareel-render-before-you-hit-send-4966</link>
      <guid>https://dev.to/dylan_yu_7ffff00b5355942d/price-a-monareel-render-before-you-hit-send-4966</guid>
      <description>&lt;p&gt;&lt;a href="https://monareel.com/" rel="noopener noreferrer"&gt;photo to video AI&lt;/a&gt; is a single-frame video desk. One photo goes in, a finished template supplies the camera move, and a live render spends a hold you can compute before the request leaves the browser. If you are scheduling a week of clips, or you are the person who explains the bill, the arithmetic is the useful part.&lt;/p&gt;

&lt;p&gt;The photo slot is marked required. It accepts JPEG, PNG, and WebP. A live render sends that image to the model as the reference for that clip. The product says the photo is not used for training, and that MonaReel does not train the runners. H3 Turbo, Seedance 2, and Seedance 2.5 are third-party models. Template samples play with no model key, so you can watch the move before the account has a balance. Signup adds nothing.&lt;/p&gt;

&lt;h2&gt;
  
  
  The hold
&lt;/h2&gt;

&lt;p&gt;Each model has a silent 5-second 480p base. Ten seconds doubles it. 720p multiplies by 1.5. Audio adds 15, once per clip. Count runs from 1 to 4 and multiplies the whole hold.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;hold = (round(base * duration * resolution) + audio) * count

base       H3 Turbo 12, Seedance 2 24, Seedance 2.5 36
duration   5s = 1, 10s = 2
resolution 480p = 1, 720p = 1.5
audio      0, or 15 if the switch is on
count      1 to 4
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Those bases match the rate card:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Model&lt;/th&gt;
&lt;th&gt;5s 480p&lt;/th&gt;
&lt;th&gt;5s 720p&lt;/th&gt;
&lt;th&gt;10s 480p&lt;/th&gt;
&lt;th&gt;10s 720p&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;H3 Turbo&lt;/td&gt;
&lt;td&gt;12&lt;/td&gt;
&lt;td&gt;18&lt;/td&gt;
&lt;td&gt;24&lt;/td&gt;
&lt;td&gt;36&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Seedance 2&lt;/td&gt;
&lt;td&gt;24&lt;/td&gt;
&lt;td&gt;36&lt;/td&gt;
&lt;td&gt;48&lt;/td&gt;
&lt;td&gt;72&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Seedance 2.5&lt;/td&gt;
&lt;td&gt;36&lt;/td&gt;
&lt;td&gt;54&lt;/td&gt;
&lt;td&gt;72&lt;/td&gt;
&lt;td&gt;108&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Audio sits on top of the row, then count multiplies. A silent H3 clip at 5 seconds and 480p is the floor, 12 credits. Leave audio on, which the desk can do by default, and the same clip is 27. People misread 27 as the price of H3.&lt;/p&gt;

&lt;p&gt;Two sends to check a spreadsheet against the button:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;H3, 10 seconds, 720p, audio on, count 1: round(12 × 2 × 1.5) + 15 = 51.&lt;/li&gt;
&lt;li&gt;The same settings at count 2: 51 × 2 = 102.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Seedance 2 at 10 seconds and 720p is 72 silent and 87 with audio. Seedance 2.5 is 108 silent and 123 with audio. The number beside send is the quote for the controls you set. If the sheet and the button disagree, trust the button.&lt;/p&gt;

&lt;p&gt;H3 is the cheap probe. Seedance 2 is the steadier camera, for orbits, walks, and stage turns, and it unlocks on a paid plan. Seedance 2.5 is the finer pass, the one to use when a face has to survive a longer move. Probe on H3 at 5 seconds, 480p, silent, count 1. Step up after a clip is close.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a month can cover
&lt;/h2&gt;

&lt;p&gt;Plans are a monthly grant.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Plan&lt;/th&gt;
&lt;th&gt;Credits&lt;/th&gt;
&lt;th&gt;Monthly&lt;/th&gt;
&lt;th&gt;Yearly / mo&lt;/th&gt;
&lt;th&gt;Billed yearly&lt;/th&gt;
&lt;th&gt;Silent H3 clips&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Basic&lt;/td&gt;
&lt;td&gt;500&lt;/td&gt;
&lt;td&gt;$19.90&lt;/td&gt;
&lt;td&gt;$15.90&lt;/td&gt;
&lt;td&gt;$190.80&lt;/td&gt;
&lt;td&gt;41&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Pro&lt;/td&gt;
&lt;td&gt;1,500&lt;/td&gt;
&lt;td&gt;$49.90&lt;/td&gt;
&lt;td&gt;$29.90&lt;/td&gt;
&lt;td&gt;$358.80&lt;/td&gt;
&lt;td&gt;125&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Ultra&lt;/td&gt;
&lt;td&gt;3,000&lt;/td&gt;
&lt;td&gt;$99.90&lt;/td&gt;
&lt;td&gt;$59.90&lt;/td&gt;
&lt;td&gt;$718.80&lt;/td&gt;
&lt;td&gt;250&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;41 × 12 is 492, which is why Basic stops at 41 clips rather than 42. The grant is spent during its cycle and replaced when the next one lands. Unused monthly credits expire in 30 days. At 27 credits, Basic is about 18 clips. At 51, it is about 9.&lt;/p&gt;

&lt;p&gt;Each plan lists no watermark and a library on that device. Ultra is described as the fastest queue. All three list one live clip at a time. A count of 4 is a more expensive send, not a pool of parallel workers. Budget wall-clock time as serial.&lt;/p&gt;

&lt;h2&gt;
  
  
  Failure and the photo
&lt;/h2&gt;

&lt;p&gt;A failed live render returns the hold to the paid balance. Removing a finished clip from Library does not. A pipeline that retries by deleting and sending again pays twice for a success, and once, refunded, for a hard failure. Retry when the progress state says the model failed. Keep the file when the model succeeded and you dislike the shot.&lt;/p&gt;

&lt;p&gt;The template direction stays on the server. You can add your own line in the description box. For a batch, keep the template stable and vary the photo, the length, and the model on purpose. Write down the hold you saw.&lt;/p&gt;

&lt;p&gt;The card also says what the photo should contain, and the hints differ. Orbit 360 asks for a standing full body. Sticker Peel wants a simple background. Turning Metal wants a front-facing portrait with even light. A wide group photo sent to a card that asked for both eyes is a paid lesson.&lt;/p&gt;

&lt;p&gt;Watch the sample, then send one live clip at the floor price with a photo that matches the card. Compare it to the sample before you multiply count or step up to Seedance. The desk at &lt;a href="https://monareel.com/" rel="noopener noreferrer"&gt;photo to video&lt;/a&gt; shows the hold on the button. The table above is how that number is built.&lt;/p&gt;

</description>
      <category>aivideo</category>
      <category>credits</category>
      <category>monareel</category>
      <category>workflow</category>
    </item>
    <item>
      <title>Checking AI image metadata: 20 useful reads and listings</title>
      <dc:creator>dylan yu</dc:creator>
      <pubDate>Wed, 21 Oct 2026 23:44:30 +0000</pubDate>
      <link>https://dev.to/dylan_yu_7ffff00b5355942d/checking-ai-image-metadata-20-useful-reads-and-listings-23k6</link>
      <guid>https://dev.to/dylan_yu_7ffff00b5355942d/checking-ai-image-metadata-20-useful-reads-and-listings-23k6</guid>
      <description>&lt;p&gt;Before you post an AI-assisted image, it is worth knowing what the file says about itself. Generators and editors can leave a signed C2PA manifest (what LinkedIn's "CR" icon reads), XMP or IPTC tags marking the image as AI-generated, prompt text in PNG chunks, and ordinary EXIF such as GPS. None of it shows in the preview.&lt;/p&gt;

&lt;p&gt;The pages below explain those layers, and each one points to &lt;a href="https://removeaimeta.com/remove-exif" rel="noopener noreferrer"&gt;delete EXIF data&lt;/a&gt; as a way to inspect and strip them in the browser. If you want to go straight to the tool, the &lt;a href="https://removeaimeta.com/ai-metadata-cleaner" rel="noopener noreferrer"&gt;AI metadata cleaner&lt;/a&gt; handles one image at a time.&lt;/p&gt;

&lt;h2&gt;
  
  
  Understanding the labels
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://dev.to/dylan_yu_7ffff00b5355942d/why-instagram-adds-an-ai-info-label-to-your-photo-and-how-to-check-the-file-first-45ch"&gt;Why Instagram Adds an "AI info" Label to Your Photo&lt;/a&gt;: how a small generative edit can trigger the label.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://dev.to/removeaimeta/the-linkedin-cr-icon-is-a-manifest-not-a-sticker-31he"&gt;The LinkedIn CR icon is a manifest, not a sticker&lt;/a&gt;: what the icon actually reflects.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://removeaimeta.hashnode.dev/does-a-screenshot-remove-c2pa-data-from-a-chatgpt-image" rel="noopener noreferrer"&gt;Does a screenshot remove C2PA data from a ChatGPT image?&lt;/a&gt;: a plain answer, with its limits.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://dev.to/removeaimeta/clean-a-jpeg-in-the-tab-you-already-have-open-3en"&gt;Clean a JPEG in the tab you already have open&lt;/a&gt;: why cleaning a file is not a promise about platform labels.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Hands-on how-tos
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://dev.to/removeaimeta/strip-c2pa-and-iptc-metadata-from-ai-images-before-you-publish-79d"&gt;Strip C2PA and IPTC Metadata From AI Images Before You Publish&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://removeaimeta.hashnode.dev/inspecting-and-removing-c2pa-and-iptc-metadata-from-images" rel="noopener noreferrer"&gt;Inspecting and Removing C2PA and IPTC Metadata from Images&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://removeaimeta.hashnode.dev/stable-diffusion-and-comfyui-pngs-carry-your-prompt-how-to-see-what-s-inside" rel="noopener noreferrer"&gt;Stable Diffusion and ComfyUI PNGs carry your prompt&lt;/a&gt;: finding the saved generation recipe in a PNG.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://practicalwebtoolsnotes.blogspot.com/2026/10/what-your-ai-images-quietly-say-about.html" rel="noopener noreferrer"&gt;What Your AI Images Quietly Say About Themselves&lt;/a&gt;: three layers to check, with an exiftool command.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://dev.to/dylan_yu_7ffff00b5355942d/whats-actually-inside-your-image-and-pdf-before-you-upload-it-3j8l"&gt;What's actually inside your image (and PDF) before you upload it&lt;/a&gt;: covers PDFs as well as images.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://slides.com/removeaimeta/where-ai-metadata-hides-in-a-jpeg-png-and-webp-and-how-to-confirm-it-is-gone" rel="noopener noreferrer"&gt;Where AI metadata hides in a JPEG, PNG and WebP&lt;/a&gt;: a slide deck on locations and verification.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  For developers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://github.com/kibovrwa/ai-image-metadata-checklist" rel="noopener noreferrer"&gt;ai-image-metadata-checklist&lt;/a&gt;: a GitHub checklist of metadata locations with exiftool commands.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://registry.modelcontextprotocol.io/v0/servers/com.removeaimeta%2Fremoveaimeta/versions/1.0.0" rel="noopener noreferrer"&gt;MCP registry entry&lt;/a&gt;: the tool as a Model Context Protocol server.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://dev.to/dylan_yu_7ffff00b5355942d/troubleshooting-remove-ai-meta-real-error-messages-and-what-to-do-1c10"&gt;Troubleshooting Remove AI Meta&lt;/a&gt;: error messages and fixes.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Where it is listed
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://aitoolfinder.ai/tools/remove-ai-meta" rel="noopener noreferrer"&gt;AI Tool Finder&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.withaitools.com/tools/remove-instagram-ai-info" rel="noopener noreferrer"&gt;WithAITools&lt;/a&gt;: the Instagram-focused page.&lt;/li&gt;
&lt;li&gt;&lt;a href="https://productwatch.io/products/remove-ai-meta" rel="noopener noreferrer"&gt;Product Watch&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://buildvoyage.com/products/remove-ai-meta" rel="noopener noreferrer"&gt;BuildVoyage&lt;/a&gt;: includes the tech stack.&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.uneed.best/tool/remove-ai-meta" rel="noopener noreferrer"&gt;Uneed&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://newname.ai/products/remove-ai-meta" rel="noopener noreferrer"&gt;newname.ai&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.directree.io/tool/remove-ai-meta" rel="noopener noreferrer"&gt;directree&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A note on limits
&lt;/h2&gt;

&lt;p&gt;Removing metadata changes what the file declares. It does not remove pixel watermarks such as SynthID, and platforms may still label content based on other signals or on your own disclosure. To check and clean a file, use the &lt;a href="https://removeaimeta.com/ai-metadata-cleaner" rel="noopener noreferrer"&gt;AI metadata cleaner&lt;/a&gt; on &lt;a href="https://removeaimeta.com/" rel="noopener noreferrer"&gt;Remove AI Meta&lt;/a&gt;.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>How to Test Hair Colors Before You Dye Your Hair</title>
      <dc:creator>dylan yu</dc:creator>
      <pubDate>Tue, 20 Oct 2026 23:09:30 +0000</pubDate>
      <link>https://dev.to/dylan_yu_7ffff00b5355942d/how-to-test-hair-colors-before-you-dye-your-hair-7n0</link>
      <guid>https://dev.to/dylan_yu_7ffff00b5355942d/how-to-test-hair-colors-before-you-dye-your-hair-7n0</guid>
      <description>&lt;p&gt;Dyeing your hair is a big commitment, and a color that looks great on a swatch can look very different on you. Here is a simple process for testing hair colors first.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Know your skin undertone
&lt;/h2&gt;

&lt;p&gt;Blue or purple wrist veins suggest a cool undertone; green suggests warm. Cool tones suit ash and burgundy; warm tones suit copper and honey blonde.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Preview colors on your own photo
&lt;/h2&gt;

&lt;p&gt;Take a clear, evenly lit selfie, then use an AI tool such as &lt;a href="https://easyfaceai.com/hair-color" rel="noopener noreferrer"&gt;this AI hair color try-on&lt;/a&gt; to see different shades and styles on your own face in seconds.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Check the color in different light
&lt;/h2&gt;

&lt;p&gt;Look at previews on a phone and a computer.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Do a strand test
&lt;/h2&gt;

&lt;p&gt;Test the real dye on a hidden strand and check it when dry.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Plan the whole look
&lt;/h2&gt;

&lt;p&gt;If you want to see outfits next to your new shade, an &lt;a href="https://easyfaceai.com/ai-clothes-changer" rel="noopener noreferrer"&gt;AI clothes changer&lt;/a&gt; can help you preview complementary clothing colors.&lt;/p&gt;

&lt;p&gt;Test digitally first, strand test second, and dye with confidence.&lt;/p&gt;

</description>
      <category>beauty</category>
    </item>
    <item>
      <title>Why Instagram Adds an "AI info" Label to Your Photo, and How to Check the File First</title>
      <dc:creator>dylan yu</dc:creator>
      <pubDate>Tue, 20 Oct 2026 12:54:48 +0000</pubDate>
      <link>https://dev.to/dylan_yu_7ffff00b5355942d/why-instagram-adds-an-ai-info-label-to-your-photo-and-how-to-check-the-file-first-45ch</link>
      <guid>https://dev.to/dylan_yu_7ffff00b5355942d/why-instagram-adds-an-ai-info-label-to-your-photo-and-how-to-check-the-file-first-45ch</guid>
      <description>&lt;p&gt;A photo with one small generative edit, like removing a stray sign with Photoshop's Generative Fill, can come out of the editor marked as AI media. Upload it to Instagram and you may get the "AI info" label, which is the same family as Meta's older "Made with AI" label. In many of these cases the signal is not in the pixels. It is in the metadata.&lt;/p&gt;

&lt;h2&gt;
  
  
  What triggers the label
&lt;/h2&gt;

&lt;p&gt;Meta has said it reads industry-standard markers that tools write into the file. Three are worth knowing:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;C2PA Content Credentials.&lt;/strong&gt; A signed manifest describing how the image was made. In a JPEG it lives in JUMBF boxes inside APP11 segments. Adobe Firefly, Photoshop generative tools, and several image generators write it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;IPTC DigitalSourceType.&lt;/strong&gt; A field whose values include &lt;code&gt;trainedAlgorithmicMedia&lt;/code&gt; (fully generated) and &lt;code&gt;compositeWithTrainedAlgorithmicMedia&lt;/code&gt; (a real photo with generated parts).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;XMP history.&lt;/strong&gt; Editors record tool names and edit steps in XMP. Generative Fill and Firefly leave a clear trail here.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Check the file before you change anything
&lt;/h2&gt;

&lt;p&gt;ExifTool shows every tag group, including duplicates:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;exiftool &lt;span class="nt"&gt;-G1&lt;/span&gt; &lt;span class="nt"&gt;-a&lt;/span&gt; &lt;span class="nt"&gt;-s&lt;/span&gt; photo.jpg | &lt;span class="nb"&gt;grep&lt;/span&gt; &lt;span class="nt"&gt;-i&lt;/span&gt; &lt;span class="nt"&gt;-E&lt;/span&gt; &lt;span class="s1"&gt;'c2pa|jumbf|DigitalSourceType|Credit'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;No output means none of those markers are present. A JUMBF or C2PA group means a Content Credentials manifest is embedded. A DigitalSourceType line tells you how the file describes itself. &lt;code&gt;Credit&lt;/code&gt; sometimes holds a generator name.&lt;/p&gt;

&lt;p&gt;If you don't want to install anything, you can &lt;a href="https://removeaimeta.com/remove-ai-info" rel="noopener noreferrer"&gt;remove Instagram AI info&lt;/a&gt; in the browser instead. It reads and cleans the file on your device, so the image isn't uploaded anywhere.&lt;/p&gt;

&lt;h2&gt;
  
  
  Strip it
&lt;/h2&gt;

&lt;p&gt;Write a new file and keep the original:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;exiftool &lt;span class="nt"&gt;-all&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nt"&gt;-o&lt;/span&gt; clean.jpg photo.jpg
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;-all=&lt;/code&gt; deletes all metadata, and &lt;code&gt;-o&lt;/code&gt; writes to a separate file. This is blunt. It removes copyright, camera and lens data, GPS, and the ICC color profile. Without the profile, colors can shift slightly in some viewers, and dropping the Orientation tag can make a portrait display sideways.&lt;/p&gt;

&lt;p&gt;To keep color, copy the profile back from the source:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;exiftool &lt;span class="nt"&gt;-all&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nt"&gt;-tagsfromfile&lt;/span&gt; @ &lt;span class="nt"&gt;-icc_profile&lt;/span&gt; &lt;span class="nt"&gt;-o&lt;/span&gt; clean.jpg photo.jpg
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;@&lt;/code&gt; means the source file. Copy copyright or orientation back the same way if you need them.&lt;/p&gt;

&lt;p&gt;If you only want the Content Credentials manifest gone and the rest left alone, a dedicated tool to &lt;a href="https://removeaimeta.com/remove-c2pa" rel="noopener noreferrer"&gt;remove C2PA&lt;/a&gt; does just that, also on-device.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check again, then upload
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;exiftool &lt;span class="nt"&gt;-G1&lt;/span&gt; &lt;span class="nt"&gt;-a&lt;/span&gt; &lt;span class="nt"&gt;-s&lt;/span&gt; clean.jpg | &lt;span class="nb"&gt;grep&lt;/span&gt; &lt;span class="nt"&gt;-i&lt;/span&gt; &lt;span class="nt"&gt;-E&lt;/span&gt; &lt;span class="s1"&gt;'c2pa|jumbf|DigitalSourceType|Credit'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Empty output is the goal. Upload that exact file. Don't open it in another editor first, because many apps write their own XMP on save.&lt;/p&gt;

&lt;h2&gt;
  
  
  What stripping can't do
&lt;/h2&gt;

&lt;p&gt;Metadata is only one signal. Some generators also embed an invisible watermark in the pixels (Google's SynthID is one example), and stripping EXIF, XMP, and C2PA leaves that in place. Meta also runs its own detection. So a file with an empty grep can still be labeled.&lt;/p&gt;

&lt;p&gt;The label exists for disclosure. If an image is substantially AI-generated, keep the label or say so in the caption. Cleaning metadata makes most sense when the mark is a side effect of a small fix on a photo you took.&lt;/p&gt;

&lt;h2&gt;
  
  
  Troubleshooting
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;The label still appears.&lt;/strong&gt; Run the check on the exact file you uploaded. If markers are still there, you uploaded the wrong copy. If the output is empty and the label stays, another signal was used, and stripping again won't change it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Saving or exporting brings the data back.&lt;/strong&gt; Phone galleries and many editing apps rewrite XMP on export, and Photoshop or Lightroom can write a new manifest if the edit history still includes a generative step. Strip as the last step, or re-check after every save.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Screenshots.&lt;/strong&gt; A screenshot usually drops all metadata, but it also resamples the image and can catch UI around the edges. It won't remove a pixel watermark. Treat it as a last resort, not a fix.&lt;/p&gt;

</description>
      <category>privacy</category>
      <category>webdev</category>
      <category>tutorial</category>
      <category>ai</category>
    </item>
    <item>
      <title>Shipping Work Through a Desktop Agent: First Bot, Computer, Then Routines</title>
      <dc:creator>dylan yu</dc:creator>
      <pubDate>Thu, 15 Oct 2026 10:59:58 +0000</pubDate>
      <link>https://dev.to/dylan_yu_7ffff00b5355942d/shipping-work-through-a-desktop-agent-first-bot-computer-then-routines-399g</link>
      <guid>https://dev.to/dylan_yu_7ffff00b5355942d/shipping-work-through-a-desktop-agent-first-bot-computer-then-routines-399g</guid>
      <description>&lt;p&gt;"AI agent" posts usually skip the boring part: how a desktop agent actually holds a computer, asks for approval, and runs again tomorrow without you re-explaining the job. If you are evaluating Grok Bot-style setups, the useful mental model is three layers — &lt;strong&gt;identity&lt;/strong&gt;, &lt;strong&gt;computer&lt;/strong&gt;, &lt;strong&gt;routines&lt;/strong&gt; — not a chat demo.&lt;/p&gt;

&lt;h2&gt;
  
  
  Layer 1: know what the product is (and is not)
&lt;/h2&gt;

&lt;p&gt;Start with a plain definition page before you install anything. &lt;a href="https://grokbot.run/learn/what-is-grok-bot/" rel="noopener noreferrer"&gt;What is Grok Bot&lt;/a&gt; is the right altitude: an agent that can use a computer and tools on your behalf, with approvals, not a magic autopilot that silently spends money and posts as you.&lt;/p&gt;

&lt;p&gt;Read that before comparison charts. Feature matrices are useless if you still think the product is "ChatGPT with a sidebar."&lt;/p&gt;

&lt;h2&gt;
  
  
  Layer 2: first bot as a scoped employee
&lt;/h2&gt;

&lt;p&gt;Your first bot should have a job description, not a personality. Good first jobs are narrow:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Draft a weekly changelog from merged PRs&lt;/li&gt;
&lt;li&gt;Triage inbound email into labels + draft replies you still send&lt;/li&gt;
&lt;li&gt;Watch a folder and summarize new PDFs&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A practical &lt;a href="https://grokbot.run/learn/first-bot/" rel="noopener noreferrer"&gt;first bot&lt;/a&gt; path matters more than a tour of every plugin. Scope equals safety. Wide open "do whatever" agents are how people discover irreversible actions the hard way.&lt;/p&gt;

&lt;h2&gt;
  
  
  Layer 3: the computer is the real API
&lt;/h2&gt;

&lt;p&gt;Chat is the interface. The computer is the capability. Files, browser, shell, and connected apps only matter if you understand what the agent can touch and what still needs your click.&lt;/p&gt;

&lt;p&gt;Skim &lt;a href="https://grokbot.run/learn/computer/" rel="noopener noreferrer"&gt;computer&lt;/a&gt; with the same seriousness you would give IAM docs. Ask:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Does this run on a remote box, my machine, or both?&lt;/li&gt;
&lt;li&gt;Which actions are reversible vs. externally visible?&lt;/li&gt;
&lt;li&gt;Where do approvals show up, and can a routine bypass them?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If those answers are fuzzy, do not wire production credentials yet.&lt;/p&gt;

&lt;h2&gt;
  
  
  Routines and skills turn demos into ops
&lt;/h2&gt;

&lt;p&gt;One-shot prompts are toys. Recurring work needs schedules, skills, and failure modes. &lt;a href="https://grokbot.run/learn/skills-routines/" rel="noopener noreferrer"&gt;Skills and routines&lt;/a&gt; is where an agent stops being a chat novelty and starts looking like a junior operator: same brief, same tools, logged outcomes.&lt;/p&gt;

&lt;p&gt;Ops hygiene that actually helps:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Name the routine after the outcome (&lt;code&gt;weekly-changelog&lt;/code&gt;), not the model.&lt;/li&gt;
&lt;li&gt;Keep secrets out of the prompt; use connected accounts and approvals.&lt;/li&gt;
&lt;li&gt;Log failures with the step that died (auth, timeout, empty input).&lt;/li&gt;
&lt;li&gt;Prefer read → draft → human send over silent send for anything external.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;For team-shaped usage, &lt;a href="https://grokbot.run/learn/ops/" rel="noopener noreferrer"&gt;ops&lt;/a&gt; notes on handoff and ownership prevent the classic failure: five people sharing one bot and nobody knowing who approved the outbound message.&lt;/p&gt;

&lt;h2&gt;
  
  
  Compare on jobs, not logos
&lt;/h2&gt;

&lt;p&gt;When you stack Grok Bot against other agent products, compare &lt;strong&gt;job completion under approval constraints&lt;/strong&gt;, not homepage adjectives. A grounded &lt;a href="https://grokbot.run/compare/" rel="noopener noreferrer"&gt;compare&lt;/a&gt; page plus concrete &lt;a href="https://grokbot.run/use-cases/" rel="noopener noreferrer"&gt;use cases&lt;/a&gt; beats another "10 AI agents in 2026" listicle.&lt;/p&gt;

&lt;p&gt;Checklist before you commit a workflow:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Can I state the job in one sentence?&lt;/li&gt;
&lt;li&gt;Does the agent have only the computer access that job needs?&lt;/li&gt;
&lt;li&gt;Is every externally visible action behind an approval I understand?&lt;/li&gt;
&lt;li&gt;Can the same job rerun next week as a routine without rewriting the brief?&lt;/li&gt;
&lt;li&gt;Do I know how to recover when a step sticks or a login expires?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Desktop agents are less about clever prompts and more about boring operational design. Get the first bot narrow, the computer boundaries explicit, and the routine repeatable — then the chat UI finally earns its keep.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
      <category>automation</category>
    </item>
    <item>
      <title>First-Session Design for Browser Mech Games: Controls, Upgrades, Boss Gates</title>
      <dc:creator>dylan yu</dc:creator>
      <pubDate>Thu, 15 Oct 2026 10:58:36 +0000</pubDate>
      <link>https://dev.to/dylan_yu_7ffff00b5355942d/first-session-design-for-browser-mech-games-controls-upgrades-boss-gates-534p</link>
      <guid>https://dev.to/dylan_yu_7ffff00b5355942d/first-session-design-for-browser-mech-games-controls-upgrades-boss-gates-534p</guid>
      <description>&lt;p&gt;Browser mech fighters look casual until the first boss. Then the session splits into people who learned the control model and people who spent the whole run buying the wrong upgrades. If you build or document these games, treat the first session as a product surface: controls literacy, upgrade priority, and a boss gate that teaches — not punishes.&lt;/p&gt;

&lt;p&gt;I have been reverse-engineering what good first-session pages do for titles like Mechangelion. The pattern is consistent whether you are writing a guide or shipping a tutorial overlay.&lt;/p&gt;

&lt;h2&gt;
  
  
  Minute 0–3: teach the control model, not the lore
&lt;/h2&gt;

&lt;p&gt;Players forgive thin story. They do not forgive unclear movement, aim, and special triggers. A first-session page should name:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Move / look / fire / skill cooldowns&lt;/li&gt;
&lt;li&gt;What "stun," "overheat," or "guard break" means in &lt;em&gt;this&lt;/em&gt; game&lt;/li&gt;
&lt;li&gt;One safe drill (strafe + fire on a weak enemy) before the map opens up&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A dedicated &lt;a href="https://www.mechangelion.com/guides/mech-controls/" rel="noopener noreferrer"&gt;mech controls&lt;/a&gt; note beats burying binds inside a 2,000-word lore dump. Same for a &lt;a href="https://www.mechangelion.com/guides/mechangelion-first-session/" rel="noopener noreferrer"&gt;first session&lt;/a&gt; guide: the job is a clean loop, not a completionist checklist.&lt;/p&gt;

&lt;p&gt;If someone lands from search wanting to play immediately, send them to the playable shell — for example the &lt;a href="https://www.mechangelion.com/mechangelion/" rel="noopener noreferrer"&gt;Mechangelion play page&lt;/a&gt; — and keep the guide one tab away, not as a wall before the canvas.&lt;/p&gt;

&lt;h2&gt;
  
  
  Upgrade priority is a curriculum
&lt;/h2&gt;

&lt;p&gt;Random shops teach learned helplessness. Early currency should buy &lt;strong&gt;survivability and clarity&lt;/strong&gt; before vanity DPS:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Mobility or shield that reduces wipe chance on misplays&lt;/li&gt;
&lt;li&gt;A primary weapon upgrade that shortens time-to-kill on trash&lt;/li&gt;
&lt;li&gt;One utility that makes the upcoming boss readable (interrupt window, armor shred, heal on stagger)&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A public &lt;a href="https://www.mechangelion.com/guides/mechangelion-upgrade-priority/" rel="noopener noreferrer"&gt;upgrade priority&lt;/a&gt; page is content marketing that doubles as design documentation. If your live economy contradicts the guide after a patch, update the guide the same day — stale priority lists destroy trust faster than a hard boss.&lt;/p&gt;

&lt;h2&gt;
  
  
  Boss gates should examine the lesson
&lt;/h2&gt;

&lt;p&gt;The first boss is a unit test for the tutorial:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Did the player learn the dodge / block / interrupt?&lt;/li&gt;
&lt;li&gt;Does the telegraph read at browser latency?&lt;/li&gt;
&lt;li&gt;Is failure informative (wrong upgrade, missed interrupt) or opaque (one-shot from offscreen)?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Document the gate the same way QA would: phases, tells, common wipe reasons. A focused &lt;a href="https://www.mechangelion.com/guides/mechangelion-boss-fights/" rel="noopener noreferrer"&gt;boss fights&lt;/a&gt; write-up helps returning players more than a spoiler-heavy full walkthrough, and it gives you a place to patch notes when telegraphs change.&lt;/p&gt;

&lt;p&gt;Pair that with a short &lt;a href="https://www.mechangelion.com/guides/mechangelion-beginner-guide/" rel="noopener noreferrer"&gt;beginner guide&lt;/a&gt; that stops before midgame nesting. Beginner ≠ encyclopedia.&lt;/p&gt;

&lt;h2&gt;
  
  
  Ops checklist for guide maintainers
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Controls page&lt;/strong&gt; updates when binds or mobile gestures change.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;First-session page&lt;/strong&gt; updates when the opening map or economy changes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Upgrade priority&lt;/strong&gt; updates on balance patches that touch early shops.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Boss page&lt;/strong&gt; updates when phase order or tells change — not when a cosmetic skin ships.&lt;/li&gt;
&lt;li&gt;Cross-link play → first session → upgrades → boss as a path, not a footer farm.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Why this matters for browser games specifically
&lt;/h2&gt;

&lt;p&gt;HTML5 / WebGL titles compete with tab fatigue. A player who dies confused closes the tab; a player who dies understanding the mistake queues another run. Guides that mirror the real curriculum (controls → economy → boss exam) reduce bounce for the same reason good onboarding reduces churn in SaaS.&lt;/p&gt;

&lt;p&gt;If you only publish one new page this month, make it the first-session spine. Everything else is a satellite.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>gamedev</category>
    </item>
    <item>
      <title>Content Ops for a Small Game Wiki: Codes, Beginner, Walkthrough as Three Products</title>
      <dc:creator>dylan yu</dc:creator>
      <pubDate>Thu, 15 Oct 2026 10:58:08 +0000</pubDate>
      <link>https://dev.to/dylan_yu_7ffff00b5355942d/content-ops-for-a-small-game-wiki-codes-beginner-walkthrough-as-three-products-40ij</link>
      <guid>https://dev.to/dylan_yu_7ffff00b5355942d/content-ops-for-a-small-game-wiki-codes-beginner-walkthrough-as-three-products-40ij</guid>
      <description>&lt;p&gt;A fan wiki for a live game is not one article with three URLs. It is three products that share a domain: a &lt;strong&gt;status table&lt;/strong&gt;, an &lt;strong&gt;onboarding spine&lt;/strong&gt;, and a &lt;strong&gt;gated progression doc&lt;/strong&gt;. Mixing them is how pages go stale, spoil new players, and burn editor time on the wrong refresh cycle.&lt;/p&gt;

&lt;p&gt;I have been looking at how small teams keep &lt;em&gt;100 Days at Sea&lt;/em&gt; style sites honest without a newsroom. The workable pattern is to give each page type a job, a refresh SLA, and a hard rule about what it must not contain.&lt;/p&gt;

&lt;h2&gt;
  
  
  Product 1: the codes page is a status API in HTML
&lt;/h2&gt;

&lt;p&gt;Promo codes rot on a weekly (sometimes daily) clock. The page's job is not inspiration. It is &lt;strong&gt;Active / Contested / Expired&lt;/strong&gt; with a checked date. Redeem steps change rarely; status cells change often. Ops rule: rewrite cells, not essays.&lt;/p&gt;

&lt;p&gt;That is why a maintained &lt;a href="https://www.100daysatsea.com/codes" rel="noopener noreferrer"&gt;codes&lt;/a&gt; list should look boring on purpose. Flashy "NEW CODES!!!" banners train readers to distrust you when last week's string is still glowing. Keep Expired rows visible so dead codes stop getting reposted as fresh. If you need the method behind the labels, the verification note on &lt;a href="https://www.100daysatsea.com/guides/how-we-verify-codes" rel="noopener noreferrer"&gt;how we verify codes&lt;/a&gt; is the editorial contract — not a second redeem tutorial.&lt;/p&gt;

&lt;p&gt;Refresh SLA: short. Touch this page whenever a dump hits Discord or a major tracker updates. Do not wait for a "content calendar."&lt;/p&gt;

&lt;h2&gt;
  
  
  Product 2: the beginner guide is a Day-1 spine
&lt;/h2&gt;

&lt;p&gt;Beginner pages fail when they try to be walkthroughs. New players need a &lt;strong&gt;resource triage and unlock order&lt;/strong&gt;, not boss mechanics from week three. The job is: stabilize the raft, name the first stations, set a night-1 exit plan, then stop.&lt;/p&gt;

&lt;p&gt;A focused &lt;a href="https://www.100daysatsea.com/beginner-guide" rel="noopener noreferrer"&gt;beginner guide&lt;/a&gt; should refuse midgame spoilers the way a codes page refuses vibes. If a paragraph only helps after the first boss gate, it belongs elsewhere. Ops rule: update when the early economy or tutorial flow changes — not when a new late island ships.&lt;/p&gt;

&lt;p&gt;Refresh SLA: medium. Patch notes that touch Day 1–3 matter; cosmetic seasons usually do not.&lt;/p&gt;

&lt;h2&gt;
  
  
  Product 3: the walkthrough is gated chapters
&lt;/h2&gt;

&lt;p&gt;Walkthroughs exist for &lt;strong&gt;gates&lt;/strong&gt;: prep checklists, failure modes, "you are blocked until X." They should be chaptered so a returning player can open one stretch without swallowing the whole plot. Spoiler boundaries are a product feature, not a courtesy.&lt;/p&gt;

&lt;p&gt;Structure a &lt;a href="https://www.100daysatsea.com/walkthrough" rel="noopener noreferrer"&gt;walkthrough&lt;/a&gt; as spine mode documentation: when to follow, when to explore, what prep the next gate demands. Ops rule: update per gate when the encounter or recipe changes; do not reshuffle the whole TOC every week for SEO theater.&lt;/p&gt;

&lt;p&gt;Refresh SLA: long per chapter, event-driven per patch.&lt;/p&gt;

&lt;h2&gt;
  
  
  Shared editorial rules that keep the three from collapsing
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;One primary job per URL.&lt;/strong&gt; Codes do not teach Day-1 builds. Beginner does not list contested promo strings. Walkthrough does not bury a redeem form in chapter 1.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Timestamps match the job.&lt;/strong&gt; Codes need a "checked" stamp. Beginner needs a "early-game verified as of" line. Walkthrough needs per-chapter patch notes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cross-link as handoffs, not keyword stuffing.&lt;/strong&gt; Beginner → walkthrough when the raft is stable. Codes → beginner when someone is redeeming instead of eating. Walkthrough → codes only if a chapter is gated behind a seasonal reward.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Source methodology is public.&lt;/strong&gt; A short &lt;a href="https://www.100daysatsea.com/source-methodology" rel="noopener noreferrer"&gt;source methodology&lt;/a&gt; page turns "trust us" into a checklist outsiders can audit.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Why this split helps SEO and humans
&lt;/h2&gt;

&lt;p&gt;Search queries cluster by job: "codes," "beginner," "walkthrough / how to beat." One mega-page ranking for all three usually ranks cleanly for none after the first month, because refresh noise and spoiler complaints fight each other. Three products, three SLAs, one domain — that is content ops for a small game wiki, not a content calendar cosplay.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>gamedev</category>
      <category>contentwriting</category>
    </item>
    <item>
      <title>GAI vs FSIQ: How to Read the Gap Without Inventing a Story</title>
      <dc:creator>dylan yu</dc:creator>
      <pubDate>Thu, 15 Oct 2026 10:56:44 +0000</pubDate>
      <link>https://dev.to/dylan_yu_7ffff00b5355942d/gai-vs-fsiq-how-to-read-the-gap-without-inventing-a-story-228k</link>
      <guid>https://dev.to/dylan_yu_7ffff00b5355942d/gai-vs-fsiq-how-to-read-the-gap-without-inventing-a-story-228k</guid>
      <description>&lt;p&gt;A cognitive report that shows both a General Ability Index (GAI) and a Full Scale IQ (FSIQ) invites a tempting narrative: "I'm smarter than my IQ says" or "something is wrong with me." Most of the time the gap is a measurement pattern, not a personality plot. Here is how to read it without turning two numbers into a myth.&lt;/p&gt;

&lt;h2&gt;
  
  
  What each score is actually summarizing
&lt;/h2&gt;

&lt;p&gt;FSIQ on a Wechsler battery folds in a broad set of index scores. GAI is built from a narrower set that leans harder on verbal and visual reasoning and usually puts less weight on working memory and processing speed. That is why GAI can sit above FSIQ when those secondary indexes are the drag — and why the reverse can happen too.&lt;/p&gt;

&lt;p&gt;If you only remember one framing, use this: &lt;strong&gt;GAI is not a "true IQ" that FSIQ secretly underreports.&lt;/strong&gt; It is a different composite with different inputs. A clear comparison of that design choice is in &lt;a href="https://gaivsiq.com/guides/gai-iq-test-vs-a-wechsler" rel="noopener noreferrer"&gt;GAI IQ test vs a Wechsler&lt;/a&gt;, which is worth reading before you trust any online "GAI calculator" that never names its subtests.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why GAI often looks higher
&lt;/h2&gt;

&lt;p&gt;When working memory or processing speed are relatively weak, FSIQ drops more than GAI. The gap is then a signal about profile shape, not a prize. Parents and adults both over-index on the higher number because it feels kinder. Clinicians care about the shape because accommodations, pacing, and follow-up testing hang on it.&lt;/p&gt;

&lt;p&gt;A practical explanation of that pattern — without cheerleading — is &lt;a href="https://gaivsiq.com/guides/why-gai-is-higher-than-iq" rel="noopener noreferrer"&gt;why GAI is higher than IQ&lt;/a&gt;. Pair it with the complementary piece on &lt;a href="https://gaivsiq.com/guides/working-memory-processing-speed-and-gai" rel="noopener noreferrer"&gt;working memory, processing speed, and GAI&lt;/a&gt; if your report already shows those indexes. Reading both beats Googling "is a 12-point gap significant" in isolation.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to calculate (and when not to)
&lt;/h2&gt;

&lt;p&gt;If you have the scaled scores and a published conversion table for the exact battery and norms, you can compute GAI yourself. If you have only a marketing PDF and no table, you cannot. Wrong edition, wrong age band, or wrong combination of subtests produces a confident wrong number.&lt;/p&gt;

&lt;p&gt;Use a transparent &lt;a href="https://gaivsiq.com/guides/how-to-calculate-gai" rel="noopener noreferrer"&gt;how to calculate GAI&lt;/a&gt; walkthrough when you want the arithmetic spelled out, then plug the same inputs into a &lt;a href="https://gaivsiq.com/calculator" rel="noopener noreferrer"&gt;GAI vs IQ calculator&lt;/a&gt; only as a check — never as a substitute for the official report. If the calculator and the report disagree, trust the report and ask the examiner which composite they used.&lt;/p&gt;

&lt;h2&gt;
  
  
  A sober reading checklist
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Name the battery and edition.&lt;/strong&gt; WAIS-IV / WISC-V / etc. are not interchangeable.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;List which indexes feed GAI vs FSIQ on that edition.&lt;/strong&gt; Do not assume last year's blog post matches your booklet.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Look at the gap direction and size, then at the indexes that explain it.&lt;/strong&gt; A high GAI with slow processing speed is a different story from a flat profile with a tiny gap.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Refuse single-number identity.&lt;/strong&gt; Neither GAI nor FSIQ is a career destiny or a moral score.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ask what decision the score is for.&lt;/strong&gt; Educational placement, clinical follow-up, and curiosity hobbyists need different levels of precision.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What "good" means in this context
&lt;/h2&gt;

&lt;p&gt;People ask for a good GAI the way they ask for a good credit score. Composites are relative to a norm group, and "good" only makes sense relative to a purpose: gifted screening thresholds, discrepancy analysis, or simply understanding a classroom struggle. Absolute bragging rights are the least useful use of the page.&lt;/p&gt;

&lt;p&gt;If you are staring at two numbers and feel the urge to pick a favorite, slow down. Read the composite definitions, check the calculation path, and treat the gap as a prompt to inspect working memory and speed — not as a plot twist about who you really are.&lt;/p&gt;

</description>
      <category>psychology</category>
      <category>testing</category>
      <category>education</category>
    </item>
  </channel>
</rss>
