Damn, it took me less than five hours to go from zero to a fully usable :nixos: #NixOS 💪:

- getting #GnuPG working
- homedir encryption with #eCryptfs
- all software I need
- even managed to package 3 custom things not in nixpkgs (passrofi, my #OpenTimeStamps client fork, bemoji)

This is the result: https://gitlab.com/nobodyinperson/nixconfig

@rixx Fun. Can't backdate #OpenTimeStamps proofs in the GPG signature though 😅

https://opentimestamps.org

@pete This also plays nicely with @joeyh's :gitannex: #GitAnnex:

# have Git Annex sign all commits + adding the #OpenTimestamps
git config annex.allowsign true

You can then extract timestamp proofs that your documents existed at a past point in time (ots git-extract --annex file.txt) and you were actually the one creating the file (git log --show-signature file.txt). Neat!

When you add @pete's #OpenTimestamps (https://opentimestamps.org) and #PGP signatures to your commits, you can prove even more that it was really you doing that work *at that time*, not someone else. Even when your PGP key is compromised later.

Something along these lines:

# my PR with extra goodies, hopefully soon to be merged
pip install git+https://github.com/nobodyinperson/opentimestamps-client@configure-ots-git-gpg-wrapper-from-outside
git config commit.gpgsign true
git config gpg.program ots-git-gpg-wrapper.sh

@linux_mclinuxface One solution around the someone-claims-they-made-it-first-and-accuse-you-of-copying-it-problem is to both add a #PGP signature and @pete's #OpenTimeStamps to your commits:

https://opentimestamps.org

The faker will have a really hard time trying to prove they have created an identical version before you.

The same goes for basically any other work you do. I sign amd timestamp each and every one of my commits like this.

@libreoffice Timestamping of documents à la #OpenTimeStamps

https://opentimestamps.org/

@dachary @forgefriends I mean if you invent a name and a logo and attribute it to the public domain, no one else can register it as a trademark, right? You just need to timestamp the time of invention (#OpenTimestamps and Twitter or something) and any party being sued by someone falsely claiming the copyright/trademark should be able to defend themselves using that.

Oooh I just found out that the #OpenTimestamps (https://opentimestamps.org/) client (https://github.com/opentimestamps/opentimestamps-client) supports extracting timestamp proofs form a (timestamped) git repository also for git-annexed files:

# This creates the proof file 'annexed-file.dat.ots'
ots git-extract --annex annexed-file.dat
# This can be used to verify:
ots [--no-bitcoin] verify annexed-file.dat.ots

Very much awesome! 🎉

#Python #git

@waxwing @Bitcoinology @Hyolobrika Auditability in such a system is hard, but possible, each contract could opt-in to auditability and opting in would force the mints to publish every state update into a hash chain (committed to #OpenTimestamps or something) and interactions could refer to the latest state hash to ensure there's no tampering etc.

"[ots-dev] Stamp/Beacon Trees for Secure, Precise, Trusted Timestamping and Clock Synchronization" - https://lists.opentimestamps.org/pipermail/ots-dev/2021-January/000106.html

tl;dr: My new merkle tree construction combines the precision of NTP, and the security of Roughtime. And unlike either, it can be scaled arbitrarily with untrusted servers.

Added to the #OpenTimestamps protocol, it'd allow one service to provide both high accuracy, trusted time, and trustless, low-accuracy, Bitcoin timestamps. A one-stop-shop for all your timing needs.

Samen met Nobleton heb ik op de #Bitcoin Blockchain, met #Opentimestamps en #IPFS een vette dienst gebouwd: "Algemene voorwaarden deponeren op de Blockchain". Legal meets crypto.

https://nobleton.nl/deponeren/

Meer informatie: https://nobleton.nl/algemene-voorwaarden-deponeren-blockchain/