Tumblelog by Soup.io
Newer posts are loading.
You are at the newest post.
Click here to check if anything new just came in.
5978 06c2 420
5927 affe
2015.1.28 also my macbook has died after last few examples. graphics card issue most likely
7768 a1ab 420
7760 3c3a 420
Reposted byantihec antihec
8516 063c 420
0631 6f61
0538 85cc 420
4899 8109 420
4891 9e9b 420
4598 4cc5 420
2014.11.22. I tried to update my ios to 8.1.1 but cancelled it, tried again and this came to my email (not that I remember ever setting up such a strange email)
7661 4833 420
1177 ccf2 420
9556 25cf 420
9382 2e0a 420
2448 8996 420

About tracking and privacy

We've been using quantcast and google analytics for quite some time (I think since the birth of Soup?) to collect minimal meaningful data about the visitors, where they come from and their approximate demographics.

We've not even been using the extended feature sets of those platforms, because that would've meant putting user data into the hands of a third party.

But what do we know from these solutions? Yes, we have a lot of polish users. And we're very proud of being in the top 30 something polish websites - at least according to quantcast - despite not understanding how we got there.

And that's kinda sorta the point - insight how we got anywhere. And this means metrics.

Now, metrics is a very loaded topic. Everyone does it, but nobody talks about it, except in their Terms Of Service legalese. People immediately think of spying, and it's kinda ... somehow ... well, it's not exactly not spying. But I personally don't think it's really spying either, but that maybe because I'm the one running the platform and have many years of experience what it means to know jack shit about your users and what they're doing.

So my view on things is biased. Thus, I decided to go the pragmatic route and just commit myself and the company to explaining what we're doing - hopefully in a way that people who are not into metrics can get a grasp too. If I can't explain it, or it feels creepy to explain it, well, that should be enough to make me think it over. And I'm taking a huge flaming pile of dung on legalese, because, you know, fuck you - not.

So my take on it is, metrics should be more like a census and what's called "city development data". To be able to plan what areas to develop, a city needs to know where people go to work, when and where they buy things, what the average income is etc.

It's the same with a web platform like Soup, except for jobs and shopping centers we have blogs and groups, and instead of cars and net worth of the individual we have posts and days since registration.

Anyhow, @whatweknow is dedicated from now on to explain what we're collecting, what we're doing with it, and maybe even post some results. If you have an interesting question that we should be able to answer with metrics, don't be afraid to ask @kitchen or reply to a post here! Sometimes we may be unable to give answers or give them not in absolute numbers, but we should be able to crank out at least a percentage or a general vicinity every once in a while. And if not, you may at least get an explanation why :)

Last but not least, a word to the wise: be inquisitive about your privacy on the internets, and use tools such as ghostery or disconnect to understand what sites know about you.

Reposted fromwhatweknow whatweknow
1501 d8d7 420
4743 147b 420
4518 520e 420
6759 91b2 420
Older posts are this way If this message doesn't go away, click anywhere on the page to continue loading posts.
Could not load more posts
Maybe Soup is currently being updated? I'll try again automatically in a few seconds...
Just a second, loading more posts...
You've reached the end.

Don't be the product, buy the product!