if you're a web developer we make an SDK for building things with tldraw's canvas. Learn more at tldraw dot dev

RT @btn0s: got it! set up @aisdk and gave the agent tool calls which control an event bus via webhook SSE and an agent-puppet on the client….

just signed in, what’s the move

RT @thinkscientist: This is wild! @tldraw has blown my mind with how far down the rabbit hole their infinite canvas has got. @steveruizok g….

RT @ravdeepchawla: I don't know what rock I was under but I had never seen before and my god! Such brilliant no-non….

RT @btnelson: If you haven't tried tldraw computer, you really should. @steveruizok has built something really special.

RT @tldraw: visual summaries of canvas regions

Anyway, no immediate actions planned but something on my mind. It’s never been easier to write code (with the help of the products like @cursor_ai and @lovable_dev) but it can still be easier by making info more available.

GH discussions has its own funnel but at least developers already have a GH account. It could be easier to write some scripts that answer questions automatically, too. (Also possible on Discord).

I really like answering questions on Discord and chatting sync with folks. But it’s such a big filter to have someone look for answers, not find them, find the Discord, join the Discord, wait 15 minutes for security, and then ask and wait for a response.

As a positive, FAQs can be versioned and have frontmatter about which SDK version was active when the FAQ was written. That’s useful for keeping things up to date, but also for allowing people/agents using older versions to find docs/answers that relate to their version.

Not everything can be captured in a Q&A format though. There’s a lot of context and discussion that might be relevant. It’s good to know who asked what. I’ve chased people from old phpbb posts to ask follow-up questions. Can’t do that with a FAQ.

That has some obvious advantages (quicker question-to-answer times) but also some disadvantages. If we extracted all the good questions and answers into a FAQ, then we’d be able to guarantee the accuracy/veracity/quality of those answers and maintain them over time.

The upside of using a message board or GitHub discussions is that the information is findable via Google or ChatGPT.

(This would also be true if we were using Slack or any other closed chat app).

The choice relates to search and bots. Discord can’t be indexed by Google and it can’t be scraped by AI model providers. That means that the information is generally impossible to find outside of Discord.

Regular tldraw .com and other end user app stuff could stay on Discord, but I feel like the platform is a big problem for the developer conversations around the tldraw SDK (tldraw .dev).

Would you be mad if I moved our dev community off of our 8k member Discord channel and onto GitHub Discussions instead?.

RT @jp_kiser: We need a Tic-Tac-Toe in TLDraw benchmark for agents.

RT @Infoxicador: Apart from us, the code editors (cursor et al) and @tldraw . Who else is doing Agent (Ai) driven Ui?.

did you know?