pull down to refresh
40 sats \ 2 replies \ @k00b 16 Oct 2022 \ parent \ on: OpenTimestamps: Scalable, Trust-Minimized, Distributed Timestamping with Bitcoin bitcoin
I'm surprised it took me this long to invest time into understanding ots. Thanks for the motivation! I created a GH issue for it: https://github.com/stackernews/stacker.news/issues/206. Should be pretty straightforward to add. UX could just be a little ots logo next to Items with upgraded timestamps.
In this centralized context where practically everything is trusted, trusting SN to keep and not forge time is probably a relatively small concern, but it would be fun and also relieving to chip away at the trust monolith.
I'll try to get it done.
Nice!
Note that upgrading timestamps is optional. The calendars will make the data available indefinitely, and third parties can back it up, so it's reasonable to just store the incomplete ones in your databases.
The way I'd implement it is to timestamp the content after the edit window has closed. Also, ideal would be for the SHA256 hash of what you're replying too also be part of the timestamped content, so there's a complete record of the context. Don't forget to hash content like inline photos too.
reply
Great recs. I’ll update the issue.
reply