This blog post is for folks who’ve been with Nirvana since the early days of development.
Today is the last day to convert your account to Nirvana Plus for $29/year !
Be sure to login to your account and go Plus for uninterrupted service. Otherwise your account will be converted to Nirvana Basic tomorrow — which means that while you will still have access to all of your data, and you will still be able to create and edit tasks, you may not be able to create new projects (if you are over the Nirvana Basic limits).
Here is the support article that describes all of this in detail.
Please consider upgrading right now!
We just updated our SSL certificates. But because Nirvana uses html5 offline caching, and because Chrome (erroneously) caches SSL credentials, we needed to trigger a cache refresh from our servers. You will see the “Nirvana has been updated… please reload!” message. Reload and all will be good.
(There wasn’t really an update, but this was the best way to get everyone’s offline cache up to date)
Note to Safari users: sorry you got caught up in this workaround for Chrome… there really was no need to refresh your cache, but we didn’t have a way to target only the Chrome users. Oh the internets…
We’ve been heads down for a few weeks getting the iPhone (iPod) app ready for prime time. We’ve had more than a few inquiries as to why the silence on the blog. We tend to congregate over on the discussion forums and twitter, only to neglect our lovely blog here. Our bad.
So, here’s what we’ve been working on:
- Polishing up the iPhone app for App Store approval
- Begin porting the work we’ve done for iPhone app to Android
- Mobile web app overhaul for compatibility with more devices (win, bb)
- Preliminary work on iPad app
- Preliminary work on getting references lists into the app
- Migrating support to Zendesk (a better system for our current needs)
- Integrating with Chargify for simple monthly/annual subscription plans
- Incorporating Nirvanahq, Inc as a separate entity from PLU Communications, Inc for cleaner accounting vis-a-vis Chargify
- Setting up our new merchant account for billing (dependency: Nirvanahq, Inc)
- Resurrecting our Facebook presence
- Looking into alternate sign-in for users via google, facebook, twitter
- Updating our on-ramp experience… getting started video needs to be re-done, faqs need updating etc.
We also quietly removed the need for invite codes last month, effectively making Nirvana open-signup, and have almost doubled our active user-base since that time.
We’re almost there, we’re almost there…
N2 Build 389 brings some minor but nifty additions.
- Links to evernote:// within task notes are now clickable
- Added some more font choices (calibri, tahoma, verdana…)
N2 Build 390 fixes a bug that was introduced in Build 389 where changes made on one device was not being reflected in the UI of other devices. Changes were being posted to the cloud just fine, but we’d botched the timestamp persistence in the local cache so changes from the cloud were sometimes being ignored.
NOTE: you must logout and then login for the Build 390 fix to take effect. (Local cache gets cleared on logout, and then rebuilt on login.)
QUICK FIX: N2 Build 391 fixes a rare edge case where a repeating task could yield spawned tasks named (untitled) on save … also related to timestampage that we missed in build 390.
File this post under technical fyi / cya / wtf.
For the past few weeks we’ve been working out the kinks in our server-side processing of large data sets relating to scheduled and recurring tasks, which has affected a small but significant subset of users.
In a nutshell, prior to build 358, N2 relied on each client (desktop/mobile browser session) to process nightly task movement locally, and then post any changes (scheduled to next, next to focus etc) to the cloud. Since build 358 the primary responsibility for processing tasks has been moved back to the cloud, which then pushes changes out to the client. Role reversal.
The initial worker scripts we wrote to do all of this processing were a bit over-zealous in their consumption of memory. Kinda saw this coming, and to preempt it being a show-stopper we added some client-side code to detect if there are tasks that should have been processed but weren’t, with a “manual override” that conditionally appears in your Scheduled and Focus lists if relevant.
The appearance of the buttons “Move Scheduled Items Into Place Now” or “Bring Focus Up To Date Now” is N2’s way of letting you manually invoke the routine that moves tasks into place locally, without waiting for the cloud to do the processing. In an ideal world, you would never see these buttons as everything should be automatic. But you know… it’s like when the automatic doors don’t open when you walk up to them, at least you can still push ‘em open to get through. Or something like that.
I’ve been up all night monitoring and adjusting the worker scripts, and it looks like things are finally working as intended. But for folks in timezones GMT +1 ,0, -1, -2, -3, -4, -5 and -6 (ergo, the 8 hours preceding this post) you may see the “Bring Focus Up To Date” button. Just click it if you see it and you’re good to go. Also, if you’re in the aforementioned time zones you may not have received your daily email poke today. Sorry about that.
Will continue to monitor things for awhile, and if things continue to look good we’ll be able to put this issue behind us and move on… to more fun things that all this server-side processing makes possible, like calendar feeds and the like. :-)