If you are not on it already, it would be a good time to pull precious information from US sites and data portals.
git init
git annex init
git annex addurl --file <goodname> <urltoresource>
git commit -m "goodmessage"
will preserve the content, checksum, time of download, downloader and origin location in a #gitAnnex repository.
This is a good starting point to put things back together later on.
@spandexbob Were we walking across London Wall some time after a meet-up?
I think your point from approx 10 years ago is still true - all that data is outside the repo and easily lost. I still occasionally ponder if things like issues could be better recorded in #GitAnnex or similar.
Using the pre-built standalone 
#gitAnnex version on 
#NixOS:
https://gitlab.com/nobodyinperson/nixconfig/-/commit/78f719211cc9310a8bde1be7b7d8894341ab7b65
(to get the latest version, nixpkgs is typically quite behind)
I want a build system that:
- is as powerful and flexible as #SCons
- as readable and concise as #SnakeMake
- has a fricking progress bar+ETA
- is 
#datalad / #gitannex agnostic (knows that files can be fetched from elsewhere
- remembers how long building things takes
- balances that to decide if rebuilding locally instead of fetching gigabytes via slow internet is favorable
- integrates well with #nix for reproducibility
In the latest DataLad blog post I try out two changes which were introduced in git-annex within the last year: git-remote-annex Git remote helper (this is the big one!) and a small change to enabling WebDAV special remotes. They work brilliantly, and combined they enable read-only data publishing on Nextcloud instances.
Are you still looking for inspiration for your contribution to #distribits2025? Or maybe you just can’t wait any longer to hear more about #opendata and #rdm tools like @datalad and #gitAnnex.
Check out the new and improved display of the #distribits2024 talks on our website: https://distribits.live/talks/, and when you’re done, don’t forget to register your attendance!
OK! I think I'm starting to get th hang of #gitAnnex . Got a few scary moments with losing (?) some files at the beginning but if I don't have the assistant running in the background to eagerly mess with my repo without me noticing it goes well. :)
The events of the past weeks have again upped the urgency of moving away from the US tech cloud. After forever Google and 18 years GitHub this is hard for me.
I am lucky that @distribits gave me the enthusiasm and the tools to make this happen for me and the #infrastructure of the #research group I am heading.
This is the first post in a series that documents our new #selfhosted setup, starting with the centerpiece forgejo-aneksajo -- #forgejo with #gitAnnex built in.
Every few years I'm thinking of how to manage arbitrary non-text files in a project, and I remember #GitAnnex exists
and then I try to learn how to actually use it to manage files in a project, and I wake up three hours later in a puddle understanding nothing
Does anyone know a tool that automatically (!) maintains a readily accessible list of 
#git / #gitAnnex repos on the current machine? I have *so* many repos (I basically keep my life in git) that an overview tool would help.
I imagine hijacking my git executable with a wrapper to have it write a somewhat informed directory into ~/.cache/..., another tool that goes through the list and filters out the actual repos, plus a filesystem scanner service.
Hey #gitAnnex people, I decided to try again to use annex because it looks amazing. I decided to have a central repository on my server, so my home raspberry pi can connect there whenever I have internet at home and get data from the server, while I send things to the server whenever my laptop has internet access (internet at home is through my phone sharing connection...). I have my repository on my laptop setup ok, same on the server (gitolite, I followed the wiki and was able to get the web app to find it and register it as a transfer repository). I cloned the repository on my raspbery pi and was able to set up things the same way there. I set the repository on the raspberry pi to be a full backup from the web app. Now, how do I make my computer aware of the raspberry pi? My understanding is that my laptop won't send anything there unless it knows it should use it to send to the pi?
Hello fellow #distributed #data enthusiasts 
It’s time to register and submit your abstracts for #distribits2025! Find the link and learn more at https://distribits.live.
23-25 October, 2025
Düsseldorf, Germany (and online)
Nothing — it’s free!
Join us to talk all things @datalad #gitannex, #opendata, #rdm, and everything in between.
I *finally* taught #annextimelog¹ to properly count total time without double-counting overlaps. 
Now a `atl ls work last week` shows the expected summed time. 
One of annextimelog's selling points is that it can record arbitrarily many parallel things (something many other time tracker refuse to do), so this was a long-missing feature.
If you're unaware, annextimelog is my #cli time tracker that uses #gitAnnex as backend.
Does anybody have experiences to share or examples to point out of using #gitannex to store generated artifacts in the same repository as the sources?
One of my #systemd services is politely being stopped (”A stop job for unit ... has begun execution”) after ~70s without daring to explain why. It happens while the service runs `git restore .` in a large #gitAnnex repo on a rather slow HDD. It's okay that it's slow, but why on earth does systemd just kill my service!? 
Apparently, #gitAnnex can't export the synced/* branches to exportree=yes special remotes:
https://git-annex.branchable.com/bugs/Can__39__t_export_synced__47___branches
Oooh, @matrss has fixed (image) diffing in #forgejoAneksajo (
#forgejo with #gitAnnex support), so now you can very elegantly compare graphics such as plots which you put into the annex to not pollute your #git repo 
