Why was there such a long delay between me updating PocketFlock from using 0.7 to 1.0?
I'm broke
That’s the most commonly asked question on Outraged-Artists (or at least it was until spammers made it unmanageable).
I can break this down into two categories, what’s in my power to change, and what’s outside my power to change.
Here’s the answer (both long and short)
Time, Time, T I M E
This was pretty much a one-man-show and while I used to have plenty of time to devote to this project, I’m now working a full-time job as well as school (on top of a recent move across the state).
Flock 0.9 sucked for portability
Seriously, Flock 0.9 would write files to parts of the drive other than the profile folder. Terrible no-no that might have left some of your personal data (especially posts) on other people’s drives, and since I don’t have the manpower (or machinepower) to tweak/fix/and recompile Flock (as well as licensing issues if I used home-brewed binaries) that’s mostly out of my hands.
On the upside Flock 1.0 fixes most, if not all of the previous portability problems, and Flock 1.1 (really gonna be worth the upgrade) has built-in email capabilities (something people like me have been crying for since 0.4!) and will only make PocketFlock the perfect Mobile Browser for people who’re connected.
There are two ways to help further PocketFlock, like any other OpenSource Project… donate.
Time or money, I could always use a hand managing such a product, or a beer to properly motivate my fried neurons.
Ok, there’s a third way… Promote PocketFlock, let everyone know that just because you have to take it with you, doesn’t mean that you can’t take it with you.
Tags: flock, pocketflock, opensource, beer, sotired