I often see this tactic on X (where you can create and host your Live Space) + on YouTube. I think that the very first time I saw it when @_maxblade was streaming. Then more and more people started doing it. IMO, it is a good tactic when you have a powerful fanbase/community on a certain platform. Do you think it is a "strong invitation" to participate in upvoting?
What other (unusual) tactics can help?
The Perplexity CTO announced at their developer conference this week that they're moving away from MCP internally. Garry Tan tweeted "MCP sucks honestly." Pieter Levels called it useless. The "MCP is dead, long live the CLI" post hit the top of Hacker News. OpenClaw, the hottest open-source agent project in the world, deliberately chose not to support it.
The argument: MCP tool definitions eat your context window. Auth is clunky. The whole thing is an unnecessary abstraction over APIs that already exist. LLMs are smart enough to call APIs directly, or use CLIs, or write their own integration code. Why add a protocol layer?
The more complex the community becomes, the more difficult it is to handle some things. I manage (several) communities and have to face many things that are not convenient to solve but have to do anyway so I would share my approach. It may help you. I picked 3 of the most common scenarios I face frequently. Hate comments, swear words, impolite convo I usually report these because some swear words can result in "copycat" behaviour (sometimes even for no reason) + which damages the brand. Bot comments Do not answer or report them as AI / fake accounts Concerns expressed over data in comments Although some businesses collect data, it is necessary to refer to the privacy policy you need to attach the link. (People are warned about this before using the product and they should be reminded to read it beforehand.) What were the struggles you had to solve?
We can enrich each other about "crisis communication."
Meow Monday I recently enjoyed reading this Discussion on insights and best practices to get more stars on GitHub. @zoltanszogyenyi suggested nailing the README file -- the most important of a repo? -- as it's the first thing everyone looks at. So, what makes a README file awesome from your point of view? What are the key elements you'd expect when reading one? Any good example?
