Comments

• By lich_king 2026-03-1214:212 reply

  You break highlighting and copy-and-paste. If I want to share or comment on a piece of your website... I can't. I guess this can be a "feature" in some rare cases, but a major usability pain otherwise.

  I'm not a fan of all the documentation and marketing content for this project evidently being AI-generated because I don't know which parts of it are the things you believe and designed for, and which are just LLM verbal diarrhea. For example, your GitHub threat model says this stops "AI training crawlers (GPTBot, ClaudeBot, CCBot, etc.)" - is this something you've actually confirmed, or just something that AI thinks is true? I don't know how their scrapers work; I'd assume they use headless browsers.

  By larsmosr 2026-03-1214:391 reply

  Copy-paste breaking is intentional for protected content but it's opt-in per component, not whole-site.

  On the AI docs concern, fair point. To answer directly: I've confirmed the obfuscation defeats any scraper reading raw HTML via HTTP requests. Whether GPTBot or ClaudeBot use headless browsers internally, I honestly don't know. The README threat model lists headless browsers under "what it does NOT stop" for that reason.

  By larsmosr 2026-03-1215:02

  Full user-agent string: Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; GPTBot/1.3;

  Official OpenAI documentation: https://platform.openai.com/docs/gptbot

• By obsrcdsucks 2026-03-1214:331 reply

      function decodeObscrd(htmlOrElement) {
        let root;
        if (typeof htmlOrElement === 'string') {
          root = new DOMParser().parseFromString(htmlOrElement, 'text/html').body;
        } else {
          root = htmlOrElement || document;
        }
      
        const container = root.querySelector('[class*="obscrd-"]');
        if (!container) { return; }
      
        const words = [...container.children].filter(el => el.hasAttribute('data-o'));
        words.sort((a, b) => +a.dataset.o - +b.dataset.o);
      
        const result = words.map(word => {
          const chars = [...word.querySelectorAll('[data-o]')]
            .filter(el => el.querySelector('[data-o]') === null);
          chars.sort((a, b) => +a.dataset.o - +b.dataset.o);
          return chars.map(c => c.textContent).join('');
        }).join('');
      
        console.log(result);
        return result;
      }

  By larsmosr 2026-03-1214:40

  Yep, that works. The data-o attributes are readable in the DOM so you can reverse it with custom code. That's in the threat model. The goal is raising the cost from "curl + cheerio" to "write a custom decoder per site." Most scrapers move on to easier targets.

• By dec0dedab0de 2026-03-1214:21

  Reminds me of when AOL broke all the script kiddy tools in 1996 by adding an extra space to the title of the window. I didn't have AOL, but my friend made one of those tools, and I helped him figure it out.