For these folks, here’s a quick tutorial video that shows you how your files are stored and shared.
Some Kerika users — specifically those who had signed up directly — had trouble logging in if they had left Kerika running overnight on a browser.
Their browser was endlessly refreshing itself, bouncing between the /app and /setup URLs. There was a workaround (type “https://kerika.com/logout” to clear Kerika’s cookies) but the workaround was far from obvious, so obviously some people were inconvenienced.
(Would have been a lot more had it not been for the Christmas holiday season!)
This has been fixed now. We found a problem with the configuration of our NGINX web server software.
One of our users had a problem recently when they mis-typed an email address while adding someone to a Board Team: the mistake was essentially a typo of “.com”
The user didn’t notice their error, but our system did: when Kerika tried to send the email invitation to the mis-typed address, the email bounced (naturally).
And while the user didn’t notice or complain, we want help our users avoid these mistakes by including some email checking when someone is being added to a Board Team.
Kerika now tries to see if the email address looks incomplete or malformed, and alerts you if you made a typo.
The Box Platform has some limitations that you may bump into:
Kerika is going to take of this silently from now on: if you try to rename a file using a character like “/” that Box can’t handle, Kerika will silently ignore that character in your renaming action.
This means that in some languages, file names may have to be much shorter, depending upon how many bytes are needed for storing each character, which in turn depends upon the size of their alphabets.
Some folks from Thailand were running into this problem: Kerika will start detecting this better, and provide more useful error messages
We recently got hit by spammers signing up as Kerika users, using fake emails from domains like mailinator.com, which seems to exist principally to help people do bad things on the Internet.
After signing up, these spammers (who seemed to be based in the Philippines) would invite hundreds of people with accounts on Tencent’s qq.com service in China. This would result in invitations being sent to these qq.com people to join the spammers on their Kerika boards.
This doesn’t affect the majority of our users, since most people sign up using their Google or Box accounts. And because the reCAPTCHA works silently, it shows up only when Google has reason to doubt that the person at the keyboard isn’t human.
We added a feature recently (or did we actually a bug?) for our direct login users: when you reference a file that’s attached to a Kerika card, canvas or board, from another place in Kerika — e.g. another card’s details or chat — we now show the file’s name instead of just the URL.
This makes it easier to cross-reference file attachments from within different Kerika cards or boards, where different work items or conversations refer to the same shared file.
Here’s an example:
We have a new (five-minute) video that gives a fast overview of Kerika’s many capabilities:
Let us know what you think!
Did you know that we have made it really easy to download files that you attach to a Kerika card, canvas or board?
Just hover your mouse over an attachment, and you will see these buttons appear on the right:
These buttons let you:
Couple of other points to note:
Rename a file shows off our integration with Google Drive (for our Kerika+Google users) and with Box’s service (for our Kerika+Box users): renaming the file from inside Kerika will automatically rename it in your Google Drive or Box folder as well.
Deleting a file attachment doesn’t actually delete the file from your Google Drive or Box account: it just means that file is no longer attached to that particular Kerika card, canvas or board.
This helps ensure that you are going to be able to easily collaborate with other people from your company, who may have signed up already using their Google or Box IDs.
Here’s an example: firstname.lastname@example.org tries to sign up directly, and we suggest automatically that he sign up as a Kerika+Box user since so many of his colleagues already have Kerika+Box accounts:
We offer three ways for you to sign up as a Kerika user:
Using a Google ID means you are getting Kerika+Google: the version of Kerika that offers amazingly smooth integration with your Google Drive and Google Docs.
Using a Box ID means that you are getting Kerika+Box: the version that offers amazingly smooth integration with the Box platform.
And signing up directly means that you can use any email address you like, and leave it to Kerika to store your files for you.
Originally, we had just Kerika+Google, and then we built Kerika+Box to address the market for enterprises that preferred using Box to Google.
And, finally, we built the direct login method for people who didn’t care about how their Kerika files were stored, and were happy to just leave that whole job for us to take care of.
We are now trying to streamline that process even further.
If you already have a Gmail address, it is very likely that you are already comfortable with using Google’s services, which means you should really be getting a Kerika+Google account so that you can benefit from all the great, smooth integration we have already done.
In the same vein, if the majority of people from your company have already signed up for a particular service, e.g. Kerika+Box or Kerika+Google, then it makes sense for you to sign up in the same way so that you can share boards with your coworkers.
This process is now more automated, and, we hope, simpler: when you sign up, we look at the email address you are using to set up your Kerika account and try to set you up with the version of Kerika that will make most sense:
This should make for less confusion about which flavor of Kerika is going to be tastiest for you…