illright

In the comments there's a link to consumer rights wiki that includes Raspberry Pi's response to this:

> there may be a minor financial gain in buying a part with say a 2GB part, swapping it for an 8GB part of dubious origin, and reselling it as an 8GB device. However, this brings an element of risk to the user - the board hasn't been tested by us - and is a potential support burden for us, with customers complaining of unreliable devices. We therefore remove the commercial incentive by locking devices to their original RAM size.

Frankly, that sounds pretty reasonable to me

The software still remains free, it's the registry that would become a paid service under such a model, that's what was proposed in the article. And even then, the registry would remain free for individuals, so it would merely be a price of convenience

I think it's a great idea and I hope someone inside the teams of popular registries sees this and they actually give it a go. I imagine the shitstorm of reactions that it's gonna cause from people who aren't even included in the "required to pay" group and I wish the registry maintainers strength to get through this

I think this article presents a good rebuttal to this model — foundations will never pay the long tail, and sometimes the payout may not even be all that substantial for them to bother. The model in the article has the benefit of being automatic and applies to all packages that actually get used by for-profit companies

I wonder why they only support Apple platforms, citing CoreML. Doesn't Android have a similar framework, ML Kit?

That bit of text looks pretty unremarkable to me, what makes you think that no one talks or writes like this?

Thanks for the write-up, I've been interested in connecting RF-controlled devices to Home Assistant myself lately! Your experience will definitely come in handy :)

Are you following HA's latest push towards proxy devices? A few months back, they have been improving support for RF and infrared controlled devices through proxy hardware — as far as I understand, it lets you have just one RF transmitter in the home and have several integrations use it for sending their chosen commands on their chosen frequency, a sort of transport/logic decoupling. It's new, so there's not a lot of stuff that uses these proxies, but I want to play around with them and wanted to get them on your radar as well!

I'm glad that Lumo has image editing capabilities now, if it's half as good as ChatGPT, that means I no longer have to upload photos of my room to OpenAI to try a new paint color.

However, I trust Lumo only marginally more than ChatGPT, they really don't do themselves any favours by claiming it's all open-source when only the frontend is

I didn't read the title of the article in that way, and I believe it to be a bad-faith reading.

I understood the title to mean "the people in FOSS whom we treat with the same morbid curiosity and provokation as the mentally ill people and other deviants who used to be displayed in circuses for other people's entertainment".

It's also clear to me from the text of the article that Drew does not hold contempt for neither of the two individuals he talks about, and the postscript demonstrates that he approaches this difficult topic with due diligence and respect for the people

I don't find it appropriate to make these kinds of assumptions about the author. It's okay to disagree, but it would help the conversation if you elaborated why you didn't enjoy the article

Nice article, it does a good job of conveying just how simple it is to use the OS primitives for secure-ish* delivery of secrets.

I think it falls short in meeting people where they are when they use env files. I appreciate the section at the end that says "if you must use dotenv files", but surely there's gotta be a middle ground where you can still leverage the OS and not lose out on convenience.

I think it could even look like an npm package that helps you set up the service correctly for local development, accounting for the reality that there is likely several projects on a developer's machine and some of these projects are there temporarily.

* of course, there's still all that stuff about environment variables being visible to other processes, so we still need decent runtime infrastructure for envvars like `DATABASE_URL_FILE`, a temporary file where the application can read the secret at runtime. I'd love to see that in Node instead of the `env-file`

I disagree that this submission has no value at all or that it should be auto-banned — there is a difference between thoughtless vibe-coding and spec-driven coding, guarded by tests. It seems from the next thread that this project is hopelessly outmatched by the sheer complexity of taking on something as the Docx spec, but this project has value, and for someone, it may be all that they need.

However, I do agree with your point about live debugging. In light of that, I prefer to treat this submission as a curiosity about current model capabilities, and let the authors keep improving this project if they find it worth their time.

Let's be more respectful to the differing goals of people