home.social

Search

226 results for “wjorth”

  1. The Aesthetics of Resistance, Volume III - A Novel
    Peter Weiss
    1977
    #antifascism #german #literature #history #resistance #proletariat #art
    "The masses of those who had no more to offer than their desperation swelled, and desperation was the most worthless of all superfluous things; (...)"

  2. Why Are Laws Vital to Ukraine’s EU Integration Stuck in Parliament as the Country Loses Money?

    President Volodymyr Zelensky recently signed laws abolishing the VAT exemption for foreign parcels worth up to €150 ($168)…
    #Europe #EU #EuropeanUnion
    europesays.com/europe/166652/

  3. In this article

    • What llms.txt is
    • What the evidence says
    • What actually decides whether AI can read you
    • Structure is not the same as being worth citing
    • What I would do, in order

    We publish an llms.txt file on our own site. It is a short markdown file that describes Geology in two sentences and lists the pages we would most like a language model to read. I am not going to pretend it is doing much. When people ask me whether they need one, my answer is "sure, if you have ten minutes, but please fix three other things first."

    "llms.txt" is searched about 5,400 times a month in the US, and plugins now generate the file in one click. Here is what it is, what the evidence says, and what I would check before you spend any more time on it.

    What llms.txt Is


    llms.txt is a proposed convention, documented at llmstxt.org: a plain markdown file at /llms.txt with a short description of the site and a curated list of links, sometimes with a fuller /llms-full.txt holding the content itself. It is not a standard from any search engine or AI company, and it does not grant or block access to anything. That job still belongs to robots.txt.

    What the evidence says


    In June 2025 Google's John Mueller wrote on Bluesky: "FWIW no AI system currently uses llms.txt." He added that consumer chatbots fetch pages for training and grounding, "but none of them fetch the llms.txt file," which he said is obvious from server logs (Search Engine Roundtable).

    You can check this on your own site in a few minutes. Search your access logs for requests to /llms.txt and note which user agents made them. If the only visitors are SEO tools and curious developers, you have your answer.

    None of that makes the file harmful. It is cheap to publish, and some developer tools and coding assistants do read documentation in this format, so for a software company with public docs it can be a real convenience. For most brands trying to be recommended in ChatGPT, Perplexity or Google's AI answers, it is simply not where the gains are.

    What actually decides whether AI can read you

    File or settingWhat it controlsWhy it matters more than llms.txtrobots.txtWhich crawlers may fetch which pathsA blocked AI crawler cannot read the page at allServer-rendered HTMLWhat a fetcher sees without running JavaScriptMany AI fetchers do not run JavaScriptXML sitemapWhich URLs exist and when they changedSearch engines that feed AI answers use it for discoveryPage status and canonicalsWhich version of a page countsBroken or conflicting signals keep pages out of indexes


    We keep a list of the AI crawlers and what each one does in robots.txt for every AI crawler. The mistake we run into is rarely a missing llms.txt. It is a robots.txt rule (how to set one for AI crawlers), or a security or CDN setting, that blocks GPTBot, OAI-SearchBot or PerplexityBot without anyone having decided to.

    Structure is not the same as being worth citing


    A lot of the llms.txt enthusiasm comes from a broader belief that tidy, machine-friendly structure is what gets a page cited. We tested a closely related claim. In our study of 3,352 AI citations across B2B SaaS buying queries, schema markup showed almost no relationship with how often a page was cited (r = 0.103), and pages with FAQ blocks were cited slightly less often than pages without them. What did line up with citations was depth of coverage and outbound links to good sources (GEO for B2B SaaS).

    Structure helps machines parse a page. It does not make the page worth quoting.

    What I would do, in order


    1. Check robots.txt for AI crawler rules nobody chose. Our free robots.txt tester shows them crawler by crawler.
    2. Fetch your key pages without JavaScript and confirm that prices, product names and your main claims are in the HTML.
    3. Keep the sitemap current (our free sitemap checker flags broken entries) and submitted in Google Search Console and Bing Webmaster Tools. Bing's index has long been one of the sources behind ChatGPT's web search, and it is the one most teams forget.
    4. Make the pages worth citing: cover the buyer's question completely, put the facts early, and link your sources.
    5. Then, if you like, add llms.txt. Ours took a few lines. Just do not report it as an AI visibility win until your logs show something reading it. If llms.txt becomes a real standard, the sites that did steps one to four will benefit from it most anyway.


    #ai #aicrawler #seo #agents #software #coding #development #engineering #inclusive #community
    Do You Need an llms.txt File? What It Does, What It Does Not, and What to Fix First

  4. My wife and I saw You can See Everything last night, and it's a great Movie and a terrible documentary. Definitely worth watching, I enjoyed it a lot even though I find it kind of nihilistically post-modern in how it ignores (and obscures when convenient) the Facts that were available

  5. From my run today in . Pouring rain, but the mist and colors made it worth it.

    Then I saw the movie with my family. To see my city and my trails brought to life by a local studio and an author from a band I love, sitting beside the two kids I once read the book to, I was overwhelmed.

  6. Count down six days until I take my CCNA exam. I feel like I have a 50/50 shot and been using Boson's exsim exams as well as there simulation labs. Well worth the cost. #CCNA

  7. Homelessness reduces human identity to an institutional label: "service user." Secure tenancies allow individuals to rebuild civic roles, kinship, and autonomy. Help educate local service providers: housing restores the positive identity necessary for self-worth. #HousingIsAHumanRight
    #HousingFirst

  8. How do you feel about someone setting up an automated process that hammers restaurant-reservation websites to gain an advantage in booking a table?

    The NY Times thinks this is not only acceptable; it's a "killer task" for AI, worth paying $100/month.

    nytimes.com/2026/10/25/technol

  9. Thank You, Brussels: Making the Dashboard the Next USB-C

    In part one I argued that convenience is the bait, and that doing things the hard way is worth the friction. I also conceded Cory Doctorow’s point: individual choices won’t fix enshittification. Policy will. This post covers why GrapheneOS needs that policy to survive, who is actually writing it, where they should point it next, and what you can do to help.

    fed.brid.gy/r/https://gaggl.co

  10. We Life in Time (2024) is, at its heart, a paint-by-numbers weeper. But it's well done because the actors elevate it. And that's enough for this one to be worth watching again someday. #MovieReview
    letterboxd.com/average_joe/fil

  11. In the 1980s, Sylvester Stallone bought Monet for USD 110,000 and sold it for USD 3M; years later, it made its way back to him, now worth USD 130 million |

    In the 1980s, Sylvester Stallone bought Monet for USD 110,000 and sold it for USD 3M; years later,…
    #NewsBeep #News #Artsanddesign #artinvestment #Arts #ArtsAndDesign #AU #Australia #ClaudeMonet #Design #Entertainment #HaystacksMonet #Monetpainting #SylvesterStallone
    newsbeep.com/au/940059/

  12. Thought for the Week

    "The road from bad to good often has a little stretch of awful in between. It takes a whole lot of courage to face and go through the awful stretch, but it will be totally worth it when you do. "Doe Zantamata Lady Dyanna offers email service in Spiritual Development and Tarot Readings

    ladydyanna.com/2026/10/25/thou

  13. The U.S. Grid Counts On Canadian Power. Canada Is Eyeing Other Options

    Canada and the U.S. share the longest international border in the world. But worth paying attention to is…
    #Canada
    europesays.com/canada/263319/

  14. IGN just posted:

    New Avengers: Doomsday Trailer Pokes Fun at Multiple 'Captains America'

    Marvel dropped a new trailer for Avengers: Doomsday that leans heavily on the dynamic between Thor and Steve Rogers, especially their shared worthiness to wield the enchanted hammer Mjolnir.

    ign.com/articles/avengers-doom

    #gamingNews #IGN

  15. In the 1980s, Sylvester Stallone bought Monet for USD 110,000 and sold it for USD 3M; years later, it made its way back to him, now worth USD 130 million |

    In the 1980s, Sylvester Stallone bought Monet for USD 110,000 and sold it for USD 3M; years later,…
    #NewsBeep #News #US #USA #UnitedStates #UnitedStatesOfAmerica #Artsanddesign #artinvestment #Arts #ArtsAndDesign #ClaudeMonet #Design #Entertainment #HaystacksMonet #Monetpainting #SylvesterStallone
    newsbeep.com/us/893614/

  16. If you have ever voted the way your family always did, that's a fine place to start. Plenty of us learned it at the table.

    It's also worth checking once whether those picks still match what you care about today. Maybe they do. Maybe one surprises you. The choice stays yours.

    No time to check those picks? See how your members of Congress voted and who paid for their campaigns, in about 10 minutes: voterchoice.vote

    #Congress #Midterms2026 #CivicEngagement #VoterChoice

  17. Nourishing yourself in a way that helps you blossom in the direction you want to go is attainable, and you are worth the effort. ~ Deborah Day

  18. RE: mastodon.ie/@dwmalone/11749782

    "Accidental Leap Second" seems like a great band name, although for what genre I'm not sure.

    (But if you are running Strat1/Strat2 infra, probably worth checking and keeping an eye on this.)

    #ntp #ntp_synchronization

  19. #NYT #Arts #Culture #ArtHistory #NVO987 #NEXARIUM
    8 New Movies Our Critics Are Talking About This Week
    Whether you’re a casual moviegoer or an avid buff, our reviewers think these films are worth knowing about.
    nytimes.com/2026/10/23/movies/

  20. @KrusekopfD @schwarissa.bsky.social

    This is a collection of shredded Japanese banknotes (Bank of Japan notes) and related printed materials.

    The bag contains approximately two banknotes' worth of shredded currency (a mix of various denominations).

    Since shredded banknotes are typically incinerated or recycled into products like recycled paper or solid fuel, this is a rare opportunity to obtain them.

    #BankOfJapan
    #BanknoteShreds
    #ShreddedCurrency
    #nipponginko

  21. This video tells the story of Malone Lam, a 20-year-old from Singapore who helped steal over $230 million worth of Bitcoin through an elaborate social engineering scam. No sophisticated hacking tools or complex code, just deception, impersonation, and a convincing scheme.

    From scamming Minecraft players to tricking a wealthy cryptocurrency investor into handing over access to his Bitcoin, Lam's activities escalated into one of the largest cryptocurrency thefts in history. The stolen fortune funded an extravagant lifestyle filled with luxury cars, lavish mansions, private jets, and nightclub bills reaching hundreds of thousands of dollars.

    But the spending spree eventually attracted the attention of federal investigators, leading to arrests and a sprawling investigation into where the stolen Bitcoin went, much of which remains unaccounted for.

    Video Credit: youtube.com/@InVoyceYT

  22. Thai Diner in Fort Wayne, Indiana, really dramatically exceeded my expectations for Thai food in a medium-sized Indiana city. Legitimately worth a return visit to sample other dishes. #thai #food #fortwayne #yum

  23. For years the main reason to add an FAQ section was the dropdown it could earn in Google results. That reason has gone. The page itself still matters, though, because AI assistants and AI search features pull short, direct answers from pages, and a well-built FAQ is one of the easiest things on a site for them to lift.

    This post covers what changed at Google, what still makes an FAQ worth writing, and the HTML pattern we use so each answer stands on its own.

    Disclosure: Appie.run publishes this post. The AI FAQ Generator and Website FAQ Generator mentioned below are our free tools. Everything else here works with any CMS and no tool at all.

    What Google changed (as read on 26 Oct 2026)


    From Google's Search Central updates and Search Console Help:

    • FAQ rich results stopped appearing in Google Search on 7 May 2026, and Google added a deprecation notice on 8 May.
    • On 15 June 2026 Google removed the FAQ structured data documentation, the FAQ report in Search Console and FAQ support in the Rich Results Test.
    • Search Console API support for FAQ appearance data was removed in August 2026.
    • Google says existing FAQPage markup can stay on your pages and causes no harm.
    • In the same June update Google noted that an llms.txt file isn't needed for Google Search.

    So: no more SERP dropdown, no penalty for leftover markup, and no special file required. What's left is the content.

    Why an FAQ is still worth writing


    Nobody outside the AI companies can tell you exactly how each assistant picks its sources, and we won't pretend to. What you can control is whether your answer is easy to find, easy to extract and correct when pulled out of context. A question-and-answer block does all three if you write it properly:

    • The question matches the way people actually ask it.
    • The first sentence of the answer is the answer.
    • The answer makes sense without the paragraphs around it.

    Those same properties help a human who lands on the page from a support link, so the work isn't wasted whichever way the traffic arrives.

    Step 1: Collect real questions


    Don't invent questions in a meeting. Pull them from places where customers already asked:

    • Support tickets and live chat transcripts
    • Sales call notes ("Does it work with...?", "What happens when...?")
    • Reddit and community threads in your category
    • Your site search logs

    Group duplicates, then keep the 8 to 15 that come up most or block a purchase.

    Step 2: Write answers that survive being quoted alone


    A quick test for each answer: paste it into a blank doc with only the question above it. Does it still make sense?

    Weak:

    Yes, as mentioned above, it does, depending on your plan.


    Better:

    Yes. Team plans include SSO via SAML. The Starter plan does not.


    Rules we follow:

    1. Answer in the first sentence. Yes/no, a number, or a name.
    2. Name the thing. Say "the Starter plan", not "this plan".
    3. Keep it to 40 to 80 words for most answers. Link out for detail.
    4. Date anything that changes. "As of 26 Oct 2026, the Starter plan costs $19/month." Prices and limits go stale, and a stale quoted answer is worse than none.
    5. Only state what the page can back up. If the policy lives elsewhere, link to it rather than paraphrasing it loosely.


    Step 3: Use plain, semantic HTML


    You don't need a plugin. Headings for questions and paragraphs for answers are enough, and they render the same for every crawler:

    <section id="faq" aria-labelledby="faq-title">
    <h2 id="faq-title">Frequently asked questions</h2>

    <h3 id="faq-sso">Does the Starter plan include SSO?</h3>
    <p>No. SSO via SAML is included on Team plans only. The Starter plan
    uses email and password sign-in. <a href="/pricing">Compare plans</a>.</p>

    <h3 id="faq-cancel">Can I cancel at any time?</h3>
    <p>Yes. You can cancel from the Billing page, and your plan stays active
    until the end of the current billing period.</p>
    </section>

    If you prefer collapsible answers, <details>/<summary> keeps the text in the HTML:

    <details>
    <summary>Can I cancel at any time?</summary>
    <p>Yes. You can cancel from the Billing page, and your plan stays active
    until the end of the current billing period.</p>
    </details>

    Avoid loading answers only via JavaScript after a click. If the text isn't in the served HTML, some crawlers will never see it.

    Give each question an id so you can link straight to it from support replies and docs.

    Step 4: Keep or add FAQPage markup (optional)


    Google no longer shows FAQ rich results, and it says leftover markup does no harm. Other consumers of schema.org data may still read it, so if it's already there, keep it in sync with the visible text. If you add it, mirror the on-page wording exactly:

    <script type="application/ld+json">
    {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
    {
    "@type": "Question",
    "name": "Can I cancel at any time?",
    "acceptedAnswer": {
    "@type": "Answer",
    "text": "Yes. You can cancel from the Billing page, and your plan stays active until the end of the current billing period."
    }
    }
    ]
    }
    </script>

    The risk with markup is drift: someone updates the visible answer and forgets the JSON. If your FAQ comes from a CMS field, generate both from the same source.

    Step 5: Put the FAQ where the question is asked


    One giant /faq page is fine as an index, but the most useful placement is next to the thing in question: pricing questions on the pricing page, setup questions in the docs. A short block of 4 to 6 questions per page tends to stay accurate because the owner of that page sees it.

    Step 6: Review it on a schedule


    Add a "last reviewed" date and put a recurring reminder on someone's calendar. Every price, limit and integration claim in the FAQ should be checked against the product at least each quarter.

    Getting a first draft faster


    If you have the source material but not the time, two of our free browser tools can produce a draft for you to edit (both run a captcha check first):

    • AI FAQ Generator (appie.run/tools/ai-faq-generator): paste up to 2,000 characters of text, pick 1 to 10 FAQs, a language and a tone. The answers are grounded in the text you pasted, and it doesn't add policies or prices that aren't there.
    • Website FAQ Generator (appie.run/tools/website-faq-generator): give it up to 5 public URLs. It skips questions it can't answer from those pages instead of guessing.

    Treat the output as a draft. Check every answer against Step 2's rules before it goes live.

    Checklist


    • [ ] Questions come from real customer sources
    • [ ] Each answer starts with the answer
    • [ ] Each answer makes sense on its own
    • [ ] Prices and limits carry an "as of" date
    • [ ] Questions and answers are in the served HTML
    • [ ] Any FAQPage JSON-LD matches the visible text word for word
    • [ ] A review date is set

    Google sources: Search Central blog and Search Console Help pages on FAQ rich results and structured data, read 26 Oct 2026.

    RG, Founder, Appie.run#seo #html #webdev #ai #software #coding #development #engineering #inclusive #community
    How to Write a Website FAQ That AI Answers Can Quote (Now That Google's FAQ Rich Results Are Gone)

Share on Mastodon

Enter the server where you have an account.