38 karma · joined April 5, 2017
Neither would it give us enough data to create what we have done. The algorithm in the extension is smarter about what it flattrs than a cookie could ever be. And more privacy friendly too.
That what you liked was actually exactly why we failed so far.
1. Users needed to do a conscious choice, clicking the button. Our research and data showed that was not what people wanted or did.
2. The button was to hard to add to a site and also visible and promoted a brand etc. All things publishers don't want. Besides the button does not work on any social network or content platform. The new solution works anywhere and is when it's hardest to use adding a meta-tag.
The new solution is a "fire and forget" solution. You set it up ones and then it just work. For both contributors and creators/publishers.
We keep all your private data on your device where the algorithm runs and makes decisions on what to flattr. Instead of sending it all to us and then do the same on our servers. This is very conscious choice to make the service privacy friendly.
That said, a FW from .net to .com seems logical, and a link to the site too, hehe.
(The change history is included in the history access scope in Chrome.)
For the huge sites, a cut of the ad revenue is taken, more or less as for any other ad network/service really. The full info is here https://acceptableads.com
We have tried to be as thorough as we could with what data the extension saves in local storage, even with the first release. There are always improvements that can be done and will be done.
We are going to add to the blacklist to not send things like twitter settings or wp dashboards etc.
Youtube is a bug that sneaked in just before release, in reality the UI does not reflect that youtube is supported and used. It's being addressed right now.
But not all data or everything you visited etc, as that is a to high of a privacy invasion.