Seriously, on the Firefox AI commit controversy. I don’t see the point in complaining. Anyone threatening to move to another browser over it isn’t escaping anything. Every major company is using AI heavily. Even in ways you don’t see through code. It’s just something we need to accept. AI is a tool.
For search, @kagi.com is really good. I didn’t see any mention of this aspect in the post.
Older safe style with a twist combination lock are pretty good. I just don’t trust this digital lock stuff. There is always a key backup, so kinda pointless.
Still private, but @shepazu.bsky.social is working on one. You better believe accessibility is at the heart of it. blog.fizz.studio/fizz-charts-...
Worth having a discussion to put it in the idea hopper.
The individual commits is also stunning. That’s a more important number to focus on IMO. Chromium clearly has a huge focus for people. And even being able to get that much from individuals given the complexity of everything is fascinating.
Legally, it actually doesn’t need to exist. Everything is full copyright by default. When you do have it, it’s supposed to be original year then a list of years in which significant changes happened. If multiple years are consecutive, then you range those.
T-Fiber (T-Mobile's new fiber home internet, where they bought up others to jump start it) has to be the most incompetent gathering of anyone working in IT and Support I've ever seen. They can't get anything right and support will leave notes in tickets that is the exact opposite of what was said.
I’m down. The best part is, we don’t need a law. Companies just need to do it. There is no legal requirement that older people be served the same. Only in employment. So, we can boot most of Congress and state leaders. Let them reap what they sow.
Current curve view tools don’t make much sense for humans either. Without the ability to actually mark comments being left as needing changes, general questions or optional changes. Everything is left a chaotic mess of just sort it out later.
The manicotti is the real prize. Can we forget the other thing and just do a potluck?
Then, who would we share ketchup with?
They are making local publishing require 2FA. So that’s the real auth gate after the first publish. Still, hamfisted rollout and major package providers can’t even move due to no bulk configuration allowed. (The definitely typed ecosystem for one.) We do need better, It might be new registry time.
Markdown support needs to be enabled. Not sure if pasting works though. Might still need to be s as fine you upload. support.google.com/docs/answer/...
codepen.io/Garbee/pen/V... Here is a functioning example of the implementation too.
It pretty much has it.
```
const pos = ['en-US', 'fr-FR', 'de-DE', 'es-ES', 'zh-CN', 'ja-JP', 'ko-KR'];
const sup = Intl.DateTimeFormat.supportedLocalesOf(pos);
for (const l of sup) {
const dis = new Intl.DisplayNames([l], { type: 'language' });
console.log(`${l}: ${dis.of(l)}`);
}
```
The cost benefit is pretty easy when you just want to ‘cd’ and have the shell switch to the runtime for the nvmrc definition automatically. Less error prone day to day compared to manually switching the versions.
If your org only uses one node version consistently for everything, then it’s no issue
When you force an extended government shutdown so no one is there to even try to stop you, everything is legal.
So, the ports are what most professionals asked for. These units sold like crazy compared to the previous models.
Confirmed, Apple lost nothing with the redesign. You personally just don’t want them so you’d rather no one did.
What’s worse too, I feel most of the people complaining wouldn’t even use it to begin with. They were just mad it was paid at all.
It’s awful that OS has created such a divisive situation with compensation for work.
Not according to the blog post. Just GitHub releases for now.
Elegance is too subjective to personal opinion. What did they lose?
@leviathanapp.bsky.social Bulk importing could use one key improvement. I have a text list exported from another program. Upon importing it, foils are correctly marked. But all normal cards are "Unspecified" for the finish. Tons of time would be saved if we could filter an import and mass update.
This is a paypal problem with how it’s configured. As others have already said. Kofi can’t mask it because they are trying to not be an intermediary. They would need to take a cut of the transaction if they became that.
I did this a few weeks ago… whoopsie. At least I caught it before things got too far.
This is way better and far less time consuming and mentally draining as the big survey. Both have their place to rank things, but the simplicity in this is refreshing.
This is traditionally buggy in Webkit. It also isn’t always what you want. It’s situational as to whether the content within is mostly text.
It’s an option in the right case, but you make it sound like a new rule to follow for all uses.
-checks notes- Justin is correct again.
Either he is pleaded with by Hollywood to remove it, at which point he is benevolent and does so. (After pilfering what he can.) Or, he realizes it can’t work and removes it on his own. At which point, it did its job somehow and isn’t needed.
Exactly this. Unless it is transitioning to an existing maintainer, essentially giving them more control, I want the clear indication. Just like Chrome extensions doing bad things after new owners.
We know some parts of the App Store (account management), some system settings (Applecare), and others use webviews internally. It’s just masked to appear highly native. It isn’t new that they’ve been doing it. It’s years old.
