In this collection of parables on free software, the first parable related to food struck a cord within me. For one, the food, or in broader sense anything we can acquire and consume, by virtue of the process we obtained them (i.e. bought the food to be cooked and eaten), should be considered already our own.This article won't discuss the difference and issues between the proprietary/closed source solutions and free and open source ones, it's already been discussed to death since the last quarter of the 20th century. In this article we discuss the issues on free and open source software licences (that's spelled with a 'c' rather than 's', I'll stick to real English on this one), particularly between the GNU General Public License (hereafter to be referred to as simply GPL) and the Berkeley Software Distribution (BSD), making it simpler when analogized with food preparation.
Wednesday, June 29, 2011
On Food, Software Licence and Extinction by Starvation
Labels:
bsd,
gnu,
gpl,
public domain,
software licence,
software license
Tuesday, June 21, 2011
Google Docs and Time-Saving Tips on Encoding Very Long Text Documents
As I have already written before, I still keep a day-job and recently, I realized having the alter-ego of a startup apartment owner. Along with that role, I have to formulate a just, tenant- and owner-friendly rental agreement, thanks to Landlording: A Handymanual for Scrupulous Landlords and Landladies Who Do It Themselves for the great assistance.
How does Google Docs figure in this equation? Their new feature that goes by the tonguetwister Optical Character Recognition or better known as OCR, which was very very handy when I needed to encode a long document from the aforementioned book as model for the rental contract. In this article I'll discuss the steps I took, how it went, the plus and minuses of the process and the overall benefits.
How does Google Docs figure in this equation? Their new feature that goes by the tonguetwister Optical Character Recognition or better known as OCR, which was very very handy when I needed to encode a long document from the aforementioned book as model for the rental contract. In this article I'll discuss the steps I took, how it went, the plus and minuses of the process and the overall benefits.
Thursday, June 16, 2011
Proposal for a Federated Telecommunication System
My application for postpaid cellular phone service was recently denied, and what's worse, they just sent me an SMS saying so without any explanation why. Their very brief if not cryptic message further rubbed into my person that their time is more important than mine.
In frustration, I thought of an alternative: VoIP-based telecommunication infrastructure that any cellular phone or computing platform with VoIP and Wifi can connect to, call, chat and exchange email over. Thus, the idea of a federated telecommunication system is born. I will outline here a system architecture to build this infrastructure as far as my experience can guide me, hopefully you'd send in comments and suggestions to make this better. I hope you'd bear with me that it took me some time to go over this setback and also to refine and polish this article.
In frustration, I thought of an alternative: VoIP-based telecommunication infrastructure that any cellular phone or computing platform with VoIP and Wifi can connect to, call, chat and exchange email over. Thus, the idea of a federated telecommunication system is born. I will outline here a system architecture to build this infrastructure as far as my experience can guide me, hopefully you'd send in comments and suggestions to make this better. I hope you'd bear with me that it took me some time to go over this setback and also to refine and polish this article.
Labels:
asterisk,
federated,
telecommunication,
voip
Subscribe to:
Posts (Atom)