We appear to have possibility resolved the issues around unicode support without requiring an update. The issue appears to have originated from the server and the current version works without changes. Unfortunately, existing articles and feeds will not show up properly, but ongoing articles should properly begin showing up as of today.
If you still have issues with certain characters or character sets not displaying, please let us know or drop us a comment.
[Updated Feb 19, 2010 6:48 AM EST] We apologize for the extra downtime. Everything should be back up. Let us know if you see any issues. We hope to get our 2.0 testing started this weekend. Note that we still have room for testers, so email us to get on board.
—–
[Updated Feb 18, 2010 8:30 AM EST] Unfortunately our update process did not go as smooth as we hoped so things are taking longer to resolve. We hope to be back up by mid day. Thanks for your continued patience.
—–
[Updated Feb 17, 2010 11:30 PM EST] RSS Viewer is now down through the nite for updates
—–
RSS Viewer will be going down for maintenance tonite at 11 PM EST in order to begin transitioning to our next release set to begin alpha testing this weekend. We plan to be down all nite migrating everything over. All access including logging into RSS Viewer will be unavailable. We will update this blog and our twitter account when the maintenance starts and completes.
If you are interested in alpha/beta testing and have not yet replied, please send an email to info@znetdevelopment.com. We still have spots available.
Thanks,
Nicholas Hagen
As many of you know we were trying to get our 2.0 release out by end of January. Unfortunately, that date has passed, but we are still hard at work trying to tie up the final loose ends of the release. All of our planned features have been implemented and we are just cleaning up and trying to get everything nice and polished. We want to ensure a great experience when we release our update, so continue to bear with us.
That being said, we will be looking for beta testers in the upcoming weeks to help us test this release to ensure we meet that great experience. If you are interested in helping us out, send us an email at info@znetdevelopment.com with your registered email address. Note that you must not be using a jailbroken device to participate in the beta program. Unfortunately, we will only be selecting a few users. In particular we are looking for users who want to test out the following:
Thanks again for everyone’s continued patience.
Several people have asked when the next version of RSS Viewer will be coming. Here is an update to that question as well as a list of some of the more prominent features. We are currently trying to release a version to Apple by the end of January. The following features are some of the highlights for this release:
We are also improving performance and several bug fixes.
Thanks,
Nicholas Hagen
[Update 1:15 AM] We are back online and everything looks good. Let us know if you see any issues.
RSS Viewer will be having a maintenance outage on Monday, Nov 16 at 12:30 AM. The outage should only last 1-2 hours at which point all services will be unavailable. We are further expanding our capacity to provide faster updates once again.
Thanks
Everything is back up again. There was an intermittent issue with accounts not creating properly. The issue has been addressed and everything should be functional again. If you notice any issues, drop us a note so we can help resolve it quickly.
We will be down for a quick maintenance at 1:00 AM EST. We should be back up within 15-30 minutes.
Thank you to everyone who has purchased our application and stayed with us as we continue to improve upon things. We are now averaging about 20,000+ push notifications per day and only expect that number to climb more and more. We have much more in store over the coming months and hope you continue to stay with us as we improve our application and systems each day.
[Update] We have re-enabled user registrations. However, we will be disabling accounts in which push notifications fail to be delivered. This does not mean that you have to enable push notifications. It only means that if you enable push notifications and we are unable to deliver a message (typically due to invalid devices or uninstalled applications), then we will disable the account temporarily. If your account ends up disabled and you are unable to login, send us an email and we can re-enable the account. Once our next client version is released, we will have better measures in place to avoid unauthorized usage. At that time we will remove these measures.
As many of you have realized, our servers have been having several issues through the past weekend. Unfortunately, are servers are under attack, which we are working to alleviate and resolve. We will most likely be releasing a new client version with a fix in place to stop illegal usage of the application. At that time, you will be required to update your application as we will block all prior versions. This is an unfortunate step back, but we are working to make this as painless as possible while also stopping unauthorized usage.
Thanks,
Nicholas Hagen
As some of you may have noticed, this week we rolled out a new updated server base. While this does not bring you any client side updates (that will be coming soon as we are actively working on completing our next set of enhancements), it does bring you some other notable updates:
As always if you notice any issues or uncover a possible bug, let us know right away so we can quickly resolve it.
Thanks
RSS Viewer
Update [Oct 15, 2009 4:09 AM EST]: Looks like we are back up and running again and things are working much smoother now. If you see any issues, please send us an email right away so we can quickly resolve it (info@znetdevelopment.com). Notifications are currently disabled and under test and should be back live around 9:30 AM EST. Thanks for your patience. Hopefully these server updates will improve the application performance and usage.
Update [Oct 15, 2009 12:14 AM EST]: We will be going down again in 45 minutes (1:00 AM EST) for about an hour or two to move over to our latest server updates. We should have all of the kinks work out and be live soon again working better.
Update [Oct 12, 2009 7:45 AM EST]: Apparently, feeds are not processing properly and a few other issues have arised. We have decided to revert back to the old version while we look into the specific issues. We did manage to improve the performance of loading the recent items, so that fix is currently running. Stay tuned as we hope to get this major server update out in the next day or two.
Update [Oct 12, 2009 6:45 AM EST]: We are back up again and everything should be functional again and things seem more responsive and faster. Once we release our next application update, we hope to improve the performance in that aspect as well and make this one of the fastest RSS readers in the app store. Until then, stay tuned. If you notice any issues, let us know so we can investigate. This was a pretty major server-side update and while we attempt to ensure full functionality, we know that guarantees are never possible. Thanks again.
Update [Oct 12, 2009 1:44 AM EST]: We are now down and should be back up by 3:00 AM EST (7:00 AM UTC/GMT)
Update [Oct 11, 2009 12:15 AM EST]: We are postponing this until Oct 12, 2009 1:00 AM EST in order to do some final verification testing to ensure we get everything working properly. More details coming tomorrow.
This upcoming weekend we will be rolling out another set of server-side changes that should improve performance and reliability even more. This will most likely resolve the remaining issues of login difficulties, timeouts, and inability to get recent feeds or inconsistency between push notifications and recent feeds. We plan to begin rolling these updates out on Sunday, October 11 early morning starting at 1:00 AM ET (5:00 AM UTC/GMT). The expectation is to have a downtime of about an hour. During this time push notifications will not be sent and you will be unable to login. However, once the server is brought back online, you should immediately start noticing drastic improvements. Check back here to get further updates and progress or follow us on Twitter.
We would like to thank everyone for their continued support and for all of our first time buyers in the first month. Once we stabalize our servers and reliability this weekend, we plan to jump right back in to improving the client side interface and our upcoming feature list. We would love your feedback though to help us prioritize which features get in the next release. Add a comment stating your preference including google reader synchronization, dynamic keywords, sharing (digg, twitter, etc), site management (naming feeds), improved language and encoding support, landscape support, and any others you can think of.
Thanks