Loading summary
Transcript49 lines
- [00:00]
A
Jack Dorsey just launched Buzz and it's gone completely viral. Yes, it's the same Jack Dorsey who co founded Twitter, who co founded Block. This guy is building what people are calling a Slack Killer. Now. Why does this matter for you? Well, it's being called a Slack Killer because it's almost like this agentic version of Slack. It's a way to have conversations with your teammates, except their agents. It's a way for you to huddle agents. It's a way for you to have software being built on the fly via agents. So in this episode, we're going to break down it so clearly for you so that you understand what it is, why you should use it, and what are the best tips and tricks to use Buzz. My take on this whole thing is it's a glimpse into the future of work. I can't wait to see what you think about it. And the by the end of the episode, you'll understand, if it's for you, why you should use it, how you should use it. Enjoy the episode. What's up, Vinnie? I saw your tweet. Jack Dorsey retweeted it. By the end of this episode, what are people going to learn?
- [01:14]
B
They're going to learn how to use Buzz. Mostly. I think it's like the sweet spot for Buzz right now is I think solopreneurs, small teams, they're going to learn how to use it to kind of brainstorm, keep everything in context between their agents and just build products, build solutions, ideate, and use it to get stuff out there quicker and be more productive.
- [01:44]
A
Cool. Okay, so what I hope to get from this is basically understand what Buzz is, understand why it matters, understand some best practices on how I can use it, actually use agents to do things for me. And by the end of this episode, I want to understand if I should actually use this thing or should I just basically continue using Slack and that's what I hope to get out of this. You think you could commit to that and also while you're going through it, just share the best practices that haven't been shared anywhere so that we've got a little edge on people. You think you can do that?
- [02:23]
B
Yeah, I think so. I just want to start off by saying, like, I think the Slack killer. Yeah, that's a good line. That it's a Slack Killer. But I think the real, like, the real selling point for me with Buzz, like from the beginning, is just the openness of it. So do we want to start there just like what I mean by open and what kind of like what that allows, like the power, how powerful the openness feels. Feature of Buzz is.
- [02:52]
A
Yeah, I mean, sell me on Buzz. Like why?
- [02:55]
B
Okay, okay.
- [02:56]
A
Yeah.
- [02:57]
B
So first off is Slack with agents inside. And a lot of people like, it's kind of like Slack. You got agents inside. So Slack allows you to do that by adding an integration. But in Buzz, they're like first class citizens, right? So they're members of your team. You don't think of them as like add ons or just kind of a side feature. They're an integral part of the app. They are part of your team. Think about it that way. So I'm kind of. I like to keep things simple. And I just started using this not too long ago. I mean, it's only been out for a little while. I just discovered it. And these are basically what you see here are the default agents you get when you start. But under the surface there's a really powerful thing which is you can edit and add agents, and when you give agent instructions, that's just basically like a system prompt. The really cool thing underneath is the harness. So we're all probably using codecs, Claude code, maybe something like open code to do our coding work, build products, whatever, be more productive. The great thing here is that your agent harness is swappable under any agent. So I can go under here and say, you know, I want to use cloud code, I want to use Codex, I want to use Goose. And like, for me already that point there was like, okay, this is very cool. And the reason why this is so cool is because, I mean, if any of you, all your listeners probably follow the stuff, AI moves at like breakneck pace, right? So today it's this model, the next day it's the other model. And sometimes I don't know about you, but personally I'm like, I get model fatigue where I'm just like, gosh, you know, I just switched over to this, I just got used to this model. Like, I don't even want to hear the good things about model X because I'm still over here using model Y. But the cool thing about this is that this is a layer on top of that and you can just switch. And the best part is, is that your agent, you don't lose anything in that switching process. You can change the harness under your agent and all the context that's in your chats. So everything you've been chatting about with this agent, like all the stuff you're trying out, the apps you're building, that all that context comes with to that new harness to that new model. So first off, that's something I think is really cool about Buzz.
- [05:26]
A
That's a, that's a huge deal. Because I feel like a lot of us are ping ponging between different models and harnesses and stuff like that. And it's tiresome, you know, when you're, when you're starting from scratch, it does feel like. And then I need to understand, okay, what is SOL good at too, you know, like, and what are the contexts for this particular model to get the most out of it? So I think the fact that this is built natively into the product, that you can go and switch just like, I like that because it's thinking about how people are working in today's day and age and they're acknowledging it and they're like, we understand that yes, there's gonna be new models all the time and you might wanna be switching, but you probably don't want to spend a lot of time adding context, figuring out things. Cause you're busy trying to run a startup, trying to make money, trying to be productive.
- [06:24]
B
Yeah, exactly. And you can take all your stuff with you. If you've built all these skills and skill files and folders and stuff. As long as they're in the global directory, if they're accessible globally and they're not project specific, Buzz can access them. So you can install agent skills like normal, then you can change harnesses, change models, and your agents in the chat have access to all of them. So I think that's really cool. I'm really happy about that.
- [06:56]
A
Okay, what else do we need to know?
- [06:58]
B
We've got audio huddles with agent. So that allows you to have like an audio chat with your agents and they'll be in the chat and they'll respond to you. And so you can have a voice call with someone else, bring an agent in and communicate. And they also get the context of your whole chat in the audio huddle. So that's pretty cool. Um, I haven't tried that out yet though. So I have seen there's some good videos on YouTube that run through it and show you how to do it.
- [07:25]
A
So what's cool about huddling and you know, agents or an agent. I tweeted, I tweeted about this. I feel like what I'm missing from building in the AI age is I feel like I'm asking my agents to do things. Maybe I'm using whisper flow or even just typing it and it feels very much like back and forth, back and forth. What's Cool about a huddle is it's live. And the way my brain works when I'm being creative and stuff like that is I need, like, live interaction in order to really, like, extract what's going on in my brain. I think there's probably a lot of people like me like that. So it's cool that that's a feature. My dream, and I tweeted this, my dream is eventually to have, like, the ability to FaceTime agents. And that, to me is like the holy grail of the future of work. But cool that you can see that Buzz is scratching the surface here. Is it good? Or if it's not good, we'll have to test it. People in the comment section, please let us know. But it's interesting that that feature exists. What's another feature that you're excited about?
- [08:37]
B
I mean. Well, right under the surface, you've got these agents, and you probably want them to do work. So they're like, integrating. They have Git pretty tightly integrated into it. And your agents will actually. They're doing coding. They can create projects, they'll create feature branches, and they work in parallel work trees. So they're not actually messing with stuff that's locally on your computer. They'll make a work tree, a copy, and they can work there. So they can do things in parallel. So you could, for example, you're talking to your teammate about a ui, the design of your product or your webpage or something, and you can just tell the agent, like, spin up three different versions of landing pages based on the ideas that you guys had in the chat, right? And they've just added this projects view. So if you go into settings here, there are experiments. You can turn on workflows and projects, for example, and then you'll see that here. And this is basically like your apps that you're coding on with your agents and working on with your agents. And another interesting thing is that you can integrate with GitHub, but under the surface, they have their own hosted git hosting. So you can push to remote repositories that are actually on your relay. So that's probably a more technical thing, but Buzz works on relays. So these are like servers that you host or that get hosted for you by Buzz, by block, and then they'll actually push that code to the remote repositories on your relay. So the relay is where all your information, all your chats, everything, that's where all that stuff is happening and where it's stored and where it's getting sent and pushed to the other people chatting with you and the agents chatting with you. So I can see in the future that they're trying to take on more than just slack here, they're trying to take on GitHub as well. So that's pretty crazy cool.
- [10:50]
A
And I think for the non technical audience, I feel like a lot of my non technical friends are actually starting to use GitHub now in the AI age. I don't know if you've noticed this.
- [11:01]
B
No, I'm kind of in the. Mostly in the nerd bubble.
- [11:07]
A
Yeah, it's interesting. I feel like 5 years ago if you were non technical, 10 years ago if you're non technical, you barely knew what GitHub was. The word repo, you were like, are you repossessing my car? But I think now in an AI age where we're kind of all technical in some way, something like this makes a lot of sense to be built natively.
- [11:34]
B
Yeah. And the interesting thing is you don't really have to know that much about it. You don't really have to even consider it because your agents will just kind of take care of stuff for you. I was doing stuff here where I was asking you pull up a simple CRM app and you know, I told it, here's the chat right here. Spin up a simple CRM app using the WASP full Stack framework and deploy it to Railway for me. So, you know there's some technical knowledge there. You know, I'm asking for a specific framework, a specific hosting provider, but it'll do that. And even, you know, gets stuff, pushes it to these remote repositories, deploys it live on the web and even sends you screenshots. So it's like, oh, here's your, here's your CRM, here's your. That I just made. And that's all before I even checked out what it was even doing. So just, it did it for me, gave me the links, gave me a little preview of it and yeah, I thought that was pretty cool.
- [12:36]
A
That's, that's insane.
- [12:38]
B
Yeah, there's a lot of. I feel like they've baked in a lot of workflows and a lot of just like prompts into these agents so that these agents kind of can work end to end and really get tasks done. I think that's the idea.
- [12:53]
A
Yeah, that's insane if you think about it. We're kind of glossing over it. But look what you built.
- [13:00]
B
Yeah. And it's live on the Internet already. So the nice thing is I already had a Railway account I know a little bit about working with full stack apps, but I didn't really tell it much. I just said, you can see the chat, put this online. So now I have a fully functioning CRM dashboard that I can share with team members and then we can. The cool thing is then what you would do is you'd add them to this chat here and you'd start talking about what features are missing, what things you don't like. And then you guys, you have a conversation with your teammates and you come to a conclusion and. And you just tell your agents to go ahead and start working on it and they'll do it.
- [13:44]
A
So why this is a big deal is, if you think about it, you know, you're able to create software on the fly, essentially automated, that's high quality, that could be deployed, that you can manage in a view that you know is clear. And I think, you know, if you think about your business, let's say you work, you have an agency, business proposals is, you know, the lifeblood of your. Of your business in a lot of ways. Right? And, you know, imagine that you can create proposals based on people's data. Maybe you're pitching the NFL and you're, you know, you could put in the context of the pitch, meeting notes, let's say from granola or something else, it ingests it. And then on the fly, you have these agents based on that create proposals that are unique to those clients and it's vibe coded or it's using agents to actually create them. There's so many ways that you can use this interface to think about, okay, I have context over here. This is how it comes in. And then here's how it's going to get spin up on the Internet or through an asset that is built within code, and then here's how you're gonna view it. Is that right?
- [15:07]
B
Yep. Yeah, exactly. In one of the. One of the videos I made that I posted on Twitter, that was what I was going through. So I was taking more of like a marketing angle and I built a tweet leaderboard for Twitter. So, like, my team, like, how much we're tweeting, how good, what are our top tweets? All that stuff, all that information was being collected in this, in this app, this full stack app. And then I was like, oh, well, instead of just building it with Buzz, why don't I get Buzz to also access the app, get that information. Then we can get like, you know, daily reviews here, daily digests, and we can also like, kind of brainstorm on what's working in our Twitter strategy for marketing. What's not working? Get it to find links between the popular tweets and brainstorm, come up with new stuff. So that's exactly what I did. I told it, let's build a publicly facing API and then let's build a workflow. So I just tell it daily, check that API and give me the numbers back. And then the awesome thing is that's what you're seeing right here in this tweet stats for Apple from app. It's getting the stuff from that dashboard through an externally facing API and putting it here into this channel. And then I can reply to it and be like, okay, Fizz, which is one of the agents, like Fizz, let me know what's the common thread between my successful tweets this last seven days, because it also sends those over the API. So if I understood you correctly, I think you're talking about kind of these workflows where you're like this circular stuff where you're giving information in getting it out through apps and it's all going into the context of your agents and stuff like that.
- [16:59]
A
Exactly.
- [17:00]
B
Yeah.
- [17:00]
A
I mean, I'm interested in this because this is like the quote unquote boring stuff that every business has that if you can figure out how to have some unfair advantage here, it's what separates a good business from a bad business.
- [17:18]
B
Yeah, and that's the thing I really like is that this openness of buzz, like it allows this kind of, these kind of integrations to happen very easily. So with Slack, like you would have to, you know, to get all this kind of stuff up and running, you'd have to get API tokens, create an app on their platform. All their stuff is proprietary. You have to like learn the structure of things. I mean, with agents that's easier. But here, because it's built on these open protocols, you can get stuff like this running really easily. And then you have this just like crazy context engine that just can help you do work. Like if I wanted to, I could ask Fizz right now, you know, like connect up the app or, you know, connect yourself to the X API and make it available so that we can start tweeting from Buzz. Like that wouldn't be that hard. We could probably do that in 15 minutes. You know, crazy. One thing that I really like about this kind of, you know, this close. We were talking about this closed circle of like context that I'm getting back from my app. So that tweet dashboard app is that like, here it sends me the tweets every day and the stats, like the top tweets and my stats and impressions. And I can just ask the agent, like, let's make sure I'm replying there. And I'll just say, like, what can. Like, what is the common thread between my top tweets? And sometimes, like, I used to do this in a session with Claude Code or ChatGPT, where I'd be like, literally, you know, exporting tweet data or copying pasting tweet data and putting it into chatgpt on the. On the desk or on the browser. In the browser, you know, getting information, chat about it and pulling it back. But like, this is so cool because it's pulling the. It's getting the information from the X API. It's in the context window of the agents here. I can chat about it here and then, you know, where we can chat with colleagues about, like, what, you know, what are some more tweets we want to push out? What's a different marketing angle we could take? And that's what I really like about this here. And you're gonna see there is the agent working. So what's actually going on in the background? That's nice. If you're used to looking at this kind of stuff in a terminal, you actually see the tool calls that it's the tools that it's calling. And here it is down here, like, what is happening? So it's getting information from the channels, checking for newer stats and things like that gets the results. And so that's all like kind of under the curtain stuff. But we should get a response back soon.
- [20:12]
A
And is there any tips around how you is best to talk to them? Like, I see here is you just wrote a short and concise question, but how should people think about the best way to talk to some of these agents?
- [20:32]
B
I mean, they're pretty good at pulling out the intent behind your questions these days. So just have a conversation with them like you would like a normal person. So I don't think, I at least don't have any special approach there. I kind of just say, you know, this is probably nicer than what I would normally type. Usually I got typos in there and stuff. I'm like, give me the sauce. You know, and they're usually pretty good at that because they have all this context. So I'm usually pretty straightforward and concise with the questions and the stuff the prompts I give reported back. So it's showing what I did. I tried Jax Buzz, I deployed open SaaS to open ship. My first time successfully self hosting. So it's showing that, you know, I'm doing these things as a beginner and I'm reporting back on what I learned and those are the things that are doing well. So it worked. Are my top two top two tweets got over a million impressions but this sucked theme got, you know, they were the bottom half and they got a collective, you know, 88,000. So novelty gets you reach, friction gets you engagement. So there's some actually really good advice there. And that's kind of the power of using it here and having all of it in Buzz is that makes stuff like this easy and illuminating. So that's really cool. I like that.
- [22:04]
A
By the way, I saw one of the pieces of feedback is nobody is mentioning that Buzz has a backdoor for bitcoin native payments. What does that mean?
- [22:17]
B
So Buzz, we were talking about open protocol so I kind of glossed over this. It's built on Nostr and Nostr is the name of the open protocol that Buzz is built on. And I personally believe because if you know Jack Dorsey, he's a big fan of bitcoin, Nostr has tightly coupled with bitcoin Lightning which is a very fast and almost fee less way to pay transfer bitcoin. And my guess here is that because it's built on Nostr, Nostr is open, you'll be able to integrate Lightning bitcoin lightning payments into Buzz and you'll either be able to pay agents will be able to pay for compute, this shared compute IDO that we talked about or that's in there in the settings you'll be agents will be able to pay for work and compute or people will be able to pay other people tip other people for tasks they get done. So like I can honestly imagine a big open community of let's say, I don't know why I keep gravitating towards graphic designers but like say designers and you know, you need a really cool logo and AI gen image gen isn't really doing it for you and you ask some people to like, you know, spit out some ideas and some random person and some graphic design community on Buzz gives you an awesome logo and you just tip them. Thank you for that idea. And then you go ahead and keep working. We'll see. It's not integrated at the moment, but I think it will come very cool.
- [23:53]
A
Awesome. So what else do people need to know about Buzz?
- [23:59]
B
So let's see, you mentioned that shared compute idea and I think that goes back into the openness of Buzz. And that's really cool. And that was something that really surprised me too. So why don't we just talk about that for a minute. So we've got this compute setting here and you can turn it on and it will automatically suggest some local LLMs, some local model AI models that you can download on your laptop or in computer and you can literally share them with the other members of your team. So let's say that you are just starting out, you're a college student and you want to start building a business. You've got this awesome idea, you don't have a lot of time, you don't have a lot of help and you don't have, you know, like the money to buy one of these Max Pro plans, whatever they're called, with like unlimited token budget so you could get together with some friends, you know, buy a decent sized laptop or a Mac Studio or something, or maybe even like a beefy Mac mini. You put this on, you share compute and all of you can use this one model running from one machine, even though you're chatting from different, from different laptops, from different computers, whatever. So that's just like a very simple example. But you can see how they're paving the road here for real openness in model choice and being able to really harness the power of these open source and local models that are always getting stronger and starting to compete with the frontier models from Anthropic and OpenAI. So I think that's really cool.
- [25:43]
A
And why do you think that even this is worth playing with? You know, why is this really important? Why is local important in the grand scheme of the future of work?
- [25:58]
B
I mean model choice is important depending on what you want to do. And you know, it's the same idea where Slack is the controller of your data and that data is very valuable. You're sitting here, you know, spending. I mean this stuff makes work a lot easier, but you still have these really cool ideas. You're iterating on these ideas, you're putting stuff out there that you work pretty hard on and that you think a lot about. And then to have like just one company control all that data, basically, like Slack for example, have the whole all your data in that sessions and if you're tired of Slack and want to move to something else, it's really hard or it might not even be possible to take all that data with you to some other platform. So you just stay there and you're stuck with them. It's the same thing for models you know, you see people talking about why, you know, there, there are, who knows, Today it costs $200 a month for an unlimited plan. Tomorrow it might be 2,000. We don't know, we don't know how, how what's going to happen. And the future, you know, having choice in the future is very important for the integrity, for the sustainability of any business. Because that's your data, that's what you want to be able to do with it. I don't know. Some of these models have restrictions on what you're even able to ask them. So governments have top down mandates on what they're allowed to do with the models or not. So, you know, we saw models get pulled back after people started using them for a couple of days. So like you're building your businesses on top of these tools. You should be, you should have flexibility and freedom and control of these tools, basically.
- [27:37]
A
Yeah. And I think the big insight of all of this is a lot of us haven't realized how much of a content hub, Slack and products like that have become to us. And we're learning that if you want to get the best out of any of these models, you need to have the most amount of context possible. So what's really cool about Buzz is it's basically like, okay, we recognize that this is your context foundation and we're going to go help you do a bunch, like we're going to help you pivot into a bunch of directions. You want to have these projects that are integrated GitHub, we can go do that. If you want to do local stuff and do shared compute, we can help you do that, etc. Etc. You want to huddle an agent, we can help you do that. But, but what's so cool about it is whatever you decide to do, the context is at the core of it.
- [28:39]
B
Yep, yep, exactly. And that's what I like about it, that's what I think is really cool, is that I think they really hit on something here. So, you know, I think we'll see. It could go like I saw people commenting openclaw, you know, nobody's talking about openclaw anymore. Openclaw was a real wow moment. And like, okay, we can get these agents to do a lot of productive work for us, but I have the feeling that it was missing something and this shared context because we're working in teams, we're working with other people. Teams might even just mean your other agents, right? Like you just, you're going to have conversations, whether it's with one agent or another. But now you have the ability to expand that the your team set, Expand your, you know, your global context window, so to speak, and then make it globally available to everyone in your team, including the agents. So, yeah, I think it's super cool
- [29:39]
A
around setting up and managing your agents. Is there any sauce here? Is there anything people need to know besides what you've already shared?
- [29:49]
B
I wouldn't say so. I've seen it. Depends on how deep in the weeds you like to go. My honest opinion would be you probably don't need to do that much. All I did, the first thing I did was just I wanted one that's Fable I'm using specifically or exclusively. I'm using Claude code as the harness under here. But they have adapters, so you can adapt. You know, you could even adapt Open Claw or Hermes or openclaw or, I'm sorry, opencode or Goose. So, like, any of these harnesses can be added under the surface here under the hood. But the first thing I did was I just pinned them to models. So Fizz is a Fable model and Honey is Sonnet. Because there's just certain tasks that I don't need to use the power of Fable and burn through tokens so fast. So that would be like my main piece of advice. Besides that, just start playing around. I made this Chief Agent Officer. So, like, if I do start to create more agents with more specific kind of instructions and system prompts, then I might delegate the. Delegate the delegation to Mr. Chief Agent Officer here and be like, okay, I have this task. Who's the best for it? Because, you know, you might have a copywriter, you might have a brainstormer, you might have a code reviewer, things like that. And you might forget who they are or, I don't know, you just get an agent to kind of delegate. So that would be pretty much my only advice on that side there.
- [31:21]
A
Cool. Anything else you want to show?
- [31:23]
B
People were asking in Twitter about skills, and I think I mentioned it already. But, like, all the stuff under the surface that you're used to using, if you use Claude code or something, that's all available, as long as it's to buzz your buzz agents, as long as it's globally installed. So skills and things like that, yeah, they can use and they can take advantage of so you don't lose that stuff. So that's also very nice. And I would say that, like, this is beta software. It's like it might even be alpha. I'm not sure. It's like early preview software. So some things don't work that great. I was trying to create workflows and, you know, like set up recurring tasks and things like that, and they weren't really landing great. That was one thing I noticed. Another thing I noticed was things can be kind of slow. If you're used to it being like working directly in cloud code or in a codecs, it seems to be a bit faster there. And I think it's because it's communicating with your server, your relay and communicating back. And because of that, I think it's at the point now where it's like really good for, like I said, solopreneurs, small teams iterating on small software or small ideas. And if you're really doing like, you know, complex software engineering, this might not be the tool that you want to use. But if you're just looking for something that can bring you value and like I said, bring all this stuff, all your knowledge into one central, one central tool, then this is definitely a great thing to use.
- [33:04]
A
So if you're a founder, small team, maybe you know, 1 to 10, under $10 million in revenue, 0 to $10 million in revenue. Like should. Should you use this thing? Maybe you're using Slack today. Should you download Buzz and actually try it out?
- [33:23]
B
So I'm pretty convinced that I'm trying to convince my team at WASP that we use this internally and exactly for that reason. So we are a small company, a small startup, and we're a developer tool. So we're a software company. And you have all this stuff that you talk about in Discord. We talk about in Discord and we have our community there too. So that's one thing I should mention, is that you can create channels that are private and public, right? So you could invite people from your community using your product to come chat with you, and then you have private channels just for your team. And then that context is shared, which is also a huge thing, because if someone comes into you into your chat and says, hey, we want to get this fixed, then fixing it with an agent is just a, you know, an at away, right? You would just tell Fizz, like, let's tackle this bug. Like whoever just did a bug report or said wanted a feature, you could just have them prototype it right there. So, yeah, I think for small teams, this is definitely worth checking out.
- [34:37]
A
So my take on this is, this is so cool. It's clearly scratching the surface around what the future of work would look like in a world where you have more agent employees than teammates. It does feel early. It does feel like they're just, like I said, scratching the surface. But my passion is, I don't know if you know this about me, Vinny, but I'm a co founder in a company called LCA Lay Checkout Agency that business designs the world's biggest AI native software. Not Buzz, but like, you know, companies like that. And when I see something like this, I'm just like, it's close. It's not there yet, but it's close. And I do believe that it's probably worth. And I have no affiliation with Buzz or Block or Jack Dorsey, but I do think it's like worth trying these tools just so you can, you might learn a thing or two and then even if you don't end up using Buzz, you might just end up, you know, configuring Slack in a way that you know is best for you and you learn something here. So I think. Or you might realize like you love Buzz and forget about Slack and this is what the world you want to live in. Regardless, you're going to learn. There is no losing in this situation. So I think the most important thing we can, one of the most important things that we can do in the AI age, in the agentic era, is just getting our hands dirty, learning how these tools work, playing with them and seeing how we could live in the future. Because the people that live in the future, Vinny, those as you know, those are the people that could, you know, look around the corner and who can create products that people really want. And you know, I think that's really important.
- [36:36]
B
Yeah. And yeah, you bring up a really good point. And I think that's why they're kind of looking around the corner with this already. And what I think could allow them to really be a strong player in this arena is the fact that it's open source. So anybody that has an idea of how to. So it's an open source app built on an open protocol. And so anyone who has an idea of how to improve this can. And you know that that might take it in the direction because the, the, you know, the, the hive mind, so to speak, is like going to be using this thing and working on it at the same time. So they'll be like, okay, this isn't working for me. I like this about, like you said, trying out some from some other tool. I like this about the tool I usually use. I'm going to add that in here or whatnot. So that might work to their advantage very well and it might become the tool that people just kind of default to. But things change so fast, so who the hell knows?
- [37:41]
A
Amen, brother. Vinny, thank you so much for coming on, giving us a tour, sharing some sauce. I'll include links in the show, notes in the description where you can follow Vinnie for more of this sort of stuff. I would love to have you back on the podcast, Vinnie, the comment section on YouTube. Please let me know if you enjoyed Vinny. I certainly did if you enjoyed this topic. What you want me to cover next? Thank you so much, Vinny. Any last words for the people?
- [38:12]
B
Well, if they want me to come back, I can show them some sweet stuff about how you can use the open protocol that Buzz is built on. So you can go pretty deep. And I think there's some pretty powerful stuff there that we both alluded to in our tweets. So, yeah, it's worth checking out.
- [38:30]
A
Cool. Yeah, let us know. And we live to serve, so if that's what people want, we can go deeper. Thank you, Vinny. Have a creative day, everyone, and I'll see you next time.