home.social

Search

1000 results for “nobodyinperson”

  1. Ugh this morning the Android support on my phone entered a crash/restart loop, rendering all Android apps unusable 😩

    Apparently the Android VM runs out of memory and there's no fix.

    UPDATE: It seems I have found a solution/workaround¹ 🥳

    forum.sailfishos.org/t/android

    ¹forum.sailfishos.org/t/android

  2. Oh. my. god. For the first time in my life I now have access to a *wide angle camera* on my phone! 😱 🥳

    Today I was brave enough to finally update my phone to the latest #SailfishOS 5 (I could absolutely not afford a bricked phone the last ~2 years), and it was the smoothest update ever, so my fears were unfounded. 🙃

    However - in typical #LinuxPhone fashion - this¹ little hack for unlocking all the cameras makes the selfie camera unavailable, oh well... 🫠

    ¹docs.sailfishos.org/Support/He

  3. Oh. my. god. For the first time in my life I now have access to a *wide angle camera* on my phone! 😱 🥳

    Today I was brave enough to finally update my phone to the latest 5 (I could absolutely not afford a bricked phone the last ~2 years), and it was the smoothest update ever, so my fears were unfounded. 🙃

    However - in typical fashion - this¹ little hack for unlocking all the cameras makes the selfie camera unavailable, oh well... 🫠

    ¹docs.sailfishos.org/Support/He

  4. Oh. my. god. For the first time in my life I now have access to a *wide angle camera* on my phone! 😱 🥳

    Today I was brave enough to finally update my phone to the latest #SailfishOS 5 (I could absolutely not afford a bricked phone the last ~2 years), and it was the smoothest update ever, so my fears were unfounded. 🙃

    However - in typical #LinuxPhone fashion - this¹ little hack for unlocking all the cameras makes the selfie camera unavailable, oh well... 🫠

    ¹docs.sailfishos.org/Support/He

  5. Oh. my. god. For the first time in my life I now have access to a *wide angle camera* on my phone! 😱 🥳

    Today I was brave enough to finally update my phone to the latest #SailfishOS 5 (I could absolutely not afford a bricked phone the last ~2 years), and it was the smoothest update ever, so my fears were unfounded. 🙃

    However - in typical #LinuxPhone fashion - this¹ little hack for unlocking all the cameras makes the selfie camera unavailable, oh well... 🫠

    ¹docs.sailfishos.org/Support/He

  6. Oh. my. god. For the first time in my life I now have access to a *wide angle camera* on my phone! 😱 🥳

    Today I was brave enough to finally update my phone to the latest #SailfishOS 5 (I could absolutely not afford a bricked phone the last ~2 years), and it was the smoothest update ever, so my fears were unfounded. 🙃

    However - in typical #LinuxPhone fashion - this¹ little hack for unlocking all the cameras makes the selfie camera unavailable, oh well... 🫠

    ¹docs.sailfishos.org/Support/He

  7. drawtext filter chokes on umlauts, causing it to drop trailing characters 😩

  8. @kevinbowen Did I miss anything? Do you prefer a Google Calendar!? 😅 might be a bit quirky old, but there are very many CalDAV integrations, servers and libraries out there, so I find it very well interoperable. 🤔

  9. I am amazed how well these 3D-printed PETG parts have survived all these years in the elements. They're gunked up, but still flexible and strong as ever.

    These were part of the sensor network I build during my , which I tore down today. End of an era for me. A good one.

  10. @matrss @mahlzahn I am still running on this system here (which has recently deprecated btw, damn!), and this even only supports 144 chars for filenames. Recently @forgejo's repo contains long test file names, making it a pain to work with on such filesystems.

  11. @matrss @mahlzahn I am still running #ecryptfs on this system here (which #nixos has recently deprecated btw, damn!), and this even only supports 144 chars for filenames. Recently @forgejo's repo contains long test file names, making it a pain to work with on such filesystems.

  12. @matrss @mahlzahn I am still running #ecryptfs on this system here (which #nixos has recently deprecated btw, damn!), and this even only supports 144 chars for filenames. Recently @forgejo's repo contains long test file names, making it a pain to work with on such filesystems.

  13. @matrss @mahlzahn I am still running #ecryptfs on this system here (which #nixos has recently deprecated btw, damn!), and this even only supports 144 chars for filenames. Recently @forgejo's repo contains long test file names, making it a pain to work with on such filesystems.

  14. @matrss @mahlzahn I am still running #ecryptfs on this system here (which #nixos has recently deprecated btw, damn!), and this even only supports 144 chars for filenames. Recently @forgejo's repo contains long test file names, making it a pain to work with on such filesystems.

  15. So about the driver needing insecure situation:

    I guess this is not only a problem but concerns anyone wanting to use their Kyocera printer on Linux. I understand that pypdf3 is deprecated and one should use just pypdf, but the kyocera driver is proprietary, so how would one fix that? 🤔

    I guess Kyocera themselves don't care whatsoever...

    github.com/NixOS/nixpkgs/pull/

  16. @DoctorMad Damn, the web version works very well now, amazing!! 🥳

  17. @DoctorMad Damn, the #SolveSpace web version works very well now, amazing!! 🥳

  18. @ivan @schmittlauch agenix is also for runtime, not evaltime secrets, so that's not what they meant. For a long time I also had a public config and looked for good ways to conceal private parts (e.g. with ) but eventually realised it's too much pain and hinders reusage by others, so went the arguably cleaner way: utilities in a public repo that you and others can source in their private ones. Can't point to specific service configs then, though...

    discourse.nixos.org/t/public-r

  19. @ivan @schmittlauch agenix is also for runtime, not evaltime secrets, so that's not what they meant. For a long time I also had a public #nixos config and looked for good ways to conceal private parts (e.g. with #gitAnnex) but eventually realised it's too much pain and hinders reusage by others, so went the arguably cleaner way: utilities in a public repo that you and others can source in their private ones. Can't point to specific service configs then, though...

    discourse.nixos.org/t/public-r

  20. @ivan @schmittlauch agenix is also for runtime, not evaltime secrets, so that's not what they meant. For a long time I also had a public #nixos config and looked for good ways to conceal private parts (e.g. with #gitAnnex) but eventually realised it's too much pain and hinders reusage by others, so went the arguably cleaner way: utilities in a public repo that you and others can source in their private ones. Can't point to specific service configs then, though...

    discourse.nixos.org/t/public-r

  21. @ivan @schmittlauch agenix is also for runtime, not evaltime secrets, so that's not what they meant. For a long time I also had a public #nixos config and looked for good ways to conceal private parts (e.g. with #gitAnnex) but eventually realised it's too much pain and hinders reusage by others, so went the arguably cleaner way: utilities in a public repo that you and others can source in their private ones. Can't point to specific service configs then, though...

    discourse.nixos.org/t/public-r

  22. @ivan @schmittlauch agenix is also for runtime, not evaltime secrets, so that's not what they meant. For a long time I also had a public #nixos config and looked for good ways to conceal private parts (e.g. with #gitAnnex) but eventually realised it's too much pain and hinders reusage by others, so went the arguably cleaner way: utilities in a public repo that you and others can source in their private ones. Can't point to specific service configs then, though...

    discourse.nixos.org/t/public-r

  23. @jrg If it works for you, this sounds good. [1] is an amazing project that does basically that: an auto-updating base and for the apps. Nothing wrong with that. You can use nix-flatpak [2] to put your flatpaks into configuration.nix, but then you might as well just use the native apps from nixpkgs, which probably work better in general. nix-env is pretty evil and I'd say avoid it.

    [1] nixbookos.org/
    [2] github.com/gmodena/nix-flatpak

  24. It's surreal: From what I have tested, the *only* way to decide what documents a user can see, is who the owner of a document is or who can view it. First, there is no UI to see who the owner or viewer of a document is, you can just search for documents of a specific owner. Then, you can assign an owner to selected documents - a document can just have *one* owner. Conclusion: It's impossible to share certain documents with/between non-superusers. 🤷

  25. First road bump with for me today. The permission system is weird. It seems impossible to make a user that can just view documents with a certain tag or from a certain correspondent. Apparently one needs to manually (or automatically on document addition) add that user as "owner". And paperless doesn't seem to have a link sharing system for *multiple* documents or a specific search. Only for individual documents. Meh. 🫤

  26. Wrote my first :rust: program today. A small utility to grab the last value of a matching column in a matching csv file. I had hacked something together with , and , but those were all too slow for fast repeated calls. This Rust version executes 10-100x faster: a few ms on a :raspberrypi: 4, neat! 👌

    Rust and :nixos: is also a match made in heaven, omg is the experience better than Python 🫠

    $ csvget scd30 co2
    940.66

  27. Weil es letztes Jahr beim so gut angekommen war, mache ich wohl beim sogar zwei :nixos: workshops:

    1. Workshop: Einstieg, Motivation, Killer Features, Basics
    2. Workshop: Deep Dive ins Nixos-Modulsystem, schreiben eigener Module, secrets management mit , vllt. Live-Deployment auf einen :raspberrypi: vor Ort

    Was meint ihr?

    tuebix.org/callforpapers/

  28. Weil es letztes Jahr beim #Tübix2025 so gut angekommen war, mache ich wohl beim #Tübix2026 sogar zwei :nixos: #NixOS workshops:

    1. Workshop: Einstieg, Motivation, Killer Features, Basics
    2. Workshop: Deep Dive ins Nixos-Modulsystem, schreiben eigener Module, secrets management mit #agenix, vllt. Live-Deployment auf einen :raspberrypi: #RaspberryPi vor Ort

    Was meint ihr?

    tuebix.org/callforpapers/

    #Tübingen #LinuxTag #FOSS

  29. Weil es letztes Jahr beim #Tübix2025 so gut angekommen war, mache ich wohl beim #Tübix2026 sogar zwei :nixos: #NixOS workshops:

    1. Workshop: Einstieg, Motivation, Killer Features, Basics
    2. Workshop: Deep Dive ins Nixos-Modulsystem, schreiben eigener Module, secrets management mit #agenix, vllt. Live-Deployment auf einen :raspberrypi: #RaspberryPi vor Ort

    Was meint ihr?

    tuebix.org/callforpapers/

    #Tübingen #LinuxTag #FOSS