{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Web3 Tech Brief By HackerNoon","title":"Your Community's Moderation Bot Shouldn't Have a Single Point of Failure","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/a8d6df75\"></iframe>","width":"100%","height":180,"duration":730,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/your-communitys-moderation-bot-shouldnt-have-a-single-point-of-failure.\nFarcaster mod bots quietly depend on one AI vendor's API key. Here's an architecture that removes the single kill switch, using decentralized GPU compute.\nCheck more stories related to web3 at: https://hackernoon.com/c/web3.\n            You can also check exclusive content about #decentralize-ai, #decentralize-ai-hackathon, #ai-inference, #ai-infrastructure, #ai-compute, #farcaster, #nosana, #agentic-ai,  and more.\nThis story was written by: @kazani. Learn more about this writer by checking @kazani's about page,\n            and for more stories, please visit hackernoon.com.\nCommunity moderation bots on Farcaster typically route inference through a single centralized AI API, reintroducing the platform risk the protocol was built to avoid. This essay proposes an architecture that swaps exactly one piece, where inference runs, onto decentralized GPU markets like Nosana, using open-weights moderation models with a human-review floor. It also spends real time on the unsolved part: verifying subjective classifications from untrusted hosts without re-centralizing.\n        \n        ","thumbnail_url":"https://img.transistorcdn.com/eO2Jn0gxT_H9qDuuD0uleszE2n40sbZ-1T2r0zOcj9c/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMTY4LzE2ODMz/MTU4ODQtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}