And update submitted to BlackBerry World. Let’s see how long it takes for them to review and approve.
I’ve pulled Todo.txt Enyo for the PlayBook from BlackBerry World today and I will no longer be developing for this particular device. My biggest reason has to do with the SDK and the odd bit of hacking it took to build this particular application (the combination of Java and Adobe AIR to build HTML5 apps is a bit bonkers). With Dropbox deprecating v1 of their API I felt it was a good time to bring this particular effort to an end. The source code will continue to be available from my site for those who wish to build their own BAR files. On the brighter side of things the Palm SDK still continues to work so I’ll be continuing support for webOS. I’ll be posting more on that in the near future.
Found some old stickers I used to have in my cubicle once upon a time.
Back to work with a bang today. Nearly 3k unread emails in my inbox and more that 50% of them I was able to toss as pure noise. 😊
Adding another target into my occiasional cross posting mix, this time feeding back into my main blog. Because I can. :p
I now have microblog posts showing here along with a distinct RSS feed.
This isn’t anything to do with that Google program. I’m just putting out a quick post about what I’m up to these days.
I’ve jumped back into mobile development once more now focusing on Ubuntu Phone and Sailfish OS. I see a lot of potential in both of these platforms and some opportunity to expand my skills while having a little fun. I have a social app currently being roughed out and in development. More on that as it progresses. And on the topic of social, I’ve also been tinkering with some new social APIs that some App.net peeps have been developing. Nothing earth shattering yet but it’s been fun to try new things, expand my knowledge, and keep in touch with some awesome folks from that network.
Renamed Todo for BlackBerry 10
I received notification from Dropbox yesterday that they are deprecating v1 of their API. In about a year they’ll be shutting it off and any apps that rely on it will no longer function properly. Renamed Todo relies on that API for it’s one and only sync option. I am in the process of trying to restore my BB10 development environment to see what I can do. I’m not sure if I’ll put out an update yet or if the app needs to be fully retired. I’m aiming to get something out there though since I know there are at least a few people who use it.
Todo.txt Enyo for WebOS and PlayBook
This app (a predecessor to Renamed Todo) is also impacted by the Dropbox API change. Since this code is open source I will be publishing an update in support of the API changes. There will be an IPK to go along with it, but a BAR file for the PlayBook will depend on if I can get that development environment restored or not.
I am looking to publish more of my source code over the summer. But rather than posting to github I’d rather self-host my public code repository and evaluating different options. I’m interested in what others are using and any good or bad that has gone along with it. Please do share your suggestions and experiences!
I’ve been running my owner Friendica instance for a couple of months now. And so far I’ve been pretty happy with how it’s turned out thus far. There are however some quirks with how it works between the various networks. With that I decided to go ahead and run a dedicated instance for GNU social (gs.monkeystew.net) and start following my various ostatus contacts from there. I’ll continue to run Friendica and leave ostatus enabled but my interactions are going to be a little more split. I cross post frequently so feel free to follow me in both places or just one if I repeat myself too much. :-) @email@example.com
A few weeks back I decided to give hosting my own social service a try. There are a various different projects that are being developed many of which have a pretty solid community around them. I have been using Diaspora pretty actively now for the last couple of years so that was my initial choice. But I have also poked around other networks like status net and pump, both of which are pretty active too. Ultimately I decided to use Friendica as my service.
Friendica is an open source social web platform which runs on a typical LAMP (Linux, Apache, MySQL, PHP) stack. Installation is fairly easy because it relies on common and popular components which can be found on most Linux installs as well as hosting services. Friendica supports native connectivity to different open social networks such as Diaspora and StatusNet. For services that are not supported natively there are connectors for networks like pump.io, App.net, and even Twitter.
The end result is a system that I own and control which brings together my friends across many different networks seamlessly. I can stay connected and engaged with people regardless of the network they use. Provided of course that network has an open API that can be accessed. Today I’m interacting with friends on the Friendica network, Diaspora, Hubzilla, pump.io, App.net and StatusNet. All through my Friendica server and it works!
I will be writing more posts about this and the open social web as I explore and discover new and exciting things. You can find my Friendica profile and links to my other social accounts at thrrgilag.com.
#friendica #diaspora #thefederation #socialweb