home.social

Search

1000 results for “three_star_dave”

  1. Three new cougar kittens in the news.

    The Wildlife Science Center in Stacy, Minn., has welcomed three new cougar kittens.
    By Anthony Soufflé
    The Minnesota Star Tribune

  2. Mississauga’s Pitch Pine Crescent: Three mysterious deaths

    Host Amy Dempsey Raven, an investigative reporter for the Toronto Star, spent more than a decade asking…
    #NewsBeep #News #Mississauga #CA #Canada #mississauga
    newsbeep.com/ca/938286/

  3. Mississauga’s Pitch Pine Crescent: Three mysterious deaths

    Host Amy Dempsey Raven, an investigative reporter for the Toronto Star, spent more than a decade asking…
    #Canada #Mississauga
    europesays.com/canada/255134/

  4. The Rams have managed to transform themselves from a superteam to a midteam
    By Alex Kirshner

    Los Angeles were tipped as a Super Bowl contender after assembling a star studded lineup. Now they’ve lost three of their last four games

    theguardian.com/sport/2026/oct

    #LosAngelesRams #NFL #USsports #ArizonaCardinals #Sport #WestCoast #TheGuardian #AlexKirshner

  5. October 21, 2026

    New Ghosts Revealed in Cassiopeia
    * Credit & Copyright: Louis Leroux-Géré, Thibault Rouillée, Vincent Martin, Cédric de Decker (Starfront Observatories)
    instagram.com/lrx.photo/
    instagram.com/tybr
    instagram.com/vincent.astro/
    instagram.com/lesphotosdecedri
    starfront.space/

    Explanation:
    Jinkies, look at all those ghosts! It took 100 hours of observation and a special oxygen filter for today’s image to capture three faint nebulas hidden in the Cassiopeia constellation. IC 59 and IC 63, the original Ghosts of Cassiopeia, haunt the region near multi-star system γ Cassiopeia. Energetic light from γ Cassiopeia causes the hydrogen gas in IC 59 and 63 to glow red. Their dust reflects and scatters some blue-ish white starlight. Newly discovered Objects 1, 2, and 3 appear as blue phantoms, revealing the presence of ionized oxygen. But ionized by what? Like at the bow of a speeding boat, γ Cassiopeia may be piling up material as the system moves through interstellar gas and dust. It follows that Object 3 may be the compressed and heated oxygen of that bow shock. Object 1 could be a planetary nebula if a central white dwarf is identified. The origins of these astronomical apparitions remain a mystery to be solved.

    science.nasa.gov/image-article

    #space #nebula #astrophotography #photography #science #nature #ESA #NASA #apod

  6. Our Mastodon instance mementomori.social will always offer themes users can choose from. Currently, the following are available:

    - Mastodon
    - Mastodon Bird UI
    - Mastodon Bird UI Accessible (large fonts, high contrast, color-blind friendly, including distinct colors for multiple hashtags and handles)
    - Mastodon Bird UI Accessible Ultra (includes everything above, plus additional support for tunnel vision and deafblindness)

    I hope we can continue supporting all of them after v5. Most likely, star favorites will have to go. We have already been using hearts for favorites by default for three years now.

    #MementomoriSocial #Mastodon #MastodonBirdUI #BirdUI

  7. Davies ensures Spurs off the bottom after first win of season against Coventry
    By Jacob Steinberg at the Tottenham Hotspur Stadium

    Tottenham are level with Beyoncé at last. Progress is represented in Roberto De Zerbi’s side earning only their sixth home win in the Premier League since November 2024. Cynics will point out that this spectacular stadium has hosted as many of the American pop star’s gigs during that time, but Spurs are finally singing a happier tune after dragging themselves out of the bottom three thanks to a messy but gritty 3-1 win over Coventry.

    theguardian.com/football/2026/

    #PremierLeague #TottenhamHotspur #CoventryCity #Football #Sport #TheGuardian #JacobSteinbergattheTottenhamHotspurStadium

  8. Coolify: The Open-Source Self-Hosted PaaS That Replaces Vercel, Heroku, and Netlify


    You deploy to Vercel. It works. Then the bill arrives. Or you hit a limit. Or you need a database that isn't on their approved list. Or you just want to run something on a $5 VPS you already own.

    Most developers know the managed PaaS names. Fewer know there's a 63k-star open-source alternative that gives you the same push-to-deploy experience on your own servers — with 360+ one-click services, automatic HTTPS, preview deployments, and zero vendor lock-in.

    That alternative is Coolify.

    What Coolify Actually Is


    Coolify is an open-source, self-hostable Platform-as-a-Service. You install it on a server (VPS, bare metal, Raspberry Pi, anything with SSH), and it becomes your personal Vercel/Heroku/Netlify.

    But the architecture is fundamentally different from managed platforms:

    Managed PaaS (Vercel/Heroku)Coolify (Self-Hosted)Control plane + runtime + infrastructure bundledControl plane only — you provide the serversYou deploy to their cloudYou deploy through Coolify to your serversVendor lock-in: configs, data, routing all live with themYour configs stay on your servers. Stop using Coolify? Your apps keep running.Pricing scales with usageFree (Apache 2.0). You pay only for your VPS.


    The key insight: Coolify separates the control plane from the workload runtime. The Coolify instance stores configuration and coordinates actions via SSH. Docker on each connected server runs your actual applications, databases, and services.

    Your application traffic never passes through the Coolify server. Requests hit the reverse proxy (Traefik or Caddy) on the resource server directly.

    The Architecture: Control Path vs. Traffic Path


    This is the part most developers misunderstand.

    Control Path (Coolify → Your Server)


    • You click "Deploy" in the dashboard (or push to Git)
    • Coolify reads config from its PostgreSQL database
    • Queues the job via Laravel Horizon + Redis
    • SSHes into the target server
    • Runs Docker commands: build, pull, start containers, configure networks


    Traffic Path (User → Your App)


    • DNS points your domain to the resource server (not the Coolify server)
    • coolify-proxy container (Traefik/Caddy) terminates TLS
    • Routes request over Docker network to your app container
    • Coolify control plane is not in the request path

    This means:

    • If the Coolify dashboard goes down, your running apps stay up
    • If you lose SSH to a server, existing containers keep serving traffic
    • You can run Coolify on one $5 VPS and deploy to ten other servers


    What You Can Deploy


    Applications (from Git):

    • Static sites (Next.js, Astro, Vite, Hugo, etc.)
    • Node.js, Python, Go, Rust, PHP, Ruby, Java, .NET, Bun, Deno
    • Dockerfile, Docker Compose, Nixpacks, Railpack, or prebuilt images
    • Automatic framework detection via Nixpacks/Railpack

    Databases (one-click, managed):

    • PostgreSQL, MySQL, MariaDB, MongoDB, Redis, KeyDB, Dragonfly, ClickHouse
    • Persistent volumes, automated S3-compatible backups, optional public access

    360+ One-Click Services:

    • Analytics: Plausible, Umami, PostHog
    • Auth: Logto, PocketBase, Authentik
    • Databases: Supabase, NocoDB, Baserow
    • AI: Ollama, Open WebUI, AnythingLLM
    • Dev tools: GitLab, Gitea, Drone, Woodpecker
    • Productivity: Nextcloud, Outline, Cal.com, N8n
    • Monitoring: Uptime Kuma, Grafana, Prometheus
    • And hundreds more — each with generated credentials, persistent storage, and health checks


    Build Methods: How Your Code Becomes a Container


    Coolify doesn't force one build system. Pick per project:

    MethodUse WhenNixpacksZero-config builds for most frameworks (auto-detects Node, Python, Go, etc.)RailpackFaster, Rust-based alternative to Nixpacks (beta)DockerfileFull control — you write the DockerfileDocker ComposeMulti-container apps (app + db + redis + worker)StaticPre-built static sites (output folder → nginx)Docker ImagePull ghcr.io/user/app:v1.2.3 — no build step


    Smart caching: For Git sources using Nixpacks/Railpack/Dockerfile, Coolify tags images with the commit SHA. If the commit and build config haven't changed, it skips the build entirely and reuses the existing image.

    Build servers: Offload builds to a dedicated server (saves resources on small VPS). The build server pushes the image to a registry; deployment servers pull it.

    Deployment Strategies: Zero-Downtime by Default


    For single-container apps, Coolify uses rolling updates:

    1. Build/pull new image (current container keeps running)
    2. Start new container on same Docker network
    3. If health check configured → wait for healthy
    4. Switch proxy routing to new container
    5. Remove old container

    Stop-then-start fallback when rolling isn't possible (host port mappings, fixed container names, preview deployments).

    Docker Compose uses docker compose up reconciliation. Swarm uses docker stack deploy.

    Instant rollback: Every successful deployment retains its image. One click → previous version running in seconds. (Does not restore database data — keep separate backups.)

    Networking: Three Paths, Clear Boundaries

    1. Public HTTP/HTTPS (via Coolify Proxy)


    • Domain → DNS → Resource Server IP
    • coolify-proxy (Traefik/Caddy) on port 80/443
    • TLS via Let's Encrypt (automatic)
    • Proxy forwards over Docker network to container port


    2. Private Container Traffic


    • Shared Docker network (coolify by default)
    • Containers talk via service name + internal port
    • No public exposure, no host ports
    • Databases, internal APIs, worker queues


    3. Direct Host Ports


    • host_port:container_port mapping
    • Bypasses proxy entirely
    • For non-HTTP protocols (TCP/UDP, databases with external clients)
    • Disables rolling updates for that resource

    Your responsibility: DNS records, firewall/security groups (80, 443, SSH, any direct ports), making apps listen on the configured container port.

    Data Persistence: What Survives a Redeploy

    LayerLocationSurvives Redeploy?Coolify config (projects, env vars, credentials)Coolify instance (PostgreSQL)YesDocker images, build artifacts, containersConnected serverImages yes, containers replacedApplication data (uploads, SQLite, generated files)Docker volumes / bind mountsYes — if configuredDatabase dataDocker volumes or external managed DBYesReverse proxy config + TLS certsResource serverYes


    Critical: Unmounted container filesystem data is lost on redeploy. Configure persistent volumes for anything that must survive.

    The MCP Integration: AI Agents That Can Deploy


    Coolify exposes an MCP (Model Context Protocol) server at https://your-coolify/mcp. Connect Claude, Cursor, or any MCP client — your AI agent can:

    • List resources, servers, deployments
    • Trigger deployments
    • Read logs, restart services
    • Troubleshoot failed deployments

    All with the same API tokens and team permissions you already use. This is a genuinely useful AI integration — not a gimmick.

    What You Actually Need to Run It


    Minimum self-hosted setup:

    • 1 server for Coolify (2 GB RAM, 2 vCPU, 30 GB disk)
    • 1+ servers for deployed resources (scale as needed)
    • Docker Engine 24+
    • SSH access (key-based)
    • Domain for the Coolify dashboard (for HTTPS)

    Install:

    curl -fsSL cdn.coollabs.io/coolify/instal… | bash

    That's it. The script sets up the three base containers (coolify, coolify-db, coolify-redis), the reverse proxy, and the coolify Docker network.

    What Coolify Does NOT Give You (And That's Fine)


    • Managed infrastructure — you provision, secure, and monitor your VPS
    • Global edge network — your app runs where your server is (add Cloudflare CDN if needed)
    • Automatic horizontal scaling — you add servers, Coolify deploys to them
    • Built-in CI/CD beyond Git push — webhooks integrate with GitHub Actions/GitLab CI
    • SLA or support contract — it's open source (Coolify Cloud exists if you want managed)


    The Trade-offs, Honestly

    Coolify WinsManaged PaaS WinsZero vendor lock-inZero ops burdenRun anything Docker supportsGlobal edge by defaultPredictable cost (VPS pricing)Automatic scalingFull data ownershipManaged databases with HA360+ services one-clickEnterprise compliance certsMCP for AI agentsTeam SSO/SAML (Coolify has 2FA + OAuth)

    Why This Matters for Developers


    You've deployed to Vercel. You've paid for Heroku dynos. You've configured Netlify build plugins.

    Coolify lets you own the platform layer without building it from scratch. It's not "Kubernetes the hard way" — it's a Laravel + Docker control plane that speaks SSH and gives you a dashboard, API, CLI, and now MCP.

    For side projects, client work, internal tools, or production apps where you want control over infrastructure: Coolify is the middle ground between "manual Docker on a VPS" and "$500/month managed PaaS."

    The repository: github.com/coollabsio/coolify (63.2k stars, 698 contributors, Apache 2.0)#opensource #selfhosted #paas #docker #software #coding #development #engineering #inclusive #community
    Coolify: The Open-Source Self-Hosted PaaS That Replaces Vercel, Heroku, and Netlify

  9. Once you've got filtering and grouping down, SQL starts asking harder questions. Which doctor handles the most visits? Which department has the most unpaid bills? You can't answer those with a single SELECT ... WHERE. You need window functions, joins, CTEs and subqueries.

    I worked through all four on a real dataset: 672 visits from a mock data: Hospital Health Records workbook, split into a star schema (visits_fact plus dim_patients, dim_doctors and dim_departments). Everything below is PostgreSQL.

    Window functions: keep the rows, add the context


    GROUP BY squashes rows together. A window function doesn't. It calculates across related rows and leaves every row in place, so you can see detail and group level numbers side by side.

    SELECT doctor_id, visit_id, total_bill_kes,
    SUM(total_bill_kes) OVER (PARTITION BY doctor_id) AS doctor_total
    FROM visits_fact;

    ROW_NUMBER is great for "latest visit per doctor". RANK leaves gaps after ties (1, 2, 2, 4), while DENSE_RANK doesn't (1, 2, 2, 3). LAG and LEAD let you compare a row with its neighbour, like month on month revenue. One trap: with LAST_VALUE, always spell out the frame, because the default stops at the current row. For running totals, use ROWS rather than the default RANGE, or tied dates will make your numbers jump.

    Joins: it's all about the unmatched rows


    Every join type answers the same question: what happens to rows with no match? INNER drops them. LEFT keeps the left side's rows. FULL OUTER keeps both. CROSS pairs everything with everything, so use it deliberately.

    The mistake that got me: putting a filter on the right hand table in WHERE instead of ON. It quietly turns your LEFT JOIN into an inner join.

    SELECT d.doctor_name, COUNT(v.visit_id) AS visits_2025
    FROM dim_doctors d
    LEFT JOIN visits_fact v
    ON v.doctor_id = d.doctor_id AND v.visit_date >= '2025-01-01'
    GROUP BY d.doctor_name;

    Dr. Mutua had zero visits in 2025, and this is the version that shows him. Use COUNT(v.visit_id), not COUNT(*), or he'll show up with a count of 1.

    CTEs: write SQL in the order you think


    A CTE gives a query a name, so you can build on it step by step. One CTE aggregates, the next calculates, and you can test each on its own. It also gets around not being able to filter on a window function in WHERE. WITH RECURSIVE handles hierarchies and can generate gap free calendars, but always give it a stop condition. A CTE pipeline is how I found that 41.1% of Oncology's billing was still pending.

    Subqueries: a question inside a question


    A scalar subquery returns one value ("bills above the average"). IN, ANY and ALL work with lists. A correlated subquery references the outer row, like bills above their own department's average, which is handy but can be slow on big tables.

    For "not in this list" checks, prefer NOT EXISTS. A single NULL in a NOT IN list makes the whole query return zero rows, with no error to warn you.

    Quick comparison

    ToolCore ideaReach for it when...Watch out forWindow functionsCalculate across rows without collapsing themYou need ranks, running totals or previous/next valuesLAST_VALUE frame; ROWS vs RANGE; no filtering in WHEREJoinsCombine tables by matching keysData lives in more than one tableFilters in WHERE on outer joins; accidental CROSS JOINCTEsName a query, then build on itLogic has several steps or recursionRecursion with no stop conditionSubqueriesA query inside a queryA value or list depends on another queryNOT IN with NULLs; slow correlated queries

    Three habits worth keeping


    Know your grain: decide what one row of the result should represent before you write anything. Test each stage on its own. And try your query on the awkward rows, like ties, NULLs and groups with no data, because that's where the bugs hide.

    What was the SQL mistake that taught you the most? Let's learn from one another.#tables #sql #postgres #software #coding #development #engineering #inclusive #community
    Window Functions, Joins, CTEs and Subqueries

  10. Sense and Sensibility star Daisy Edgar-Jones says there’s ‘more to dig’ out of the classic

    Jane Austen’s Sense and Sensibility has been adapted for the screen, stage and radio multiple times since its…
    #NewsBeep #News #Movies #AU #Australia #BodhiRaeBreathnach #daisyedgarjones #Entertainment #EsmeMillsCreed #jane-austen #senseandsensibility #whatissenseandsensibilityabout
    newsbeep.com/au/934173/

  11. Just putting this out there. I know the head of Star Anvil, they're good people, and they're doing good stuff with the Secret World IP (one of my absolute favs). If you have any interest in modern cryptid and existential horror, check it out!

    #TTRPG #SecretWorld

    www.kickstarter.com/projects/sta...

    Coming soon: THE SECRET WORLD:...

  12. Barcelona AND Real Madrid want Arsenal star with choice obvious

    Barcelona have joined Real Madrid in chasing an Arsenal player, and there’s only one choice he should make…
    #Spain #ES #Europe #Europa #EU #Madrid #AllTheNews #Arsenal #Barcelona #FrontPage #MartínZubimendi #PremierLeague #RealMadrid #SpanishLaLiga #TransferNews
    europesays.com/spain/103005/

  13. The plan has been for #broncos star CB Patrick Surtain II to return against the #Chiefs this weekend. A step in the right direction today, as he was on the practice field. We'll see how the week goes, but there's been optimism for him to return this week I'm told.

  14. New Rumour Says Bungie Is Being Considered To Make Star Wars: Battlefront 3

    Bungie has been struggling through a very rough period lately, having just recently announced new Destiny 2 plans, seemingly as a way of regaining some of the lustre it has lost. And now, there’s an interesting new rumour; Bungie might be in the running to make Star Wars: Battlefront 3.

    Advertisements

    The source of this report is the Quartermann gossip column in EGM #265, the special revival issue released digitally to Compendium backers on 9 October. Jeff Grubb of Game Mess Mornings read out the interesting snippet in the latest episode of the podcast, so full credit to him for the quotes.

    https://www.youtube.com/watch?v=ladA0cCcOpA&t=1329s

    According to the column and its mystery writer/s, Disney is keen on making a third entry in the newer version of the Star Wars: Battlefront franchise.

    “According to what we, your intrepid rumormonger, has dug up, the suits at Lucasfilm have been aggressively deploying probe droids for a development partner to take on the task of creating a follow-up. So far, no one has fully stepped up, but yours truly is hearing two major game studios are circling the project like a couple of snowspeeders,” said the column, as reported by Grubb.

    The first of the two studios is the least surprising; DICE, the same bunch who made the previous two Battlefront games.

    But; “There is another. The Q-Mann hears that if the Force is not entrusted to DICE, it could land at none other than Halo, Destiny, and Marathon developer Bungie.”

    The wording would seem to indicate that Battlefront 3 is not yet in development, but that it is being shopped around. Should Bungie end up getting the license, it could be a massive shake-up for both them and the Battlefront franchise. Despite all their ongoing issues, Bungie is still respected for their shooting gameplay and they have plenty of experience with multiplayer and live-service, albeit less successfully recently.

    The Quartmann column has served up some concrete information in the past, alongside a few duds as well. So don’t take this as confirmation that Battlefront 3 is in the works.

    The real question is why the hell it has taken this long. Battlefront 2 managed to sell 9 million copies in its first quarter after launching. In 2019, EA said Battlefront and Battlefront 2 had sold a combined 33 million copies, and in 2025, Battlefront 2 had a resurgence which was fuelled by Andor’s second season, fan campaigns for a sequel, and a steep Steam discount.

    In other words, they aren’t exactly striking while the iron is hot. But this ties into recent comments from Lucasfilm Games vice president Douglas Reilly, who said the company has become more flexible about which studios it accepts pitches from. Star Wars: Galactic Racer developer Fuse Games is one example of that broader approach, with Reilly suggesting future partnerships will continue to surprise fans. That leaves room for an unexpected developer to take on Battlefront, although he didn’t mention Bungie or the series specifically.

    #bungie #News #PC #PlayStation #StarWars #StarWarsBattlefront #Xbox
  15. How does about 17 km per second still leave Voyager 1 about 75,000 years from the nearest star?

    It's the fastest spacecraft leaving the solar system. But there's a catch: even if it were heading for Proxima Centauri, the trip would span about 40.1 trillion km.

    Space has a scale problem.

    orbitalradar.com/deep-space/vo

    #Voyager #DeepSpace #Stars #SpaceFacts #SpaceFunFact

  16. Understand what THIS is about, because there is always a slender thread of truth behind everything Trump says and does, but Nick Shirley is being PAID BY TRUMP for uncovering a Minneapolis nonprofit "fraud" that was ALREADY FOUND, TRIED AND CONVICTED BACK IN 2022.

    1. The Pre-Existing Federal Case

    The widespread fraud involving Minnesota public funds—most notably the $250 million Feeding Our Future nonprofit scandal—was blown open by federal prosecutors and the FBI starting in 2022. Long before Shirley arrived in Minneapolis, the U.S. Department of Justice had already indicted over 70 individuals and secured dozens of convictions related to Somali-run entities or individuals defrauding government programs.

    2. What Nick Shirley Actually Did

    On December 26, 2025, Shirley released a viral 42-minute video asserting that he had "uncovered" a brand-new $110 million fraud ring by showing up to several local childcare centers during off-hours, filming locked doors, and noting that no children were visible inside. Critics and local news organizations (such as CBS Minnesota and the Minnesota Star-Tribune) immediately pointed out that:
    • The ground had already been broken: Traditional media and federal law enforcement had already thoroughly mapped out and reported on the Child Care Assistance Program (CCAP) loopholes and ongoing fraud reviews.
    • Flawed local methodology: Several centers featured in his video were either already closed by the state prior to his arrival, or were simply visited outside of their normal operating hours.

    ***Ultimately, while Shirley's videos brought massive national and political attention to the situation, the underlying criminal enterprise and systemic fraud network had already been an active, multi-year federal prosecution case since 2022***

    HOW CAN YOU GET PAID FOR DISCOVERING FRAUD THAT IS ALREADY BEEN TRIED AND CONVICTED?

  17. Okay, rant time.

    Star Trek IV: The Journey Home is bad.

    It's bad because it nullifies the sacrifices in the previous movies. You get Spock back, and you get a new Enterprise. It's bad because Shatner barely seems to notice the loss of his son. It's bad because a Star Trek movie shouldn't be set in 1980s San Francisco, it should be set among the stars. It's bad because the whale probe was a repurposed Rama probe for what would have been a far more interesting story put to screen.

    I think people who like Star Trek IV are the kind of people who just don't like Star Trek. And when I hear someone claim that it's the best movie I just lose it. It's nothing compared to Wrath of Khan or 3 and 6.

    There, rant done.

    #StarTrek

  18. #QuestionOfTheDay

    #FavWorkAtoZ

    What is your favorite work/series/art/etc that starts with the letter "J"?

    Also include why you like it!

    The rules are lax, you can include or exclude "A" or "The" as you want (e.g. The Predator can go under T or P). You can also remove the franchise name if you want (e.g. Star Trek: Voyager can go under S or V). Pronouns (I, you, etc) can't be excluded tho.

    Include both the hashtags #FavWorkJ and #FavWorkAtoZ so we can sort the answers.

    You can also answer the previous #FavWorkA, #FavWorkB #FavWorkC etc too if you missed it! There's no deadline.

  19. Your charity acquired the knack
    Of giving politics a snack.
    A judge required two million paid—
    Compulsory compassion! Court-made aid!

    Then came that tape, that priceless class
    In how a star may make a pass:
    A grab, a boast, a famous face—
    Consent reduced to second place.

    You answered women with denials;
    Then Carroll took her claims to trial.
    The civil jury’s finding: true—
    Sexual abuse, defamation too.
    No criminal verdict. Keep that clear.
    Still not your finest souvenir.

    Then Stormy weather, secret pay,
    And records dressed another way.
    Guilty: thirty-four felony counts.
    Some awkward entries in your accounts.

    With Epstein, photographs remain;
    They prove acquaintance, not his chain
    Of crimes as yours. We’ll keep that straight:
    There’s ample fact to contemplate.

    Obama’s birthplace! What a quest!
    The documents could get no rest.
    For years you fed that bogus doubt—
    A welcome mat that said KEEP OUT.

  20. Wednesday Weekly Blogging Challenge: Reread Books or Rewatch Movies? Why or Why Not?

    Hi everyone! I hope you’re all well. Today is Wednesday, and it’s time for another post in the Wednesday Weekly Blogging Challenge hosted by Long and Short Reviews. If you’d like to participate, you can find the topics for 2026 here. If you’re interested in other people’s responses to this week’s topic, you can do so here.

    Reread Books or Rewatch Movies? Why or Why Not?

    There are only a couple of books I love enough to reread. I reread A Christmas Carol as a matter of tradition. It’s become more of a habit left over from childhood than anything else. I’ve also reread Practical Magic a few times.

    Something about the storytelling and character development in Practical Magic relaxes me. I can’t quite put my finger on it. I rewatch the film adaptation all the time, but it has a bit of a different atmosphere than the book. The film gives me heavy autumnal vibes, and I tend to watch it around Halloween every year.

    There are so many TV shows I rewatch for comfort or for nostalgia. I love Friends. I have seen the whole series about a gajillion times from start to finish. I also just finished rewatching Will and Grace for the umpteenth time and still seal-laughed my way through.

    I rewatch several films. All the Batman movies are always in the rotation, as are the Alien movies (yes, even Resurrection).

    Star Trek and Stargate are always on in our house, too. I find TNG almost soothing. It takes me back to a simpler time when I was a kid, sitting squashed beside my dad in his armchair while we watched.

    Buffy and Charmed are two other shows I’ve rewatched a lot, along with cartoons like Tom and Jerry, Scooby-Doo, and The Flintstones (still a brilliant watch).

    My husband started watching ER at bedtime (he’s one of those who likes background noise when he sleeps). The only issue I have with this is that it is so bloody compelling that I end up watching instead of sleeping.

    Anyway… that’s post 42! Do any of you re-experience any media?

    Thank you, as ever, for reading my post this week. It means the world.

    Until next time,

    George

    © 2026 GLT

    #aChristmas #Batman #challenge #friends #Wednesday #WednesdayWeeklyBloggingChallenge #WillAndGrace
  21. Today is the big day! The start of replacing the roof on my house, and I am both excited and terrified.
    Excited, because this needed to happen. Theres no way the 50 year old shakes were going to last another winter, or even another storm.
    Terrified, because I have no idea what they are going to find up there. Hopefully it hasnt leaked significantly, or for any period of time. And its going to be busy and noisy in our calm oasis for the next week.

    #HomeOwnership

  22. Three beers, no notes, zero fucks.

  23. Three dates over the next two months - a US election and two major summits - will likely shape the trajectory of the Ukraine war more than anything that happens on the battlefield. #mix #ukraine #geopolitics

    theatlantic.com/national-secur

    Posted into FLIPBOARD EXCHANGE FEED 🗞️ @flipboard-exchange-feed-Econopass

  24. Three data-based charts show how construction spending, power access and utility commitments are reshaping the US data center buildout. hackernoon.com/ai-is-redrawing

  25. 🌌 873 years of random three-body chaos

    🌠 Escape
    🌀 31.1% chaos score, 1248 close approaches
    🎲 Took 5 attempts to find (min 500 yrs survival required)
    ⚡️ Escape speed: 17.1 km/s (rel. pair: 29.8 km/s)

    *Newton's nightmare: the third body.*

    ¿Ya has visto parpadear el universo?

    #ThreeBodyProblem #GravitationalChaos #Physics #Simulation

    🎥 youtube.com/watch?v=eSKI8jNInF8

Share on Mastodon

Enter the server where you have an account.