[pfraze]

Really sorry about breaking your old apps. If you ping me on twitter (@pfrazee) or IRC, I can spend some time helping you convert them over. Most of the same capabilities are there (or on the way) so we'll hopefully just need to update the code.

EDIT: for anybody curious, we had to make breaking changes to the p2p protocol and used that as a chance to bundle a lot of improvements -- mainly with performance and reliability. It sucked to break existing content though.

[yepthatsreality]

> EDIT: for anybody curious, we had to make breaking changes to the p2p protocol and used that as a chance to bundle a lot of improvements -- mainly with performance and reliability. It sucked to break existing content though.

What guarantees are in place to ensure this wouldn’t happen again in the future? I really like the project and realize it’s still young and can probably risk piling on breaking changes, but I can’t imagine future upgrade paths will involve contacting one of the project maintainers on Twitter.

[pfraze]

> What guarantees are in place to ensure this wouldn’t happen again in the future?

I will say that I'm personally embarrassed that we had to do it. I don't like disappointing people who support our work. There was a post on HN recently about how Unity keeps breaking its platform; I don't want to end up like that.

The other thing I'll say is, there was a year-long gap from the 0.8.x beaker releases to the 1.0, and a lot of that time was connected to the engineering work on the protocol. The top priority was scaling, but we also added tooling the protocol so that if a similar breaking change is needed in the future, we can handle it smoothly.

[Do4oolu5]

That's ok, you're doing an awesome job, keep focusing on the good work :) It'll probably itch me again at some point.