Earlier quoted context omitted.
I'm curious, but I'm not sure if you can say - has Adafruit ever published anything about Flux?
[flagged]
Adafruit sure has a lot of stories they are eager to tell lately.
Adafruit receives demand letter from Fenwick legal counsel on behalf of Flux.ai
81–90 of 300 posts
Re: Adafruit receives demand letter from Fenwick legal counsel on behalf of Flux.ai
#82As an electrical engineer who has tried to use it multiple times, I think Flux is an absolutely awful product. No surprise at all that they want to sweep details about their “intellectual property, commercial traction and user base” under the rug.
Yeah this stuff isn't even realistic as well. A number of years ago I was working on something professionally and there was a problem. Only about 1 in 5 boards assembled wouldn't crash the CPU. After much debugging it turned out one of the ICs had an open collector output and it wasn't loaded correctly with a pull up resistor. This caused a cascading failure, held the bus up when initialising the hardware which hit t…
Everything you said is exactly the proper argument against vibe coding.
If you can’t or don’t entirely go over the output, the failure mode is invisible.
Re: Adafruit receives demand letter from Fenwick legal counsel on behalf of Flux.ai
#83>The letter further asserts claims under the Computer Fraud and Abuse Act. Adafruit accessed only information that Flux’s own systems made publicly available through a server misconfiguration A confession
They vibe coded their system and it showed Adafruit something? Or showed some information with trivial prodding? Sounds like your average cross-tenant leak. Maybe showing more than intended or some caching issue. Many options some not really not fault of Adafruit.
I don't know the details of the case, but what they worded there is a textbook unauthorized intrusion and a naïve teenager "the door was open" defense.
Mind you there can be nuances, but that quote is like saying "I took their stuff, but it was poking out of their pocket."
Re: Adafruit receives demand letter from Fenwick legal counsel on behalf of Flux.ai
#84Earlier quoted context omitted.
I'm curious, but I'm not sure if you can say - has Adafruit ever published anything about Flux?
[flagged]
My take is I've never heard of Flux but I've repeatedly heard of Adafruit getting into drama, so the bayesian in me is definitely not prepared to jump on whoever Flux is. Better to wait for the facts, than give Adafruit the benifit of the doubt.
Re: Adafruit receives demand letter from Fenwick legal counsel on behalf of Flux.ai
#85Earlier quoted context omitted.
> There are some AI-driven autorouters out there now. Placement is probably the big issue that needs to be solved now. Interesting that within an IC this is basically "solved", or at least properly automated with classical numeric techniques such as simulated annealing. I would have thought there's a big opportunity in a mixed-technique approach, where you use AI to extract unstructured data from datasheets and then…
> mixed-technique approach I think my biggest annoyance with the way we rolled out AI is that nobody seemed to want to use it to augment already working solutions. Just throw everything out and have an LLM do it instead.
I've been frustrated with Copilot in this regard.
I work on a large C++ codebase, with large files. Human developers jump around between files with the Visual Studio fuzzy search, set breakpoints to trace execution in the Debugger, use the IDE's refactoring tools.
Microsoft's answer to this was to just ... expose none of this to their Agent Mode!? Replace the working semantic autocomplete with fucking lies!?
Maybe it's changed, I haven't been paying that much attention after bouncing off of this. I've gotten mild acceleration from using gptel-mode in emacs, manually adding references to context, and having models do various mechanical transformations on code. And I've even had some limited success writing tools for it to do LSP lookups.
Re: Adafruit receives demand letter from Fenwick legal counsel on behalf of Flux.ai
#86Earlier quoted context omitted.
Yeah this stuff isn't even realistic as well. A number of years ago I was working on something professionally and there was a problem. Only about 1 in 5 boards assembled wouldn't crash the CPU. After much debugging it turned out one of the ICs had an open collector output and it wasn't loaded correctly with a pull up resistor. This caused a cascading failure, held the bus up when initialising the hardware which hit t…
Everything you said is exactly the proper argument against vibe coding. If you can’t or don’t entirely go over the output, the failure mode is invisible.
Vibe coding is certainly the main part of it. But another problem is how deep our software and hardware stacks are. There is too much information to retain to solve problems now.
Re: Adafruit receives demand letter from Fenwick legal counsel on behalf of Flux.ai
#87>The letter further asserts claims under the Computer Fraud and Abuse Act. Adafruit accessed only information that Flux’s own systems made publicly available through a server misconfiguration A confession
They vibe coded their system and it showed Adafruit something? Or showed some information with trivial prodding? Sounds like your average cross-tenant leak. Maybe showing more than intended or some caching issue. Many options some not really not fault of Adafruit.
Or someone found server.domain/path/subdirectory/resourceX and was like "shit, I was hoping to find resourceY but I can't find a link to it, I wonder if I just click in my address bar and change the X to a Y", and voila, resourceY is right there.
To some of us, this is elementary navigation. Like going up the stairs if the elevator is out. Often it's faster than waiting for the damn elevator, too.
To others, it's cybarrrr-criiiimeeee!!!!!!11111one
Re: Adafruit receives demand letter from Fenwick legal counsel on behalf of Flux.ai
#88Earlier quoted context omitted.
> There are some AI-driven autorouters out there now. Placement is probably the big issue that needs to be solved now. Interesting that within an IC this is basically "solved", or at least properly automated with classical numeric techniques such as simulated annealing. I would have thought there's a big opportunity in a mixed-technique approach, where you use AI to extract unstructured data from datasheets and then…
> mixed-technique approach I think my biggest annoyance with the way we rolled out AI is that nobody seemed to want to use it to augment already working solutions. Just throw everything out and have an LLM do it instead.
A few days ago someone on HN commented that a teammate uses Claude to search for text in files on their own computer. Buddy... There's Command-line Tools Can Be 235x Faster Than Your Hadoop Cluster and then there's Command-line Tools Can Be ∞ Faster Than Your AI.
Re: Adafruit receives demand letter from Fenwick legal counsel on behalf of Flux.ai
#89Earlier quoted context omitted.
They vibe coded their system and it showed Adafruit something? Or showed some information with trivial prodding? Sounds like your average cross-tenant leak. Maybe showing more than intended or some caching issue. Many options some not really not fault of Adafruit.
I don't know the details of the case, but what they worded there is a textbook unauthorized intrusion and a naïve teenager "the door was open" defense. Mind you there can be nuances, but that quote is like saying "I took their stuff, but it was poking out of their pocket."
It is bit grey area. You are evaluating something. Do some basic checks. Actually end up seeing something you should not. You stop and tell them to fix it. They then silence you.
Now it is bit questionable should you check things like this during evaluation or not. Strict legal reading probably not. With reasonable customer relations you thank them and put it on top of the priority list. Unless they clearly enumerated everything they got their hands on or tried to run more real scans.
Re: Adafruit receives demand letter from Fenwick legal counsel on behalf of Flux.ai
#90Earlier quoted context omitted.
> mixed-technique approach I think my biggest annoyance with the way we rolled out AI is that nobody seemed to want to use it to augment already working solutions. Just throw everything out and have an LLM do it instead.
I recently saw a Claude skill that used Claude, with no tools, as a spell checker. I wanted to hurl my laptop out to the window.
I swear that so many AI usecases I see are: "I did not have the skill or realize that you can write a program for this obvious logic".
I guess that works if you aren't a programmer or don't want to hire somebody, but then wtf would I pay for your service or product?