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
ari_verse
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.
Thank you! that fixed it - I only had "undertermined" selected as language. It's curious that other communities did not show this problem before.
For a low end, small, low consumption Intel box for HTPC/Kodi, Home assistant, Frigate, small Home Server or all of the above, I can recommend any N100-based box or mini itx mobo. It's very fast compared to prior Intel low consumption CPUs (apollo lake etc), does 4K, HDR, AV1.
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
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.