Hi b@ users and supporters-
I've decided to proceed as planned and discontinue b@ before the new year. B@ will go offline indefinitely sometime during New Years Eve day, 12/31/16. There may be a server disconnected message but this will eventually be replaced with a blog post explaining the discontinuation.
I want to thank those who signed up to support b@'s potential continued operations in 2017. We raised up to $374/month, which was more than enough to cover the server cost. As of this message, I have cancelled the Patreon page and no users who signed up will be charged. If you were charged, please send me a message and I will provide a refund.
I still think it's the right decision to shut down b@ as planned. To enumerate some of my top reasons:
1. Support - Covering server costs is a great first start, but the fact is this aging codebase requires someone to pay attention and fix issues and vulnerabilities. We all know people are constantly poking and probing b@ to find weaknesses and we can't keep up. To keep someone on part time is up to $1600/month and it also requires a significant amount of my personal time to triage issues, respond to customer issues, document fixes, etc. I don't have a product management intern or resource required to offload this enormous time commitment that falls on me today.
2. Tech Debt - Bottom line: B@'s codebase is very OLD. I began writing this version, line 1 character 1, in 2010 using PHP and a text editor. It has evolved significantly to keep with the times (i.e. a robust Rest API) but the underlying LAMP architecture is just not the way to go today. And I don't think I should have any part in the technical design of the products I build today. If b@ was to continue I would rather scrap the technology and start over.
3. Stress - B@ is a barrage of constant stress for me. I can't do it anymore. For the sake of my own health, not having the burden of managing the wild west of b@ behavior is absolutely necessary. This point can't be understated... it really is hard on me, physically, mentally. I think in a way we could all benefit from disconnecting from this medium.
That said, I haven't ruled out the possibility of building something entirely new, from the ground up. I very likely will not make something in the next year, but launching a new service is not completely off the table. If anyone is interested in helping me build the next version of b@ (that's not b@), feel free to send me a message.
I think that's all there is to say right now. T minus ~48 hours, b@.
Jae