There is nothing like that in our extension, feel free to check the code =)

Not now, but what about the 10th update?

In general, I don't think it works that way.

If you want people to install your code in a privileged position (such as a browser extension), you need to appear trustworthy.

You essentially ask your users for a credit of trust. And yes, being able to say "just read the code" is absolutely necessary, but it is not sufficient. You usually get trust by having a great track record in the past, or by cooperating with others who do have such a track record.

Yes, now it's a subscription service.

Nope, not possible on any content site (eg youtube) and it also needs the site to add it.

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.

You hit the head on the nail, but from the wrong angle ;)

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.

Nope, Patreon focuses on person and fame, and is one to one payments. We focus on content and divides your money to any number of creators.

4. North Korea

Absolutely the opposite!

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.

Yes, this is correct. In general payment providers has these set of rules/policies, that because the large institutions like Visa, Mastercard and banks does not accept these areas of payments.

Ok, that is not really what happened. But it's a too long story for a HN comment ;)

Yes, and the exact true story is only know by the ones involved :-)

Yes, like me.

Ah, true. The reason the blog is on .net is for security reasons. We don't want to have a WP blog (with all it's flaws) on a domain that should be trusted by our own system.

That said, a FW from .net to .com seems logical, and a link to the site too, hehe.