@xdej Just to be clear: #radicale is a caldav/carddav server which just uses files as storage and can be configured to commit any changes to git. My #nixos module services.radicale.git implements that and also automatic sync with given remotes. It's not a general-purpose syncing module, but that's on my todo list as well, using plain #git or #gitAnnex.
#gitAnnex
@nobodyinperson I'm asking you first because involving #gitannex would be high on my priority list. Really this wouldn't need to be #hledger specific as it could just as well be paired with #ledgercli or #beancount either directly or via CSV or whatever. I'm not a huge GitLab fan these days but can do it if you prefer. Codeberg seems more aligned or GitHub having the advantage of contributor pool. Thoughts?
@musicmatze What I am also interested in is how to bring the information from paperless back into my #gitAnnex. Paperless can't replace a shared folder where you put e.g. SVGs, spreadsheets or documents you edit, it's an archive for static content.
@Atemu regularly runs an export and uses that as a git annex special remote. But the configurable directory structure is rather limited. Maybe I'll import it to a subdirectory of our git annex repo+metadata would be amazing.
@musicmatze Yeah, I dumped our shared :gitannex: #gitAnnex folder into it and it's a lot 😅 Also the ASN QR code thing¹ is amazing, put a QR code on the start of every related bunch of papers, then scan the whole stack at once → #paperless splits it automatically and sets the ASN metadata field.
Dokumente im Posteingang: 110
Dokumente insgesamt: 4805
Zeichen insgesamt: 45.402.448
Aktuelle ASN: 122
#forgejoAneksajo #gitAnnex #dataLad crowd:
Anyone else running into this experience-crippling #forgejo bug causing the activity page (de facto landing page for every user) to take extremely long to load (for me 10 seconds)?
https://codeberg.org/forgejo/forgejo/issues/9040
@datalad @forgejo
Some more `git subtree push` quirks:
• `git subtree push` (obviously) does not push :gitannex: #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: #datalad you can't commit at once.
scrolling through #gitAnnex backlog that I have not had time to look at yet. 375 messages going back a long while.
Always feel bad about not getting to everything, but I do eventually get to most things.
Anyway, it's really nice that I actually have funding for some hours each month to try to keep up with all the messages, and sometimes even dig into the backlog, sponsored by the INM-7 at Forschungszentrum Jülich.
My kids are tech-privileged. They're playing Super Mario 64 on the steamdeck via #RetroArch, and wanted to play Kirby. While they played, I SSHed onto the Steamdeck, and #GitAnnex get'ed the Kirby ROM from my fileserver. #techdad
I"m currently thinking a bit how I want to organise my stuff.
I noticed that for a long time I only managed my calendar through the Nextcloud interface.
Which lead to the following questions.
- What if I would carry all my data with me?
- How much disk space would I need?
- Or what if I would go back to manually syncing things?
- How does #localfirst look like in 2026?
- Is #gitannex something that could help here?
- How do you play local music on an iPhone?
Does someone have experience with this and would like to share some inputs?
I've seen that #offlinefirst is a hashtag that is mainly used for a development practice, how do we call this for users?
I've set up a #gitAnnex self-organised session for at #39c3 day 3 0:30.
If you're already a user or just curious about the tool, come by and have a chat! :)
https://events.ccc.de/congress/2025/hub/event/detail/git-annex-workshop
Organising my :nixos: #nix code and splitting out sharable things into a separate repo. Here for example is my package for #forgejoAneksajo (:forgejo: #forgejo + :gitannex: #gitAnnex support) with a couple of my patches applied:
> nix build --refresh gitlab:nobodyinperson/yannix#forgejo-aneksajo
> result/bin/forgejo -v
forgejo version 13.0.3-git-annex2 built with go1.25.4 : sqlite, sqlite_unlock_notify
RE: https://mastodon.social/@whitequark/115635167578691059
Thank you
- @joeyh for :gitannex: #gitAnnex
- @matrss for maintaining #forgejoAneksajo
- @simonmic for :hledger: #hledger
- John Collins for #latexmk
and many people maintaining other #FOSS projects I rely upon
@inlovewithpda Is it still not resolved, what a mess. I switched to :gitannex: #gitAnnex for file syncing a while ago, so I am unaffected, but man...
How appropriate that today I got to add another org to the #gitAnnex thanks page! https://git-annex.branchable.com/thanks/
The Distribits2025 talks have been published. Many of them concerned #gitAnnex, and I've put together a list of those here.
Do you have big data to share in a forge? Try #forgejoaneksajo! It's an active soft fork of @forgejo, adding git-annex support.
@matrss gave a nice talk about it on @distribits, which you can watch there. Thank you!
https://www.distribits.live/talks/2025/risse-forgejo-aneksajo-a-git-annex-datalad-forge/
PS: I wish #GinGNode (gin.g-node.org) will update to this at some point in the future! It goes one step further, adding DOIs to datasets/code.
#gitAnnex can now use Iroh to connect two repositories located anywhere, including behind firewalls needing hole punching.
As well as sending data with git-annex, git pull and push works too
https://git-annex.branchable.com/special_remotes/p2p/git-annex-p2p-iroh
Developed at the #distribits hackathon in collab with matrss
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst