GitHub, tweets & extensions

On the quest to bring you more stuff to flattr we’ve reached a new milestone. Ten months ago we made all Twitter profiles flattrable and now we’re ready to take the next step.

Starting today all tweets are flattrable – not only that – we’re also adding GitHub to the mix and making all non-organizational GitHub profiles, repos, commits and gists flattrable. Found some hot new open source project that you want to support? Now that’s only a few clicks away.

To make all this possible and easy to discover we’ve updated our Chrome extension so that it shows up in the address bar for all the new content – it should have updated itself in the background and be ready for you to use right away.

What about the Firefox users out there? You want to flattr cool tweets and commits as well? We know – that’s why we’re also launching an initial version of a Firefox add-on today. It’s still in review by Mozilla and there are additional things we want to do with it – but you needed to be part of this so we’re launching it early anyway. (Wikipedia-support for Firefox will come at a later time, until then Flattr icon will show up in articles that already have been flattred.)

Both the Chrome extension and the Firefox add-on are built on top of our API – they are asking if a URL is flattrable and if yes then our icon is shown in the browser’s address bar. That also means that most of the API already supports the new GitHub and Twitter things and are just waiting for you to start mashing it up.

We’re pretty thrilled about launching this and hope that you feel it’s a great step towards making more and more of the fantastic content available on the web supportable through real donations. Just remember – if you flattr someone who hasn’t signed up yet then you need to make them aware that they have a donation waiting and they should claim it. You’re the right person to do it, it’ll be nice and personal that way.

Have fun flattring new stuff!

/ The Flattr dev team

NB! Firefox + Chrome combined represent around 65% of all visitors. 0.3% visit us via their Playstation, thought you might want to know :)

30 thoughts on “GitHub, tweets & extensions

  1. Would be great to have icons incorporated into these sites by default, i.e. if the user has a flattr account, a flattr icon would show up next to her comments, commits, repos, tweets etc.

  2. @Daniel: We’re probably going to experiment with some such solutions in some of our browser extensions in the future – I agree that it for things like tweets and commits it would help a lot

  3. @Mika Tuupola: It’s enough to just connect Flattr and GitHub – if you have one of our browser extensions installed then you will see a flattr symbol in the address bar for all things flattrable – like GitHub repos and such – and if you click that you will come to a page where you can flattr it.

    If the owner of a GitHub thing that’s flattred hasn’t signed up yet then the flattr will be pending until they sign up and claim their GitHub account by connecting it to their Flattr account.

    For coders the system behind is rather simple – the extensions first do a call for the URL and if they find out that the URL is flattrable they then show the icon and sends the user to when the icon gets clicked.

    So if our extensions isn’t enough for someone or if they are too much – then one can easily create another workflow :)

  4. Nice!

    Would be great if there was a way to flattr Github on the normal Flattr website, just like there is for Twitter. I was just about to migrate my donations ear-marked for Github from TipTheWeb to Flattr, when I hit that snag. Without installing one of the browser extensions (or writing your own client for the API), you cannot do it right now.

    Maybe a developer can throw together a bookmarklet or something like that (there are a few days left in the coding contest, too ;-)

  5. @Harrie: The Opera community is better at supporting that then us – and they in fact was faster in producing an add-on for opera than we were at producing one for Firefox:

    @Alexander: I agree that it would be interesting to have such a possibility at the Stack Overflow sites – but the wiki-nature of Stack Overflow makes it hard to know which person that should receive the money and on top of that Stack Overflow themselves has said very clearly that they think Flattr support on Stack Overflow would be a very bad thing. So – it likely wont ever happen.

  6. In my opinion is interesting to give the flattr in wikipedia to wikimedia foundation and not to single authors. The authors of a single voice of WP are a lot of and the fee for everyone is very very small. In my opinion is better if the fee go to wikimedia foundation and not to authors. (I’m an author of wikipedia).

    The flattered voice is a big pleasure for the authors. Authors are voluntaries.

  7. > The Opera community is better at supporting that then us – and they in fact was faster in producing an add-on for opera than we were at producing one for Firefox:

    That’s probably worth another blog post and tweet. Anything similar for Safari?

    > the wiki-nature of Stack Overflow makes it hard to know which person that should receive the money and on top of that Stack Overflow themselves has said very clearly that they think Flattr support on Stack Overflow would be a very bad thing. So – it likely wont ever happen.

    Relevant thread over at Stack Overflow:
    and also

  8. @Pelle,

    I am curious as to the reasons Stack Overflow is not interested in Flattr support. Could you explain or link me to a conversation? I searched stack overflow and this blog and did not find any relevant topics. Thanks!

  9. @Eric: Organizations isn’t flattrable since we have no way of claiming an organization – the way our current claiming system works is that you connect an external identity and everything that is owned by that external identity is assigned to you. A GitHub organization is an identity that is shared between many GitHub accounts and when those GitHub accounts connects to our system they connect as their individual identities – not as an organizations – and there is no obvious way for handling the connection of secondary identities.

  10. So in my chrome now the flattr-icon shows up everytime something is flattr-able. For example because you can add it (like a tweet) or it is added allready, right?

    I see some trouble there, because it also shows up at urls already (manually?) added for example which doesn’t seem to be added bei Spiegel Online…

  11. @Andreas,

    Yes, the plugin will now show up anytime the current url, or one less specific is a flattr thing. For example, if I sign up a personal blog, like, and a user visits, the flattr icon will appear and take you to the flattr thing linked to So it is a convenient way to allow ‘global’ flattrs for a site that you own.

    In the case of, it appears likely that someone claimed that URL, even though they do not own it or the content on it. This would be in violation of section 4 of the terms of use (pasted below).

    If you notice something like this, please click the ‘Report’ link on the flattr thing page. I have done this for multiple sites (such as since installing the browser plugin. I’ll leave for you!

    In addition, you agree that you will not use the Service (including, without limitation, by “flattring” any Content) on behalf of or at the request or instruction of any third party. Furthermore, you will not request any third party, pay or otherwise attempt to influence any third party to manipulate or otherwise affect the Flattr Site in any manner. Flattr may remove any part of the Content or Flattr User Accounts (defined below) at any time for any reason (including but not limited to upon receipt of claims or allegations from third parties or authorities relating to such Content and Flattr User Accounts) or for no reason at all. To report Service abuse, please complete the form at:

  12. Yes, true. It seems there is a balance to be struck between favoring expansion and preventing abuse. Personally I would lean on the side of expansion and try to fight abuse as it comes up, as opposed to limiting expansion due to potential abuses. It’s not my site though, ha.

    One idea would be to query whois upon signup and make sure the registered contact email exists on the account. Alternatively, flattr could send an email to the domain contact to notify them someone has signed the domain up for flattr.

  13. Um… how does one find flattr blogs? Are you expected just to discover them by accident as you surf the net or is there something I have missed here? I have placed a bunch of flattr buttons on my own site articles, but not sure how to find other peoples’.

  14. It’s a real shame this only shows up in the address bar; it’s great placement, for anyone who doesn’t hide it. I downloaded the plug-in, and was disapointed to find there was no way at all for me to put the button anywhere else (somewhere I could use it without having to show my whole address bar).

    Cool idea, cool UI, but doesn’t catch all cases, so I can’t use it. :(

  15. @james: What would you like instead? A toolbar button? The Firefox add-on SDK doesn’t make that very easy and the Google Chrome design guides says that the button should be in the address bar and nowhere else, but may be possible to eventually add to the Firefox extension anyway – add a feature request to it perhaps to keep track of it?

    A cool new addition for the GitHub flattring is btw this git CLI-extension: The best UI is no UI ;)

Comments are closed.