Lately, we’ve been getting a lot of feedback about Twinity, not all of it positive, but we’re listening. I wanted to take a few moments to share some of the feedback, and what we’re doing to try to continue to make Twinity better for you.
- Release notes don’t come with the release. This has happened in the past on a few releases. We’ve been moving towards a more controlled release process during the past couple of months, and we should be in better able to produce the release notes at the time of release moving forward. You will have seen that the last release, last week Thursday, had release notes within 1 hour of the release going live.
- Too many newsletters. There’s a lot of fun stuff going on inside Twinity, and we’ve wanted to showcase that to all interested Twinizens. Going forward, we’ll try to be a bit less frequent with those, and we’ll instead publish events here on the blog, and of course, on the Twinity events calendar.
- Not enough transparency. This applies to a couple of different areas – development and operations. We’ve heard questions about our server infrastructure, regarding its sufficiency, and our development roadmap and timeframes. From the operations side, we will commit to informing you when there are server or infrastructure-related issues, and share with you the reasons and the solutions, as best we can. From the development side, we are working to include information on the immediate roadmap and any current hot topics from the development team in the newsletter.
- Unable to connect to Twinity. We’ve heard this from some members, and particularly from Mac owners. We’re looking at a number of different solutions, but in the immediate short-term, we are focusing our efforts on increasing the quantity and quality of our logging. Those logs can be sent to us via our Twinity diagnostics, via our crash reporting, and of course, our customer support team may need them in helping you connect. We’re starting a new effort to confirm the ability to connect to Twinity from a variety of environments, such as Internet cafes, libraries, DSL/Cable home lines and corporate networks. We’re looking to work one-on-one with anyone experiencing chronic inability to connect to Twinity. If this is you, please let our support team know, and they’ll contact you to try to set up a time to test together.
- Twinity performance. We’re currently working on tweaking Twinity’s performance with a content delivery network. This should ensure smoother teleports and loading of assets for all Twinizens worldwide. Aside from that, we’re reviewing key sections of the code that can have a big effect on performance.
- Encouraging the discussion. I’d like to personally invite all Twinizens to comment more here on the blog. Most of the feedback mentioned above has come via individual emails and messages. By moving more discussion here to the blog, the conversation can be more opened, and followed by the whole Twinity community.