home.social

Search

1000 results for “whale_murugan”

  1. Spot the relatively simple ChatGPT fails. Yet more reasons to take answers from AI with a pinch of salt...

    While Googling the Trump phone to see how terrible it was, I used ChatGPT to find an appropriate anagram of the words “Trump Mobile” to describe it…

    #AI #aiFail #ChatGPT #Tech #Error #OpenAI #Trump #TrumpMobile #LLM #LLMs #Computing #Phone #Anagram #Anagrams #Failure #Computer #artificialintelligence

  2. DATE: October 7, 2026
    SOURCE: AMERICAN PSYCHOLOGICAL ASSOCIATION

    TITLE: What to say when someone shows up sick

    URL: time.com/article/2026/10/07/wh

    The key is to make your request clear while reassuring the person that you care about them and would like to see them when they’re feeling better.

    URL: time.com/article/2026/10/07/wh

    -------------------------------------------------

    Private, vetted email list for mental health professionals: clinicians-exchange.org

    Unofficial Psychology Today Xitter to toot feed at Psych Today Unofficial Bot @PTUnofficialBot

    -------------------------------------------------

    #psychology #counseling #socialwork #psychotherapy @psychotherapist @psychotherapists @psychology @socialpsych @socialwork @psychiatry #mentalhealth #psychiatry #healthcare #depression #psychotherapist #SettingBoundaries #HealthyBoundaries #CommunicationTips #SelfCare #StayHealthy #HealthAndWellness #SickDay #Relationships #AssertiveCommunication #Wellness

  3. Autumn in the woods comes with a fear I feel every year: that the colour will peak and fall in the gap between one visit and the next, and that I will miss it for another whole year. There is a great deal of anticipation in the season. There is a fair amount of anxiety in it too.

    timsmalley.co.uk/blog/waiting-

    #woodlandphotography #landscapephotography #nature

  4. HELLO, MY NAME IS DORIS [2015]

    what a wonderful movie!! almost quit watching movies for binging series altogether - and so i'm very happy that i found this one while chasing #natashaLyonne, who only appears thrice.

    but, main role #sallyField, OMG, why have i never heard of this actress?? and it's such a nice [yeah, fuck it, i said it, NICE] #neurodivergence coming-of-age story!

    maybe i am doris. or will become. or whatever.

    en.wikipedia.org/wiki/Hello,_M

    #rebcommendations #netflix #nd #diversity

  5. What did they do? What crime did they commit to deserve being killed? What sin did their mother commit to spend her whole life in anguish, pain, and suffering because of their loss? 😡🥹

    #palestine #genocide #Israel #freepalestine

  6. Hamas said airstrikes carried out by the zionist occupation army on the Islamic University campus in #Gaza City martyred three university staff members and wounded several others while students were present. The movement characterized the strike as a war crime and an extension of an ongoing genocide lasting more than three years, accusing the enemy government of violating the ceasefire agreement through daily bombardment of residential neighborhoods, displacement tents, and civilian institutions, as well as advancing the yellow line westward to seize land and blocking basic food supplies.

    Hamas called on mediators and the agreement's guarantor nations to intervene immediately and pressure the occupation to halt its actions against civilians, lift the siege, and deliver aid to more than two million people.

    25/10/2026
    t.me/Palresistmirror/97396

    #IsraelWarCrimes #warcrimes #IsraelTerroristState #hunger #CeasefireViolations #palestine

  7. Proactively: I think the route planning interface could use a big big overhaul. But the proposal above changes virtually nothing in the UI while unlocking way more natural route planning.

  8. Second Death

    Hi everyone! I hope you’re all well. Today, I thought I’d share a little horror short that I wrote a while ago and couldn’t decide what to do with. I hope you enjoy it!

    Second Death

    He felt the spark of consciousness fill his mind. He was aware now.

    He tried to move but found that nothing worked; even the muscles that lifted his eyelids failed him. In fact, every muscle in his body was frozen. He was paralysed, though by what or how, he could not say.

    His mind was sluggish and foggy, his memory having all but failed entirely, depriving him of the knowledge of who or where he was, but leaving everything else. The only reasoning for his current situation that he could come up with was that he had been in some sort of terrible accident, perhaps having been run over by a horse and buggy, and was now lying on some bed in the London hospital, a poultice wrapped around his head. The streets were a mess with horses and buggies these days. He knew that, at least.

    The fact that his mind had woken before the rest of his body did not frighten him. He knew this sort of thing happened every day in London; people being brought to the hospital in all manner of conscious states, and since he felt no pain, he was certain that somebody was taking very good care of him indeed.

    As he lay there, waiting for his body to catch up with his brain, some vestigial ember, a flicker of activity deep inside his mind, sparked, sending images rushing to the fore. A jumble of faces accosted him as his memory began to slowly filter through the abstract dam that had thus far held it back; women in long grey dresses with white aprons and white caps, and men, some old and bearded, some young and clean-shaven, but all wearing dark clothes. Somehow, he knew they were doctors and nurses.

    However, since waking up, he had heard no doctors or nurses—nor anybody else for that matter—coming to check on him. Had he been forgotten? Had they left him alone, thinking that he might never wake? His heart began to quicken at the thought that he might actually be stuck like this forever, that he might be trapped inside the confines of his own mind, his own mental walls slowly closing in on him. Surely, he would begin to disappear into insanity.

    The thought of being left in his current state until his body died of starvation and dehydration filled him with anxiety. He had to wake up. He had to force his mind and body to work in unison once more. He had to move, somehow; his very survival depended on it.

    Forcing his mind to work harder, he saw flashes of whitewashed walls and long, narrow corridors, and at first, he thought perhaps he might have been conscious upon his arrival at the hospital. 

    As sensation began to return little by little to his muscles, it occurred to him rather suddenly that there was a lack of sound. For a brief moment, he considered the fact that he may have gone deaf; he had known it to happen with head injuries, although he didn’t know how he knew, but the sound of his own breath leaving his lungs quelled the fear instantly.

    He was further relieved when he began to wiggle his toes, and further still when his fingers began to twitch. With each passing moment and every twitching phalanx, he felt the fear of his being trapped inside of himself ebbing away.

    Straining, he tried to open his eyes. He felt his lids fluttering, but everything remained dark. As he tensed and released each muscle in his legs and arms, still unable to fully move them yet, he willed his eyelids to cooperate—but darkness remained absolute. He tried again, and again, panic surging as he considered that he may have gone blind; he knew this, too, could sometimes happen with head injuries and again, how he knew this eluded him.

    As his heart quickly became a bass drum inside his ribcage, threatening to burst out at any moment, adrenaline surged through his body, and he felt his spine twitch—he willed his body to sit up, but the most he could manage was a slight raising of his head. He tried to gather himself, taking a deep breath, and then tried again, straining against himself as he attempted to fully reconnect his mind with his body. Drawing on every ounce of strength he could muster, he tried again, straining, straining, straining and… yes… yes… and…

    He jerked upward and—SLAM! His forehead collided painfully with something solid. The impact caused a spark, and in an instant, everything came rushing back. He was Eliot Smith, a doctor at The London Hospital. The adrenaline had acted like coal being shovelled into a waiting empty furnace; his whole body was mobile now; he could move his arms, his hands. He reached up, frantically exploring the area around him.

    As he felt the silk lining, the unyielding wood. The truth slammed into him with cold brutality—he had been buried alive.

    Terror consumed him. He screamed and clawed desperately, tearing at the lining and wood until his fingers bled. He pounded, kicked, and screamed until he felt his heart burst painfully in his chest. And with one final gasp of horror, he fell silent again—this time, forever.

    The End.

    Thanks for reading, if you did. I appreciate your time, and I hope you enjoyed it!

    As ever, thanks for stopping by!

    Until next time,

    George

    © 2026 GLT

    #death #horror #horrorStory #shortStories #shortStory #stories #writing
  9. Kyiv mayor shares photos of damage to Pivdennyi Bridge

    Kyiv Mayor Vitali Klitschko has posted several photos showing the damage caused by a Russian missile strike on the Pivdennyi Bridge in the Ukrainian capital.

    Source: Klitschko

    Details: Klitschko said the bridge remains closed to traffic while specialist services are assessing the extent of the damage.

    "Train services between Osokorky and Chervonyi Khutir on the metro's Green Line have also been suspended," he wrote.

    The bridge
    Photo: Vitali Klitschko

    Background: The Pivdennyi Bridge was closed to traffic after being hit by a Russian missile during an overnight attack.

    Support Ukrainska Pravda on Patreon to help us keep reporting!

    pravda.com.ua/eng/news/2026/10/27/8059871/

    #Ukraine #News #UkraineWar

  10. AI can generate a financial model that looks coherent, contains valid formulas, and produces a plausible result while still being wrong in ways that matter.

    A formula can reference the wrong cell. A cost assumption can be expressed in the wrong unit. A revenue schedule can omit a phase. A model can calculate correctly from an unsupported market assumption.

    These are different failure modes, and they need different controls. For real estate feasibility models, the objective should not be to ask whether an AI-generated workbook looks correct. It should be to establish which properties can be tested automatically, which assumptions require evidence, and which decisions must remain with a qualified human reviewer.

    A useful validation architecture has five layers:

    1. Structural validation
    2. Deterministic calculation checks
    3. Domain and consistency checks
    4. Evidence and provenance checks
    5. Human review and approval

    No single layer is sufficient.

    1. Separate the output from the evidence


    Consider a hypothetical development model with the following inputs:

    • Site area and developable area
    • Permitted gross floor area
    • Unit mix or lettable area
    • Revenue assumptions
    • Construction and other development costs
    • Financing assumptions
    • Development programme
    • Exit assumptions

    The model calculates development costs, revenue, cash flows, residual land value (RLV), and potentially internal rate of return (IRR).

    For example, a model might calculate an RLV of £4 million. That output can be mathematically consistent with the workbook and still be commercially misleading if the revenue assumptions are unsupported or the construction cost basis is outdated. Validation therefore needs to test both the calculation and the justification for its inputs.

    2. Layer one: validate the structure before the numbers


    Before reviewing financial logic, validate the shape of the generated output. If an AI system is expected to return structured data before creating a workbook, define an explicit contract. JSON Schema is one established option for specifying required fields, data types, and constraints.

    See the JSON Schema getting-started guide.
    A simplified model input contract might look like this:
    {
    "project_id": "DEMO-001",
    "currency": "GBP",
    "site_area_sqm": 5000,
    "gross_floor_area_sqm": 12000,
    "construction_cost_per_sqm": 1800
    }
    This is illustrative data, not a market benchmark or a recommendation for a production schema.

    A structural validator could check that:

    • Required fields are present.
    • Numeric values are actually numeric.
    • Areas and costs use declared units.
    • Currency is explicitly identified.
    • Values fall within defined technical bounds.
    • Unexpected fields are rejected or handled deliberately.
    • Missing values are not silently replaced with zero.

    The last point is important. Zero and unknown are not equivalent. If a finance rate is missing, substituting zero can make a model appear more profitable. A missing value should normally trigger a validation error or an explicit unresolved status.

    Structural validation establishes that the model can be interpreted. It does not establish that the model is economically sensible.

    3. Layer two: use deterministic checks for deterministic rules


    Rules that can be expressed precisely should not depend on an LLM's judgment. For example, if a model defines construction cost as gross floor area multiplied by construction cost per square metre, the expected calculation is:

    \text{GFA}
    \times
    \text{Cost per sqm}
    ]
    For the hypothetical inputs above:
    [
    12{,}000 \times £1{,}800 = £21{,}600{,}000
    ]
    A deterministic test can independently calculate the expected result and compare it with the workbook output.
    from decimal import Decimal

    gfa_sqm = Decimal("12000")
    cost_per_sqm = Decimal("1800")
    reported_cost = Decimal("21600000")

    expected_cost = gfa_sqm * cost_per_sqm

    assert expected_cost == reported_cost

    This test checks arithmetic for the stated formula. It does not establish that the GFA is permitted, that the cost rate is appropriate, or that the formula captures every relevant cost.

    A production implementation should also define tolerances where appropriate, particularly when comparing rounded spreadsheet values or calculations involving floating-point numbers.

    Other deterministic checks might include:
    Revenue equals the sum of its components.

    • Total costs reconcile to their component schedules.
    • Cash flow totals reconcile across periods.
    • Unit counts and areas reconcile between schedules.
    • The reported output matches an independently calculated result.
    • A sensitivity case actually changes the intended input.
    • Required formula cells are not unexpectedly blank or replaced by constants.

    Where possible, use independent calculations rather than simply checking that a formula cell contains a formula. A formula can exist and still be wrong.

    4. Layer three: validate model relationships


    Many serious errors are not syntax errors or arithmetic errors. They are inconsistencies between parts of the model.

    Suppose a development model contains:

    • 120 residential units in the unit schedule
    • 116 units in the sales schedule
    • Revenue calculated using the sales schedule
    • Construction costs calculated using the unit schedule

    Every formula may evaluate successfully, but the workbook contains a discrepancy that needs resolution.

    Domain-level checks can flag conditions such as:

    • Unit counts that differ across schedules.
    • Areas that exceed a declared model constraint.
    • Revenue periods that do not align with the programme.
    • Cost totals that exclude a populated cost category.
    • An exit value that uses an inconsistent timing assumption.
    • A sensitivity scenario that changes revenue but leaves dependent calculations unchanged.
    • An IRR calculation using a cash-flow range that omits a period.

    These checks should be encoded as explicit rules wherever the intended relationship is known.

    Some rules require context. For example, whether a particular cost should be included in a development budget depends on the model's scope and conventions. A validator should not impose a universal rule where none exists.

    Instead, it should identify the relevant condition, record the rule being applied, and send ambiguous cases for review.

    5. Layer four: validate the provenance of assumptions


    A financial model can pass every arithmetic test and still fail as an analytical tool.

    The reason is straightforward: calculations cannot establish the truth of their inputs.

    For every material assumption, a validation system should try to preserve:

    • The value and unit.
    • The source or origin of the value.
    • The source's date and relevant data period.
    • The geography and asset type, where applicable.
    • The transformation from source evidence to model assumption.
    • Any manual adjustment made by the analyst.
    • The model locations that depend on the assumption.

    Consider a construction cost assumption of £1,800 per square metre. A validator might confirm that the figure is numeric, the unit is recorded, and the workbook uses it consistently. Those checks do not establish whether the figure is suitable for the location, asset type, specification, and cost period. That question requires appropriate evidence and professional interpretation.

    An LLM may help extract candidate assumptions from documents or explain how a value is used in a workbook. The extracted result should still be checked against its source, and the resulting assumption should remain distinguishable from the underlying evidence.
    A useful principle is:
    Traceability makes an assumption inspectable. It does not make the assumption correct.

    6. Layer five: make human review a defined state transition


    Human review should not be an informal final glance after an automated process has already treated the model as complete.

    A practical workflow can represent validation explicitly:

    GENERATED
    |
    v
    STRUCTURE_CHECKED
    |
    v
    CALCULATIONS_CHECKED
    |
    v
    DOMAIN_CHECKED
    |
    v
    EVIDENCE_REVIEWED
    |
    v
    HUMAN_APPROVAL_REQUIRED
    |
    +----> APPROVED FOR THE DEFINED PURPOSE
    |
    +----> RETURNED FOR CORRECTION
    |
    +----> BLOCKED: UNRESOLVED ISSUE

    The states are illustrative, but the distinction matters. A successful automated test should not automatically mean that a model is approved. Approval should be scoped to a defined version of the workbook, its assumptions, its evidence, and its intended use.
    A reviewer should be able to see:

    1. What was generated.
    2. Which automated checks passed.
    3. Which checks failed or were skipped.
    4. Which assumptions lack adequate evidence.
    5. What changed after a correction.
    6. Who approved the model and for what purpose.

    If a material input or formula changes after approval, the system should identify which checks need to run again and whether the earlier approval remains valid. This is where versioning and change tracking become part of model governance rather than administrative overhead.

    7. Design the exception path before the success path


    Validation is often designed around a clean example: the model is generated, every check passes, and the user receives the output. Production systems need to handle less convenient outcomes.

    A failed check should produce actionable information. “Validation failed” is less useful than “The unit count in the sales schedule differs from the unit schedule; review the linked inputs before approving revenue.”

    Similarly, a warning should not disappear simply because a later stage of the workflow succeeds. For auditability, preserve the check identifier, the model version, the result, the relevant evidence, and the resolution.

    8. Measure validation quality without inventing an accuracy score


    A single “model accuracy” percentage can hide important distinctions. A workbook might pass every arithmetic test while containing several unsupported assumptions. Another may contain a harmless formatting issue but have fully reconciled calculations and well-documented inputs.

    A more useful validation report separates categories:

    • Structural checks passed or failed.
    • Deterministic calculation checks passed or failed.
    • Domain checks passed, failed, or were not applicable.
    • Assumptions with verified, missing, or conflicting evidence.
    • Open exceptions and their severity.
    • Human review status.
    • The scope and version of the approved output.

    If the system is evaluated over time, track false negatives and false positives for individual validation rules against a reviewed test set. Record the test cases, expected outcomes, rule versions, and known limitations.

    Do not interpret a high pass rate as proof that the model is correct. It may simply mean that the checks cover only a narrow set of failure modes.

    The purpose of validation is to make known risks visible and testable, not to manufacture certainty.

    9. A practical implementation sequence


    A team introducing validation around AI-generated financial models does not need to automate every review step at once.

    A sensible sequence is:

    1. Define the contract. Specify the required inputs, output fields, units, and missing-value behaviour.
    2. Write deterministic tests. Start with totals, reconciliations, formula ranges, and independent calculations.
    3. Add domain checks. Encode known cross-schedule relationships and clearly defined constraints.
    4. Track provenance. Associate material assumptions with sources, dates, units, and transformations.
    5. Introduce exception handling. Make failures explicit and prevent unresolved material issues from being silently treated as passed.
    6. Define human approval. Record the reviewer, workbook version, purpose, and outstanding qualifications.
    7. Build a regression suite. Retain representative valid and invalid examples and rerun the checks when the generation logic or validation rules change.

    The test suite should include deliberate failures, not only successful examples. Examples might include missing finance assumptions, inconsistent unit counts, a formula referencing the wrong period, and a source whose geography does not match the project.

    This helps test whether the validation process detects the intended problem rather than merely accepting a plausible-looking output.

    Conclusion


    Human-in-the-loop validation is not a person checking an AI result after the important work is finished. It is a system design in which deterministic rules handle deterministic questions, domain checks expose inconsistencies, evidence is kept separate from assumptions, and a human reviewer remains accountable for unresolved judgments.

    For financial modelling, that distinction is material. A workbook can be well-formed without being economically sound, mathematically consistent without being supported by market evidence, and ready for review without being ready for a decision.

    The objective is not to make every AI-generated model look trustworthy. It is to make the model's logic, assumptions, limitations, and unresolved issues sufficiently visible that a professional can challenge it before relying on the result.#feasibility #realestate #ai #financial #software #coding #development #engineering #inclusive #community
    Human-in-the-Loop Validation for AI-Generated Financial Models

  11. #Arts #Fashion #NVO987 #Culture #NEXARIUM
    What Not Dating Is Really Like, According to Relationship Experts
    Spoiler: You can want sex and love while not actively looking for all of it.
    cosmopolitan.com/relationships

  12. Hackers Use Malicious Instagram Ads to Infect iPhones With Spyware Without a Click

    Hackers are using malicious Instagram advertisements to infect vulnerable iPhones with spyware while users scroll through their feeds. A documented attack used a World Cup advertisement to deliver the P7 variant of DarkSword, exposing sensitive information without requiring the victim to tap the ad, download a file, or install an application. The findings show how […] The post Hackers Use Malicious Instagram Ads to Infect iPhones With Spyware Without a Click appeared first on Cyber Security News .

    Pulse ID: 6ae02edf3afbfc8b42023841
    Pulse Link: otx.alienvault.com/pulse/6ae02
    Pulse Author: CyberHunter_NL
    Created: 2026-10-27 04:55:59

    Be advised, this data is unverified and should be considered preliminary. Always do further verification.

    #Instagram #SpyWare #Deliver #OTX #CyberHunter_NL

  13. Most deployment advice starts with architecture. Draw the boxes, pick the services, ship it. I believed that was the whole job until a client project showed me otherwise.

    Two projects can have the same architecture diagram and still need very different deployments. What decides it is the features of the app and the shape of its traffic. This post is about the project that made that clear to me, and how I ended up on EC2 with Ansible instead of the more fashionable options.

    The client


    I took over a project and moved it onto EC2 first. The brief was short: keep it secure, and don't let it fall over when traffic jumps.

    Traffic was not large, about 3K users a day. What made it interesting was how it moved:

    WhenTrafficWhat it meantNormal dayAbout 3K usersTwo modest servers are enoughProduct releases/eventsDouble or more, in burstsExtra capacity for a few hours, not all yearDecember holidaysA different pattern againDon't pay for peak capacity every month


    The important detail is that I knew these dates in advance. Fixed servers would have been either oversized all year or too small on release day.

    Which setup for which situation


    Before the details, here is the short version. Find the row closest to your project.

    Your project looks likeGo forTrade-offSteady traffic, small team, spikes on known datesEC2 + Auto Scaling + ALBCheapest at steady load, but you patch the serversSudden, unpredictable spikesECS on FargateNothing to patch, but a higher price per unitSmall event-driven jobs (resize an image, send an email)LambdaPay only when it runs, but 15 minute limit and DB connection pressureWebSockets or long-lived connectionsFargate or EC2Connections stay open, a poor fit for LambdaHeavy 24/7 loadECS on EC2 + Savings PlansBest price at constant load, but two layers to scaleA team already living in KubernetesEKSReuses existing skills, big operational cost


    ECS and Fargate are sometimes presented as rivals. They are not: ECS is the orchestrator, and Fargate is one way for ECS to run your containers.

    The app has to be ready first


    Before anyone touches a server, a few things must be true in the code. I have seen more "infrastructure problems" caused by these than by AWS itself.

    • The app is stateless. If sessions or files live on one machine's disk, you cannot run two copies. Sessions go in JWT or Redis, uploads go to S3.
    • There is a /health endpoint. The load balancer and Auto Scaling both rely on it to decide whether an instance is alive.
    • I know my database connection limit. Every new instance brings its own connection pool. Ten instances with a pool of 20 is 200 connections, and the database may not allow that.
    • Cron jobs run in one place. Otherwise they fire on every copy of the API at the same time.

    None of this is infrastructure work. It is plain application code, and it decides what you can do afterwards.

    The options, judged for this client

    OptionIn its favourAgainst itFor this clientEC2 + Auto Scaling + ALBCheapest at steady load, full control, my Ansible roles work as they areI patch the OS, new instances take minutes to boot, I tune the scalingMy pickECS on FargateNothing to patch, scales per taskRoughly 15 to 40% more per unit than raw EC2, no host access, no GPURight if nobody wants to own serversLambdaNear-zero cost when idle, instant scaling15 minute limit, DB connection pressure, awkward for WebSocketsSide jobs onlyEKSHuge ecosystemSteep learning curve and running costOverkill


    I chose EC2 with Auto Scaling for three reasons. The traffic is small, I know the spike dates, and I already had Ansible roles that configure the servers. Scheduled scaling covers the known spikes without paying a Fargate premium all year. If nobody on the team wanted to own patching, I would flip that decision and use Fargate without a second thought.

    Autoscaling: what scales on what


    This is the part where being a developer helped most, because several of the real problems live in the app and not in AWS.

    Minimum capacity. Two instances across two availability zones. If one dies, the site stays up.

    The scaling rule. I use target tracking, either CPU around 60% or ALB requests per target. Requests per target follows actual traffic, so there are no thresholds to guess.

    Known events. A scheduled action raises the minimum before a release or before December. A new instance takes minutes to become useful, so waiting for the spike to start is already too late.

    Boot time. I bake an AMI after the Ansible role runs. New servers start ready instead of installing everything at boot.

    Health checks. Use the ELB health check type, pointed at /health, so a broken instance is replaced automatically.

    The database. Compare the maximum connections against instances multiplied by pool size. This is the most common surprise when a Node app scales out.

    One Node-specific trap is worth knowing. Node runs on a single core per process. On a 2-vCPU instance running one Node process, CPU may never go much past 50%, so a CPU-based rule never fires. Run one process per core (PM2 cluster mode works) or scale on requests per target instead.

    Before any release day, load test staging with k6 or Artillery. It tells you more than any estimate.

    Security: EC2 versus Fargate

    ConcernEC2FargateOS patchingMeAWSSSH accessI have to lock it downNone (ECS Exec if you need a shell)IsolationI manage the shared hostEach task is isolatedIAMInstance roleTask role per serviceHost-level security agentsPossibleNot possible


    If compliance requires an agent on the host, that points to EC2. Otherwise Fargate gives you a smaller attack surface for less work.

    On EC2 my Ansible hardening role covers the basics: key-only SSH with root login disabled and no public SSH (Session Manager or a locked-down IP), servers and database in private subnets with security groups chained from ALB to app to DB, secrets kept in Ansible Vault or Secrets Manager and never in the repo, and automated RDS backups together with a restore I have actually tested.

    Ansible and Terraform: who does what


    I work with Ansible, and this setup lives in it.

    • Roles configure the servers: packages, users, SSH hardening, nginx, Docker.
    • A playbook deploys a new version one server at a time, with a health check between each.
    • Ansible Vault holds the deploy-time secrets.
    • A dynamic inventory (aws_ec2) finds the instances that Auto Scaling created, by tag. Instances come and go, so a hard-coded host list breaks quickly.
    • The same roles bake the AMI.

    Before changing anything, I preview it:

    ansible-playbook -i inventory/prod.aws_ec2.yml site.yml --check --diff

    And this is a trimmed version of the deploy playbook:

    - hosts: web
    become: true
    serial: 1 # one server at a time, the ALB keeps traffic on healthy ones
    vars_files:
    - secrets.yml # encrypted with ansible-vault

    tasks:
    - name: Run the new version of the API
    community.docker.docker_container:
    name: api
    image: "{{ app_image }}:{{ app_version }}"
    state: started
    recreate: true
    restart_policy: always
    published_ports: ["3000:3000"]
    env:
    DB_HOST: "{{ db_host }}"
    DB_PASSWORD: "{{ db_password }}"

    - name: Wait until /health answers
    ansible.builtin.uri:
    url: http://localhost:3000/health
    status_code: 200
    register: health
    retries: 10
    delay: 3
    until: health.status == 200

    I don't use Terraform on this project, but it is worth saying where it fits. It is strong at creating and tracking cloud resources such as the VPC, ALB, RDS and IAM, with state you can review. A team that rebuilds environments often may prefer it for that layer and keep Ansible for what runs inside the servers. The two are not rivals.

    When I would choose differently


    • If nobody wants to patch servers, or traffic becomes unpredictable, I would move to Fargate.
    • If the load turns into a heavy 24/7 one, I would look at ECS on EC2 with Savings Plans.
    • If the team grows into Kubernetes, EKS starts to make sense.
    • For small side tasks like image resizing or emails, I would add Lambda next to the main app.


    What I took from it


    The server was never the real decision. The traffic shape, the app being ready to scale, and a setup I can repeat with one command were. Pick the simplest option that survives your busiest day, keep it in code, and load test it before that day arrives.

    If you have deployed for a client with spiky traffic, I would like to hear what you chose and what you would change.#aws #node #ansible #webdev #software #coding #development #engineering #inclusive #community
    Same Architecture, Different Deployment: Why Traffic Shape Beats Diagrams


  14. October 27th

    As a writer, what do you need right now?

    A whole month of vacation with nothing to do.
    But it's almost the end of the year, so my workplace needs my efforts for inventory and year-end closing. Shame.

  15. #Kyiv feels like a surreal train that never stops.

    The weirdest carriage is #sex — the kind that makes Cronenberg's Crash and Cavani's The Night Porter look almost wholesome.

    Fucking through ballistic alerts while a missile hits the next building isn’t resilience. It’s a twisted, multi-layered addiction. And somehow we’re still here, still doing it.

    #writingcommunity #blog #art #photography #ukraine

  16. Tencent's Hunyuan team has open-sourced Hy-SimulMT, a speech-to-speech interpreter that translates Chinese and English while the speaker is still talking, cloning the voice in real time. Tencent puts the lag at about 3 seconds on the RealSI benchmark, below the 4 to 5 seconds human interpreters need. It is free in the Hy Translate app.

    pandaily.com/tencent-hunyuan-h

    #China #Tech #AI

  17. Why Does Trump Get a Pass? Patriarchy and the Double Standard Protecting His Power

    Why does Trump get a pass? This commentary examines patriarchy, male privilege, and the political double standard that rewards domination while demanding more from women.

    egbertowillies.com/2026/10/26/

  18. FINALLY I GET TO POST ONE OF THESE AGAIN!

    Thank God. Even with 2 winning teams in the next 6, I feel very little confidence. At least we put together a whole game. #Cowboys #DallasCowboys #CowboysNation #HowBoutThemCowboys #AmericasTeam #NFL #Week7 #DALvsPHI #CryEaglesCry

  19. Why Does Trump Get a Pass? Patriarchy and the Double Standard Protecting His Power

    Why does Trump get a pass? This commentary examines patriarchy, male privilege, and the political double standard that rewards domination while demanding more from women.

    #authoritarianism #democracy #DonaldTrump #EgbertoWillies #genderDoubleStandards #genderEquality #MAGA #malePrivilege #misogyny #patriarchy #politicalAnalysis #PoliticsDoneRight #powerfulMen #progressiveCommentary #sexismInPolitics #TrumpAccountability #TrumpCriticism #womenInLeadership wp.me/p1OjMZ-phW
  20. @jasonbeets Lean D sounds about right from where I sit. I've got Flanagan at 64 in 100 and D+2.0, a bit tighter than her poll average (D+3.4 across 17 polls), since the polls aren't the whole model. #Minnesota

  21. I moved a client's marketing site to Astro a few weeks ago. Astro 7 was the reason — the Rust compiler and stable route caching cut the build from ~4 minutes to about 90 seconds. Fast builds were the whole point.

    Then I hit the one thing Astro can't do out of the box: accept a contact form submission.

    Here's the honest version of what I tried, what worked, and the two gotchas that cost me an afternoon.

    Why Astro forms trip people up


    Astro is component-first and ships almost zero client-side JavaScript. Most "add a form" tutorials assume a Node runtime. Three things follow from that, and they're the reason this feels different from a Next.js or Rails form:

    1. A form has to POST somewhere. The action attribute is just a URL. There's no "submit to Astro" without an adapter.
    2. Astro Actions need a server adapter. They're stable and genuinely type-safe, but they require output: 'server' or 'hybrid' plus @astrojs/vercel / netlify / cloudflare / node. On the default output: 'static' build, they don't run.
    3. No spam filtering is included. Neither Actions nor a plain <form> ships with detection. That's on you.


    What I tried (and why I backed out)


    Astro Actions. Beautiful DX, end-to-end typed. But to handle one 3-field contact form I had to flip output: 'static' to 'server', add an adapter, manage secrets, and accept cold starts. My "static site" now had a server. That's a lot of surface area for a page that asks for a name, an email, and a message.

    Netlify Forms. Five minutes, genuinely nice — but the site was on Vercel, so it was a non-starter. The lock-in matters more than the price tag.

    Cloudflare Turnstile + Workers. Turnstile is a great CAPTCHA (free, accessible, no image grids). But to use it on Vercel I now maintain a Worker. I'd traded an adapter for a different server to maintain.

    What actually shipped: a plain HTML form POSTing to an external endpoint. No adapter, no server, no secrets.

    The form


    This is the entire integration. src/components/ContactForm.astro:

    <form
    action="https://api.usesmartform.com/api/v1/f/YOUR_FORM_ID"
    method="POST"
    >
    <label for="name">Name</label>
    <input id="name" name="name" type="text" required minlength="2" />

    <label for="email">Email</label>
    <input id="email" name="email" type="email" required />

    <label for="message">Message</label>
    <textarea id="message" name="message" rows="6" required minlength="10"></textarea>

    {/* Honeypot — bots fill it, humans never see it */}
    <input type="text" name="_gotcha" style="display:none" tabindex="-1" autocomplete="off" />

    {/* Where to send the browser after a successful submit */}
    <input type="hidden" name="_next" value="https://yoursite.com/thanks" />

    <button type="submit">Send Message</button>
    </form>

    Drop it in a page and you're done. Astro's whole pitch is zero JS by default, and a method="POST" form navigates to the endpoint and back — the service returns a 302 to your _next URL. No client-side state, no hydration cost, no framework.

    It doesn't matter whether the surrounding page is an Astro component or a React/Vue/Svelte island. As long as the rendered DOM contains <form action="..." method="POST">, the submission lands.

    Gotcha #1: the Accept header


    If you want an inline success message instead of a page redirect, use fetch. The first version I wrote returned a 302, and fetch followed it cross-origin into a CORS error that looked like a server outage.

    const res = await fetch("https://api.usesmartform.com/api/v1/f/YOUR_FORM_ID", {
    method: "POST",
    body: new FormData(form),
    headers: { Accept: "application/json" }, // ← required
    });

    if (res.ok) {
    const data = await res.json(); // includes next_url
    status.textContent = "Thanks — we'll get back to you shortly.";
    form.reset();
    }

    Always send Accept: application/json. You get JSON back (including next_url) instead of a redirect.

    Gotcha #2: the honeypot needs three attributes


    display:none alone isn't enough. I had style="display:none" and still saw bots post clean submissions, because they'd learned to skip hidden inputs. Adding tabindex="-1" (keeps it out of keyboard nav) and autocomplete="off" (keeps password managers out) closed the gap.

    To actually test the filter I removed the honeypot for a day, watched bot traffic arrive, then put it back and watched those same submissions get dropped server-side — silently, with no email and no quota deduction.

    Spam: layer it, don't pick one

    MethodFreeUser frictionCatchesHoneypot fieldYesNoneThe dumbest botsCloudflare TurnstileYes (≤20 widgets)Almost noneBrowser-level botsreCAPTCHA v3Yes (≤1M/mo)NoneScript bots, but flags real users sometimesML filter (server-side)YesNoneTargeted / scripted spam


    What I ended up with: honeypot as the cheap first layer, a server-side classifier behind it, and Turnstile in front only on the demo-request form where a false positive costs us a lead.

    When I'd use Astro Actions instead


    If you already have output: 'server' and an adapter, use Astro Actions. If you're tying submissions to a logged-in user, or the form writes to your database, Actions is the right tool. I'm not against it — I just didn't want to add a server to a static site for one contact form.

    It's also fine to mix. That site uses Actions for in-product feedback and an external endpoint for the marketing contact form. They're independent.

    Verdict


    For a static Astro site with one marketing form, the whole thing should be ~20 lines of HTML and zero infrastructure. That's what I shipped. The hosted-service part is my own tool, so treat that section as biased — but the underlying pattern (a plain POST to an endpoint) works with any provider, including one you run yourself.

    I didn't want to write this as a sales pitch, but full disclosure: the external endpoint I used is my own product, SmartForm AI. The plain POST pattern works with any provider. If you want the full comparison matrix, I put the long-form version on my blog (linked in the comments).

    Happy to answer questions in the comments.#astro #webdev #frontend #tutorial #software #coding #development #engineering #inclusive #community
    I Added a Contact Form to an Astro Site Without a Backend

  22. Enes Kanter Freedom, one of two former NBA players who have sought to enter the 2027 WNBA draft by claiming to be women, invoked several anti-transgender tropes while criticizing the league for declaring him ineligible.

    metroweekly.com/2026/10/enes-k

    #transgender #trans #LGBTQ

  23. #UniLife #Lesbian #Wound
    So I had to take Jennie with me this morning the doctor's office. She watched some anime on her phone while we waited. I watched the first episode of last season's Taskmaster.
    So I was getting my foot wound treated. They had to debride the wound, that means cut away the dead or ill flesh so I'm left only with healthy flesh, then they wrapped it up, and then they gave me a air-cast which I have to wear for a couple of weeks. I also have to stay off the foot as much as possible. Afterwards I took Jennie to A&W for breakfast, bacon & Eggers and hash browns before I took her to school, I had to hobble into the main office to sign her in. Since then I've been in bed. Hello boredom!

  24. Trump’s Inflation Lies Collapse: The Numbers Expose His Economic Con

    Trump’s inflation claims collapse under scrutiny. Official data expose the false history, while profit research reveals how corporations helped squeeze working families.

    egbertowillies.com/2026/10/26/

  25. Watti Update: Now anyone can bring my real robot to life! reddit.com/r/robotics/comments Watti update! Some of you have been following this project for a while, and today I have something exciting to share! I've temporarily opened Watti Studio to everyone! You can now create your own animations directly in your browser, on your computer or phone. Move the virtual robot, add keyframes, adjust the timing, and bring your

  26. Well, I want HotSyncing my Palm OS devices to work on FreeBSD, so I guess I'm about to learn a whole lot about FreeBSD drivers.

  27. @bastardsheep
    Horrifying. But thanks for posting about it & kudos to the person who did the research in such a creative way (finally AI good news story).

    Read through the whole thread hoping to find news on a tv that doesn’t do the sneaky stuff but was disappointed.

    Now wondering if Choice is aware of these issues and/or has integrated them into a review of tvs.

    #Choice #tvs #sneakyStuff

Share on Mastodon

Enter the server where you have an account.