I’d like to image with a bit more work, the Firefox core dev team funding this into a CI test and chipping aaay at performance both of Firefox and policies around what goes in the store. Better scanners when extensizoms are unplosded would likely suppprt big gains in removing the poorest quality stuff here and addressing what is leaking memory and is over resource hungry.
I honestly enjoyed the article and agree with their move but I did have a chuckle reading all the way through and then see g right there under the article the X social media sharing icon.
I’m sure it’s on its way out, but I did quietly laugh to myself from the irony.
I’ve mainly been using cloudflare for the very excellent (and free) premium DNS offering.
Easy upload of bind test files
Flattened CNAME to support naked domains
Robust free role based permissions to add other ppl
Anyone have suggestions for moving a stack of domains, many being little community and hobby projects away from cloudflare for a small overall price. Agency pricing like migadu offers for email on custom domains is what I have in mind.
I've found every other offering to be lacking. Some examples: Cloudflare is alright but has settings footguns if you're not used to Their Way of Doing It™ (e.g., before using DNSControl, I had to manually flip switches to turn off proxying every time I updated my zones). deSEC is free and okay, but sometimes quite slow to propagate and its UI+API are unwieldy. DNS Made Easy is often pushed on social media, but it's ridiculously pricey for what you get if you don't need a SLA. DNSimple seemed nice but IIRC I couldn't get a different API token per zone (?).
I'm currently relying mainly on LuaDNS. For me, it functions as a "dumb" DNS host (i.e., not using their Lua configuration-as-code system). Their API is oddly designed, but it's been passable since a recent-ish update, which has allowed me to safely port my zone files to DNSControl.
> DNSimple seemed nice but IIRC I couldn't get a different API token per zone (?).
We overhauled our account tokens a few years back: https://blog.dnsimple.com/2023/11/scoped-access-tokens/ . With account tokens you can specify fine-grained scoped access control, including specifying only one or more zones that a token has read or read/write access to.
I think you're right about dnsimple tokens unless they've changed recently. I ended up writing a proxy that held the powerful token and then issued its own tokens to get around that... A bit convoluted
Annoying for dynamic DNS and DNS ACME challenges where you want a server to manage its own records and nothing else
I've put a comment on the parent thread, but unless I've misunderstood what the poster said, we addressed the limitation back in 2023 with scoped access tokens.
I used them in the past (many years ago) and was very surprised when my DNS was affected by a cloudflare outage. Turns out (back then) they relied on the cf network for DoS protection against their resolvers[1]. I was surprised to learn that and honestly thought that if I already take a dependency on cloudflare I might as well have them host my zones directly for free.
At one point we were using Cloudflare's DNS Firewall product for our entire edge network. We have since moved half of our edge network to our own infrastructure and are currently in the process of expanding our edge network further, so at this point an outage at Cloudflare should be at least partially mitigated for our customers due to our separate edge network, and eventually it should be completely independent.
I make a point of using a dedicated service provider for each distinct service. YMMV but I'm happy with DNSMadeEasy (DNS), IWantMyName (registrar) and Fastmail (email).
> Notably, the rollout will be handled by an “intelligent” update system that leverages machine learning to determine when a device is ready to receive the update.
> Curiously, there seems to be a lack of transparency around how Microsoft’s machine learning system decides when a device is ready to receive the automatic update.
The open secret is that the LLM has been prompted to make the call and no human in Microsoft is able to interrogate why the agentic AI is pushing updates to some machines and not to others.
> Surely our camera gear is exponentially better now
They are better, but not exponentially. You can't beat physics, film cameras can still compete in terms of dynamic range and resolution, the optical elements haven't changed that much. The 1972 photo was taken on medium format film, which is twice the size of the sensor area in the modern one, which means more photons and less noise. The recent image was take at a really high ISO, which adds to the noisiness.
I’ve looked at Casa. It wasn't CasaOS, but now I'm remembering.. I think they supported casa's marketplace conventions.. so that's how as a new project it had a big marketplace as they sort of piggy backed all the apps that casa supported onto their own marketplace.
I like these conventions. Another personal practice I us the body for is where I’ve relied on any webpages; blogs, issue reports, stack overlap pages etc to help the commit come together.
The example of using one library over another, especially if research has gone into which to choose, regularly involves say finding a good article that compares the alternatives.
I’ll say though that I usually include links to more notable references, I won’t usually commit refs to a libraries own docs and more obvious stuff; revealing and keeping references to resources found that went towards getting it done are what I keep and add to commit body.
Maybe there’s spaces for useful references to be added to the spec/conventions.
Personally I usually show links like this after the body message.
reply