Silent

Thanks! This confirms for me that both are the same issue, that is good to know.

See https://github.com/PCSX2/pcsx2/pull/12128 for a fix.

> * `BusFault` handler checks for `0xDDDDDDDD` and 64K after it to determine "Possible use-after-free" Just sanity checking - is nothing mapped there in the Cortex M4 memory map? Peripheral...

This game also needs the Frame Limiter set to `PS3 Native` or else it can reach framerates over 30FPS and run too fast.

Furthermore, even in this plugin, `page.last_modified_at` is already used for LD-JSON generation: https://github.com/jekyll/jekyll-seo-tag/blob/f449b1af64cbaf9080e7a3c677090cfe6e8f0021/spec/jekyll_seo_tag/drop_spec.rb#L298-L315 Example from my website: ``` {"@context":"https://schema.org","@type":"BlogPosting","author":{"@type":"Person","name":"Silent"},"dateModified":"2025-04-23T13:30:00+00:00","datePublished":"2025-04-23T13:30:00+00:00" ```

@ashmaroli Looking at https://github.com/jekyll/jekyll-seo-tag/blob/f449b1af64cbaf9080e7a3c677090cfe6e8f0021/lib/jekyll-seo-tag/drop.rb#L114-L123, the current `article:published_time` isn't exactly great either and instead it should be `seo_tag.published_time` - it's used for LD-JSON already, but not for the HTML template. I...

Additionally, this duplicates #447, albeit using `last_modified_at`.

> Is the specific problem that a Document without a date gets `property="article:published_time"` instead of `property="website:published_time"`? should we just omit this field if no date exists instead? No, it's kind...

I just discovered that this defect has another consequence - because of the same problem, `JSON-LD` entry classifies all those pages as `BlogPosting`: https://github.com/jekyll/jekyll-seo-tag/blob/d61a2a84b885ea2e406e2d4c84fbcd37243bd0e7/lib/jekyll-seo-tag/drop.rb#L125-L137