1000 results for “it_is_soup_time”
I finally finished my writeup about my bikepacking trip! Here it is!
Boston to Bar Harbor: A 500km Bike Tour
#bikepacking #cycling #BikeTooter #bike #BikeTour #Boston #BarHarbor #Maine #NewEngland
https://magiklog.com/posts/boston-to-bar-harbor-bikepacking/
Did you get what you want?
Do you know what it is? Do you care?
Is he better than me?
Was it your place or his? Who was there?
CF Signals: TESINOS – VS 001 [Tlaloc Records]
Tlaloc Records is one of those Mexican labels we have proudly followed for a long time, and with good reason: its selection of artists is as consistent as its sound is unmistakable. Every release that comes out under that name arrives with a clear intention and a character of its own. It is no coincidence that they are on our list of favorites: it is a merit they have earned release after release. Now they return with their next release of the year and, as always, they know exactly whom to invite.
https://clubfuries.com.mx/2026/04/07/cfp-tesino-glomizer-tlr159/
From Spain, TESISNOS returns to the label, this time to present VS 001, an EP of just two abrasive tracks, just like the previous time. Volcanic lava in full eruption, seeping across the dancefloor, amid environments that seem warlike and apocalyptic. It is a constant and transversal tension, one that positions the sound at the very top of the speakers.
https://soundcloud.com/clubfuriess/cfs-tesinos-vs-001-tlr066
A climax that arrives inevitably, among wars over time, and anxious emotions that the sound channels through latent, effervescent, and demonic rhythms. Labyrinths that emerge amid already-initiated paths, and deep immersions.
Label: Tlaloc Records
Artist: TESINOS
Title: VS 001 EP
Catalog: TLR166
Release Date: October, 2026
Support & Buy: Bandcamp
Tracklist
1. VS 001 06:05
2. Ganico 05:40
TESINOS
SoundCloud | Instagram | Threads
Tlaloc Records
SoundCloud | Instagram | Facebook | Bandcamp | Linktree
Club Furies
Website | SoundCloud | Instagram | Threads | TikTok | Facebook | Bandcamp | Linktree
#AmbientTechno #AtmosphericTechno #CFPremiere #clubFuries #ClubFuriesPremiere #DroneTechno #Electrónica #Electronic #Electronica #ExperimentalTechno #industrialTechno #Mexico #Premiere #premiereCF #PremiereClubFuries #Spain #techno #Tesinos #TlalocRecords #VS001 #VS001EP
14. Dependency injection is a useful coding pattern for being clear about what your dependencies are and where they come from. (Have objects, methods, and so on receive their dependencies as parameters rather than instantiating new objects themselves.) This does make API signatures more complex, so it is a trade-off. Ending up with a method that needs 10 parameters for all its dependencies is good sign your code is doing too much, anyway. See https://www.martinfowler.com/articles/injection.html by Martin Fowler.
"In a decaying society, art, if it is truthful, must also reflect decay. And unless it wants to break faith with its social function, art must show the world as changeable. And help to change it."
- Ernst Fischer
capitalism 5. 12x15''. found object. adam sturch
Major review of Leicester hospital parking launched amid claims of four-year wait for staff permits
Frontline worker claims it is ‘only a matter of time before someone is assaulted’ A major review will…
#NewsBeep #News #Healthcare #Employment #GlenfieldHospital #Health #healthcare #LeicesterHospitals #LeicesterRoyalInfirmary #NHS #UK #UnitedKingdom
https://www.newsbeep.com/uk/812788/
Some tunes remind me 8 Bit Brothers (and maybe Tub Ring), and it is ok.
Henge - Brains
https://youtu.be/Vs9pvPSoQvg?si=LdEKObJ1UxCo8ZFF
Minnesota Vikings News and Links: There Are No Easy Games!
I think it is a big game this week. They all are really. The Colts are going to…
#NFL #IndianapolisColts #Indianapolis #Colts #Football #MinnesotaVikingsdiscussion #OpenThreads
https://www.rawchili.com/nfl/1036001/
If you care how your music sounds, Qobuz is worth a look. Founded in Paris in 2007, it streams Hi-Res audio up to 24-bit and 192kHz, has no free ad-supported tier, and says it is the first platform with its average payout per stream (about $0.0187 in the year to March 2024) validated by an independent audit. https://choosingeurope.eu/2026/09/22/qobuz-%f0%9f%87%ab%f0%9f%87%b7-france/
#Qobuz #Music #HiResAudio #Europe
Hermes Geta Tote Handbags
Hermes' unpopular Geta Tote Handbags, Hermes' clog bag is a popular niche bag type, From the perspective of fashion sense, cost-effectiveness, and compatibility, it is all good, With a hint of artistic atmosphere, Fang Fang's bag is very eye-catching, Size 20 * 14, item number 31139,
https://guestcn.com/product/hermes-geta-tote-handbags/?utm_source=mastodon&utm_medium=jetpack_social
Age pensioners say system punishes them for wanting to keep working
As Australia’s population ages, it is expected more people will want to continue working beyond retirement age, whether…
#NewsBeep #News #Personalfinance #agedpension #AustralianChamberofCommerceandIndustry #Business #Centrelink #CouncilontheAgeing #federalgovernment #Finance #olderaustralians #PersonalFinance #PeterGibney #ServicesAustralia #UK #UnitedKingdom #Work
https://www.newsbeep.com/uk/814891/
Age pensioners say system punishes them for wanting to keep working
As Australia’s population ages, it is expected more people wil…
#NewsBeep #News #Personalfinance #Aged #agedpension #AustralianChamberofCommerceandIndustry #Benefits #Brisbane #Business #CA #Canada #centrelink #CouncilontheAgeing #Drake's #federalgovernment #Finance #NewZealand #olderaustralians #PersonalFinance #PeterGibney #Qld #Queensland #ServicesAustralia #Supermarket #teacher #work
https://www.newsbeep.com/ca/947352/
Age pensioners say system punishes them for wanting to keep working
As Australia’s population ages, it is expected more people will want to continue working beyond retirement age, whether…
#Australia #‘aged #agedpension #AU #AustralianChamberofCommerceandIndustry #Austrlia #benefits #Brisbane #centrelink #CouncilontheAgeing #Drake's #federalgovernment #NewZealand #olderaustralians #PeterGibney #QLD #Queensland #servicesaustralia #supermarket #teacher #work
https://www.europesays.com/australia/130202/
RE: https://types.pl/@sainati/117508916402165623
Me watching The Signal Path…
“The operation of this terraherrz mixer is obvious….”
The fuck it is.
I prefer water at room temperature. Not for alleged health reasons — it’s just how I like it. It is my second favorite way to drink water.
My favorite way to drink water is hot and passed through ground coffee beans.
Hmmm...
I do wish I could answer with certainty without looking it up what the value of (equalp 123.456 #C(123.456 0.0)) is...
I only _think_ it is true; not good enough.
I'm impressed by what the #AI does but also WHY?!?!?
I feel like it lost completely track of the task and instead of just doing it it is now trying to write some nix code to do the task...
RE: https://mastodon.social/@X_net/117466669603712368
📢 This Thursday!
#4DConference is back
When power grows obscenely large, mocking it is a way to bring it back down to human size — and take action.
📅 29/10 · Barcelona, as part of #MozFest
🎟️ Free entry with registration: https://4d.cat/en/conference/
Meet our speakers 🎙️✨
Women’s Ballon d’Or 2026: Will anyone stop Alexia Putellas winning?
While Putellas is now tormenting Women’s Super League defences in the blue of London City, it is another…
#Football #Soccer #News
https://www.europesays.com/football/77885/
Death victorious by Augusto Roma, 1915. He is wearing a stylish shroud decorated with art deco owls (or at least they look deco to me, although it is a bit early for the movement).
#OwlishMonday #owl #31DaysOfHalloween #Spooktober #artdeco
The Breath Before the Sentence: Block’s Dessa
The first thing you notice is the breath. Not a word, not a greeting—just the small, involuntary intake of air before a sentence, the sound a person makes when they are about to speak and haven't quite decided what to say. It is a sound so ordinary it is almost invisible in human conversation, and it is precisely the sound that conventional voice AI has spent years erasing. But Dessa, the speech model unveiled by Jack Dorsey's Block in October 2026, begins with the breath, and in that […]https://balakrishnantr.wordpress.com/2026/10/26/the-breath-before-the-sentence-blocks-dessa/
An agent that goes quiet for ten minutes does not feel autonomous. It feels broken. A spinner and a made-up “82% complete” label are not much better: they encourage users to trust a number your system cannot justify.
The fix is not to stream the model's hidden reasoning. It is to publish a small, evidence-backed account of the work: what phase the run is in, the last verified milestone, whether it needs a person, and what will happen next. This article shows how to build that contract for long-running, tool-using AI agents.
The progress problem is really a trust problem
Users ask three practical questions while an agent runs:
A token stream answers none of these reliably. It can continue while a tool is stuck, and it can stop even though a durable workflow will resume later. Likewise, an LLM-generated status such as “almost finished” is a prediction, not evidence.
Treat status as a product contract. The user-facing timeline should be derived from workflow events your system can verify: a job was accepted, a connector returned records, validation passed, an approval is waiting, or a final artifact was stored. The model may suggest a label, but it should not be the source of truth for state.
This distinction also protects privacy. A useful update is “Checked 42 invoices; 3 need review,” not a transcript of the agent's scratch work, retrieved customer text, or chain of thought.
Start with a state machine, not a progress bar
Long-running agent work has more states than running and failed. Model the states explicitly and make transitions durable.
queuedWork is accepted but has not startedrun record createdCancelrunningA worker currently owns the runlease heartbeatStopwaiting_on_toolThe run is awaiting a bounded external calltool request ID and deadlineCancelwaiting_on_userA decision or missing input is requiredapproval or question IDReview / answerretry_scheduledThe system will retry laterretry time and error classCancel / view detailssucceededThe requested result was verified and savedoutput receiptOpen resultfailedThe run cannot continue automaticallyfailure class and last checkpointRetry / contact supportcancelledWork was intentionally stoppedcancellation receiptRestart
Avoid a vague paused state. If the workflow is paused because it needs an address, show waiting_on_user. If it is paused because a vendor rate-limited it, show retry_scheduled. Specific state names let a user decide what to do without reading logs.
Here is a compact TypeScript event shape. It is deliberately about observable work, not hidden reasoning.
type RunEvent = {
runId: string;
sequence: number; // monotonic per run
at: string;
type: "phase_started" | "milestone" | "approval_needed" |
"retry_scheduled" | "completed" | "failed";
phase?: "preparing" | "collecting" | "verifying" | "delivering";
message: string; // reviewed, user-safe copy
evidence?: {
kind: "artifact" | "tool_receipt" | "checkpoint" | "approval";
id: string;
};
action?: { label: string; url: string };
};
Persist these events in the same transaction that changes workflow state, or attach them to an outbox. A UI event that says “report ready” before the report is stored is worse than no event at all.
Publish milestones, not a narrated thought process
Choose milestones at boundaries where the system can prove something changed. Good milestones are stable across model versions and useful if a run resumes tomorrow.
For a document-analysis agent, the timeline might be:
Notice what is absent: “thinking about clause 7” or “I believe this source is probably relevant.” Those claims are neither a dependable progress signal nor an appropriate audit record.
Each milestone needs an owner. The workflow engine owns checkpoint messages; the connector owns data-fetch receipts; the policy service owns validation results. If no component can produce evidence for an update, leave it out.
That rule prevents a common failure mode: a chat interface keeps emitting cheerful prose while the actual job stopped moving. Your supervisor should detect stale progress independently of the agent. For example, mark a run stalled internally when its lease heartbeat is fresh but neither a checkpoint nor a tool receipt has advanced within the expected phase window. The user-facing text can then say, “Still working longer than expected; no action needed yet,” or escalate honestly to “This task needs attention.”
Design an honest progress model
Percent complete works only when units of work are known. A migration over 10,000 rows has a denominator. An open-ended research task generally does not.
Use one of these models instead:
318 of 500 files checkedKnown workflowcompleted phaseVerifying findings (3 of 4 phases)Open-ended workelapsed time plus latest verified eventLast verified update: sources indexedApproval flowblocked state and decision impactNeeds approval before sending 3 emailsRetryable external worknext retry and preserved checkpointRetrying connector at 14:05; 18 items saved
Do not convert phase count into a false percentage. Four phases do not necessarily take equal time, and the model can loop inside one phase. If you show an estimate, label it as a range derived from similar completed runs, and hide it when the sample is weak.
function statusCopy(run: Run) {
if (run.status === "waiting_on_user")
return "Your decision is needed before this task can continue.";
if (run.completedUnits != null && run.totalUnits != null)
return `${run.completedUnits} of ${run.totalUnits} items verified`;
return `Last verified update: ${run.latestMilestone.message}`;
}
The word verified matters. It teaches users what the timeline represents and sets a standard your team can test.
Make waiting visible and actionable
The most damaging silence is not a slow model call. It is an agent waiting for a person while the product looks busy.
An approval event should include the decision, the consequence, the safe default, and an expiry rule. Keep the payload concise and reviewable:
{
"type": "approval_needed",
"message": "Three customer records have conflicting addresses.",
"question": "Which address should be used for the renewal notice?",
"options": ["CRM record", "latest support ticket", "skip these records"],
"default": "skip these records",
"expires_at": "2026-10-26T15:00:00Z",
"evidence": { "kind": "approval", "id": "apr_8f2" }
}
Never bury an approval in a scrolling chat. Surface it as a run state, send a notification only when action is required, and ensure a resumed run re-reads the approved decision from durable storage. This pairs well with approval gates, but it solves a different problem: making the wait understandable to the person who initiated the work.
Transport updates without building a fragile realtime system
Start with the simplest transport that fits your product.
status, latest_event, and etag; back off when nothing changes.Last-Event-ID.waiting_on_user are normally worth interrupting someone; routine milestones are not.Regardless of transport, the client must tolerate duplicate and out-of-order events. Use the sequence field, make the event stream append-only, and fetch the authoritative run snapshot after reconnecting. The UI is a projection; the workflow database remains the authority.
Build the API around a durable run record
A small API surface is easier to secure and test than a channel full of ad hoc text.
GET /runs/run_123
{
"status": "waiting_on_user",
"phase": "verifying",
"latest_event_sequence": 17,
"latest_event": {
"message": "42 records verified; 3 need a decision",
"at": "2026-10-26T12:04:12Z"
},
"actions": [{ "kind": "approve", "approval_id": "apr_8f2" }]
}
Keep sensitive tool arguments, raw documents, and internal exception stacks behind a permissioned diagnostics view. The default run page should disclose only the minimum a user needs to understand progress and take the next action.
Test the status contract like an API
Status is part of the user experience, so add tests beyond the happy path:
succeeded without an output receipt.waiting_on_user run always exposes a decision action and cannot spend tools until it resumes.it("does not claim success before output exists", async () => {
await workflow.emit({ type: "completed", evidence: undefined });
expect(await runs.get("run_123")).toMatchObject({ status: "failed" });
});
This is also where observability earns its keep. Measure time to first verified milestone, time spent waiting for users, stale-run recovery rate, and the share of runs that finish with a useful artifact. Avoid treating the number of progress messages as a health metric; a noisy timeline can conceal a poor workflow.
A practical rollout plan
Do not retrofit every agent at once. Start with one workflow where users currently refresh a page or ask support whether a job is stuck.
The result is deliberately less theatrical than a stream of simulated thinking. It is far more useful: people can leave a long-running agent alone, return with context, and intervene exactly when their judgment is needed.
Keep the language stable across releases
Treat visible status copy as part of your API. Changing waiting_on_user from “Needs your decision” to “Paused” may seem cosmetic, yet it can break notification rules, customer runbooks, and accessibility labels. Version the event schema, localize messages at the presentation layer, and keep a small compatibility test suite for every public state. That discipline pays off when new models, tools, and workflow engines arrive: the user still receives the same clear promise about what has happened and what they can do next.
FAQ
Should an AI agent show its chain of thought as progress?
No. Show concise, evidence-backed milestones instead. They are more reliable, safer for sensitive data, and easier for users to act on.
How often should an agent send status updates?
Update on meaningful state changes, verified milestones, and action-required moments. For long silent phases, add a bounded heartbeat that says the job is still owned, not a stream of filler messages.
Is a percentage complete useful for AI agents?
Only when the work has a known denominator, such as files processed or records checked. Otherwise show the phase, elapsed time, and most recent verified milestone.
What is the best state for an agent waiting on a person?
Use a specific waiting_on_user state with the exact question, a safe default, and a resumable approval ID. Do not leave the run labeled running.
Can polling work for long-running AI workflows?
Yes. Polling is simple and reliable for background tasks that update every few seconds or minutes. Use ETags and backoff, then move to SSE or WebSockets only when the interaction requires it.
How do you detect an AI agent that is stuck?
Track worker leases, tool deadlines, and the time since the last verified milestone. A supervisor outside the model should classify stale runs and surface a recovery state.#ai #ux #programming #devops #software #coding #development #engineering #inclusive #community
AI Agent Status Updates: Build Progress Users Can Trust Without Exposing Chain of Thought
In an animation explainer, the decision is whether to write words first or pictures first. I would write them together, beat by beat: one sentence for one visual change, with a pause where the motion needs room. That keeps narration from racing ahead of the image and keeps the image from waiting for words.
What matters when you choose how to pair words with pictures?
These criteria conflict. More on-screen text speeds understanding but splits attention; more pauses slow the pace but let motion land. Choose based on the single idea the viewer must remember.
How do you judge each criterion in an animation explainer?
CriterionA useful checkOrder of ideasRead the script while hiding the storyboard; does each sentence create the next picture?Match with visible objectsPoint to the screen for every noun; if nothing is there, cut or move the sentence.Speed of deliverySpeak the line at normal pace while watching the motion; stop if you finish before the motion ends.On-screen textRemove every on-screen word that repeats the voice; keep labels and numbers the voice skips.Pauses for movementMark a short silence where an object enters, exits, or changes; if the voice fills it, the motion feels rushed.
Order of ideas. A newcomer does not need the conclusion first. If the first sentence names the benefit before the problem exists on screen, the picture has nothing to do. Start with the object or situation the viewer sees, then add the claim. For example, show a cracked pipe before saying that pressure causes leaks; the sentence then explains what the eye has already found.
Match with visible objects. The voice should not describe a thing that appears later. When the sentence names a part, that part should be the part the eye is already on. If the sentence is abstract, give it a concrete visual anchor before it is spoken. A phrase like "the system fails" needs a visible failure, not a diagram of the whole system.
Speed of delivery. Fast speech can sound confident, but it leaves no time for recognition. A line that fits the motion often feels slightly slow on its own. That is usually right, because the viewer is doing two jobs at once. If you feel the urge to speed up, the sentence is probably carrying two ideas.
On-screen text. Text is not a transcript. It works best as a label, a number, or a short phrase that the voice does not repeat. If the viewer reads and listens to the same words, one of them is wasted. A label such as "step two" can guide attention while the voice explains why step two matters.
Pauses for movement. Motion is part of the sentence. A wipe, a build, or a character crossing the frame needs time to register. A pause of a few words, or a breath, lets the picture finish its thought. If the voice fills that space, the motion looks like background decoration.
Which red flags show it is the wrong choice?
One red flag is enough to stop and revise. Fixing it early is cheaper than fixing it after the animation is built.
What should you ask before you commit?
These questions are not a checklist to pass once. They are a way to find the sentence that is doing too much.
Frequently asked questions
Should the script or the storyboard come first?
Neither should be finished first. Start with a rough list of pictures, write one sentence beside each, then revise both. The first draft of an animated video is usually a set of beats, not a polished page of prose. If one side is locked early, the other is forced to serve it. The goal is a shared order, not a winner.
How much on-screen text should an explainer video use?
Use on-screen text for labels, numbers, and short phrases that the voice skips. An explainer video does not need a transcript on screen. If the text and the voice say the same thing, cut one of them. The viewer should not have to choose between reading and listening. Text earns its place when it reduces the number of words the voice must carry.
What if the animation is already finished?
Write the narration to the motion, not to your original idea. Watch the sequence once without sound and note what changes and when. Then write one line for each change. If a sentence has no matching change, it is probably commentary and can be cut. An explainer video script written after the pictures should be shorter than one written before them, because the pictures have already done part of the explaining.
Try this on your next draft: read the script beside a rough storyboard and mark every sentence that has no visible partner. Rewrite those sentences or cut them, then read the whole thing aloud while watching the motion. The goal is not fewer words; it is words that arrive when the picture is ready for them.#animation #video #design #writing #software #coding #development #engineering #inclusive #community
Writing narration for an animation explainer
RE: https://unattributed.cc/2026/10/25/creative-commons-licenses-and-ai/
Today's post is about my disappointment with #CreativeComons response to #AI and the damage it is doing to #OpenCulture and the #OpenWeb. As a supporter of #CC for over a decade, and a #writer for the #OpenWeb, reading their recent documents was quite disheartening.
I am still very much searching for people to follow on Mastodon. My feed is very quiet due to the lack of content to engage with. That said, it is far better than being flooded with AI slop, spam, ads and irrelevant content that I have no interest in. #newbie #community
Continuing to dabble with a Black and White mood on this #SilentSunday...
It seems everyone knows about Bixby Bridge, to the point where the selfie-culture got so silly that parking around it is now banned.
But it's not the only spectacular example of the open-spandrel bridge design that was the go-to for Big Sur spans in the 1930's.
The Big Creek Bridge IMHO is just as pretty, tucked into the rugged coast near San Simeon
#Photography #LandscapePhotography #BlackAndWhite #PacificOcean
So sad to see Arc turn into slop. I used it until AI became too much in Arc, and now it is being sunsetted in favor of "AI browser"?
WIPE WARNING: Rotate credentials and comb your access logs on that third-party learning platform now — if it touched your network, assume it's the weak point.
Reward: You've received the Everest Expedition Badge. It is made of data you no longer have.
#Ransomware #CyberSecurity #InfoSec #PwC #DataBreach #AchievementUnlocked (2/2)
19. DRY (Don’t Repeat Yourself) matters much less in tests than it does in production code. Readability of an individual test file is more important than maintainability (breaking out reusable chunks). That’s because tests are executed and read individually rather than themselves being part of a larger system. Obviously excessive repetition means reusable components can be created for convenience, but it’s much less of a concern than it is for production.