Most of the supply chain vulnerabilities I’ve seen published and talked about lately have been trying to do things like exfiltrate keys/secrets from developers, including ci.

So of you’ve got a pr open with the vulnerable package update on it then you’ve goofed. Even potentially without merging if you’ve not got ci set up very securely, which is probably more common than we’d like to admit

<VNT

What do you mean by “make” what do you want it to do that you aren’t getting.

Maybe some existing model via ollama - llama-uncensored?

Do you need to add context with some specific set of data, should it be retrieval based or tuned or cross trained?

Which Al? Bundy? Yankovich?

the same thing a person could do

asking for clarification seems like a reasonable thing to do in a conversation.

A tool is not about to do that because it would feel weird and creepy for it to just take over the conversation.

From experience, that works even on soft furnishings

I hit those many times when signed out just scrolling through the code. The front end must be sending off tonnes of background requests

I think there’s a risk element too

If I fuck up some plumbing in an appliance things are going to get wet, near whatever electrics are used to drive it.

There is a non zero chance someone might get electrocuted if I’m not inclined to be handy and attempt to fix things just with available service manuals and YouTube videos.

People should try, yes. But, you stake the cost of parts against your ability, repairs take time, being cautious takes time.

When someone hasnt already started repairing your shit these are the things that disincline people from starting.

I suppose the smell of acetone would probably put off police dogs, they’re probably drug related enterprises

Maybe www.jitx.com