First of all I wish to thank Sebastian who gave me the invite to Flattr to begin with, a few months ago. This was not only helpful to me, but also allowed me to have a bit of insight on the whole evolution of the service over these.
Now, I haven’t really written much about it before, mostly because I didn’t want to stress its presence — if you read my blog through syndication on Planet Gentoo or Gentoo Universe, the fact that the posts have a flattr button is hidden from you altogether. But since there has been a lot going on in the past month, I thought it might have been the right moment to write down some notes about it.
You might or might not have heard the fact that Debian developers got into bickering about what is and is not allowed on Planet Debian, mostly about Flattr, with a number of very different ideas about why it is bad for their developers to have Flattr at all – ranging from calling it a scam for the 10% they get from the poured money, to calling the “social networking buttons” webbugs (including Feedburner), to simply saying that it’s a commercial use of the Debian infrastructure – whatever the outcome, I don’t think Flattr stands to gain many fans here.
But what I found interesting in that outcome is the consideration that the Flattr platform itself might not be faring too well; the reason why that’s said is that after the initial money inflow of the registration, just like the “real world economy”, the consumers pay, and the producers get the money. In my case, I haven’t really had the need to add any means since I registered, and while I feel bad about it, I don’t think that will change anytime soon (mostly, because I’m actually going through a patch rough enough that I cannot afford to do so realistically; even though I promised myself not to withdraw funds anytime soon at least, I ended up doing so to pay for the SSL certificate from StartSSL, as well — so thanks to all of you who contributed!).
The one thing that it seems to lack here, though, is support for the same metadata API used by Facebook: OpenGraph — right now you have to provide the URL to flattr, the description, the tags, the type and so on so forth whenever you provide a flattr widget. This means that any of the index pages of my blog is repeating the same content many, many times. On the other hand, if it was using OpenGraph, maybe slightly extended (even Facebook has a fb_admins value that is not documented there), it would only take the URL, then the rest of the service would be able to access the details from there.
Having such a situation would also make it nicer to have “Flattr anything” extensions: right now they really cannot work, because you do not know who owns a given webpage, which kind of webpage it is, which tags to use, and so on; and you cannot either declare a canonical URL to use, so the same page could be submitted twice, if it is reachable by two different URLs (like most of this blog is); and this is considering we have two, not one, methods to declare these canonical URLs.
Finally, I have to say that from at least one side, Flattr has proven itself profitable to me; in the past two months, where its usage surged, I received around €20/month with it, which is definitely not a lot (at least considering the expenses Tinderbox has caused me in the same time), but it’s not little. Once again, thank you all.
Also it has been funny to see some of my older posts being flattred from time to time, I guess some people actually ended up finding them with google, I hope they found what they were looking for.
I am not sure whether this widget is the cause or if one of your botcheck scripts is the issue but on your page from a Windows IE client I use at work to view your blog I get a spawned screen that declares ‘The operation is aborted: the page cannot be displayed’ and then once it goes away the page will display At some times in the past it would not display at all from there.I do not see this issue from firefox or chromium on linux
Can be interesting to know that Flattr do support oEmbed for some content and extending that to support OpenGraph or similar will probably be needed in a hopefully not too far distant future.Regarding the problem of figuring out the owner of a piece of content on the web, that’s something that I’m currently sketching on solutions for and we will have something to share there very soon – keep your eyes on the Flattr blog.
Pelle, is there any documentation about how flattr uses oEmbded? I’ve been running my head around the oEmbed problem in FSWS for a friend of mine and it wouldn’t be too bad to have oEmbed support in Typo if Flattr used it…
Most oEmbed consumers are only accepting content from trusted providers because of problems with security, discovery etc. The same is true for Flattr – but right now even most of that embedding has apparently been disabled because of incompatibilities with https.
I see, I was assuming that only risky tags were being filtered, rather than everything entirely.Please let me/us know when you plan on enabling that feature though, I’d very much like to try it out!