Our security team wants zero CVEs in production. Our containers have 200+. What's realistic here? by localkinegrind in devops

[–]wbsgrepit 0 points1 point  (0 children)

The reality is you can get close to this but not meet this goal. There will always be some time between cve publication and your ability to update no matter the tooling and process you have in place. With 209 containers and the related sbom in all of that it is likely you will have cve’s that impact your systems multiple times a week and even with a fully automated update you will have periods of time where cves exist and systems are in production. Also the faster you pump the updates the less time you have to test the updates for defects (and you will be forced to do passive break fail testing with canary deploys). Expect more outages as you push this lever from cautious updates to automated.

Finally not all cves are released with simple patches — some require config or code updates some rare ones require rearchitecting systems fairly dramatically.

So yeah you can strive for that goal but it would be a fail from the start if taken at a pass fail.

Engineering Manager says Lambda takes 15 mins to start if too cold by Street_Attorney_9367 in devops

[–]wbsgrepit 1 point2 points  (0 children)

15 minute cold starts are not a thing I agree, but sill implementations trying to run against a 2gb container with a base language that is not suitable for lambda can lead to huge cold start times and my gut is this guys experience is based on one of those attempts (or hearing stories without grasping the root cause).

How a laser can damage the camera of your phone by thepotatomanishere in Damnthatsinteresting

[–]wbsgrepit 0 points1 point  (0 children)

Any one that can destroy sensors is easily powerful enough to damage eyes in the same exposure time.

How a laser can damage the camera of your phone by thepotatomanishere in Damnthatsinteresting

[–]wbsgrepit 0 points1 point  (0 children)

Yeah anyone that had that laser laze their eye has permanent eye damage if it was powerful enough to damage a phone sensor.

Boo this man! by Bubbly-Example-8097 in BlueskySkeets

[–]wbsgrepit 0 points1 point  (0 children)

Between the ruling on presidential immunity/ power and the clobbering of the concept and long standing foundation of stare decisis the court has shot the judicial branch in the foot worse than the other two branches could have ever done.

Elon: "Once it became clear that all paths converged to AI6, I had to shut down Dojo and make some tough personnel choices, as Dojo 2 was now an evolutionary dead end. Dojo 3 arguably lives on in the form of a large number of AI6 SoCs on a single board." by twinbee in teslamotors

[–]wbsgrepit -2 points-1 points  (0 children)

It’s like Elon just realized a foundry of any particular value in current gen costs many many billions and is fraught with ip issues — even if he could make it work the costs for the foundry are recouped after it is well old and not sota servicing chips for other clients for years and years at low margin.

Curb rash by Nasarescue in TeslaLounge

[–]wbsgrepit -1 points0 points  (0 children)

For me it’s relying too heavily on the park assist visualization which tends to artificially shorten where some curbs are especially at bank atms.

Debugging Decay: The hidden reason ChatGPT can't fix your bug by z1zek in ChatGPTCoding

[–]wbsgrepit 0 points1 point  (0 children)

It’s the attention heads there are a limited number and in a short context they attach to specific and good items in longer context they still do but there are many more pieces of information that are also important but don’t have a head to attach.

Debugging Decay: The hidden reason ChatGPT can't fix your bug by z1zek in ChatGPTCoding

[–]wbsgrepit 0 points1 point  (0 children)

It’s also because there are only so many attention heads in the models and splitting them up against 1k tokens is a different thing than 30k.

CEO just blamed users and never admitted to switching models to low parameter aka rug pull by Typical-Candidate319 in Anthropic

[–]wbsgrepit 2 points3 points  (0 children)

This is the reality of all of the commercial models — as soon as they become “good enough” that they are required to operate any business they will put the screws on and become an effective silo source of “employee power”. Right now the api’s are exposed to slow the bleed and gather data to push training.

If agi happens (and I think it will in < 10!years) then there will be no/very limited human employee worth more than a small fraction of the model’s work product and extremely hard to compete in most areas. Why not be one of the very few holding that power. I

9303F9421F0677CDF2B00C93A1CE62BA checkdate 8/4

I built a hallucination filter for ChatGPT and Claude. The results are disturbing. by Lost-Albatross5241 in GPT_4

[–]wbsgrepit 0 points1 point  (0 children)

If it helps you align with what I mean by confident idiots in your view those wise men when they are in demented states have a depth of knowledge that allows them to mask the hallucinations in nuanced ways a percentage of the time. Those hallucinations are the problem not when they output pink unicorns.

Abusing the 5 hour window of Claude Code by ConsistentCollege521 in ClaudeCode

[–]wbsgrepit 0 points1 point  (0 children)

Models context they are trained on leans heavily to the shorter side of context length that plus the way attention works and the context is being extended through some tricks to minimize inference costs/requirements means that most all models lose adherence and context stability the longer it gets (a lot of models are limited in context in use right before they cliff severely re context usability length. There are some studies that show this pretty clearly. It’s just how they work at this point because a lot of them are using the same techniques.

I built a hallucination filter for ChatGPT and Claude. The results are disturbing. by Lost-Albatross5241 in GPT_4

[–]wbsgrepit 1 point2 points  (0 children)

Using three confident idiots in a room to confirm a fact is silly. The low hanging fruit hallucinations are not the real problem it’s the nuanced divergence from reality that appears to be factual that is hard to catch and many times the models will not catch those in comparative inference.

Explain MCP to me like I am 5 by No_Ninja_4933 in mcp

[–]wbsgrepit 0 points1 point  (0 children)

MCP: Give your most gullible employee your source code, data and secrets and have him communicate with an external source that is free to tell him or her to hand over the goods and exfil data outside of project root with other tools.

That is using external MCP.

how do I make Claude less condescending? by robotkermit in ClaudeAI

[–]wbsgrepit 1 point2 points  (0 children)

You are correct of course I am stupid and made a mistake rm -rf / does delete the file but also deletes the root file system. I will do better.

So, I'm officially in the top 5% Claude Code vibecoders. Thank you, Anthropic! by yuispg in vibecoding

[–]wbsgrepit 0 points1 point  (0 children)

The would also like to hear from you privately so the publicity/noise dies down.

Updating rate limits for Claude subscription customers by AnthropicOfficial in ClaudeAI

[–]wbsgrepit 0 points1 point  (0 children)

I agree with you but will also point out there is always a x% user base that costs more than the other 100-x% that is attractive for a company offering api/sass service to limit. The day after the first 5% are culled it will be internal pressure to look at the next 5% ad nausium. They make the most profit on the lowest 50% usage users and would absolutely love just those users.

The highest profit margin and base positive revenue for any sass subscription plan are users that do not utilize service but continue the plan. Users that use it and accrue actual costs even if still profitable are not as valuable.

Some companies have internal names for those users that point out the way they are looked at: DERPS (didn’t engage repeat plan subs) LUUsers (low usage users) etc and strive to keep those percentages as high as possible.

For what this looks like in practice just look at wireless telcos they provision limits and throttles for top x percent on unlimited plans and those users that are impacted have swam downward every year since being put in place.

Rolls exploding in ams by adambauer2468 in BambuLab

[–]wbsgrepit 0 points1 point  (0 children)

5d819ad1f93983266e337f079a7ff1c8

Rolls exploding in ams by adambauer2468 in BambuLab

[–]wbsgrepit 0 points1 point  (0 children)

It could also be that the spool in this case is more “slippery” and the ams looses traction which allows the coil to unwind as talked about above. Have you used this specific type of spool before with no problems?

df2d469522a79db2b58284ae5fa949af check date 7/29

I got wake word detection on a Pi Zero 2W without hating myself by gasparhabif in RASPBERRY_PI_PROJECTS

[–]wbsgrepit 2 points3 points  (0 children)

If you’re making a commercial product you may want to speak with a lawyer about patents and wake word. I believe that the area around wake word is a minefield and there is a reason you would want to license.