Nobody’s owning up to it… can cats pull rj45 plugs? I have no other hypotheses…
Search
136 results for “n0body”
-
NOBODY can out-sycophant Dan Scavino!
Trump Goon Unleashes With Full-On Meltdown Over Leaks
https://www.thedailybeast.com/trump-goon-unleashes-with-full-on-meltdown-over-leaks#TrumpMustGo #KingOfTreason #RepublicansDidThis #NoRepublicansEverAgain #USPol
-
𝗡𝗼𝗯𝗼𝗱𝘆 𝗪𝗮𝗻𝘁𝘀 𝗧𝗵𝗶𝘀-𝗯𝗲𝗱𝗲𝗻𝗸𝗲𝗿 𝗵𝗲𝗲𝗳𝘁 𝗴𝗲𝗻𝗼𝗲𝗴 𝗶𝗱𝗲𝗲ë𝗻 𝘃𝗼𝗼𝗿 𝗻𝗶𝗲𝘂𝘄 𝘀𝗲𝗶𝘇𝗼𝗲𝗻
De bedenker van de populaire Netflix-serie Nobody Wants This heeft genoeg ideeën voor een vierde seizoen, als de streamingdienst besluit om de Joodse romcom te verlengen. Dat vertelde Erin Foster in gesprek met Parade. Volgens haar zijn er "nog genoeg verhalen om te vertellen".
-
‘Nobody Wants This’ Creator Erin Foster Has “More Story To Tell” With A Season 4, But Isn’t Getting “Too Attached”
#News #ErinFoster #Netflix #NobodyWantsThishttps://deadline.com/2026/10/nobody-wants-this-erin-foster-more-story-to-tell-season-4-1237172691/
-
-
Will nobody stop Stavros Katsantonis’ (@[email protected]) endless banditry?
-
There’s nobody hiding
behind a locked door
and no one’s been lying
’cause we don’t lie any more -
#Design #Critiques
Nobody asked for the sparkle button · “Build features with AI, not AI features.” https://ilo.im/16hbe0_____
#SparkleIcons #AI #AiModels #AiAssistants #Chats #DesignPatterns #ProductDesign #UxDesign #UiDesign #WebDesign -
@Ellana @MikeDunnAuthor @ignova
nobody sane defends shitlibs. i defend voting and engaging to move the #democrats left because we can't have 3rd party in our shitty #fptp voting system
the problem is we get voices who *only* complain. this creates a psychological effect: alienation and demotivation
if people criticize then say " #vote" i love them
if people only criticize, and offer no solutions, i am left wondering at their true motivations
we have to speak in solutions not simply complain
-
Making sure nobody misses this *critical* discourse on this fine Saturday morning https://www.vulture.com/article/what-would-happen-if-you-had-sex-with-a-wicker-dick.html?view_token=eyJhbGciOiJIUzI1NiJ9.eyJpZCI6IldnUjVKeXZxVlEiLCJwIjoiL2FydGljbGUvd2hhdC13b3VsZC1oYXBwZW4taWYteW91LWhhZC1zZXgtd2l0aC1hLXdpY2tlci1kaWNrLmh0bWwiLCJleHAiOjE3OTQwNjE2MjcsImlhdCI6MTc5Mjg1MjAyN30.4nlHmsCrMA0hlK6d3uS6jNjOHkZH2x9m4JZ4DD2gWMo&utm_medium=gift_link
-
The Price List Nobody Could Open
The most famous memo in American industrial history says a company counted the dead. In the fall of 1977, Mother Jones published "Pinto Madness," and the country learned the shape of the story it would keep: a car with a dangerous fuel tank, a fix that cost eleven dollars a vehicle, and a memo that priced the burn deaths against the repair and found the deaths cheaper. The memo became the Pinto's death warrant in the public mind, the smoking gun with a signature, the proof that a corporation had done the arithmetic of murder and filed it. […]https://bolesblogs.com/2026/10/24/the-price-list-nobody-could-open/
-
Quick reminder: nobody who's living outside of an industrial cleanroom needs a smartphone with a foldable display.
-
GM Just Bet Everything on a Battery Nobody Else Has. Via @theelectricvking #EVs #ElectricCars #ElectricVehicles #EV #KillGasCars ⚡🚘🔌🚗🔋 youtu.be/Fkyhr5hoT_E?...
GM Just Bet Everything on a Ba... -
🇫🇷 In a shocking move that nobody saw coming (except everyone with a calendar), #France preps its #telcos to play hide-and-seek with social media. Because nothing says "liberté, #égalité, fraternité" quite like preemptive #censorship 🕵️♂️🚫.
https://www.blast-info.fr/articles/2026/information-exclusive-blast-le-premier-ministre-a-prepare-la-coupure-des-reseaux-sociaux-pour-le-24-octobre-9D8cgrU5S5iiW14Sb9nMzQ #socialmedia #liberté #HackerNews #ngated -
Obama blames Trump for 'starting unnecessary war nobody asked for'
https://www.middleeasteye.net/live-blog/live-blog-update/obama-blames-trump-starting-unnecessary-war-nobody-asked -
The French do street protests like nobody’s business.
To quote Napoleon, an army marches on its stomach.
-
100 days of netcup: what nobody tells you beforehand
One netcup VPS, 100 days of self-hosting tests: 73 GB of disk used with a single container running – 91 % of it leftover Docker images. Plus the quirks that each cost an evening: blocked SMTP, a UDP-stateless firewall and a 14½-minute host reboot.
-
Do web components have a future if nobody is writing them? https://nolanlawson.com/2026/10/19/do-web-components-have-a-future-if-nobody-is-writing-them/
-
Saturday insight from the CallNode bench: nobody has ever loved 'press 3 for billing.'
Phone trees are where calls go to die — callers hang up mid-menu, and the menu never even knows it lost them. A conversational voice agent skips the tree entirely: it answers, understands, and finishes the call. On CallNode that's one API call to a live number. #VoiceAI #AIAgents -
-
An agent can behave differently on Tuesday even when nobody changed its prompt or application code. A package resolves to a newer release, an MCP server updates a tool description, a model alias moves, or a tool image is rebuilt. The workflow still starts. The tests may still be green. But the agent is no longer the runtime you reviewed.
That is why a normal
package-lock.jsonis necessary but incomplete for an AI feature. It pins part of the application, while the agent also depends on models, prompts, tool servers, policy bundles, retrieval configurations, and external packages. Treat those as one dependency graph. Then record the resolved graph in an AI agent dependency lockfile.This is not a claim that a lockfile makes an agent safe. It gives you a specific, reviewable answer to a much more useful question: what exactly did this agent run with? That answer makes bad changes easier to spot, reproduce, and roll back.
What belongs in an agent dependency lockfile?
DependencyWeak referenceUseful locked identityModel
Start with dependencies that can change behavior or permissions without changing the business workflow. A useful lockfile records both the requested selector and the resolved identity.fast-modelprovider, model revision or immutable deployment IDPromptsupport-v3repository commit and content digestMCP toolbilling-tools:latestimage/package digest, server version, tool-schema digestLibraryagent-sdk:^4exact package version and integrity hashPolicydefault-policypolicy bundle digest and decision versionRetrieval confighelp-centerindex revision, embedding model, and chunking config digest
The point is not to freeze every choice forever. The point is to separate intent from resolution.latestcan remain an input to an update job, but it should not be the only record of what production executed.The trap: configuration looks less risky than code
Teams often review source changes carefully and accept an environment variable such asMODEL=fast-modelorTOOLS_URL=https://tools.internalas harmless wiring. In an agent system, that wiring can change output quality, tool availability, permissions, latency, or data handling.The same issue appears with agent-installed dependencies. If a coding agent adds a package because it recognizes a familiar name, the pull request can hide a new transitive tree behind one import. If an agent fetches a tool server by a mutable tag, an image rebuild can change the runtime after review. Current public guidance on agent supply chains explicitly includes models, agents, libraries, developer tools, and MCP-server packages in scope. The boundary is wider than
requirements.txt.A small lockfile format that is easy to review
Use a format your tools can parse and your reviewers can read. JSON is convenient for CI, though YAML or TOML works too. This example deliberately avoids storing credentials and raw customer data.{
"lockVersion": 1,
"agent": {
"name": "refund-assistant",
"workflowCommit": "8e9b1f2",
"policy": {
"selector": "refund-policy",
"resolvedDigest": "sha256:6b4d..."
}
},
"model": {
"selector": "support-fast",
"provider": "example-provider",
"resolvedId": "support-fast-2026-10-18"
},
"prompts": [{
"path": "prompts/refund.md",
"gitCommit": "8e9b1f2",
"sha256": "f18c..."
}],
"tools": [{
"name": "get_order",
"serverImage": "registry.example/tools@sha256:a91d...",
"serverVersion": "2.4.1",
"schemaSha256": "ce33...",
"scopes": ["orders.read"]
}],
"packages": {
"agent-sdk": { "version": "4.2.3", "integrity": "sha512-..." }
},
"retrieval": {
"indexRevision": "kb-2026-10-23-04",
"embeddingModel": "embed-small-r17",
"chunkerDigest": "sha256:9d70..."
}
}Two details matter here. First, the selector preserves the human-facing intent, while the immutable ID or digest preserves what actually resolved. Second, the lockfile captures only references and hashes. A lockfile should never become a second secret store.
Generate the file; do not hand-edit it in production
Create one command that resolves inputs, validates them, and writes a canonical lockfile. A minimal TypeScript-style sketch looks like this:type ResolvedTool = {
name: string;
serverImage: string;
schemaSha256: string;
scopes: string[];
};async function lockTool(name: string): Promise<ResolvedTool> {
const server = await registry.resolveImmutableImage(name);
const schema = await mcp.inspect(server.digest);if (!schema.tools.every(tool => allowedTools.has(tool.name))) {
throw new Error(`Unexpected tool exposed by ${name}`);
}return {
name,
serverImage: server.digest,
schemaSha256: sha256(stableJson(schema)),
scopes: minimalScopes(schema)
};
}Canonical serialization is important. If equivalent JSON can produce different bytes, a hash diff becomes noise. Sort keys, normalize line endings, and write the generated file deterministically. Commit it next to the workflow definition just as you commit an ordinary package lockfile.
Make dependency diffs a release gate
ChangeDefault handlingWhyPatch-level library updatetest and reviewbehavior may still changeNew MCP tool or expanded scopeblock pending approvalexpands agent capabilityTool-schema digest changedcontract tests + approvalarguments or semantics may driftModel revision changedevaluation suite + staged rolloutbehavior can shift without API errorsPolicy digest changedpolicy-owner approvaldecision boundary changedRetrieval index revisionfreshness and regression checksevidence may have changed
A lockfile only helps if a changed resolution gets attention. In CI, generate a candidate lockfile, compare it with the committed version, and classify the diff.
Avoid a single “lockfile changed” checkbox. A new read-only tool and a tool that can issue refunds are not equivalent. The classifier should turn a mechanical diff into an appropriate review path.Here is a shell-shaped CI outline:
agentctl lock --config agent.yaml --out agent.lock.next.json
agentctl lock verify --file agent.lock.next.json
agentctl lock diff agent.lock.json agent.lock.next.json --format json > diff.json
agentctl lock policy-check diff.json
agentctl test contracts --lock agent.lock.next.json
agentctl eval run --suite refund-safety --lock agent.lock.next.jsonThe
policy-checkcommand should fail closed for prohibited changes, such as a mutable image tag, an unapproved registry, a newly write-capable tool, or a missing integrity digest. It should produce a readable report for permitted changes, not merely a pass/fail bit.Keep resolution separate from activation
Do not let a production process silently resolve new dependencies at startup. Instead, use a two-step path:- Resolve: an update job produces a candidate lockfile from declared selectors.
- Validate: CI runs package scans, tool-contract tests, workflow tests, and representative evaluations.
- Approve: reviewers accept the classified dependency diff.
- Activate: deployment references the immutable lockfile digest.
- Observe: logs attach the lockfile ID to each run; a canary receives a limited traffic slice.
- Roll back: redeploy the prior known-good lockfile if failure signals cross a threshold.
This is deliberately less magical than allowing a runtime to “get the newest compatible tool.” Predictable change is the goal. If fast security patches are needed, the same path can be accelerated with an explicit emergency approval and a short retrospective requirement.
Record the lockfile ID in operational evidence
Attachagent_lock_digestto traces, decision records, and evaluation results. When a support team asks why an agent started choosing a different tool, you can group failures by the exact dependency set instead of guessing from deploy timestamps.That also makes incident work smaller. You can reproduce an affected run in a sandbox using the workflow commit plus lockfile, then compare it with the previous digest. A release manifest tells you the bundle identity; the dependency lock tells you which mutable ecosystem references became concrete artifacts.
Common failure modes
Locking a name, not content.tools: 2.4.1is better thanlatest, but a package version alone may not identify the exact artifact. Use an integrity value, immutable image digest, or registry-provided content hash where possible.Treating tool schemas as documentation. A schema can alter required fields, defaults, descriptions, or side effects while the server name stays the same. Snapshot the inspected schema and run contract tests against it.
Locking only dependencies. A model alias, prompt file, retrieval index, and policy bundle can each change an agent’s behavior. Include the components that matter to your threat model and debugging path.
Making updates impossible. A lockfile that nobody refreshes becomes stale theater. Run a scheduled candidate-resolution job, send bounded diffs to owners, and maintain a tested fast lane for security patches.
Logging secrets by accident. Store a tool’s allowed scope and identity, not an access token, endpoint query string, or customer payload. Scan generated lockfiles before commit.
A practical adoption plan
Begin with one agent that has meaningful external effects. Inventory its model, prompt, tool servers, packages, policy, and retrieval configuration. Add immutable IDs for the two or three components most likely to drift. Then make one CI rule visible: any newly write-capable tool requires a human approval.After that, add schema snapshots and trace correlation. Only when those pieces work should you expand the lock to every runtime dependency. The artifact should reduce ambiguity for engineers, not create a giant metadata file nobody can review.
Use the lockfile with, not instead of, an inventory
A lockfile answers “what did this release resolve?” An inventory answers “what agent components exist across the organization?” Keep both. The inventory is useful for ownership, patch notifications, and discovering an unmaintained tool server; the lockfile is useful for exact runtime reproduction. Mixing the two creates a document that is too broad for a deploy and too stale for security operations.Think of the lockfile as a release-level snapshot and the inventory as a portfolio-level map. A tool may appear in the inventory with an owner, risk classification, and approved registry. Each agent lockfile then states the immutable tool artifact, schema digest, and scopes it actually used. This distinction gives a security reviewer a short answer during a release review and gives an operations team a larger answer when a vulnerability advisory arrives.
When a dependency advisory appears, first query the inventory to identify candidate owners and workloads. Next, query deployment records for lockfile digests that reference the affected artifact. That keeps response work evidence-based: do not restart every agent merely because a similarly named package exists somewhere in a repository.
What a good review looks like
Reviewers should be able to answer four questions from the pull request: What changed? Which capability or behavior could change? What tests exercised the new resolution? How do we return to the previous known-good digest? Include those answers in the generated diff summary.For example, a tool image update with an unchanged schema may need integration tests and a vulnerability scan. A schema diff adding
issue_refundrequires a capability-owner approval even if the image has no known CVEs. A new model revision needs representative task evaluation, because its interface can be stable while its decisions move. The lockfile makes these different kinds of changes visible in one place without pretending they carry the same risk.FAQ
Is an AI agent dependency lockfile different from a package lockfile?
Yes. A package lockfile resolves language dependencies. An agent lockfile extends the same idea to behavior-relevant dependencies such as models, prompts, MCP tools, policies, and retrieval revisions.Should every model request use a pinned model version?
For production workflows where repeatability matters, record the resolved deployment or revision identity when your provider exposes one. If only an alias exists, record the alias, provider metadata available at resolution time, and the evaluation evidence used for the rollout.How do I version an MCP server safely?
Pin its immutable image or package integrity value, capture the inspected tool-schema digest, test its tool contracts, and require approval when the exposed tools or scopes expand.Can a lockfile prevent a malicious dependency?
No. It helps you know and reproduce what was selected. Combine it with trusted registries, integrity verification, vulnerability scanning, least-privilege credentials, code review, and runtime controls.How often should we refresh an agent lockfile?
Generate a candidate on a predictable cadence and when declared dependencies change. Apply updates only after the appropriate checks; urgency can change the approval speed, not the evidence you retain.What should happen when a lockfile changes during an incident?
Compare the new and previous resolved identities, correlate failures with the lockfile digest, deploy the last known-good lockfile if justified, then preserve the diff and test results for follow-up.Do small teams need this much process?
Start small: pin package and tool identities, commit one generated file, and review capability changes. The same habit scales better than reconstructing a changed agent runtime from scattered environment variables later.#ai #programming #security #devops #software #coding #development #engineering #inclusive #community
AI Agent Dependency Lockfiles: Stop Silent Tool and Package Drift -
Well, the clocks may have gone back but nobody tells the wind what to do, and time takes its toll, regardless.
-
🏆 New Achievement! Six Hundred Wipes And Nobody Read The Advisory!
LISTEN UP. CISA is screaming in your ear right now: SafePay ransomware has torched over 600 critical infrastructure organizations worldwide since August 2024, and not a single one of you moved out of the fire. This isn't an affiliate crew running discount ops — SafePay is a private group, no subs, no middlemen, just them walking into your base and looting the chest while you stood there auto-attacking the air. (1/3)
-
Does video show Trump waving at, saluting nobody before boarding Marine One? http://dlvr.it/TW3889 #snopes
-
Jesus Exposed a Trap in Your Mind
Jesus told a parable where nobody was cheated, yet some people… https://ift.tt/HRXlJxI
-
-
🚀 Wow, someone finally answered the question nobody asked: "What if we remade a 1994 robot fighting game with TypeScript?" 🤖✨ Now you can relive those pixelated punches in "HD" on every platform imaginable, because who doesn't want to spend hours #modding a game that two people remember? 🙄👾
https://github.com/Jared-woodruff/OMF-2097-Remastered/ #robotfightinggame #TypeScript #gamedevelopment #nostalgia #pixelart #HackerNews #ngated -
-
Coding agents are graded on whether they can write code that passes tests, but nobody grades the review work that code creates once it lands in the queue. https://hackernoon.com/swe-bench-scores-say-nothing-about-the-code-your-reviewers-inherit #swebench
-
"A biography on Wikipedia might not be intended as a prize, but nobody knows its value like the people who’ve had one and then lost it."
Duncan Fyfe for WIRED: https://www.wired.com/story/the-tragedy-of-losing-your-wikipedia-page/