@alpennec @davidbyttow there are a lot of great tools out there for solving the wiki problem. In contrast, we have a hybrid approach that brings together a lot of concepts that people want. It should be easy to debate issues, share a cool idea, and land new employees somewhere they can catch up and get acclimated to how people share ideas. All the while trying to stay as simple as possible 🐻

@copypastaa thank you guys so much!! It's a honor to serve. 🙏

@davidbyttow Congrats David. I am excited to see how this product plays out. When I used it for the first time, I was very impressed by how novel the concept of ambience music and assistants in a publishing product. There is no doubt that this product will get compared with Medium for personal usage and Docs/Dropbox/Slack Notes for internal company communications. But, given your track record and what I know about how you think about products from your blog, I am sure you have already foreseen all those comparisons and have already incorporated that in your roadmap. After all, both Slack & Medium succeeded despite the presence of strong players and existing behaviors in their respective spaces.

@sarthakgh have you not tried Ommwriter?

@chrismessina @sarthakgh Ommwriter is indeed cool!

@davidbyttow Any plans on tackling the "stale" article problem that every company's documentation faces...that is, keeping content up to date, especially when things change quickly and document owners might be changing too?

@andrewliebchen @davidbyttow the "stale" article problem is hard, we've used Bold for 10 months internally to keep track of standards, roadmaps, product opinions so we have developed much more compassion towards the problem. All of us have worked at different organizations and understand the problem about documenting the latest information, it takes a lot of time, and its not fun keeping everyone and everything up to date. One thing is for sure, human effort will always be necessary to solve this problem. So the writing experience needs to leave the author feeling light and without burdens. I am starting to believe that when requirements and beliefs change quickly, writing a new post that reflects the 'new world order' is an adequate way to combat old & stale articles because it keeps the conversation going. I'm willing to wager that our stream will help teammates see the latest posts. If an article needs to be permanent, anyone can pin the post onto the home page. If a post needs a visual representation of being referenced, we have post replies that append a label to the top of the post preview to represent the post's origin. We also designed Bold to be simple and compliment other products well, so if you do need your permanent Library of Alexandria somewhere, you can just link to it. Our goal with Bold is to keep it conversational where people continue to add to each others ideas instead of purely making amendments. Hope that helps! 🐻

@eriktorenberg thanks for the kind words! Even though the use cases are different, the products share the same core technology. The intent is to explore which aspects are the most useful, and take our learnings to continue to improve on our offering. At the end of the day like most creators, we love building what people need/want. We get good metrics such as # of posts made, company sign ups, and # of co-workers joined. Most company specific behaviors are more opaque because we can't reach into each company for specifics, but we feel bullish that people will jump on our Slack community and share all of the needs, wants and desires they may have.

@ldesserrey thank you !! 🙏🙏

@vladzima Looking into this now. Did you add a subdomain?

@vladzima @davidbyttow we are looking into this now, thank you for surfacing 👍

@meanjim @vladzima should be fixed!

@traf agreed. seeing the price helps me decide whether its worth my time to try it out.

@traf Hey James, appreciate the kind words! Bold Pro is $5/user a month. You're absolutely right that the pricing should be explicit; we're working to remedy that right now. In the meantime, feel free to sign up—we won't ask for a CC upfront or notify your team (promise).

@jeffrey_wyman @traf thanks for surfacing this! we really appreciate it. 🙏

@alexyoungkwon thank you! 🙏

@alexyoungkwon Thanks Alex :D

@desmonddantzler Hey Desmond, we're huge fans of Notion and similar products like Paper. While those products are great for real-time collaboration, we find that a single-author model works best for sharing ideas, news, and knowledge with your team. Bold is more akin to an internal blog rather than a documents app :)

@sirbenlee @desmonddantzler definitely fans of Notion! I think we are trying to assist teams in different ways as Ben mentioned earlier. I feel like I can build a whole knowledge product for my team within Notion, and I think for that reason we have different goals.

@ptrko Hi Patrick. Few things here as the acting CTO. First, nobody can view the posts easily because all content is encrypted at rest in our database and text content is NOT redundantly copied to other places (e.g., redshift, etc). We are not in the business (nor do we want to be) of reading any content by our users, this is extremely important. We use all of the best practices when it comes to securing both our internal systems (AWS) and employees' access to them (2FA, MFA, etc). Second, we do not retrieve or ask for any content access to your Slack messages and only request access to public channel names. Hope that helps!

@stelly_ryan thanks for the kind words Ryan!

@jpatcourtney I think that a blog format is easier to parse when new team members want to get an understanding of how the team has changed / grown over the years. It becomes really cool when you are able to see turning points, fun events, product launches, etc. A wiki at times feels like a place to throw information / deliverables and forget about it.

@jpatcourtney Hey John, great question. Wikis are great for housing institutional knowledge, but didn't fit the bill for our other needs—mainly thoughtful and transparent communication within teams. We've found that wikis typically require an active effort to build up, maintain, and organize. With Bold, a historical archive and knowledge base organically forms when a team publishes their memos, ideas, product spec, etc. This becomes invaluable when combined with search.

@sidie thanks a ton! big ups to @richcsmith 🙌

@singhamardeep thank you!! 🙌

@hanswerme thanks Scott!! 😎