Some more `git subtree push` quirks:

• `git subtree push` (obviously) does not push  #gitAnnex files to the remote. Syncing annexed files there is unergonomic.
• `git subtree push` also strips commit signatures (e.g. GPG and as such #OpenTimeStamps timestamps). The truth lies in the monorepo only. Understandable, but very uncool.

git submodules have neither problem, but without tools like  #datalad you can't commit at once.

#git #gitSubTree

#Haskell library and -client for working with #OpenTimestamps.

(OpenTimestamps is a protocol for creating and verifying timestamps for digital files, which can be used to prove that a file existed at a certain point in time.)

https://photonsphere.org/post/2025-09-04-haskell-opentimestamps/

Haskell library and client for OpenTimestamps

Haskell library- and client for OpenTimestamps

@SeaFury I can imagine! I'm in Geoscience, where things are mostly published.

But of you cite such sources as email, do you take extra precaution to preserve, archive or prove their existence? I mean an email is a pretty unreliable thing.

I think I would at least timestamp them with #OpenTimeStamps, so I could prove that this email file really existed at that time. 🤔

Hier ist die Aufzeichnung meines #TdF4 talks letzten Samstag über „Das Leben in Git (Annex)”:

https://media.ccc.de/v/tdf4-26-das-leben-in-git-annex-

 #git  #gitAnnex #radicale #opentimestamps #annextimelog #passwordStore

Das Leben in Git (Annex)

media.ccc.de
@nina_kali_nina @unregisteredhypercadence Once upon a time I learned the one and outs of `rsync` options to permit cross platform file synchronization. File name limitations, path limitations, journaling, extended attributes... bluh. Then I decided Windows and macOS file systems were too much trouble and went all-in on Debian-flavored machines and Android phones, all held together by #syncthing, b2sum, and a sprinkling of #opentimestamps.
I wonder if @internetarchive uses #opentimestamps or a non-blockchain equivalent for its various snapshots. I would love to be able to independently verify the integrity of each page and/or asset against a merkle tree rooted in something reasonable, public, and obvious. #SecurityNow 996.

Hier ist die geschnittene Aufzeichnung meines #Tübix Vortrags zum Zeitstempeln von Dateien, z.B. mit #OpenTimestamps:

https://tube.tchncs.de/w/jcJWeiQFPxgvi5jJZyrPmC

#OBS hat natürlich mal wieder nur ein Standbild, aufgezeichnet aber immerhin gibts vernünftiges Audio durch das bessere Mikro.

Schneiden der #SolveSpace-Workshop-Aufzeichnung wird noch etwas dauern. Das ist komplizierter, weil mehr Dialog zum rausnehmen und weil das Mikro leider hoffnungslos übersteuert hat 😅

Tübix 2024: Dateien zeitstempeln, um damalige Existenz zu beweisen

PeerTube

Tübix 2024: Dateien zeitstempeln, um damalige Existenz zu beweisen

https://tube.tchncs.de/videos/watch/93682310-f92b-494f-9644-c69854354c50

Tübix 2024: Dateien zeitstempeln, um damalige Existenz zu beweisen

PeerTube
@joeyh As a bonus, one can prove the timely existence of any git-tracked file when timestamping commits with #OpenTimeStamps. It also has  #GitAnnex support, by the way. Very useful when you need to prove that a certain photo or document really existed back then and was not forged into existence yesterday. Think previous-damage photos for a landlord, or a contract, etc.

@joeyh Plus, considering to timestamp commits and their gpg signatures along the way with #OpenTimeStamps to keep signatures meaningful, even when a gpg key is compromised later.

https://opentimestamps.org

It basically puts a merkle tree hash of the commit into the #Bitcoin #blockchain (yes, I know...) which provides a rock-solid proof of the time the commit and signature was made (some hours precision).

This is one actually valid blockchain use case, I think.

OpenTimestamps: a timestamping proof standard

OpenTimestamps aims to be a standard format for blockchain timestamping.