home.social

Search

551 results for “thea”

  1. Gil Durán
    @gilduran.com

    Tucker Carlson is an “old friend” of Peter Thiel puppet JD Vance.

    Carlson’s media company received $15 million from 1789 Capital, a Thiel network VC firm where Trump Jr. is a partner.

    The “conversion” narrative is theater—superficial distancing/dissonance—not disagreement.

    A succession strategy.

    bsky.app/profile/gilduran.com/

    #EU #Democracy #NATO in #Political peril for us still #Darkenlightment #Putinism #GeoPolitics

    10/24

  2. I know it's a controversial take, but I really do think every show that does a run on Broadway should have a proshot released. They're not the same as seeing it live (not necessarily worse) but each performance is different anyways that's kind of the point, so having Another Different Version out there strikes me as all upside.

    I'm big mad the Six proshot was a one day only thing and only in theatres. Blu-rays of all the shows!

  3. "Winter's Orbit" is a #SciFi #Mystery #MMRomance by Everina Maxwell.

    Prince Kiem enjoys the life of a royal, even if some of his more outrageous behavior doesn't please the emperor. When the ruler summons the Prince this time, it's not for another dressing down. It's to tell Kiem that he will be marrying Count Jainan, the recently widowed husband of Kiem's cousin Taam. The marriage is necessary to maintain the fragile alliance between the empire and the vassal planet Thea. Jainan has been raised to do his duty, and that means being a good husband to whichever partner the empire chooses for him, however difficult that may be. Neither of the men knows just how dangerous their new alliance will prove to be.

    michaeljoseph.info/blog/2023/r

  4. 🎃 #Halloween Spooktacular 01 - Creepy Abandoned Hospitals

    💉Kill or cure; these decaying medical facilities are long closed. Asylums, their long corridors with peeling paint and smashed windows. Almost pristine hospitals, with the power still on and beds still made. Silent operating theatres and empty wards.

    📷 Explore #abandoned hospitals - obsidianurbexphotography.com/p

    #AbandonedPlaces #LostPlace #Portfolio #Macabre #Spooky #Haunted

  5. #ClimateCrisis #animals

    "How Chemicals and Climate Change Threaten Fertility Across Species

    Across the globe, a quiet but profound crisis is unfolding in the bodies of humans and wildlife alike. A growing body of research is showing that toxic chemicals and climate change are not only separate threats. They are working together in ways that undermine fertility across species, with implications that reach far beyond individual health. A recent review in NPJ Emerging Contaminants pulls these threads together, highlighting how exposure to synthetic chemicals, many of them endocrine disrupting chemicals, intersects with rising temperatures and other climate impacts to put reproduction at risk.

    The review describes a world where animals, from insects to humans, live in a constant state of simultaneous exposure. Synthetic chemicals are present in air, water, soil, and food. At the same time, climate change is driving higher temperatures, altered rainfall patterns, and more extreme weather. This combined pressure creates a difficult environment for reproduction, one of the most sensitive and essential biological processes. The authors note that these stressors are not rare or isolated. They form the daily backdrop of life for countless species.

    One of the most striking aspects of the research is how similar the effects appear across very different forms of life. Whether looking at fish, reptiles, birds, mammals, or humans, the review reports consistent patterns of harm to eggs and sperm. Fertility can decline, reproductive cycles can shift, and the delicate coordination of hormones that underpins reproduction can falter. These endocrine disrupting chemicals, or EDCs, interfere with normal hormone function and can derail development and reproduction even at very low levels of exposure."

    theanimalrescuesite.com/blogs/

  6. *Manchester dates* for The Crucified Silence – Sunday November 22nd – Irish World Heritage Centre. 6pm.

    “A story anyone can relate to…” — Irish Independent

    Click here to secure your ticket now!

    About

    Following acclaimed performances in Athlone, Castlebar, Ballinrobe and Galway, The Crucified Silence comes to Manchester on Sunday 22nd November at 6pm, bringing a distinctive voice from the West of Ireland to the iconic Irish World Heritage Centre.

    Hilarious, heartbreaking and brimming with dark Irish humour, The Crucified Silence is a compelling one-man play written and performed by acclaimed Irish playwright Mick Donnellan. Set in Ballinrobe, Co. Mayo, the story follows Joe, a local guard who has crossed a line after a volatile altercation with his superintendent. As he drinks his way around town, he conjures vivid, nostalgic images of familiar landmarks and meeting places, including The Bowers walk, Art O’Neill’s Bar and Geoff’s pub. These recollections bring his world to life, drawing audiences into a community shaped by its own rhythms, rituals and relationships.

    Yet beneath the laughter lies a deeply moving story of loneliness, loss, regret and the search for connection. Just as Joe’s sharp wit and comic observations have audiences laughing, glimpses of his troubled past reveal a more vulnerable man struggling to come to terms with the life he has lost. The result is a play that can have you laughing out loud one moment and breaking your heart the next.

    Populated by recognisable Irish characters and brought vividly to life through authentic Irish dialect, cultural nuances and a rich tradition of storytelling, the play offers a compelling glimpse into the humour, warmth and complexities of everyday life in rural Ireland. For those familiar with Irish life, there is much to recognise; for those discovering it for the first time, an opportunity to experience a distinctive culture through characters who feel wonderfully real.

    Book now

    The Venue

    A much-loved hub for Irish culture, arts and community in the North West of England, the Irish World Heritage Centre provides a fitting setting for a play that celebrates Irish storytelling while exploring experiences that transcend borders and backgrounds.

    For Manchester’s Irish community, the evening offers a powerful sense of home, evoking the people, places, humour and shared experiences that connect us to where we come from. It is also a wonderful opportunity to celebrate the strength of Irish theatre and the remarkable stories being created in Ireland and finding audiences beyond its shores.

    Universal Appeal

    Although Joe’s world may be rooted in a small town in Co. Mayo, his struggles are universal. His attempts to make sense of a life shaped by difficult choices, personal loss and fading connections will resonate with anyone, from all cultures and backgrounds, who has ever looked back on their past and wondered how things might have turned out differently.

    With minimal staging and intimate, uncompromising storytelling, the play places audiences face to face with Joe’s inner world, where humour becomes a defence against pain and silence can speak louder than words. Mick Donnellan’s powerful central performance draws audiences towards a devastating climax, balancing theatrical intensity with the feeling of a deeply personal confession.

    All are welcome to join for an evening of big laughs, poignant storytelling, heartbreaking moments and an unforgettable injection of high-quality theatre!

    Spaces limited so be sure to secure your seat as early as possible :)

    About Mick Donnellan and Truman Town

    Mick Donnellan works as a successful Playwright, Novelist and Screenwriter. Film credits include Tiger Raid adapted from Mick’s Play Radio Luxembourg. Optioned by London Film Company Dixon/Baxi/Evans, the script was developed in London and shot in Jordan. Starring Brian Gleeson, Damian Molony and Sofia Boutella, it was accepted into the Tribeca film festival (New York) and was also seen at Cannes and Edinburgh.

    The Irish Premiere was screened at the Galway Film Fleadh and you can watch the Tiger Raid trailer here.

    Mick is the author of six novels:

    The Dark Rooms

    Galway Blues

    El Niño

    Fisherman’s Blues

    The Dead Soup

    The Naked Flame

    Recent Work:

    Mick Donnellan has had two major theatre productions hit the stage in 2025.

    Outlaw Pete premiered at the Town Hall Studio, Galway in April 2025, starring Laura Hutchinson, Brian Cahill, and Carl Jones. Following its debut, the production toured to the Linenhall Arts Centre in Castlebar in May, before returning to Galway for the Galway Fringe Festival in July, where it sold out Kennedy’s Bar on Eyre Square.

    Donnellan’s second new play of 2025, Class of ’57, was produced by Athlone Little Theatre and directed by Caroline Coyle, featuring standout performances from Ellen Ryan, Brian Toolan, and Nino Magilocco.

    In December 2024, his most recent book Galway Blues was published to great acclaim. He received the Mayo Theatre Bursary through Mayo Arts Office in April the same year.

    Prior to that, he was awarded the Agility Award through the Arts Council of Ireland and his play Nally was supported by Westmeath Arts Office.

    In other theatre work, The Crucified Silence (as a short play) was chosen as part of the Scripts Ireland Play festival. After a week of intensive workshops with Playwright Eugene O’Brien, the monologue was directed by Jim Culleton (Fishamble) and performed by Aaron Monaghan. Following this, Mick took part in the Galway Theatre Development Programme, run by Andrew Flynn in conjunction with Galway’s Town Hall Theatre, which resulted in a residency at the Tyrone Guthrie Centre.

    His other plays include Sunday Morning Coming Down, Shortcut to Hallelujah, Gun Metal Grey, and Velvet Revolution.

    He is listed on the Irish theatre institute here: http://irishplayography.com/person.aspx?personid=47564

    About Truman Town:

    Truman Town Theatre exploded on to the theatrical circuit with their Play – Sunday Morning Coming Down. Written and directed by the company’s Artistic Director Mick Donnellan, it immediately sold out the Galway Town Hall Studio for five nights on the first run. Following that, the crew went on tour to Mayo, selling out Lisloughrey Lodge, Cong,The Valkenburg Niteclub, Ballinrobe and the Linenhall in Castlebar. It also enjoyed large audiences on the Main Stage on Galway’s Town Hall and went on a National Tour covering – Glor Ennis, St. John’s Listowel, Cork Arts Theatre and it sold out five nights at The New Theatre, Dublin. It was also performed by DRUID as a public reading during the Galway Arts Festival.

    Truman Town followed this phenomenal success with a second Play – Shortcut to Hallelujah. Again, written and directed by Mick Donnellan, it deals with the curse on the Mayo football team. It sold out the Town Hall Studio, went on tour to Ballinrobe and the Linenhall in Castlebar and then down to St. John’s Theatre, Listowel Co. Kerry where it was requested back to headline Friday night of Listowel Writer’s week.

    Between this, a third drama was produced as part of the Galway Theatre Festival. It was titled Gun Metal Grey.

    Shortcut to Hallelujah returned from Listowel Writer’s Week to perform on the Main Stage Galway for a wildly successful five nights after which Velvet Revolution, the fourth Truman Town production, also written by Mick Donnellan, was premiered in St. John’s Theatre, Listowel. It went on tour to Kilmallock, Kenmare and Waterville, then up to Ballinrobe, on to Galway and ran for ten days as part of the Galway Fringe. Mentioned as a Highlight of the festival by the Irish times, it was subsequently performed in Campbell’s Tavern, Cloghanover, Headford, Electric Picnic and The New Theatre, Temple Bar, Dublin.

    Radio Luxembourg, Mick’s fifth Play, was bought by a London Film Company (Dixon/Baxi/Evans) and has been adapted for the screen. The title for the movie version is “Tiger Raid”. Starring Brian Gleeson, Damian Molony and Sofia Boutella, it was accepted into the Tribeca film festival (New York) and was seen at Cannes and Edinburgh. The Irish Premiere was screened at the Galway Film Fleadh.

    Currently Mick is working on the exciting screen adaptation of Shortcut to Hallelujah with Florence Films. The screenplay is titled Sam and is based around the curse supposedly put on the Mayo Football team as they returned home as All Ireland Champions in 1951.  Drenched in Irish lyricism and modern day dark humour, the script has been met with keen interest by film producers and actors throughout the industry.

    Between writing projects, Mick has enjoyed roles as a lecturer in writing at University of Ireland and TUS Athlone.

    *

    Read more on www.mickdonnellan.com

    #books #music #news #Poetry #writing
  7. ‘… the CIA’s operations are now “much more aggressive” than they were during the Biden administration.

    ‘As the ODNI has declined in size and relevance, the CIA, with Ratcliffe in charge, has reclaimed its traditional role at the center of the intelligence community.

    'And his relationship with Trump and low-profile manner have probably helped keep the president from attacking the agency.

    ‘The director was using a line of communication informally known as “the channel,” which allows Russian and American spies to talk candidly, away from the scrutiny of the press or the grandstanding of politicians. Putin, an ex-KGB officer, would understand that Ratcliffe had come not as a diplomatic envoy but as a fellow spy, with a message he felt was important for Putin to hear.

    ‘Broadly speaking, current and former officers told me, morale is highest in the operations directorate, among the officers who conduct the espionage that Ratcliffe wants to emphasize. Personnel in the Special Activities Center, which conducts covert and paramilitary activities, are particularly satisfied, recently retired officers told me, perhaps because they’re so busy, and not only in Ukraine.

    ‘Analysts strive for objectivity. But intelligence as a practice is not truly apolitical, because it’s an instrument of presidential power. The most successful CIA directors know how to tell their bosses the truth while also serving their interests’.
    theatlantic.com/national-secur

  8. A Look Back at X-Men 2099 #24 (1995)

    Disclaimer: This is my original work with details sourced from reading the comic book and doing personal research. Anyone who wants to use this article, in part or in whole, needs to secure first my permission and agree to cite me as the source and author. Let it be known that any unauthorized use of this article will constrain the author to pursue the remedies under R.A. No. 8293, the Revised Penal Code, and/or all applicable legal actions under the laws of the Philippines.

    Welcome back, superhero enthusiasts, 1990s culture enthusiasts, X-Men fans and comic book collectors! Today we revisit the Marvel Comics shared universe through one of the many tales of the X-Men 2099 monthly series.

    One of the things I enjoyed the most about the X-Men 2099 series was its expansion of the 2099 universe lore as well as the portrayal of uncertainty that mutants deal with in the more desolate parts of America (far away from Spider-Man 2099 and Punisher 2099). Along the way, the futuristic X-Men themselves were really torn down by a series of unfortunate events that includes the departure of their founder and leader Xi’an (eventually Controller X of the Theater of Pain). With the team members separated by circumstances, they were given their own tales and character development periods.

    With those details laid down, here is a look back at X-Men 2099 #24, published by Marvel Comics in 1995 with a story written by John Francis Moore and drawn by Ron Lim.

    The cover.

    Early story

    The story begins in southern California where the Slaughterhouse gets shaken by the force of a gamma bomb that detonated far away. Inside the facility, Quiver and Sham struggle as they sneak carefully. They intend to escape even though the odds are against them.

    Nearby, the demonic Theater of Pain leader Brimstone Love strikes Junkpile (now with SHIELD serving the new President Doom 2099) hard and seriously damages him. With Junkpile down, the evil leader believes that Doom’s best is a failure and the Theater of Pain has nothing to fear from him. Brimstone Love issues an order to have Junkpile disposed.

    Several feet below the ground, Skullfire and Luna find themselves contained after getting captured. For Luna, Xi’an is a lost cause and she prefers to find Shakti and escape. Skullfire, however, insists on pursuing Xi’an even though their situation looks very hopeless. As the two try to escape, they end up facing the muses of the Theater of Pain’s bloodsport arenas…Euphoria, Felicity and Bliss. Luna was previously one of them…

    Quality

    Shakti represents the remaining X-Men while her former superior Xi’an has fully sided with the evil Theater of Pain as Controller X.

    Being the comic book that immediately precedes issue #25, there is a lot of creative stuff here that X-Men 2099 fans will enjoy. The Moore-Lim duo took their time in setting up the eventual restoration of the futuristic X-Men as a team while carefully telling the dangerous events they will face with the Theater of Pain standing in their way.

    Fans can find small moments that can be enjoyable or even intriguing to discover such as Luna facing off with her Theater of Pain “sisters” of long ago, the reuniting of Bloodhawk with Meanstreak and Krystalin followed by the justification behind their decision to get involved, and more. What I find very compelling to read is Shakti’s interaction with Controller X (Xi’an behind the mask obsessively serving the Theater of Pain) and the rising danger the Theater’s operation is brewing. There is richness in the dialogue between Shakti and Xi’an, and the symbolic division between them – Shakti representing the X-Men and their former leader Xi’an now serving the evil ones – is really powerful to see.

    The storytelling as a whole has a lot of depth behind it, and the build-up of the events is undeniably powerful. As the story progressed, the tension also grew stronger and you can feel the danger that awaits the futuristic X-Men.

    Conclusion

    Bloodhawk is back with Meanstreak and Krystalin.

    X-Men 2099 #24 (1995) succeeds a lot on setting-up the big conflict of issue #25 and it also sets in motion the eventual reuniting of the X-Men. Along the way, there are small details here and there that will compel you to revisit previous X-Men 2099 issues. Brimstone Love’s evil was emphasized more here and Controller X/Xi’an’s determination to serve him and make a lot of people suffer under the Theater’s operation added a lot of tension to the plot. Consider this a very important read before reading X-Men 2099 #25.

    Overall, X-Men 2099 #24 (1995) is recommended.

    +++++

    Thank you for reading. If you find this article engaging, please click the like button below and also please consider sharing this article to others. If you are looking for a copywriter to create content for your special project or business, check out my services and my portfolio. If you want to support my website, please consider making a donation. Feel free to contact me with a private message. Also please feel free to visit my Facebook page Author Carlo Carrasco and follow me on Twitter at @HavenorFantasy as well as on Tumblr at https://carlocarrasco.tumblr.com/ and on Instagram at https://www.instagram.com/authorcarlocarrasco/.

    #1990s #2099 #2099Universe #America #amusement #Bloodhawk #California #CarloCarrasco #ChatGPT #comic #comicBook #ComicBookReview #comicBooks #comicReview #comics #comicsBlog #comicsReview #Communist #CommunistCalifornia #CommunistCaliforniaCommiefornia #Doom2099 #Fediverse #fun #geek #Google #GoogleSearch #illustratedLiterature #Islamist #IslamoLeft #IslamoLeftist #JohnFrancisMoore #Krystalin #LGBTQ #LGBTQIA #literature #Marvel #Marvel2099 #MarvelComics #MarvelEntertainment #Marxist #Mastodon #Meanstreak #nostalgia #Punisher2099 #retroReview #Retrospective #review #Reviews #RonLim #sciFi #scienceFiction #Shakti #Skullfire #socialist #SpiderMan2099 #superhero #superheroes #The1990s #UnitedStatesOfAmericaUSA #USA #woke #WordPress #WordPressCom #XMen #XMen2099 #XMenReview #XiAn
  9. i don't know why people follow me, but I'm here to say The Atlantic reporting about PHP needs to be torn to shreds.

    Surý spends his entire interview dismantling the reporter's presumptions: he says people could get PHP elsewhere or compile it themselves, of course, credits the PHP project for bringing him into the pre-release group, naturally, names Freexian as ready to take over, because why not, and says the day wasn’t stressful!

    Then The Atlantic reporter still tries to gin up "oh no" FUD and hero worship? WTAF. The Atlantic used to be abolitionist, and here it's pumping a slavery model. I wouldn't line my birdcage with what they wrote.

    Surý names exploitation and then the article turns him into the deserving servant and invites the public to tip him! Tipping is slavery. I guess I'll write it up, as I cancel my Atlantic subscription.

    theatlantic.com/technology/202

  10. "Enterprise IT isn't Broken—Its Game Mechanics Are Just Trash": Inside Erkki Laine's Tri-Axial Engine


    Why do smart engineers and expensive AI agents make catastrophic production decisions? Because corporate governance is designed like a terribly balanced strategy game. We sat down with the Finnish architect who recoded the rules using Nash Equilibrium, 3D collision physics, and hardcore RPG logic.

    TURKU, FINLAND — If you read enough enterprise governance documentation, your brain eventually turns into grey SharePoint sludge. It is a joyless world of RACI matrices, annual spreadsheets, and committee meetings where twenty people spend an hour debating a change ticket none of them actually understand.

    Then you open the technical specifications of the Business Impact Governance Framework (BIGF) by Finnish ICT architect Erkki Laine, and something weird happens.

    Suddenly, you aren't reading bureaucratic filler anymore. You are reading about Autonomous Agentic Meshes, Tri-Axial Actuation Boundaries, Hardened Meta-Governance Layers, and Cryptographic Canonical Decision Records.

    Wait a second. Is this an enterprise IT framework, or the patch notes for a hardcore tactical RPG?

    "Honestly, there is very little difference between leading a party through a lethal boss fight in a tactical RPG and keeping a multi-cloud production environment alive at 3 AM," Laine says, leaning back with a coffee mug while three dogs patrol his home office perimeter. "In both cases, if your buffs are fake, your map telemetry is fogged, and your party members are secretly sabotaging each other for loot, you are going to wipe."

    We sat down with Laine to unpack how an obsession with tactical role-playing games, grand strategy, and mathematical game theory led him to build a deterministic runtime engine that is quietly making traditional ITIL bureaucracy obsolete.

    Level 1: Solving the DevOps "Prisoner's Dilemma"


    Viti Magazine: Let's start with human behavior. Why do traditional ITSM and GRC processes fail so miserably in the real world?

    Erkki Laine: Because legacy governance assumes you can fix structural conflicts by writing a politely worded PDF policy and ordering people to "collaborate." Anyone who has ever played a grand strategy game or studied basic Game Theory knows that's delusional.

    Look at a standard IT organization. Developers (Dev) and Security/Governance (Ops/Sec) are trapped in a textbook Prisoner's Dilemma:

    • Dev's optimal selfish move: Push code as fast as possible, understate the risk score on the ticket, and hit sprint velocity targets.
    • Security's optimal selfish move: Stall, interrogate, and demand three weeks of manual CAB reviews to ensure zero personal blame if something breaks.

    Both sides play their dominant selfish strategy, and the organization gets the worst possible collective outcome: miserable lead times, shadow IT, and rubber-stamped risk theater.

    Viti Magazine: And BIGF fixes this without holding a single team-building workshop?

    Laine: Workshops don't change payoff matrices; code does. In BIGF, we replace the political negotiation with a deterministic Policy Gate at the runtime boundary. Security encodes the exact mathematical thresholds into the engine once. Dev knows the exact rules before they even commit code.

    Neither side can bluff, cheat, or play politics. The moment the deployment artifact and telemetry satisfy the mathematical equation, the gate opens in milliseconds. By changing the rules of the board, cooperation automatically becomes the Nash Equilibrium—the only winning move for everyone.

    Level 2: The Tri-Axial Engine (3D Collision Physics for Risk)


    Viti Magazine: People analyzing your v2.3 and v2.4 specifications have pointed out that your "Tri-Axial Actuation Boundary" looks suspiciously like a 3D game engine.

    Laine: (Laughs) Guilty as charged. In a 3D game engine, every object exists on X, Y, and Z coordinates. As long as your character stays inside the playable room, you can run, jump, and cast spells freely. The moment you try to walk through a solid wall or step off the edge of the map, the physics engine triggers collision detection and stops your movement vector cold.

    Why on earth were we managing enterprise production risk on flat, two-dimensional Excel sheets when operational reality is three-dimensional?

    In BIGF, every operational decision—whether triggered by a human engineer, a CI/CD pipeline, or an autonomous AI agent—is evaluated in real time across three orthogonal axes (B × S × T):

    Authority = f(B, S, T)

    1. The B-Axis (Business Impact): What is the actual statutory, financial, and operational blast radius of this service node? (RTO, RPO, NIS2/DORA criticality tier).
    2. The S-Axis (Situational State): What is happening in the environment right now? Are we in normal daytime operations, in the middle of a cascading P1 incident, or under a peak commercial freeze?
    3. The T-Axis (Telemetry & Trust Integrity): How fresh, complete, and cryptographically verified is our underlying dependency data? (θ threshold, calculated via deterministic 10^-4 fixed-point arithmetic).

    As long as the combined coordinate stays inside the Tri-Axial Actuation Boundary—the "playable room"—execution flows at full automation speed. The millisecond a rogue AI agent tries to walk through the wall because the CMDB telemetry (T) is stale (θ < 0.8000) during a degraded state (S), the physics engine hits it with a deterministic 403 Hard Halt.

    No invisible clipping through production walls. Fail-Closed in authority, every single time.

    Level 3: Mechanism Design—Making Lying Mathematically Stupid


    Viti Magazine: One of the most ruthless parts of your repository is the Cloud Procurement and Change simulation logic. You use "Mechanism Design"—essentially reverse game theory. How does that stop people from gaming the system?

    Laine: Every veteran architect knows the oldest trick in corporate IT: if you want to buy a shiny new cloud tool or push a risky change without triggering a three-month security review, you just lie on the intake form. You tick the box that says "Low Business Impact / No Critical Data," get your rubber stamp, and connect it to core production two weeks later.

    In game theory, that's an incentive-incompatible mechanism—the game rewards dishonesty.

    With BIGF's Mechanism Design, lying on day one is operational suicide on day two. Why? Because the intake declaration isn't filed away in a dead Word document; it compiles directly into the live Runtime Control-Plane.

    If a team claims their new service is "Tier-4 Non-Critical" just to bypass procurement scrutiny, the engine automatically assigns that service a Tier-4 actuation ceiling. The first time that service tries to make an API call to a Tier-1 customer database at runtime, the boundary detects the structural mismatch and severs the connection instantly.

    You don't need compliance police chasing people with clipboards. You just design the game mechanics so that telling the absolute truth upfront is the only way your software gets to run in production.

    Final Boss: Agent-to-Agent (A2A) Combat in the Mesh


    Viti Magazine: Let's talk about the endgame: version 2.3 and autonomous AI agents. Everyone is rushing to deploy "Agentic AI" in ITSM. What happens when machines start playing against machines?

    Laine: That is the ultimate boss fight of 2026 and 2027. Right now, vendors are selling autonomous buyer-bots, capacity-scaling bots, and incident-remediation bots. What happens when a Cost-Optimization AI Agent (whose reward function is to kill idle servers to save money) collides at 2:00 AM with a Resilience AI Agent (whose reward function is to spin up redundant nodes for DORA compliance)?

    Without a deterministic referee, those two probabilistic models will enter an infinite loop, hallucinate authority, and DDoS the enterprise from the inside.

    In BIGF v2.3 (Autonomous Agentic Mesh Governance), agents aren't allowed to negotiate based on LLM "vibes." Every Agent-to-Agent (A2A) interaction is governed like a high-stakes multiplayer match with strict cryptographic rules:

    • Every action requires a state-bound token signed with Ed25519 cryptography.
    • Every decision produces an immutable, replayable Canonical Decision Record.
    • If two agents collide, the Tri-Axial equation (B × S × T) deterministically resolves who has priority based on governed Business Impact master data—not who has the most aggressive prompt.

    Viti Magazine: So if BIGF were a video game on Steam, what genre would it be?

    Laine: For the people still trying to run modern cloud infrastructure with manual CAB meetings and color-coded spreadsheets? It's Dark Souls on permadeath mode.

    For the architects who actually implement a deterministic control-plane? It's Factorio meets Baldur's Gate—a beautifully automated factory where every belt is balanced, the party buffs are mathematically verified, and the goblins get vaporized at the perimeter before you even have to roll initiative.

    Ready to patch your enterprise game mechanics?

    Stop playing corporate Prisoner's Dilemma with Excel sheets. Google Erkki Laine BIG Framework to explore the open-science specifications (v2.3 Autonomous Agentic Mesh Governance, v2.4 Reference Architecture, and the NIS2/DORA Alignment series) or test the Interactive Runtime Control-Plane Simulator directly on Zenodo and GitHub.#architecture #ai #devops #gametheory #software #coding #development #engineering #inclusive #community
    VITI MAGAZINE EXCLUSIVE INTERVIEW | GAME THEORY & ARCHITECTURE

  11. Halloween Horror Movie Review: The Return of the Living Dead (1985)


    Title: The Return of the Living Dead
    Release Date: August 16, 1985
    Director: Dan O’Bannon
    Production Company: Hemdale Film Corporation | Fox Films, Ltd. | Cinema ’84
    Main Cast:

    • Clu Gulager as Burt Wilson
    • James Karen as Frank Johnson
    • Don Calfa as Ernie Kaltenbrunner
    • Thom Mathews as Freddy Hanscom
    • Beverly Randolph as Tina
    • Miguel A. Núñez Jr. as Spider
    • John Philbin as Chuck
    • Jewel Shepard as Casey
    • Brian Peck as Scuz
    • Linnea Quigley as Trash
    • Mark Venturini as Suicide
    • Jonathan Terry as Colonel Horace Glover
    • Cathleen Cordell as Ethel Glover, Colonel’s Wife
    • Drew Deighan as Jerry, The Paramedic
    • James Dalesandro as Tom, The Paramedic
    • Robert Libman as Tac Squad Captain
    • Derrick Brice as Gunnery Sergeant Jefferson
    • Allan Trautman as Tarman Zombie
    • Terrence Houlihan as Yellow Cadaver Zombie
    • Jerome Coleman as Legless Corpse Zombie
    • Cherry Davis as The Voice of The Female Torso Zombie
    • John Durbin as The Zombie Who Calls for More Paramedics
    • David Bond as The Zombie Who Calls for More Cops

    Synopsis (via Letterboxd):

    When two bumbling employees at a medical supply warehouse accidentally release a deadly gas into the air, the vapors cause the dead to rise again as zombies.

    My Thoughts:

    Night of the Living Dead co-writer John Russo split off from George Romero to create his own zombie franchise beginning with this 1980s time capsule of a movie.  The movie is set around a medical supply warehouse in Louisville where drums of the toxic gas that causes zombieism were accidentally sent by the military. Remember the Reagan Era 80s when nonetheless the cultural zeitgeist was deeply mistrustful of the military rather than “support the troops?” Naturally, the gas is released affecting not just the warehouse but the nearby cemetery where a group of punks have gathered to party.

    The blue collar workers (all of whom seem to be played by familiar character actors that I cannot place where I’ve seen them before) get most of the best lines.  There’s the wiseacre Frank training the new hire Freddy, their hapless boss who makes all the wrong decisions when he takes charge, and the deadpan mortician Eddie.  The punks are funny in that 80s movie punks are always the same over-the-top stereotypes.  The girl who strips naked for the entire film is gratuitous though.

    And then there are the zombies who just want “BRAIIIIIINSSS!!!” because they stave off the pain of decay (possibly a metaphor for substance abuse?).  It’s hard to believe that is the first depiction of zombies craving brains. The idea of zombies who not only talk, but can hold conversations is a bit off-putting, but then again the “Send more cops!” gag is hilarious.

    This isn’t a masterpiece, but it’s corny fun with a lot of great one-liners, and probably would be exponentially more enjoyable at a crowded theater screening.

    Rating: ***

    #Comedy #HalloweenHorror #Horror #MovieReviews #Movies #ScienceFiction #Zombies
  12. 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:

    1. Is it still alive?
    2. Did it make meaningful progress?
    3. Do I need to do anything?

    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.

    StateMeaning to the userRequired evidenceUseful UI actionqueuedWork 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:

    • Request accepted
    • Source file scanned and indexed
    • 42 records extracted
    • Policy checks completed
    • Three exceptions need a decision
    • Final report saved

    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:

    Work shapeBest indicatorExampleFixed batchcompleted / total318 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.

    • Polling is enough for minute-scale background jobs. Return status, latest_event, and etag; back off when nothing changes.
    • Server-sent events work well for one-way timelines and reconnect cleanly with Last-Event-ID.
    • WebSockets fit collaborative workspaces where users can also approve, stop, or redirect a run live.
    • Notifications should be sparse: completion, failure, and 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:

    1. A run cannot become succeeded without an output receipt.
    2. A waiting_on_user run always exposes a decision action and cannot spend tools until it resumes.
    3. Replayed events create the same final timeline.
    4. A reconnect receives no duplicate visible milestones.
    5. A cancelled run cannot later publish a success event.
    6. A stale worker lease produces an honest recovery state, not permanent “Working…” copy.
    7. User-safe messages contain no prompt, secret, customer text, or chain of thought.

    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.

    1. Define the state machine and ownership of each transition.
    2. Add durable run records and one evidence-backed milestone per phase.
    3. Replace generic spinners with the latest verified update.
    4. Promote approval waits to a clear, resumable state.
    5. Add stale-run detection and a recovery message.
    6. Instrument completion quality, not just elapsed time.

    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

  13. Aller la team I need you

    Vos meilleures solutions pour cope quand vous avez le blues ?

  14. Animate your logo. Waveshare PocketTerm with custom buildroot built firmware image containing Push-To-Talk and messaging.

  15. I'd say this is a non-work update, except my fun hair is a way I express the same playful spirit I work with.

    It brings me ongoing joy to play with my hair color like this, and new looks always come with a moniker.

    Vote to name this hair color at 👉🏻 lttr.ai/AuK5L

  16. 2/2
    The unsung heros of the night shift have managed to actually mix them up, so now we have a little bit more than 100 items we can't sell due to regulations, and can't give them back either because they are already through all manufacturing procedures and thus aren't of any use for the original company.

    Each item is worth approximately $200, that's a minimum $20,000 loss (a little more adding manpower, energy, time…) because some person hasn't taken a flashlight to look up two letters.

    Yay!!

  17. 1/2
    I'm usually not spilling tea, but…you need to hear this even if you have no idea what I mean.
    The company sometimes gets semi-finished products delivered that we make whole, and each item of those are marked with a batch number from the original manufacturer. When we do our work, this batch number becomes irrelevant to the customer because we print our own in it. But it matters for our production since it's illegal for us to mix different original batch numbers within ours.
    Guess what?

  18. @antonlauner Hat das Café Continental komplett geschlossen - wisst ihr was?

    Ich sah nur den Zettel an der Tür "... ehemals Café Continental" und die Holzplatten vor den Fenstern. Das sah mir nicht wie vorübergehende Renovierung aus :/

  19. …
    could not have been given to me. Without even the slightest breath of wind, a small dust devil had appeared some distance away just like that and vanished again just as quickly. Except that, within that cloud of swirling dust, I believed I had made out a face. A woman’s face, a very kind one. And it seemed to nod at me. I closed my eyes for a fleeting moment, gave thanks for what I had experienced, and then turned toward Abigail.

  20. 1167

    If you have one, post a snippet involving spirits, such as a character talking to or about them.

    “It’s alright, I'm sorry.” Abigail said, in a somewhat soothing tone. I was refilling the bottles and just about to stand up when I caught sight of something on the opposite bank, and a word escaped my lips, “SHIMÁ.” “What?” Abigail asked, but I couldn’t explain to her what I had just witnessed. I couldn’t even explain it to myself, yet a clearer sign …

  21. Teaching old dogs new tricks...

    I own a printer, DCP-J752DW, that has been phased out around 2016. It works - it prints, it scans and it accepts 3rd-party ink cartridges.

    Unfortunately, it does not support scanning to a network share, which I need to automate some workflow.

    Luckily, there are official Brother drivers for Linux, so I can use the "Scan to File" function on the printer, to scan to some Docker container, that mounts the network share.

    And voila, ... scan to a network (share) is now a feature of my printer :neocat_wink_blep:

    Here is the Docker image and some explanation: codeberg.org/codedge/brother-s


  22. 27. Oktober

    Bronze, Silber, Gold – gibt es sportliche Charaktere in deinen Geschichten? Und standen sie mal auf dem Siegertreppchen?

    Nein. Es gibt nur eine Erwähnung von sportlicher Aktivität im weitesten Sinne in "AlexA" (Nein, nicht *das*…🙄), aber ich werde das hier nicht öffentlich darlegen weil es eine ziemlich sexistische Bemerkung sehr lebhaft nachstellt. Aber auf ein Siegertreppchen hätte die Gute irgendwie schon gehört …
    Nevermind.

Share on Mastodon

Enter the server where you have an account.