Fair warning, this post is intended to the technical part of our community, if you don't care about the architecture of civi, please skip this one, I'll come back to you soon with awesome datavisualisation and an interview of Micah about ssl (you'll like it).
And if you read anyway, I'm a bit of a drama queen and some of the mountains I describes are probably hills, at best.
As most not-for-profit that wants to collect online donations or has a membership base, you probably have the opportunity to have more donors giving small amounts on a monthly basis, but you have not been able to explore it given the high fees on credit cards transactions. If your organisation is based in Europe, SEPA is offering you this option.
I wrote a node module to easily connect to a civicrm server from that node.js. I found a cool module that makes it easy to generate names, addresses, phone number and emails and hacked a quick example of how civi can be used from node.js.
Without further intro:
The code sprint in London has finished yesterday. It's always a pleasure to see old civi friends and meet new ones. Thanks to Michael and Katy to have organized it. Time for a quick update of what I've been working on with the most obscure title I could find. My focus has been on usuability to make civicrm easier and faster to use.
So as every consultant, there is a bit of new projects, maintenance, stuff you do for free for the community, new ideas, meetings, pre-sales, funky developments & the dreaded admin part (invoicing/timesheet).
We have continued the research to see how often someone tweeted about organisations that happen to use CiviCRM. We analysed 2023 tweets by 724 users about 175 sites. Not a lot of new sites since last month, but a lot more tweets.
As a friday follows up of our research on how civicrm powered sites are visible on twitter, we did a casual textmining of the 1022 tweets that contains a link to an event, donation, petition or profile on one of 175 identified sites that use civicrm.