teowaki’s 300

Last week we saw the 300th user signing up for teowaki. We are still a bit far from world domination but we couldn’t be happier. And we want to thank every one of you for trusting us.

But we want more! We need you to spread the word, create organisations and teams and invite your friends to join teowaki.

Do you regularly attend a community event in your town? Create a team for it and use teowaki to keep sharing information in between meetings. Are you teaching other people how to be a better developer? Use teowaki to keep the group in touch. Changing jobs? You don’t need to stop sharing with your colleagues; just add an alumni group for your company and tell them to join and keep you up to date on what’s hot and what’s not. 

There are endless situations when a tool for sharing links, short messages, best practices and mistakes comes handy.  If there is anything you are missing at teowaki that keeps you from using it more, please let us know at We want to make the best service possible for software developers to interact with each other and we won’t stop until we get it.

This is what 300* happy users look like:


* There are actually 302 users up there

Announcements, Uncategorized

Teowaki puts you on the map

Time flies when you are having fun. It’s been already one month since we announced our public launch and we have been busy adding a lot of small things to make teowaki even better for you.

After our Xmas break, we started the year by improving our search engine and adding individual pages for links, shouts and jesters. Then we added the “personas” feature to your profile, so you can let everybody know your different online identities. In the meantime, we got the opportunity to speak at local communities of developers in Zaragoza and London, sharing with them the technologies we are using at teowaki.

And today we are proud to announce our first geolocation features. You can now add your location to your profile, so other users can see where you are based. This is the cornerstone for the rest of our geospatial functionalities. In a few weeks you will be able to filter your search results by proximity —search for people or teams close to you— or to send shouts to users around one area.

How does it work?

When you visit your profile settings, your browser will ask for permission to use your computer’s location. Unless you allow your browser to pass your information to teowaki, we won’t be able to guess your current city and country automatically.


A note on your privacy: We know it is technically possible to try and guess your current location using other techniques, like checking your IP against a database, but we think you as a user should have the last word in saying if you want us to geolocate you or not.  We won’t try to guess any geospatial information about you unless you allow us specifically to do so.*

Once you allow us to guess your location, teowaki will show your position on a map. In the rare cases where we can’t automatically locate you, or if our location is wrong, you can enter your city and country in the location text box and we will map it.


Even if you want us to keep your location, so we can use it for proximity searches, you can still uncheck the option to share your location publicly. In that case, we will store your location in our servers and we will use it internally, but we will never disclose your location to other uses. You can switch this check on and off as many times as you want. You are in total control of what and when it is shared about you.

Don’t forget to use the “Update” button to save your settings.

What does it look like?

Once you enter your location and give your permission, the name of your base location and a small map will be displayed on your profile.



Is there any way we can make this better for you? let us know at

* our analytics backend uses techniques for geolocating every request we get to the system by analyzing the IP address. This is done at as a separate process and we don’t associate this information to your user, just anonymously to every request that hits our servers for statistical purposes.