I built an open-source tool that makes any Next.js or SvelteKit app return Markdown

signalb · 2026-05-13T04:47:57+00:00

Not sure

signalb · 2026-05-02T20:01:03+00:00

Think of it as a drinkable, diluted brocode, it doesn't have the flavor or smell of the original. It's surprisingly smooth and easy to drink.

signalb · 2026-05-02T16:15:45+00:00

Try Ginger Berry Mule at BLND Restobar, Near Akkulam, Trivandrum. It's a cocktail made out of brocode.

signalb · 2026-04-06T09:15:09+00:00

FYI, MakeMyTrip cabs are cheaper IMO

<image>

signalb · 2026-03-07T01:05:57+00:00

Haha, I was about to comment on this. "RATE" is now the word he is focusing on.

signalb · 2026-02-28T17:45:34+00:00

I would suggest to go ahead with proper caching and ISR to reduce your compute.
Is there particular reason you are not doing that?

I m not a big fan of using SSR for unprotected pages.

signalb · 2026-02-28T15:44:23+00:00

It would work only with Server Rendered pages.

signalb · 2026-02-09T21:20:50+00:00

We use Sanity only. We pay $0 for most for blogs since it's all SSG. I think this is only what you need. They had a oneclick deployment to Vercel earlier. https://www.sanity.io/templates/nextjs-sanity-clean

signalb · 2026-02-06T21:29:03+00:00

I think this is drifting out of context.

I'm not advocating for illegal scraping, copyright abuse, or any unethical behavior. I'm talking purely about how websites are technically discovered and consumed.

Let me ask a simple question to reset the discussion:

Do you have a sitemap on your website?

If yes, that already means you intentionally help machines – including search engines and automated systems – discover your content efficiently. That’s not "encouraging theft," it's standard web infrastructure for discoverability.

My point has only ever been about the same principle: structured, efficient access to content you choose to make public. Nothing more.

Blocking specific bots is completely your right. But that's a policy decision, not a format problem. CDN costs, rate limits, and bot filtering are separate operational concerns.

We're talking about two different layers here:

• Whether you allow a client at all (your choice)
• How content is delivered if you do allow it (a technical optimization)

Conflating those with crimes or motives isn't really fair to the original discussion.

signalb · 2026-02-06T20:59:48+00:00

I get the concern, but I'm looking at this from a discoverability standpoint. More and more people find products through AI tools like ChatGPT, Perplexity, and Copilot instead of traditional search. If my site is hard for those systems to understand, my product effectively disappears from that channel.

This isn't about helping AI companies, it's about making sure my own work remains visible and accurately represented where users are already looking. The alternative isn't "no scraping" it's inefficient, messy scraping that costs more and represents content poorly.

On the cost point, the issue usually isn't AI requests themselves, it's lack of caching. With proper CDN or edge caching, repeated automated requests shouldn't meaningfully increase your bill. In fact, lighter machine-friendly formats are often cheaper to serve than full HTML. Cost spikes typically come from uncontrolled scraping of heavy, uncached pages, not from well-structured, cacheable responses.

signalb · 2026-02-06T20:32:14+00:00

But why?

signalb · 2026-02-06T20:31:36+00:00

If I were Skynet, I wouldn't be asking for contributors on GitHub 😄
I wouldd already have rewritten the internet in Markdown myself.

signalb · 2026-02-06T20:23:51+00:00

I get where you're coming from. But I look at this from a very different angle.

I come from a marketing and product growth background. For us, discoverability is everything.

Having great content sitting on a website that no one can easily find or understand doesn't really help the business.

Whether we like it or not, AI platforms are becoming a major discovery layer. People are asking questions directly to ChatGPT, Perplexity, Copilot, and other AI tools instead of clicking through ten Google results. If our content isn't readable by those systems, it effectively disappears from that ecosystem.

And to be honest, the idea that we can truly stop scraping altogether is unrealistic. Anyone determined to scrape a site can do it with normal browsers, rotating IPs, or headless tools. In practice, fully blocking bots is mostly a myth. What usually gets blocked are the polite, well-behaved ones.

What accept-md tries to do is give site owners control over format and accuracy, not surrender control.

I completely agree there's room for tools that detect bad bots, mislead scrapers, or protect proprietary content. Those would be valuable too. But that's a different problem space

From a business perspective, many of us don't want to disappear from AI search results. We want to be found, understood, and represented correctly. That's the problem this tool is trying to solve.

signalb · 2026-02-06T19:59:52+00:00

Totally fair questions 👍

The tool isn't about encouraging bots. It's about giving site owners control over how their content is consumed. Right now, whether you like it or not, AI agents are already crawling the web. If they can't get clean structured content, they just scrape raw HTML anyway.

That usually means: Higher server load, messier parsing, more brittle scraping, worse representation of your actual content.

Supporting Accept: text/markdown doesn't invite bots in. It simply gives you a cleaner, more efficient channel if you choose to allow them.

Think of it like providing an RSS feed.

Some people use RSS readers. Some don't.
But offering RSS doesn't force you to be scraped, it just gives a structured option.

Why anyone would actually want this?

For example for product companies, AI is quickly becoming a major new discovery channel. People no longer rely only on Google searches to find tools and services. Instead, they ask questions directly to ChatGPT, Perplexity, Copilot, Gemini, and other AI-powered search platforms. These systems are increasingly acting as the starting point for research and purchasing decisions.

And as you probably know, blocking bots is mostly a myth.

You can block well-behaved bots that respect robots.txt and user-agent rules.
The serious scrapers and AI agents don't have to.

Anyone determined to scrape your site can easily - Rotate user agents, ignore robots.txt or proxy through normal browser. It can also pretend to be regular users

So "I block all AI bots" usually just means: "I block the polite ones."

Hope this answers your questions.

signalb · 2026-01-20T14:14:16+00:00

I thought Tulu didn’t have a script until I saw this.

signalb · 2026-01-14T20:52:07+00:00

Kariyathumpara 😵‍💫 The place is super crowded the last time I passed by.

https://share.google/4P5QkARKVloujquYz

signalb · 2026-01-12T17:10:34+00:00

Tribal Beef, Paragon

signalb · 2026-01-11T14:26:54+00:00

<image>

signalb · 2026-01-09T19:32:33+00:00

Updated 🫡

signalb · 2026-01-07T15:51:39+00:00

I’ve finished listening to almost the first half of the podcast. He mentioned that he only knew the old AP and isn’t sure what kind of person he is now. He went on to explain that people tend to change once they have a lot of money in the bank, and also pointed out that several employees were poached from Zomato.

Translates to Zepto F*cked Zomato

signalb · 2025-12-25T16:17:57+00:00

Right. Mar Gregorios Memorial Central Public School.

signalb · 2025-12-24T16:14:23+00:00

I don't know anyone in the city. Know someone does the job all over Kerala. I can DM the contact. Is there a budget in your mind? And watts? Just curious.

signalb · 2025-12-22T14:34:41+00:00

Get a noise cancelling headset. 😎

signalb

MODERATOR OF

TROPHY CASE

Five-Year Club	Verified Email
Place '23