HN user
If anyone wishes to remember what that looked like.
https://web.archive.org/web/20071012231544/http://www.apple....
https://web.archive.org/web/20071012025941/http://www.apple....
Well, I wasn't intending to violate any guidelines, and I don't believe I've dismissed the article besides. I was just trying to save some people from potential frustration, as there was no warning provided upfront.
edit: Ah, I see. You left this comment after having your last response flagged.
Note that this post includes a major spoiler for the show The Good Place. The show is fantastic, so I'd suggest not reading unless you've already finished season 1, or have decided it's not for you.
I know that an uncommon name needed to be chosen, but something about the hyphenated /.well-known/ just turns me off.
I'd have really preferred another term: registered, reserved, defined, meta -- or really anything else.
Yep, they solve the same problem. I built my blog on Harry Roberts' ITCSS paradigm some ten years ago, and found it extremely easy to migrate to cascade layers. They're an underutilized solution to addressing growing specificity.
They're admittedly less useful if you're already using component-based design. That's closer to something like BEM in hyper-targeting each element.
Personally, I forget syntax all the time. There's always a warm up period after I switch languages, and it takes me longer to be start writing good, idiomatic code.
Like sure, I can probably write some python, but will it be pythonic? I might still be Java-minded for a while, trying to OOP my way into solutions.
Earlier today I needed to write some PHP and couldn't remember if it used length, count, or size. I had to look it up. I've been doing this for 20 years.
Sure, and Microsoft acquired DOS, and Adobe acquired Photoshop. At a certain point though, after 20+ years of development, you need to give some credit to the new owners for making it into what it is today.
Did vibe coding the business page inject it into ChatGPT's training data?
No, at least not directly. Inference does not train models. It is possible that OpenAI may separately collect the chat data, clean it, and feed it back into the model for future iterations. Or they could have extracted URLs for future indexing.
More likely though, I suspect, is your site just managed to be indexed naturally, and LLMs are very efficient at matching obscure data to relevant queries.
"Open source" as a term has evolved due to its success. It wasn't some malicious attempt at redefining things from the technical elite. It was a natural shifting of language, as happens with all words, as it entered more common usage.
It's entirely reasonable that this colloquial understanding would be applied to new categories such as AI models. I'm sure it'll be applied to many other things that don't fit the OSD either. That's just language for you.
Sorry, too busy "stealing code" to answer right now.
This is a pretty banal comment at this point. Open source is the term used in the LLM community. It's common and understood. Nobody is going to release petabytes of copyrighted training data, so the distinction between open source vs weights is a rather pointless one.
Well, yes, but that's why it's behind an about:config flag and users should not enable it without understanding its effects.
Single Page Applications use the History API to create a working back/forward history within the SPA. This will cause you to navigate away on use, and potentially lose data.
Chromium does include an ad blocker for "intrusive ads". ie. Those using many resources, flashing, auto-playing sounds, or otherwise behaving badly.
Manifest 3 explicitly enables ad blocking through the declarativeNetRequest API. It's trivial to do so, and many blockers exist in the Chrome Web Store.
Removing film crew, boom mics, and missed props from a scene would surely be useful to studios. It may even enable some shots that previously would have been impossible due to the positioning of cameras, etc.
Windows has a native (cloud-based) dictation software built-in[1], so there's likely less demand for it. Nonetheless, there are still a handful of community options available to choose from.
[1] https://support.microsoft.com/en-us/windows/use-voice-typing...
Bazzite KDE picked up my 8BitDo controller immediately, with no prior configuration. I didn't even have to manually pair the Bluetooth. I was very impressed.
Many people will likely be watching this show for the first time based on this thread. Please don't spoil major plot events for them.
Just in case you missed it, your quote was referring to encoding requirements. Decoding (eg. Netflix users) will have a different set of requirements. The situation will also improve over time as dedicated hardware encoders and decoders become available.
For the moment, I don't really mind if it requires more GPU power to encode media, since it only needs to happen once. I expect it will still be possible on a weaker card, but it would just take longer.
Contextual permissions are a big improvement over early and uncertain prompts. I will never agree to grant my permission when first loading a page, however, I may do so if intentionally activating a map widget. At least then I understand the context by which it's being asked, and can make a more informed decision.
Well, because it means that other energy generation sources like oil, gas, and coal aren't being used there instead. Since they cause far, far more harm than nuclear waste does, it's a net win.
Thanks for clarifying. It looks like I needed to refresh my memory of the browser APIs.
Reading further, this API only works remotely for CSS via chrome.scripting.insertCSS. For JS, however, the chrome.scripting.executeScript JS needs to be packaged locally with the extension, as you said.
It seems the advanced method is to use chrome.userScripts, which allows for arbitrary script injection, but requires the user be in Dev Mode and have an extra flag enabled for permission. This API enables extensions like TamperMonkey.
Since the Claude extension doesn't seem to require this extra permission flag, I'm curious what method they're using in this case. Browser extensions are de facto visible-source, so it should be possible to figure out with a little review.
Note that a checkbox's indeterminate state can only be set via JavaScript, so that lessens the elegance of a CSS-based approach.
I agree that using radios would be better. Or just prefers-color-scheme, which sidesteps the FOUT issue that often occurs when storing theme settings in localStorage.
Not having looked at the extension, I would assume they use the chrome.scripting API in MV3.
https://developer.chrome.com/docs/extensions/reference/api/s...
"probably should’ve added a disclaimer"
It's a violation of the Amazon Associates program to not have one.
It means exactly what it says: "What other parties do you mean?". Key players are already in lockstep on this decision, so insisting that Google must submit to the other WHATWG members doesn't make any sense in an argument for restoring XSLT or JPEG XL.
You seem to be reading subtext into a statement that was put plainly.
I made no such implication. Mozilla is certainly an other party, and their positions on standards hold water. They successfully argued for Web Assembly over Native Client, and have blocked other proposals such as HTML Import in the Web Components API. They are still a key member of the WHATWG.
The fact that Mozilla aligns with Google on both of these deprecations suggests the reasons are valid.
I personally see no reason for XSLT today. Outside of the novelty of theming RSS feeds, it sees very little use. And JPEG XL carries a large security surface area which neither company was comfortable including in its current shape. That may change based on adoption and availability of memory-safe decoders.
Which other parties? Because Mozilla's stance on JPEG XL and XSLT are identical to Google's. They don't want to create a maintenance burden for features that offer little benefit over existing options.
It's one thing to judge somebody for supporting an unjust and illegal war. It's another thing entirely to judge them for where they were born. None of us chooses our nationality.