You didn't show any altered notes, because they don't exist.

You are simply pointing to urls of resized images for optimized feed display. I explain why we do it here:

nostr:nevent1qvzqqqqqqypzp4sl80zm866yqrha4esknfwp0j4lxfrt29pkrh5nnnj2rgx6dm62qythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qywhwumn8ghj7mn0wd68ytnzd96xxmmfdejhytnnda3kjctv9uqzqgw2lpe65ytw20gf2crh9s5v5juv2evv0vhp2c049e2pv7f9klyuagv80r

Reply to this note

Please Login to reply.

Discussion

You are in control of the new link and have the power to change the media associated with that url.

That’s not how Nostr is supposed to work.

JFC do you even understand why CDNs exist in the first place?

This is an app level optimization that nobody outside the primal app benefits from.

If you're so scared the event itself, not where any given image is hosted because ffs CDNs are an industry standard precisely for scalability of different types of clients and subject to the same potential tampering, was modified then the burden of proof is on you to whip out them raw logs and packet captures with actual proof of EVENT manipulation not a screenshot of a CDN optimized url.

If I decide to delete or change the image I’m hosting on Nostr.build or on my own server will Primal’s image update.

No it wouldn’t

Kindly GFY