fair point! I forgot I was posting a comment in the budget audiophile community :). Still, looking at the sound quality/price ratio, they are up there. If you can find a pair second hand, well taken care of these should last a loooong time. I also have a pair of version 1 since 2017 that I got half price at the time. version 1 had a design issue and kef replaced the electronics for free in 2018 or so. I have them paired with a raspberry pi + hifi berry card in the family room. Looks like they will last a lifetime.

Kef ls50we2. Amazing sound. Used them daily for 4 years now

TBH yes, agreed, that would be fair. F1 though is such a tough, brutal environment for pilots, fairness doesn’t always apply. Teams try and discard

Hoping he is ok. Opportunity for colapinto?

I tested this and could not reproduce the problem, filtering by score = “rejected” works as in prior versions. I am able to see only rejected photos if I choose that. I use this as part of photo culling fairly often, to delete the photos I do not need.

In this version they expanded the light table filtering capabilities to make it more flexible (you can filter by many different metadata fields now and create filter expressions, I think) , so you may want to first click on “reset filters” and then rebuild your filter.

I always thought the sidecars are not touched unless you edit an image. And even in that case they should be very solid. All these years using darktable and never an issue

Well arguably the crash during the race was mostly their own doing. Colapinto had been asking for the right tires for the intense rain and for reasons unknown they kept him waiting.

I am using N100 and it works great in my case, custom build with with a mini ITX n100 board, with real NVMe, SSDs, using a regular Linux distro. Really happy with it

What a drive by Franco! He almost got fastest lap as well. Amazing battle with Magnussen

Two candidates for my best-discovery-of-the-year prize,

Ptyxis terminal: https://gitlab.gnome.org/chergert/ptyxis A modern take at a terminal, gtk-4 native, gpu accelerated, container-aware etc that replaced tilix in my setup. And it comes neatly packaged as a flatpak

LogSeq notes: https://github.com/logseq/logseq A different approach to note taking & journal. Very nice looking, rich plugin ecosystem, could use some performance boost but I think they are working on it

Big shootout to flatpak/flathub that for me has finally taken off, I converted all of my regular desktop apps to flatpaks. Went from 3-4 apps last year to ~20 (including Firefox libreoffice, even my terminal app) this year and not looking back. This has made doing a major host SW upgrade almost painless for the first time in 25+ years using Linux desktops.

That guy that gave the release, what was he thinking!

What a weekend for Williams and most specially for Colapinto! Here’s to hoping he will take this chance and make his 9-race-only chance the start of a brilliant F1 career. He seems to have what it takes

Well these days we have flatpak to solve the “not in the repo” (or ‘old version in the repo’) problem.

It’s a fair point but I would rather diversify and also use something that is open / less opaque

A few years ago when my org got the ask to deploy the CS agent in linux production servers and I also saw it getting deployed in thousands of windows and mac desktops all across, the first thought that came to mind was “massive single point of failure and security threat”, as we were putting all the trust in a single relatively small company that will (has?) become the favorite target of all the bad actors across the planet. How long before it gets into trouble, either because if it’s own doing or due to others?

I guess that we now know

Thank you! that fixed it - I only had “undertermined” selected as language. It’s curious that other communities did not show this problem before.

I.V. Drip blend from darkcity cofee in Toronto. Roasted a few days ago. Looking forward to my morning cortado!

I just checked that link and YES, actually it is, thanks for pointing it out. The docs must have been updated for v0.13, they added the ffmpeg prefix to the go2rtc stance, this wasn’t there before. I found this originally in a github bug discussion with the frigate dev, where he suggested the person having issues to try this out and see what happens. There was no follow up after that suggestion though.

Note - another helpful tip for 510WA cams: in this github listing: Reolink Firmware Archive, you can find a link to version 3.1.0.1387 which I have been running for a week, this version is much newer than the latest official release (.764), it adds two useful new options in t he Stream configuration section (which is only accessible via the Web interface of the cam),

• interframe space: set it to 1X
• frame rate mode: set it to fixed

what is the point of doing that? I just checked and I have hundreds of entities, it would take a huge amount of time to see which ones to keep visible / which ones are used in automations or visualization etc. What is the harm of just leaving them exposed?