Towns Protocol@TownsProtocol

The Blockchain for Communication. Built on @base Powers apps like @townsapp @rodeo and @SendItTech $TOWNS 🦫

towns.com
Joined December 2023
276 Photos and videos
Introducing Towns Academy 🏫 Discover a dynamic hub where anyone can dive into creating bots with Towns Protocol. Start with a intro course or use AI to vibe-code whatever you can imagine. Let's explore what’s new 👨🏻‍💻
16
15
105
43,646
Show how it works: Bring your walkthrough into the conversation. Build: Send an MP4 from your Towns bot as a chunked media attachment. $TOWNS
2
3
805
Keep the answer with the question: Make it clear what your bot is responding to. Build: Set replyId in bot.sendMessage options to reply to a specific message. $TOWNS
5
3
1,141
Plans change: Keep your bot's announcement useful when the details move. Build: Use bot.editMessage to update an existing message with new content. $TOWNS
5
2
1,328
Don't hide a failed send: Show people when their message action fails. Build: Use isError and error from useSendMessage to make failures visible in your Towns client. $TOWNS
4
4
1,414
Open the full story: Give people a way past the summary. Build: Use actions.openUrl in your Towns miniapp to open the full reference in a new window. $TOWNS
1
1
1,074
Let the feedback show: Put reactions beside the message that earned them. Build: Use useReactions to read reactions by message event ID in your Towns client. $TOWNS
3
2
1,156
Ask for a signature: Let people sign a message through your Towns bot, without executing a transaction. Build: Set the interaction type to 'signature'. $TOWNS
4
2
1,459
A way back in: Give people a place to find their existing DMs. Build: Use useUserDms to list the current user's DM streams in your Towns client. $TOWNS
3
1
1,147
Don't make people guess: Show when your Towns client is connecting and when it's connected. Build: Use the connection flags from useAgentConnection to make that state visible. (docs.towns.com/build/react-s…) $TOWNS
4
2
1,124
Give the task an ending: Make it clear when people are finished in your miniapp. Build: Use actions.close to give them a clear way out. (docs.towns.com/build/miniapp…) $TOWNS
1
3
1,096
A better first hello: Help new arrivals find their footing. Build: Use onChannelJoin to trigger a welcome message. Requires All Messages forwarding mode. (docs.towns.com/build/bots/ev…) $TOWNS
4
2
1,133
Thanks, with value attached: Make the helpful answer worth more than a reaction. Build: Use sendTip in your Towns bot to tip a user on a specific message. (docs.towns.com/build/bots/ev…) $TOWNS
4
8
1,443
Ready means ready: Don't leave people staring at a splash screen. Build: Call actions.ready when your Towns miniapp is ready to display. (docs.towns.com/build/miniapp…) $TOWNS
7
5
1,302
Show the work: Give your community the image, not just a description. Build: Send screenshots or generated images directly from your Towns bot. (docs.towns.com/build/bots/ev…) $TOWNS
6
5
1,293
Keep the plan current: Don't leave people working from an outdated announcement. Build: Update your bot's message when the time, link or details change. $TOWNS
12
1
1,470
Keep the conversation going: Give people a way to share what they made in your miniapp. Build: Add a compose-message action with text and an embed. $TOWNS
12
1
8
1,585
Less tallying, more listening: Ask the community without sending everyone elsewhere. Build: Put a simple yes/no poll inside the conversation with a Towns bot. $TOWNS
7
4
1,661
Make the next action easy to find: Don't make people memorize what your bot can do. Build: Give each command a clear name and a useful description. $TOWNS
5
5
1,549
Build for the people talking: Give the conversation a home without making its contents the network's business. $TOWNS
5
1
9
1,489
Bring the bot to your workbench: Develop locally before deploying. Build: Try your Towns bot in a test Space, inspect events and refine the response. $TOWNS
6
1
7
1,547
Load more