home.social

Search

174 results for “Readek”

  1. Readers Share Their Favorite Sunny Autumn Escapes for Off-Season Travel
    theguardian.com/travel/2026/oc
    Readers share their favorite off-season autumn getaways, from island retreats where summer lingers to festival-rich European cities at their quietest and most authentic.
    #travel #autumn-travel #off-season

  2. Readers share their favorite off-season autumn getaways, from island retreats where summer lingers to festival-rich European cities at their quietest and most authentic. #travel #autumn-travel #off-season

    theguardian.com/travel/2026/oc

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

  3. Landespolizeiinspektion Suhl: Motorradfahrer bei Unfall schwer verletzt – Suhl-Mäbendorf - Am Mittwochmorgen, 14. Oktober 2026, ereignete sich auf der L 1140 zwischen Suhl und Meiningen ein schwerer Verkehrsunfall. Nach dem... news-reader.info/x/42736045 #Landespolizeiinspektion #Suhl #Meiningen

  4. Landespolizeiinspektion Suhl: Drogenfahrt in der Probezeit – Zella-Mehlis - Am Mittwochabend, 14. Oktober 2026, kontrollierten Polizeibeamte in der Meininger Straße in Zella-Mehlis einen 34-jährigen VW-Fahrer. Ein Drogentest... news-reader.info/x/42736047 #Landespolizeiinspektion #Suhl

  5. Landespolizeiinspektion Suhl: Frontalzusammenstoß zwei Fahrzeugen – Meiningen - Am 12. Oktober 2026 gegen 11.45 Uhr befuhr der Fahrer eines Pkw Fiat die Dreißigacker Straße in Meiningen in Richtung Berkeser Straße. Hierbei handelt... news-reader.info/x/42720841 #Landespolizeiinspektion #Suhl #Meiningen

  6. Landespolizeiinspektion Suhl: Durch die Sonne geblendet und aufgefahren – Meiningen - Am 12. Oktober 2026 gegen 13.15 Uhr befuhr eine 52jährige Fahrerin die Neu-Ulmer Straße in Meiningen. Auf Höhe des DRK wollte ein Fahrzeug nach... news-reader.info/x/42721034 #Landespolizeiinspektion #Suhl #Meiningen

  7. CW: NSFW

    Twinks Martin Kadels Radek Pozer RAW BB Fuck
    Video Link: playmogo.com/e/au180i9hn3rw

    MORE VIDEO LINKS:

    gaystash.com?ref=BENO77
    and
    MyVidster:
    myvidster.com/profile/slobeno

    NO POP-UPS AND ADS:
    Use the BRAVE browser // brave.com/

  8. my ebook reader broke and it's so bad on repairability front. i wish i could just repair it but the only replacement screens cost more than i paid for the (used) device itself, and are glossy instead of matte, which completely defeats the purpose of an e-ink reader.

    also i dont know how to take my config and books out because to connect it to the pc you have to tap the usb option :/

  9. Last week I asked readers a question I genuinely hadn't settled: guard + alert, or guard + retry once? The answers — plus one expensive weekend — gave me a rule. It is not "retry once". It is "retry once, only when the retry is different from the attempt that failed."

    Where the question came from


    The code-fence guard post ended with my uncertainty: when an LLM completion fails validation, do you retry automatically or send it to review? Two readers gave me the two halves of the answer. One said to retry once with the validation error as feedback, then route persistent failures to review. Another (in a different thread) noted that authorization and quota errors should advance without repeating the same request five times.

    Both are the same insight: a retry is only worth it when something changes between attempts. Same request, same conditions, same failure — that is not a retry strategy, that is a hope strategy.

    The three failure classes


    Every LLM failure in my workflows falls into one of three buckets, and each bucket gets a different response:

    1. Transient (retry, with backoff). 429s, 5xx, timeouts, connection resets. The model did nothing wrong; the infrastructure hiccuped. Retry with exponential backoff. This is the only class where an identical retry is legitimate — because the failure was about the moment, not the content.

    2. Repairable (retry once, with feedback). The completion came back but failed validation: bad JSON shape, missing required field, wrong enum value. Here the retry must carry the validation error back into the prompt — "your last output failed because action_items was null; return an array" — and it gets exactly one shot. In my experience, the first retry with feedback fixes ~70% of these; the second retry fixes almost none. The failure curve flattens after one.

    3. Deterministic (no retry, alert immediately). Auth errors, quota exhaustion, 400s from malformed requests, content-policy refusals, and — the one people miss — a repeated failure of class 2. If the feedback-retry fails the same way, the problem is not in the completion. It is in the prompt, the fixture, or the model. Retrying again burns money to re-confirm a diagnosis you already have. This goes straight to the review queue, tagged for the weekly tally.

    The budget in code


    The whole policy fits in one n8n pattern. A Code node tracks attempts and classifies the error:

    const err = $input.first().json;
    const attempts = ($('Classify').first().json.attempts || 0) + 1;

    const TRANSIENT = [429, 500, 502, 503, 504, 'ETIMEDOUT', 'ECONNRESET'];
    const DETERMINISTIC = [400, 401, 403, 404, 422];

    let action = 'review'; // default: a human looks at it
    if (TRANSIENT.includes(err.status)) action = attempts <= 3 ? 'retry_backoff' : 'review';
    else if (err.validation_failed && attempts === 1) action = 'retry_with_feedback';
    else if (DETERMINISTIC.includes(err.status)) action = 'review';

    return [{ json: { ...err, attempts, action } }];

    Three branches, three budgets: transient gets 3 with backoff, repairable gets exactly 1 with feedback, deterministic gets 0. The action field drives an IF node: retry, or review queue.

    The important line is the default. Anything unclassified lands in review, not in a retry loop. A new failure mode you have never seen should never be retried automatically — you do not know its class yet, and an unknown class is a candidate for a new rule, not a guess.

    Why exactly one feedback-retry


    Two reasons, one empirical and one economic.

    Empirical: I logged 200 repairable failures over a month. First feedback-retry success rate: 71%. Second retry on the remaining 29%: 9% of those. The second retry converts at roughly a tenth of the first, and each costs a full prompt+completion. Diminishing returns hit a wall at one.

    Economic: retries multiply the cost of the failure path. A workflow that retries three times on every bad completion does not just cost 3x — it costs 3x on precisely the inputs that are hardest to get right. The retry budget is a cost control as much as a reliability control. My weekly tally has a line for retry spend; when it grows, the fix is in the prompt or the fixture, not in the retry count.

    The rule that ties it together


    Retry only when the attempt differs from the one that failed. Backoff differs. Feedback differs. Same request, same prompt, same conditions — that is not a retry, it is a loop.


    When a deterministic failure hits the review queue twice for the same prompt, the weekly tally rule fires: two weeks of the same tag is a model problem, one week is weather (from the model-change protocol post). The retry budget feeds the tally, the tally feeds the protocol. Each mechanism I have posted about — the guard, the crash boundary, the sweeper, the retry budget — is one page of the same SOP.

    What is your retry budget? I would especially like to hear from anyone running LLM steps at real volume — where does the second retry ever pay for itself?#automation #ai #webdev #programming #software #coding #development #engineering #inclusive #community
    The Retry Budget: Why My n8n LLM Workflows Retry Exactly Once, Then Page a Human

  10. Giving a reader a sex scene that is only half right is like giving her half of a kitten. It is not half as cute as a whole kitten; it is a bloody, godawful mess.

  11. Attention Barnes & Noble / Nook readers!

    The "Fall Back Into Reading: 500 Under $5" sale is on through the end of the week, don't miss out!

    (PS: grab A Slice Of Mystery while you're at it, nothing better than a cozy mystery for sweater weather!)

    barnesandnoble.com/shop/fall-b

    #ebooks #books #bookstodon #NookBookSale #BNBookHaul #BooksOnSale #DiscountBooks #Romance #RomanceBooks #YA #YALit #YAbooks #NoSpiceBooks #SweetRomance #PNR #ParanormalRomance #SciFi #Mysteries #mystery #Thriller #Fantasy

  12. I asked Enzo Reader to catch me up on my Feedbin feeds inside ChatGPT. The short digest gave me a place to start reading.

    I also tried search, full-text reading, and the controls for narrowing the list. Search and full text worked; several filters returned errors. I wrote about where I'd use it and where I'd go back to Feedbin.

    kylereddoch.me/blog/enzo-reade

  13. SPOOKY SEASON READERS!

    If you missed the giveaway for "Office Hours," don't despair! These two bone-chilling eBooks are always free from a variety of stores:

    Academic Displacement
    books2read.com/b/nwtad
    Alternate Unrealities
    books2read.com/b/au

    #free #spookyseason #ebook #ebooks #story #stories #bookstodon #booktodon

  14. What are your recommendations for:

    A RSS reader application that is good-looking, privacy-respectful, and that allows collaboration between multiple users? 📰👀

    [preferably open-source]

  15. Komga
    #Comic #Manga #BD #Ebook #Reader #Komga
    thewhale.cc/posts/komga
    A media server for your comics, mangas, BDs, magazines and eBooks.

  16. It is plain to any unbiass'd Reader, that Women excel Men in Softness, Tenderness, and those Endowments which produce the sweetest Society.

    -- Sophia, A Person of Quality (Woman's Superior Excellence Over Man, 1740 (circa))

  17. Book Promotion: Get this free Teslapunk horror story before time runs out. Ursula has run out of cigarettes and need is eating at her. (Optionally, also join my newsletter - but that's not a requirement.) #steampunk #readers #fear #fedibookfair #alternate #monsters #amreading #horror #goodbooks #germany #teslapunk #historical #reading #boost #empire (417b) dl.bookfunnel.com/w1ex0rk3rj?u

  18. @HobbyHero
    Personnaly, as a reader, I look for the author in works of fiction. If I like what I think I see of the author in the writing, I’ll likely read all of their books and I expect to see similar traces of the authors in all of them. No doubt #LLM-based #GenAISlop can produce fiction that can also provide the same hints of an author behind the story and I would feel *cheated* if I found out the work was produced with #AI. How much of AI input is used might determine the intensity of my disappointment thought, I just don’t know. A secondary beef I have with AI use in writing is that one condones copyright infringements which is worse than producing pirated books. At least the latter keep the authorship intact and might entice the reader to purchase further (legal) books from the author. AI in writing has nothing to recommend it except for the ease of #Grifting it offers (think copied/fake paintings) always at someone else’s expense. Theft.

    Which brings up the matter of *genre* esp. romance or *airport novels* which tend to be *manufactured* and *fomulaic*, here GenAISlop production wouldn’t matter at all imo. Not that I read that type of story anyway.

    As a writer, I would shun the use of AI for reasons cited above but also for self-respect. What I write is a part of me and only me, and I like it that way in my writing. Arguably, all writers bear snippets of their favourite reads, but these are tempered by our personal experiences and internal dialogues, something AI is incapable of doing.

    #Writing #WritingCommunity

  19. Galaxy S25+ Deal: 256GB Unlocked Phone 21% Off

    SammyGuru is reader-supported. We have affiliate and sponsored partnerships, so we may earn a commission when you buy…
    #EuropeSays #Korea #KR #Samsung #BestBuy #GalaxyS25 #SamsungGroup
    europesays.com/korea/187552/

  20. #WordWeavers 10/15: What piece of backstory did you invent just for yourself that readers may never learn?

    What a great question. Zerika used to enjoy feeding and playing with the family's farm animals when she was a young girl.

    #WritingCommunity #WritersOfMastodon #TheScarletMirror #FatedByFire #CozyFantasy #Fantasy #SwordAndSorcery #Romance


  21. October 15th

    What piece of backstory did you invent just for yourself that readers may never learn?

    Non, since everything is spilled within the work(s). I think it's necessary to give the reader as much information as possible so they can dive into the story as deep as I like them to be.

Share on Mastodon

Enter the server where you have an account.