Search
1000 results for “nobodyinperson”
-
OMG I have made so many LaTeX Beamer presentations and even made a proper template¹ for the @unituebingen, how come I only now learn about \pause, \item<N-> and \only<N> to slowly build up your slides step by step??? 🤯
-
@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 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 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 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 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 -
@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 -
@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 -
@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 -
@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 -
@musicmatze What works surprisingly well is having a local @ollama do the OCR, and other stuff, including writing #plainTextAccounting transactions. I haven't had time to implement that fully though.
-
After a long session yesterday evening I finally managed to print custom QR code labels for #paperless onto sticker label A4 sheets. The QR code contains 'TAG:👛 Yann' and paperless can be configured to auto-detect that in scanned documents (such as receipts) and auto-attach a tag '👛 Yann' to know from whose purse that receipt was, which is very handy for #accounting (with #hledger) later, especially for cash purchases that you otherwise don't have any other trace of.
-
#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
-
#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
-
#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
-
#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
-
#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
-
@Sigma I understand. Without any real documented alternatives and migration paths, changes like this can be expected to trip up people though 🙃
- #fscrypt only supports some filesystems, setup and migration seem very manual and tedious, no #nixos wiki page or writeups
- #gocryptfs is FUSE, but also seems tedious, nothing for nixos either
- #CryFS is totally not designed for homedir encryption (though someome tried but stopped). -
@Sigma I understand. Without any real documented alternatives and migration paths, changes like this can be expected to trip up people though 🙃
- #fscrypt only supports some filesystems, setup and migration seem very manual and tedious, no #nixos wiki page or writeups
- #gocryptfs is FUSE, but also seems tedious, nothing for nixos either
- #CryFS is totally not designed for homedir encryption (though someome tried but stopped). -
@Sigma I understand. Without any real documented alternatives and migration paths, changes like this can be expected to trip up people though 🙃
- #fscrypt only supports some filesystems, setup and migration seem very manual and tedious, no #nixos wiki page or writeups
- #gocryptfs is FUSE, but also seems tedious, nothing for nixos either
- #CryFS is totally not designed for homedir encryption (though someome tried but stopped). -
@Sigma I understand. Without any real documented alternatives and migration paths, changes like this can be expected to trip up people though 🙃
- #fscrypt only supports some filesystems, setup and migration seem very manual and tedious, no #nixos wiki page or writeups
- #gocryptfs is FUSE, but also seems tedious, nothing for nixos either
- #CryFS is totally not designed for homedir encryption (though someome tried but stopped). -
@Sigma I understand. Without any real documented alternatives and migration paths, changes like this can be expected to trip up people though 🙃
- #fscrypt only supports some filesystems, setup and migration seem very manual and tedious, no #nixos wiki page or writeups
- #gocryptfs is FUSE, but also seems tedious, nothing for nixos either
- #CryFS is totally not designed for homedir encryption (though someome tried but stopped). -
Great, ecryptfs was dropped from nixpkgs, because apparently it wasn't updated in 10 years 😑
ecrypts was always my go-to solution for encrypting only my home directory, if full disk encryption is not available.
So what does one use now for homedir encryption?
-
Great, ecryptfs was dropped from nixpkgs, because apparently it wasn't updated in 10 years 😑
ecrypts was always my go-to solution for encrypting only my home directory, if full disk encryption is not available.
So what does one use now for homedir encryption?
-
Great, ecryptfs was dropped from nixpkgs, because apparently it wasn't updated in 10 years 😑
ecrypts was always my go-to solution for encrypting only my home directory, if full disk encryption is not available.
So what does one use now for homedir encryption?
-
Great, ecryptfs was dropped from nixpkgs, because apparently it wasn't updated in 10 years 😑
ecrypts was always my go-to solution for encrypting only my home directory, if full disk encryption is not available.
So what does one use now for homedir encryption?
-
Great, ecryptfs was dropped from nixpkgs, because apparently it wasn't updated in 10 years 😑
ecrypts was always my go-to solution for encrypting only my home directory, if full disk encryption is not available.
So what does one use now for homedir encryption?
-
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.
-
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.