Yann Büchau :nixos:

@cynical13 I have two #Pinetime smartwatches. One died after a year or so, one after one week (!). To this day, @pine64eu ghosts these warranty cases. We also had to trash a now broken #PinePower USB charging station. My #Pinephone is still working though. But the quality is pretty subpar.

@IncredibleLaser Interesting. Maybe this fixes the abyssmal performance our university Samba drive has when mounted under Linux - 10-20s load time to list folder contents. I have tried all the options, nothing helps. It seems to depend on the file browser as well, #Nautilus seems to be faster and #Thunar unfortunately extremely slow.

I packaged the spyder-vim plugin to add #vim keybinding to #Spyder, below is a screencast. It's kinda meh though 😅 You have to focus a text box below the editor for the vim keybindings to be honored, and ESC doesn't focus it 🤨.

RE: https://fosstodon.org/@nobodyinperson/116526914580592694

Okay as it's such a hassle to get a working #Spyder going on #NixOS, I made this flake so you can use this command to launch Spyder with your desired packages available:

> nix run git+https://codeberg.org/nobodyinperson/nix-spyder#withPackages numpy scipy pandas matplotlib ...

EDIT: 👆 And Mastodon still can't do Markdown, so it wrecks the displayed link. If you copy-paste it, it should be correct though.

More info here:

https://codeberg.org/nobodyinperson/nix-spyder

😑 seriously?

#nix #nixos

Would be really great if

> nix run codeberg:user/repo

was possible. It works for #GitLab and #GitHub already. #Codeberg should also work. Instead, one needs to write this unergonomic thing:

> nix run git+ssh://[email protected]/<user>/<repo>

EDIT: You could upvote this feature request: https://github.com/NixOS/nix/issues/14064

#nix #nixos

Installing #Spyder on :nixos: #NixOS, ugh... 😩

• must use spyder from unstable, in stable it depends on insecure qtwebengine-5
• it runs, but the interactive terminal needs spyder_kernels module
• adding python3Packages.spyder-kernels to the python env, doesn't help
• putting python3Packages.spyder{,-kernels} both into current Python env is a problem, how do I make a nixpkgs.overlays to pick certain Python packages from unstable?

😑....

#Python

Ugh this morning the Android support on my #SailfishOS 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¹ 🥳

https://forum.sailfishos.org/t/android-app-support-crashes-after-starting-because-vm-runs-out-of-heap/24823/64?u=nobodyinperson

¹https://forum.sailfishos.org/t/android-app-support-crashes-after-starting-because-vm-runs-out-of-heap/24823/65?u=nobodyinperson

@kevinbowen Did I miss anything? Do you prefer a Google Calendar!? 😅 #CalDAV 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. 🤔

So about the #Kyocera #CUPS driver needing insecure #pypdf3 situation:

I guess this is not only a #NixOS 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...

https://github.com/NixOS/nixpkgs/pull/504557

It's surreal: From what I have tested, the *only* way to decide what documents a #paperless 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. 🤷

First road bump with #paperless 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. 🫤

Wrote my first :rust: #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 #qsv, #nushell and #python, but those were all too slow for fast repeated calls. This Rust version executes 10-100x faster: a few ms on a :raspberrypi: #RaspberryPi 4, neat! 👌

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

$ csvget scd30 co2
940.66

TIL that some #CalDAV servers just silently ignore your precious X-whatever fields 😑

Well I guess I'll have to teach caldav-event-pusher¹ to first check which fields survive an event upload...

¹https://gitlab.com/nobodyinperson/caldav-event-pusher

@Atemu Maybe I'm overthinking this. But if I'm doing backups, I want to be sure they're 100% able to get me up and running again. What good is a backup that has the service fall onto its face on restore, because of some tiny race condition or caching inconsistency during the backup?

I don't trust the servies I run (#forgejo, #mattermost, #paperless, #immich, ...) to guarantee random snapshot restore to always work. Except #radicale though, which is dead simple on disk, just files.

@platymew @msdropbear42 Oh I'd love to make videos about #hledger and #plaintextAccounting, has been on my TODO list for a long time, but I just have to prioritise other stuff. But I'll get there eventually 👍

Now I'm thinking about a new strategy:

- stop service
- make #btrfs snapshot (seconds at max)
- restart service
- run #borgBackup from snapshot, but via #bubbleWrap so it sees it as the original path and inodes for consistency&performance!
- run as many borg backups as desired to any remote, even in parallel, as the service is running again

Thoughs?

#nixos

#InfCloud hasn't been updated for a decade, yikes. But apparently it's still the *only* available statically servable (i.e. no database / no PHP / whatever) #CalDAV #CardDAV web client out there. 😱

The code is also... interesting. There's so much hard-coding going on, but maybe that's how you do web dev 😅 I made a #nix package you can override with some useful options such as increasing the animation speed and allowing vCard 4.0 support.

https://gitlab.com/nobodyinperson/yannix/-/blob/28052b214673c2b7b225a47bac13feb1637ac925/packages/infcloud.nix

@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.

More radicale goodness on :nixos: NixOS: services.radicale.git can now sync regularly and on change via radicale with multiple remotes. Currently, it'll prioritise the remote's state in case of conflicts. It's so amazing to have a git history of your calendar and addressbook! 🤩

https://gitlab.com/nobodyinperson/yannix/-/commit/3668d66b043452fff305eaf398056e815b07919d

#radicale #nixos #git

Full-sharing a #radicale calendar between users is simple with just symlinks. I guess one could do a readonly bind mount instead to get the same but without wrote access? 🤔

Radicale does have configurable rules to control such access, but those have one major flow: the accessible collections of other users won't auto-discover in cients. With symlinks they do, and with bind mounts they should as well, right?

#bindfs should allow for non-sudo readonly bind mounts.

https://bindfs.org/

@chrysn Oh wow even User Agent, that's neat! I think #radicale doesn't even expose that. 🤔

services.radicale.git.enable=true now makes nicer commit messages, for events and contacts it will list the name and even describe renames. Proof of concept, written in bash/awk. It'll be hard to write a diff-parser that covers all kinds of changes, I guess having a local LLM could do it, but it'd slow down radicale significantly.

https://gitlab.com/nobodyinperson/yannix/-/commit/a794137eeaf3526e6e945a34d8769fe468e52f10

#nixos #radicale

@jappie3 Here is a #NixOS module to enable git storage tracking for #radicale (service.radicale.git.enable=true):

https://gitlab.com/nobodyinperson/yannix/-/commit/56020051d61617aa5004a01e353be992739d57d7

Ooooh, you can easily full-share calendars of a #radicale instance between accounts by just symlinking them into other users' directories. Everyone then 'owns' that calendar and can do anything. Paired with the #git hook, this then gives you a very fine-grained log of who changed what and when. 🤩

Trying #radicale to selfhost my calendar and addressbook and having a pretty terrible time. Every calendar action takes 10 seconds even to radicale running on localhost because apparently Thunderbird sends the entire calendar at once on every update wtf. 🤦

EDIT: Okay, authentication must be set up, because only then Thunderbird allows accessing it as CalDAV, otherwise it sees it only as a single-file ics? idk...

Great, an amazing chain of events and maybe unfortunate UI design in #DAVx5 resulted in me deleting our shared #CardDAV addressbook - server side from an ancient #baikal instance, no backups (no mercy) of course. My rescue attemps of copying contacts around in #Thunderbird (why does 'export' make an effing lossy CSV without avatar!?) just made it worse, 50% of contacts now left.

It's finally time to #selfhost #radicale with #git and #borgbackup failsafes on my #nixos #homelab...

Towards simpler #btrfs raid setup with #disko:

https://discourse.nixos.org/t/btrfs-raid-with-disko/52503/3?u=nobodyinperson

#nix #nixos

🙄 You gotta be shittin' me...

Und ein weiterer Stein im Weg zum #Elterngeld...

#BundID #Personalausweis #AusweisApp #FediEltern

@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.

https://youtu.be/treF7oFLLmk?si=txA4iy0zcpxub_H_&t=119

Has anyone ever gotten `services.webdav` to work on :nixos: #NixOS?

I have a very simple and probably very common task: Expose a directory (in my case `/var/lib/paperless/consume`) via #WebDAV so my scanner can upload their PDFs there. I'm pretty much doing this¹ here, but also this person has problems uploading. I can browse the folder via WebDAV (e.g. from #Thunar or via #curl), but anything upload/file creation gives permission denied or crashes clients

¹https://discourse.nixos.org/t/webdav-cannot-write-anything/59221

#paperless

@rriemann Re: #xz backdoor, you state:

> NixOS: affected and unaffected, slow to roll out updates

But the sources you link don't state that NixOS was vulnerable to exploits, if I'm not mistaken. The backdoored code briefly landed in unstable, but wasn't exploitable due to #NixOS's unique build system. Furthermore, fixing it locally and distributing the fix without relying on the official distro cache/repos is much easier with NixOS, I would argue.

@forse I have been using a #PrusaMINI at home and at work for a long time now and am still happy.

@hisold Citing a plain website or GitHub repo is kinda unprofessional. Many widespead software packages have a publication that is well citable, e.g. #sympy has this one with a proper DOI: https://doi.org/10.7717/peerj-cs.103, same for #numpy, #scipy, #matplotlib, etc. Some have at least a #Zenodo entry (with a DOI) to be properly citable. #PlatformIO apparently has none of those.

When you've had enough of automating every little thing and just want to get stuff done and end up manually generating a bunch of (very slow to generate) PDF plots, then concatenate all of them with #ghostScript, then extract the text with #pdf2txt, use a regex in Python to find some numbers and dates in the plot's legend, to finally write them into a csv file.

🫠

It's not stupid if it works, right? 😅

#PhDLife

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: #git :gitannex: #gitAnnex #radicale #opentimestamps #annextimelog #passwordStore

https://m.youtube.com/watch?v=t5xDmslfzvs

Holy cow, they made a hand-driven CNC that does the fine work itself, in Open Source and a kit for 500€ (+your #3dPrinting costs) 🤯

I saw one of these as a commercial device at the #KIMS in #Tübingen, but as it was proprietary, there were quirks like software subscriptions etc.

I am sitting here in #Tübingen while my colleagues @umphy are in the mountains in #Austria (#Inntal) and fly our #multicopter​s with PARASITE payload (running :nixos: #NixOS) to do wind and other meteorological measurements. I can fix issues in the software (and the entire OS!) from here, over the internet. I can test my changes in a local VM here and on a spare system next to me, then deploy with one command: nixos-rebuild --target-host …

It's magical 🤩

#meteorology #mountainWeather

@scudderfish I could never find my way through #cadquery. Too weird the syntax and concepts. I forked #sdfCAD and worked on something I understood myself but in the end stayed with #solveSpace.

@jonathankoren Interesting! I use a 0.6mm CHT (high flow) nozzle on a #PrusaMINI with #PrusaSlicer and pretty much all seams are too *thick*, which makes tolerances ultra hard to get right. It feels like larger nozzles aren't yet tuned all that well in the slicers...

EDIT: scarf seams are also rather thick and ugly where they start and end.

Is there an option to tweak the seam "thickness" manually? 🤔 I didn't find any.

#3dPrinting

I am really looking forward to a time when scientific data analysis is less of a constant fuckaround and fight with technical bullshit. I'd *really* like

- #netCDF natively supporting complex numbers
- #Python #xarray and #pandas to natively support physical units (#pint is great on its own but the integrations leave a LOT to be desired)
- #Jupyter notebooks to suck less (crashes, glitches, widget plots not saved statically, an effing BUILTIN formatter, etc.)
- proper data pipeline systems
...

Laugengebäck mit #Obazda ist echt mein Endgegner 😅 Oh je...

Finally replaced the crappy O2 router with a refurbished FritzBox 7490. No network bullshit anymore, unrecognized hostnames etc. anymore. And eventually I can put #ddwrt or #openwrt on it if I so desire.

#homelab

800 lines of :nixos: #nix later and I have successfully beefed up our #3dPrinting infrastructure at work @umphy with one #RaspberryPi 4:

· a https://gethomepage.dev landing page
· three fullHD webcams, one for each printer, with current filament visible
· a smart #Tasmota multiplug to remotely power off a printer in case of a problem/hangup
· 🐙 #OctoPrint for the Prusa MK3S, #PrusaLink by the #PrusaMINI​s
· 🔐 all password-protected and certs from #LetsEncrypt

#Prusa #NixOS

Das #VPN der #UniBonn gibt mittlerweile eine äußerst unhilfreiche 404-not-found Fehlermeldung zurück, wenn man sich unter #Linux (#openconnect cli oder #NetworkManager GUI) verbinden möchte.

Die Lösung ist (natürlich!) wie hier¹ im #ArchWiki erwähnt:

> sudo openconnect --useragent=AnyConnect unibn-vpn.uni-bonn.de

Also dem Gateway vorgaukeln, dass man der Cisco AnyConnect client ist 😑

¹https://bbs.archlinux.org/viewtopic.php?id=289283

#PhDLife #academia

I find it rather weird that defining your :nixos: #NixOS machine in your flake via `inputs.mynixpkgs.lib.nixosSystem` is *not* enough to have it actually use your `mynixpkgs`. No, you need to do this boilerplate stunt. Why doesn't it do it automatically? 🤔

https://gitlab.com/nobodyinperson/nixconfig/-/commit/274f4265f37e5256ede5cd8f0fc5054ba4f408d2

#nixFlake #nix

@Seedoubleya Happens on a #PrusaMINI as well with shitty or wet filament. Very annoying indeed.

It appears there is no free #EAN / #barcode database by any chance?

UPDATE: Ah, https://opengtindb.org

Ich habe eine Hand voll :nixos: #NixOS Sticker beim #KIMS in #Tübingen gelassen.

After a lot of pain I finally managed to reinstall :nixos: #NixOS, now with #btrfs subvolumes and full disk encryption using #disko. Man was that a painful experience. 😩

XFCE also seems to have lost its capability to read keyboard shortcuts from xfce4-keyboard-shortcuts.xml, yay... EDIT: Okay, a reboot fixed it 🤷

At least I have a somewhat working system now. Enough for today... 😪