The code generated by Claude is fully under my control, and I make sure it works exactly as I intend. I could have hidden this by committing it myself, but I choose to acknowledge that I had Claude's help
It’s not your fault. The problem is now that my mother in law can vibe code a complete operating system, I cannot distinguish quality from shit any more. And the last few OSS projects that I tried that had the Claude icon where shit and breaking in many ways.
It's kinda like eternal September but for software engineering. There was a time that just being on the internet, having an email address, etc. was a signal that indicated a level of technical proficiency. Now everyone has that connectivity, it doesn't mean anything anymore.
I think your prior assumption that all OSS projects had a degree of quality is where your problem is. But I get it.
We’ve had low quality code for as long as we’ve had programmable machines. I’ve seen a lot of manually written bad code well before LLMs took over. Nowadays, I primarily look at how long a repo has been around and how active it is. A repo that has consistent activity is probably going to be a higher quality one. Even better if I can follow PRs to see how the code base is evolving.
I will admit it’s become more difficult to tell low quality git repos from higher quality ones. Missing files or incomplete README files are a thing of the past. Claude is very good at filling in the gaps to make all repos at least appear respectable.
The Claude-generated README doesn't inspire confidence in that. I believe you checked all the code, but a lot of people are going to see that README and not give the project a second chance.
macOS 27 has a feature showing 'running in background', and it's great that I can kill background processes left behind by AI Agents in the terminal or IDE after they finish their tasks—such as services started up to get access ports, scan reports, or any hung sub-worker. Or any other CLI/bash scripts that ran but still left leftover background processes.
It is the only blockchain where developers can use pre-built, customizable modules to create dynamic applications that aren't possible on other networks. Combined with optimizations to its core architecture and enhanced cross-chain interoperability, Injective offers a high-performance network, ready to efficiently and securely bring the global financial system on-chain.
Thinking about your MacBook show off ads while you are using it, and about Apple Ads. NO! Apple never does that. That's why I never use Samsung devices.
The source code of the Open Graph Protocol website had been archived by Facebook. I don't see any announcement about it. Is it still useful to implement it on the website?
User-agents are not make sence, because custom browsers can cosplay easily, just set the "good" user-agent. If some custom browsers have evil purpose, why it need show it off? Change user-agent is very easy.
Oddly enough, they simply don't do that. IDK why, but they don't. Also, there is a bit more to browser integrity check than just the user-agent. But, yeah. You'd be surprise how often I saw attacks get mitigated that were using some obviously bad UA. The attack themselves seemed sophisticated enough, but the UA was still a 12 version old IE UA string or "1337 browser 2000" or something dumb like that.
"Despite use of the word "standard" as part of its name, readers are advised that this document is not an Internet Standards Track specification; it is being published for informational purposes only."
So, there's an RFC, but it is not standardized, per se. But close enough, for many uses.
It's as standard as most file formats get. The IETF reserves the phrase "Internet Standard" for certain very important protocols -- there's no place in the process for file formats.
The IETF has a Standards process, which develops new de jure standards and this just isn't one of those. Most products of the IETFs dozens of working groups (e.g. the replacement effort for CAT is being worked on by a group named kitten) will be Standards Track documents.
IETF working groups are perfectly capable of defining file formats, eg RFC 7468.
ZStandard wasn't developed using the IETF process, that's why it isn't on the IETF Standards Track. PNG likewise is not on the Standards track, whereas Ogg (the container format) is.