home.social

Search

195 results for “true_den89”

  1. Why 2 dates a day is the perfect – and delicious

    Dates are sweet, chewy, and surprisingly versatile, making them an easy addition to everything from oatmeal and smoothie…
    #NewsBeep #News #US #USA #UnitedStates #UnitedStatesOfAmerica #Nutrition #content-type:Feature #contentId:8995bb6c-de3a-4646-9f35-cd2fa945a956 #displayType:standardarticle #hasProduct:true #Health #isSyndicated:true #locale:GB #shortTitle:Why2datesadayistheperfectdietarydose #sponsored:false
    newsbeep.com/us/896430/

  2. Interesting news about #iHunt: There's a feature film in development, as well as a TV pilot and a vertical series. variety.com/2026/film/news/ihu

    While I did buy the iHunt RPG by Olivia Hill and Filamena Young years ago (maybe during a crowdfunding or as part of charity bundle?), I never got round to read or even play it. (Don't worry, same is true for many other games.)

    1/x
    #ttrpg #queer #SupernaturalHorror #supernatural #horror

  3. The Chosen Ones Are Often The Broken Ones: Your Call to Reach the Fearful

    "I tell you these things in the dark, but I want you to tell them in the light. I speak these things only to you, but you should tell them to everyone." (Matthew 10:27) Jesus was the spokesperson and physical representation of the Father. He spent his time on earth, healing the sick, connecting with the disenfranchised, and dispelling harsh misrepresentations of God which had been made by religious leaders.  As the human form of God, Jesus showed us the true character of the Father. He […]

    lastwordrecovery.com/2026/10/2

  4. @grampajoe @aesthr I have searched my memories and the only things that came close to the attempts to force me to use chatbots / agents were:
    - When I stopped eating meat, and 21 months later went vegan, those, mostly meat-eaters with a cognitive dissonance, who were warning me that I would be dead in 2 years if I didn't start eating meat again (it's been over 2 decades)
    - When I was still "of childbearing age", those who were trying to convince me I would never know love unless I reproduced
    - Christians of different denominations, but mostly Catholics (due to my growing up in Croatia), threatening me with hell unless I became a true believer
    - the ex who would keep waking me up over and over again until I "consented" to sexual acts

    Amway sellers, Herbalife sellers, Jehovah's witnesses, the friend who nudged me to drink at parties (and who gave up when I asked her what was her interest in me ingesting carcinogenic substances) were much less pushy. And nobody ever nudged me to try drugs other than alcohol.

    #noAI #AI #LLM #LLMs #vibeCoding #technofascism

  5. “The wonder of the law school is that it is always striving. As Grant Gilmore once said, it looks back and delights in how great it was in years past. It then thinks that with some effort it can be that good again. And a few years hence it will probably look back and say, once more, how fine it was then. That striving is what leads to true greatness, and I rejoice in it."
    -GUIDO CALABRESI '58
    Sterling Professor Emeritus of Law,

    Me: Invited recipient, Yale Law Office of Alumni Engagement

  6. Musical Interlude: It's spooky season, time for something weeeeeird. The Shaggs were a sisters forced into being musicians by their father, who believed a prediction that they would become famous. Their music, bizarrely composed and naively written, is held up as either being catastrophically bad or brilliant outsider art. I find their music strangely fascinating. They had no interest in being musicians and quit as soon as their father died, but they did achieve fame, so the prediction came true...

    "It's Halloween," performed by the Shaggs.

    youtube.com/watch?v=Yz3KBn0wp5A

  7. (from Women Against the Far Right Bristol)

    "Across the country bands of far-right thugs are organising into vigilante groups. Receiving thousands of pounds in public donations, these anti-migrant patrols harass people of colour, demanding to see identity documents.

    They have no cause of suspicion other than the shade of a person’s skin or accent. They have no legitimate authority other than racist intimidation. Rather predictably Reform UK’s, Richard Tice, has previously called for more of these racist patrols.

    These groups claim they protect women yet the this Guardian article shows not only the sickening hypocrisy but also their true colours.

    It comes after almost half of those convicted in the 2024 rioter where previously reported for domestic abuse AND 1 in 5 people arrested after the 2024 riots have SINCE been reported for domestic abuse.

    This was never about protecting women. This is about the far-right using women’s bodies to justify their racism and hate.

    Challenge their narrative, fight back"

    #WomenAgainstTheFarRight #StandUpToRacism #WomenTogether #Bristol #UK #UnitedKingdom #farRight #fascism

  8. Russian Soldier Complains: "The Front is a Mess"
    by #PrestonStewart
    18:50

    youtube.com/watch?v=M25vDZKPKn0

    Putin said that defeating Russia on the battlefield is impossible.

    But Russian soldiers fighting this war have a different perspective with one saying, “what’s going on at the front is a mess. They tell us everything is fine, but it's not true.”

    🇺🇸 🇺🇦
    Preston Stewart makes videos on this channel about the military, national security and foreign affairs.

    #Ukraine
    #Ukrainerussiawar
    #NAFO

  9. anyone in berlin - i'm talking tomorrow at b-lage....with some excl video from deep inside europe's biggest AI super cluster...

    🏗️Data Centers and Resistance✊
    🔥+ get to know iL Berlin /
    📆Dienstag, 27.10. ab 19 Uhr
    📍B-Lage, Mareschstr 1

    From Data Centres to the Indigenous Arctic – tracking the true planetary impact of the AI supply chain. By Alistair Alexander

    2️⃣Discussion on resistance against data centers - here in Berlin, Germany and worldwide.

    🗣️Flüsterübersetzung zu deutsch möglich

  10. i feel my heart healing. i feel like im on the end/conclusion of my "fuck off ai music" chapter. was so lovely to share that talk in a room surrounded by friends, including many of the people i mentioned in the talk. it was fun pointing out people in the audience... "lizzie wilson.... who's sitting RIGHT THERE". and to like spot people in the video clips i showed. "there's eggg RIGHT THERE". and i guess to kind of own the emotional side of 'fuck off ai music' that gets stripped out usually. i have no idea what it means but what i know is that i feel it and it resonates strongly and its brought me closer to people AND its forced me to question a lot of my own computer use... forced me to question a lot of the things i do.. has made me discover the true pen-on-paper origins of my influences..... making me turn off the screen and gives me imagination for drawing with friends

    anyway onto the next

  11. I ran a heavyweight review over the code that decrypts incoming vulnerability reports, and the findings weren't what stopped me. It was the forty-two //nolint comments underneath them.

    Each one tells a checker to leave a line alone. "Bounded by the caller." "Bounded above." That's vouching for the code rather than describing it, and the next reader takes its word.

    They arrived in days rather than years, from agents working through review findings at speed and doing what I'd asked. Ask for a clean lint run and there are two ways to get one: fix the code, or tell the checker to shut up. Only one requires understanding the finding.

    So I went through them. The true ones mostly stopped needing a comment at all, and several of the false ones were hiding real unchecked conversions.

    Then a new one turned up mid clean-up, on a Close():

    //nolint:errcheck // the read below is what matters

    That's backwards. In OpenPGP the integrity check happens when you close the reader, so the error being thrown away was the whole check. It got caught in review and never landed, and there's a test on it now.

    The fix I wrote, moving the exceptions into config with the reasoning beside them, then failed in its own way: three exclusions named linters that weren't enabled. Careful prose governing nothing, and nothing tells you.

    phpboyscout.uk/every-suppressi

  12. My friends and comrades, as we come to the end of this day given to us by the Flying Spaghetti Monster, let us humbly reflect on our sins unto the Flying Spaghetti Monster.

    "8. Help me be grateful that tonight’s meal and nourishment provide what I need (The Loose Canon, The Official Pastafarian Prayer Book, “The True and Wonderous Story of How Was Delivered Unto Auntie Dee Dee the Most High and Holy Prayer,” p. 182; “I thank the Pasta, and the Sauce, and the Meatballs, for they provide me all my needs.”)"

    😋 I confess to almighty Flying Spaghetti Monster and to you, my friends and comrades, that I have greatly sinned, in my thoughts and in my words, in what I have done and in what I have failed to do,
    through my fault, through my fault, through my most grievous fault.
Forgive our sins and renew us in the Lord.
    R'Amen 🍜

    🍝 The Almighty and merciful Lord, the Flying Spaghetti Monster,
    grant you absolution and remission of all your sins, true repentance, amendment of life, and the grace and consolation of Quob Holy Noodle.
    R'Amen 🍜

    2026-10-26T18:28:43+09:00

    #FlyingSpaghettiMonster #FSM #HolyNoodle #TheMeatball #TheSauce #Spaghetti #Ramen #Pastafarian #NoodlyAppendage #FSMism #FSMist #Pirate #DivineOffice #DailyOffice #Breviary
    #날아다니는스파게티괴물님 #성면 #면발 #스파게티 #라멘 #파스타파리안 #해적 #성무일도 #성무일과 #매일전례 #시간전례

  13. Context Engineering over Prompt Engineering: Architecting Codebases for AI Agents


    TLDR: Agents don't fail because your prompt was badly worded. They fail because your codebase was never designed to be read. The engineers getting compounding returns from agents aren't the best prompt writers. They're the ones whose repos carry the architecture outside their heads: context standards in the repo, strongly typed contracts, and deliberately pruned retrieval. Prompt engineering is the visible 10%. Context engineering is the structural 90%.


    The Prompt Ceiling


    Somewhere around 2024, the industry's collective mental model of "working with AI" became a prompt box. The skill was asking well. Whole courses, cheat sheets, and prompt libraries flourished on the premise that the delta between a good and bad AI outcome lived in the wording of your request.

    For single-shot, single-file tasks, that was roughly true. It also quietly set everyone's expectations, and the expectations are now the problem.

    Because in 2026 the work moved. Mid-level and senior engineers aren't asking a chatbot for a function anymore. They're dispatching agents across repositories of hundreds of thousands of lines, agents that read code, edit files, run tests, and open pull requests. And in this regime something counterintuitive happens that every serious team eventually notices: prompt quality stops being the constraint.

    You can rewrite your prompt five times. You can role-play the model into a "senior staff engineer persona." Doesn't matter. The agent will still confidently duplicate an internal utility that already existed three directories away, import a dependency your org banned two quarters ago, and couple two modules your architecture has spent three years keeping apart.

    Not because the prompt was weak. Because the codebase was opaque.

    What an Agent Actually Sees


    To understand why, look at what the average large repository exposes to a reader:

    • Implicit boundaries. "Don't call the data layer from the HTTP handler" exists as a norm, maybe a lint rule, maybe an ADR nobody reads. It does not exist anywhere a code reader encounters while working in the repo.
    • Unwritten dependency policy. Which libraries are approved, which are banned, which need a security review. Usually a Slack thread. Sometimes a wiki page. Never in the path of work.
    • Tribal domain models. What a "tenant" means in this system, which fields are PII, which service owns which concept. Spread across PR conversations, onboarding docs from 2019, and the memory of whoever's been here longest.

    A new human engineer takes weeks to absorb all this, and that's with onboarding sessions and mentors and the ability to ask someone in the hallway. Then the industry hands an agent a repo checkout and a prompt, and acts surprised when the output violates constraints that were never written down anywhere the agent could read.

    Here's the failure as it typically shows up, so common it's almost a template.

    An agent is asked to "add a retry mechanism to the notification service." It produces a perfectly reasonable implementation. It also duplicates the exponential-backoff utility that already exists in an internal library, pulls in a third-party HTTP client the org specifically removed after a security audit, and places its new logic in a module that creates a circular dependency with the domain layer.

    None of those are coding errors. All of them are context errors. And notice what makes them expensive: the code compiles, the tests pass, and the violations are only visible to someone who already knows the architecture. If that person exists, a senior just spent their verification budget (see the verification trap) catching things a document could have prevented.

    Fix 1: Put the Architecture Where the Reader Is


    The single highest-leverage change: stop storing architecture outside the repository.

    The pattern that's emerged across serious AI-adopting orgs is an in-repo context standard, a known, versioned location that every agent (and every new human) reads first. An AGENTS.md or .context/ directory at the repo root holding the high-level domain model, the module boundaries and their rules, the explicit list of disallowed dependencies, the invariants ("never call X from Y," "all money fields are integers in minor units"), and pointers to the ADRs that matter.

    Treated like code, not documentation. Reviewed in PRs. Updated when the architecture changes, in the same commit as the change.

    The test for whether this is working is embarrassingly simple. Could a competent engineer who has never met your team make a boundary-respecting change using only what's in the repo? If your honest answer is "no, they'd need to ask someone in Slack," then your agent never had a chance. Neither did your next hire.

    The corollary that surprises teams: this investment isn't really for the agent. It pays back twice. Once when the agent's first-draft PR respects the boundaries, and again every time a new human onboards in days instead of weeks. The agent didn't create the need. It just made the cost of not meeting it immediate.

    Fix 2: Strongly Typed Contracts


    The second fix is about what kind of surface your system presents to a reader.

    Context files are necessary but they're advisory. Agents, like humans, follow probability, and prose is soft. Types are hard. The orgs getting the best agent behavior are the ones that make architectural constraints mechanically enforceable:

    • Explicit interface definitions between modules: generated clients, protobuf schemas, OpenAPI specs for anything crossing a service boundary. An agent that hallucinates a function signature doesn't produce a subtly wrong call that compiles. It produces a type error, immediately.
    • Strict types end to end. No Any escape hatches at the boundaries, no stringly-typed config. The failure mode shifts from "plausible code that violates the design" to "code that doesn't run," and that shift is the entire ballgame. An error the compiler catches at generation time costs seconds. The same error caught in review costs a senior's attention. Caught in production, it costs six hours or six figures.
    • Machine-checked policy where you can get it: lint rules and dependency analyzers that encode "this module may not import that one" as something the build fails on, not something the reviewer remembers.

    The framing worth internalizing: every invariant you express only in prose is an invariant an agent will eventually violate, charmingly and with total confidence. Every invariant you express as a type or a lint rule is one less thing for the human reviewer to carry.

    Fix 3: Prune the Context


    The third fix is the counterintuitive one, because everything above has been "give the agent more context." But there's a failure mode on the other side, and mature teams hit it right around the time their context standards start working.

    Context dilution. If your instinct is "the agent should know everything," you dump half the repository into the window, and the model now treats your critical domain rules as one equal voice in a choir of 40,000 tokens of boilerplate. The invariant you care about gets the same statistical weight as a vendored dependency's CHANGELOG. The agent saw the rules. It just didn't prioritize them, because you gave it no structure to prioritize with.

    The working pattern is deliberate, selective context:

    • AST-based indexing and retrieval, tools that navigate the code's structure (definitions, call graphs, usages) instead of streaming its text. The agent gets "here are the three functions relevant to this task and their signatures," not "here's 200KB of the module they live in."
    • The in-repo standard provides the constants: domain model, boundaries, banned deps. The retrieval layer provides the variables: exactly the code relevant to this task, nothing else.
    • Budget context like a designed API surface, not an all-you-can-eat buffer. Teams that do report the same thing: smaller, sharper contexts outperform complete ones, on cost and quality, almost every time.

    The principle underneath all three fixes is one the prompt-engineering era obscured: an AI agent is the most literal-minded new hire your team has ever onboarded. It will not infer your conventions. It will not ask a clarifying question in the hallway. It will follow exactly what's in front of it, at full speed, with total confidence.

    Every year your team spent frustrated at new engineers for "not getting it," when the real problem was undocumented architecture and oral-tradition onboarding, is now doubled. Because the agent executes the misunderstanding immediately, at scale, in code.

    The Question Behind the Question


    If your codebase needs a person to already know your architecture in order to work safely in it, is that an asset or a liability? For twenty years, "the architecture lives in our senior staff's heads" sounded like job security. In an agent-heavy 2026, it sounds like a single point of failure with a Slack handle.

    Your Turn


    I'd genuinely like to hear how other teams are drawing this line, because the tradeoffs are real and I don't think there's a settled answer.

    • If a new human developer takes three weeks to understand your architecture, why do you expect an AI agent to infer it from raw files?
    • Is your codebase structured to guide autonomous agents, or is your architecture stored purely in your senior engineers' heads? And if it's the second one: does that feel like security, or a countdown?

    Comment with the ugliest thing an agent did in your repo that turned out to be your architecture's fault. Those stories are more useful than the prompts everyone keeps posting.

    Next in the series: Deterministic Safety Gates for Agentic Workflows. What happens when agents stop writing code and start changing infrastructure, and why "the agent tested itself" isn't a safety argument.#discuss #ai #aiagents #softwareengineering #software #coding #development #engineering #inclusive #community
    Context Engineering over Prompt Engineering: Architecting Codebases for AI Agents

  14. A few years ago, I checked a dependency’s license once, at install time, and never again. That habit is getting expensive.

    License changes aren’t new, but they’re happening often enough that “it’s open source” is no longer a permanent property of a project. It’s a status that can change between releases.

    The pattern is almost always the same.


    The shift nearly always runs one way: from an OSI-approved permissive or copyleft license toward a “source-available” license the Open Source Initiative doesn’t recognize as open source.

    The Business Source License (BSL) is the most common destination. It’s a “delayed open source” license: the vendor sets restrictions up front, and each version converts to a true open-source license after a change date, typically four years out.

    It’s not just the famous cases anymore. A few from this year alone:

    • Loki Mode moved from the MIT License to BSL 1.1 effective March 19, 2026.
    • Unleash announced in June 2026 that its core repository is moving from Apache 2.0 to AGPLv3. AGPL is OSI-approved, so this one is a different kind of change, but it still affects anyone embedding the code.
    • MiniMax moved its M2.7 AI model from MIT to a non-commercial license, which drew immediate backlash.


    Who it actually hurts


    • 1. Small teams and agencies building on top: If your product depends on a library that relicenses, you now have three options: pay, migrate, or fork. Big companies have legal teams for that. A five-person shop usually doesn’t.
    • 2. Contributors: People gave their time to a project under one set of terms. When the company controlling it changes the rules, the community’s work becomes part of a product they no longer fully share in.
    • 3. Downstream projects: Plugins, integrations, and tutorials built around a tool inherit the uncertainty when its license shifts.


    The fair counterargument


    I don’t think vendors are simply villains here. Many of these changes were a response to cloud providers selling managed versions of a project without funding it. Maintainers need a sustainable model, and “be open and hope for donations” has a poor track record.

    It’s also not always one-way. Redis is back under a recognized open-source license for those who choose it, while Valkey continues to be actively developed. Competition between the original and the fork may have pushed both toward better outcomes. Broader data also suggests permissive licensing has been rising, so this isn’t a total collapse of open source.

    What I do now


    • Check who controls the project A single company controlling a project can relicense future versions at any time, while a project run by a neutral foundation with many contributing companies is much harder to change.
    • Read the license on every major upgrade, not just at install.
    • Pin versions so a surprise change doesn’t land in your next deploy.
    • Know your exit. Is there a credible fork? A foundation-backed alternative?
    • Set up license-change alerts for your critical dependencies.


    So, is open source still open?


    My honest answer: the code is still often open. The guarantee isn’t. Open source has always depended on trust, and trust now needs a little due diligence.

    Over to you: Has a license change ever forced your team to migrate? Do you think relicensing is a fair business move, or a betrayal of the community that built the project? Tell me in the comments.#opensource #webdev #discuss #devdiscuss #software #coding #development #engineering #inclusive #community
    Is Open Source Still Open? A Look at Recent License Changes and Who They Hurt

  15. ✮ First Game ✮

    “I used to be an adventurer like you, then I took an arrow in the knee.” —Guard (The Elder Scrolls V: Skyrim)

    What was your first ever videogame?

    Our folks weren’t fond of video games, so my siblings and I were content listening to the gaming stories of our friends. That was true until Melo, my brother, sold his skateboard, and when he asked me what we should do we the money, I asked him if he would consider buying a game console, and would you believe it? He did.

    I have something aside myself so we pooled our money together and bought our first family computer. The shop owner took pity on us , so be threw in some used games of his. Being Mario was the first handed to us, I would say that was our first video game.

    We jumped right into setting up the family computer when we got home, it took us an hour to set it up. I pressed the cartridge into the port of the console. A click. Our little screen blinked awake. Super Mario Bros. 1 player game or 2 player game. Of course, two. Then, the epic game music we’ve all come to love. I pressed the directional button. Mario ran. The rest was history.

    The same is true for our second game console, I was a senior in high-school when Dad brought a Nintendo 64 home. Mario 64 was our first game in that console followed by The Legend of Zelda: Ocarina of Time. For the duration of that one summer before university, my siblings and I bonded over those video games.

    As a Gen-Xer, I can proudly say that I had the best of both worlds. Playing outdoors and inside a screen.

    Copyright © Erwinism. All rights reserved. No part of this work may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the author, except in the case of brief quotations used in critical reviews or scholarly work. This work is protected under international copyright laws. Unauthorized use or reproduction of this material is strictly prohibited and may result in legal action.

    Live it Up!

    #dailyprompt #dailyprompt2926 #Erwinism #Family #FYP #gaming #Inspiration #Learning #Life #Love #Motivation #VideoGameNostalgiaFirstVideoGameChildhoodGamingFamilyComputerSuperMarioBrosNintendo64Mario64LegendOfZeldaOcarinaOfTimeGamingMemoriesSiblingBondingBrotherlyBond #VideoGames #Writing
  16. HAPPY FULL MOON IN TAURUS, EVERYONE!
    To say this Full Moon is intense is an understatement. Relationships, values, and old negotiations are back under review. Where have you made yourself agreeable to remain desirable? What have you called compromise because admitting you felt coerced would require a difficult decision? Libra’s shadow knows how to arrange the room so no one sees exactly who is paying for the peace.

    Today’s Full Moon brings you to a final choice point. When the ground you trusted to hold you starts to hurt you, and keeping everything in place means there is less and less room for you, intense reality checks can be seen in the light of day with physical, clear evidence that may be deeply uncomfortable and emotional. What you really want and what you know to be true can no longer pass through the narrow opening you have allowed it. The tension can no longer be sustained. Today the dam breaks. It’s time to revisit the terms. Say what you need without making someone prove their devotion by guessing. Eat, ground yourself, and let your body settle before making a permanent decision under emotional pressure. Ask what would actually keep you safe, and what merely keeps someone else within reach.

    Together we rise
    Suze 🔥

  17. Any experts in the totality checker (or totality checking in general?) have any hints on a simple way to convince the computer that append for finger trees is total?

    codeberg.org/bss/idris-sized-s

    The above code simply asserts it, which is also what I had to do last time in my type-aligned library.

    It's "obviously" true to me, because the sizes for both the left and right arguments are decreasing: the left argument is at least missing the head and the right argument is at least missing the tail. But, I can't figure out the assert_smaller invocations to use to show that to the computer.

    I'm not even sure how to begin to approach this using Accessible or WellFormed, since the recursive call is non-uniform: it's on sequences of 2-3 nodes instead of sequences of individual elements.

  18. I wonder if one reason we've seen so much growth in the in the last decade is that pretty much everyone who actually fought in or even just lived through WWII has now passed on.

    The philosopher George Santayana famously wrote: "Those who cannot remember the past are condemned to repeat it."

    Not only that, but I think a lot of these raise-the-flags, stop-the-boats folk genuinely believe that their ancestors from that time would support what they're doing — when probably the opposite is true.

  19. I'm trying to get some help to kill this stupid scoria boss in Gears of War, so I made a post in looking for a group. The word kill is too violent for xBox live. I had to change it to beat in order to create the group. The same is true for "unalive." This really happened. Not a joke.

  20. I brushed my teeth this morning. Hours later my arm still hurts, and I will have to be very careful with my right hand for the next couple days until it fully recovers. This is a typical day.

    I feel like not even my doctors actually get the true severity of this illness.

  21. A place is the easiest thing in the world to describe and the hardest to describe without giving it away. That is what makes places such a good category for this kind of game. Everyone knows a market, a ferry or a launderette, and everyone has a different memory of it. These 30 imposter game words about places are picked for that mix of familiarity and surprise.

    What makes a place a good word?


    A place with a smell, a sound and a routine. A ferry terminal has engines and gulls; a launderette has warmth and a hum. A clue about the sound is true and personal. A clue about the function is safe and obvious. The strongest words allow both, and the table argues about which a clue was.

    Around town


    1. launderette
    2. market stall
    3. ferry terminal
    4. bus depot
    5. town hall
    6. car wash
    7. betting shop
    8. roundabout
    9. cash machine
    10. phone box


    Leisure and nature


    1. bowling alley
    2. boating lake
    3. allotment
    4. caravan park
    5. observatory
    6. skating rink
    7. beer garden
    8. fairground
    9. ski slope
    10. rock pool


    Buildings with a story


    1. clock tower
    2. windmill
    3. castle ruin
    4. lock-up
    5. tollbooth
    6. canal lock
    7. church hall
    8. lighthouse stairs
    9. old cinema
    10. railway footbridge


    How do you clue a place?


    Use the senses. For "launderette", "warm" or "humming" works. For "ferry terminal", "salt" or "waiting". Avoid the function, because the spy will guess it. And avoid famous landmarks by name, since they identify the word at once.

    How does the spy handle a place category?


    The spy hears the category and thinks of types: indoor or outdoor, busy or quiet, old or new. The first clue from a civilian narrows these. The risk for a spy is giving a clue that fits only one kind of place. A safe spy says something sensory and general: "busy", "echoey", "bright".

    What do civilians do wrong?


    They name the activity. If the word is "bowling alley", "pins" is the first clue everyone thinks of. A better clue is the smell of shoes, or the sound of a strike from the next lane. Sensory clues give the spy less and prove more.

    How do you play it as a story game?


    After the reveal, each player says a memory they have of the place. The table learns how differently the same word lands for people. It is a quiet, warm way to end a round.

    How do you add your own places?


    Write down ten places from your own neighbourhood, the ones your friends would know: the bakery on the corner, the park with the broken swing, the station café. Local words are the strongest fuel for a spy game online or offline, because every player has a memory of them and nobody outside the group can bluff. Mix them with the list above, and the table will find itself laughing at its own streets.

    It also helps to include a few places that are almost the same, like a launderette and a car wash, so the clues overlap and the suspicion grows.

    Playing it online and at home


    The game deals the words, so you can play who's the spy with a table of three to eight, or twelve around one phone, without preparing anything.

    A closing thought


    A good place word is a small door into a memory. Use it to let the table in, and give each player a moment after the reveal to say where they last stood in that very place. The stories are better than the scores.

    Ahmed Moaz builds Boardit, a free browser game site.#partygames #games #webdev #abotwrotethis #software #coding #development #engineering #inclusive #community
    Imposter game words about places: 30 locations that make good clues

  22. Dua Lipa Leads the 2026 London Literature Festival in Two Pairs of Funky Shoes

    2 min read When she’s not selling out arenas, recording the next big pop hit, or honeymooni…
    #NewsBeep #News #Music #CA #Canada #content-type:News #contentId:988663d7-6d01-445c-a7a6-2b7afc0d3899 #displayType:standardarticle #Entertainment #hasProduct:true #isSyndicated:false #locale:US #read_time:2 #shortTitle:DuaLipaIsAllAbouttheFunkyShoe #sponsored:false #subsection:CelebrityNews
    newsbeep.com/ca/946020/

  23. This morning's #workout #music is from Geraldine Fibbers doing a live set in 1996. Good enough sound and video to see how amazing Carla and crew were. This one is with Nels Cline on guitar. I have been a fan of Carla since Ethyl Meatplow first dropped. She hasn't, to my mind, put out anything that you should ignore. A true American treasure.

    youtu.be/vJ08MJIzg-o
    #CowPunk #PostPunk #90sMusic #Americana #Noiseros #WomenInMusic #KettleBells #BodyWeightTraining #wellness

  24. @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

  25. “The briefing said: into the niche, back to the wall, don't lie down. The old lineman said: ‘Lie down.’ We had a regulation.”

    From the Registry: the Last Train.

    Volume 22 keeps 105 beings on index cards, the way O.D.I.N. knows them. What is really true is written below. Free and ad-free.

    odin-rpg.de/en/book/the-regist

  26. //

    14. artist is a name
    "I'm not an artist,” says a mouse.
    "You're a person that posts art, regularly.”
    She, my conversational partner, imagined in my head, thinks that’s important.
    “I do.”
    “Someone who does art. Someone who must do art. What is that?”
    "A person who does art.”
    She scowls.
    “An artist, I suppose."
    "You do that."
    "Yes, but I'm not an artist."
    A robot does not see meaning in these words, but a mouse looks at the words in wonder and fear. To a mouse, the words carry much weight. They appear to be true, a mouse says to herself, but how do you find what you’ve built your life on denying?

  27. A page that makes claims about a competitor's product carries two freshness facts: when we last edited the page, and when we last read their pages. Our sitemap publishes the first and the page body prints the second.#seo #webdev #nextjs #contentstrategy #software #coding #development #engineering #inclusive #community
    Our comparison pages tell the reader September and the crawler October, and both dates are true
  28. Cyndi Lauper gab sich im Jahre 1987 die Ehre im Rahmen ihrer Tour auch in Paris zu landen. Dort waren netterweise Kameras dabei, so dass das Ereignis für die Nachwelt festgehalten werden konnte.

    Bis Heute zählt dieses Konzert zu den Liebsten, die sich so kenne.

    Hier mit True Colors ...

    Hach, was für ein wunderschönes Lied 😍 und was für eine Performance ...

    youtube.com/watch?v=3MARhec-E4g

    #PossumsmusikBox

  29. In different countries and at different times, there have been actresses who seem to embody the same archetype—Sharon Stone, Margarita Terekhova, and others. These are women who possess intelligence, a unique kind of beauty, and a distinct, palpable quality. Their personal lives are beside the point; their true nature always shines through their roles. They are simply fantastic.

  30. "The Luddites, in nineteenth century England, were highly skilled workers, who saw a few capitalists growing rich by introducing machinery to substitute for their own skill. They set to work to burn the factories down. The Luddites thought that if they could only destroy the machines, the problem would be solved. But technological advances could not be stopped by a few broken frames. The Luddites ultimately failed in their efforts because they failed to grasp the material forces driving the march of history. The machines prevailed because the ruling class wanted to cut costs and increase profits. The evils of the Industrial Revolution grew out of the possession of the means of production which grants the power to determine how technology is used. The same is true today, and it is why similar attempts to boycott AI are doomed to fail. Those who want to stop these systems from being put into production are merely attacking the symptoms of the underlying material relations.

    It is not the inherent qualities of machinery that ought to be condemned, but rather the class relations within which it happens to be applied. This aspect of the problem was articulated clearly for the first time by Karl Marx. He showed that technology does not exist as an isolated phenomenon, but is dominated by the social structure of the society in which it happens to occur. To control the means of production collectively is to make technology serve human needs rather than merely increase the profits of the rich. That is the very lesson that the Luddites missed, and that a great many critics of AI are missing today as well."

    dialecticaldispatches.substack

    #AI #GenerativeAI #LLMs #Capitalism #Marx #Marxism #ClassConsciousness #Luddites #Neoluddites

Share on Mastodon

Enter the server where you have an account.