• 6 Posts
  • 111 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle
















  • The more basic question is, why are you regarding the web browser as the “source” of an image that needs to be verified? Anyone could make a fake website with fake images, in which case the web browser confirming that the screenshots of the site are “real” would be meaningless.

    If the web page is (say) photos taken at an event, a better solution would be to have the original photographer post hashes of the photos at the time they’re taken (or have a camera that does this automatically).


  • You can take any file, run it through a cryptographic hash function, and post the fingerprint on any site with verifiable upload dates to confirm that you had it on that date and that it hasn’t been modified since (without necessarily exposing the file itself).

    Proving how the file was created is a whole other can of worms—the obvious solution is to sacrifice control of your software and hardware to some proprietary third-party system that presumably has no stake in the outcome, but that causes more problems than it solves.