To give DarkTable credit, neural-network-based denoising will be in the next major release (5.6).
And even without neural networks, DarkTable denoising is better than open-source competitors, due to the database of camera sensor noise shipped with it. For each supported camera and ISO setting, it contains the measured values of Poissonian and Gaussian components of the sensor noise, so proper denoising becomes a one-click operation. That's as opposed to the much more complicated "drag the luminance and chrominance noise sliders until the noise disappears, then drag two more sliders to recover detail" workflow found, e.g., in ART.
The thing is, 127.0.0.53 is a fallback. The real default upstream is nss_resolve, which talks to systemd-resolved via non-DNS protocol on a UNIX-domain socket. Ubuntu disabled this in favor of the less-featured fallback. If you insist on sniffing DNS, you need to add instructions to disable the native nss_resolve module by not including it in /etc/nsswitch.conf.
Thanks for that hint! We still get the lookup if it leaves the machine unencrypted, but if you have both, the Unix domain socket and DNS encryption, we miss lookups.
The article says: "Already, it feels like there’s not much left for a human teacher to contribute, they believed". I also got a question over IM on whether it is possible to learn programming without a live teacher, using AI instead. I answered "no", and I stand by this "no". A live teacher chooses what to teach and in which order. A live teacher can insist on not skipping some boring but important topic and not advancing further until something is mastered, and AI currently can't do that.
On the other hand, avoiding AI completely is counterproductive. I do use AI, including for contributions to projects that allow this, but I do review everything that AI writes. So, in the AI era, the main skill required is code review, and there is indeed a change needed here, as existing programming courses focus mostly on writing code and then on understanding the underlying low-level mechanics.
> Anyone that cannot take 5 minutes to set up commit signing with a $40 usb smartcard to prevent impersonation has absolutely no business writing widely depended upon FOSS software.
No. As a user of your package, I want assurance that the package you publish does what it says it does and does not contain malware. This is different from the package having been published by you. I want protection against you going rogue, not only from you being impersonated. 2FA on your side does not protect me against you going rogue. A comaintainer does.
So the correct quote would be: Anyone that cannot find a comaintainer to review all the code and to prevent deliberate sabotage has absolutely no business writing widely depended upon FOSS software.
And even a mobile app (or, in fact, any single-person 2FA) would be unnecessary if we had a requirement for another live person to approve the release. As a bonus, a two-maintainers-required setup would also improve resilience against one of them going rogue or getting tortured.
The "nothing gets on main without two signatures" rule would not have prevented the xz story, where a comaintainer was able to smuggle malicious code past the review as "binary data for new tests" and, effectively, get it signed.
Exactly. "Doing it this way would prevent us from also doing X in the future; are we sure to permanently cross X from the roadmap, and are stakeholders aware?" is a valid and valuable objection. EDIT: and it can be trivially shot down by somebody with enough authority to define a roadmap saying, "we don't care about doing X".
The problem here is that a digest derived from the schema would just reintroduce the possibility of confusion of identically encoded but semantically distinct types.
You need to filter out unavailable and obsolete products.
My prompt (in Fast mode, as a guest):
"""
I need to take a trip to Turkey for a week. I would like to take a camera with me, but my Nikon Coolpix P1100 is too heavy for that (1.5 kg). I do need some zoom, let's say up to 250 mm but the exact maximum focal length is negotiable.
"""
The model seemingly failed to realize that the request is about a high-zoom compact camera. Only one of three different suggestions featured a compact camera, "Canon - PowerShot ELPH 360 HS - A Full HD Video 20.2-Megapixel Digital Camera - Black", on BestBuy (https://www.bestbuy.com/product/p/J7C86SHZLX), and it's unavailable there. So, zero success, but the 10-year-old camera suggested does fit the bill if still available from elsewhere.
This is great. thanks for taking your time to try such an ellaborate prompt. Interestingly the recommended bestbuy link is available in my location (California). Fastmode doesn't look at your location unless you are signed in.
Wondering if time permits, can you try completing your profile and try deep mode? Or i can give a try as well if you share your city or country and share you the cart link to validate. Thanks!
Not speaking on behalf of PSF, but to me, it looks like a no-go, as some packages are maintained, legitimately, by people from sanctioned countries, with no way to pay any amount outside their country.
And even without neural networks, DarkTable denoising is better than open-source competitors, due to the database of camera sensor noise shipped with it. For each supported camera and ISO setting, it contains the measured values of Poissonian and Gaussian components of the sensor noise, so proper denoising becomes a one-click operation. That's as opposed to the much more complicated "drag the luminance and chrominance noise sliders until the noise disappears, then drag two more sliders to recover detail" workflow found, e.g., in ART.
reply