I remember when I got my first smartphone.
My employer provided me with a Blackberry and I was pretty excited. I could check my email, cruise the web and text message with ease. No more was I bound to the limitations of The Simple Cellphone.
After showing it to my Pastor during a morning coffee meeting, he said:
They gave that to you, so you’ll work more hours for them.
If you haven’t heard of SOPA and PIPA, you’ve been living under a technological rock for the last few months. SOPA and PIPA are the bills sitting before congress that supposed to give authorities a stronger ability to enforce online piracy. While it sounds like a reasonable proposal, some parts of the bills could spell an effective “death penalty” for many websites. For this reason, many major technological companies, including Google, Wikipedia, and others, have voiced strong opposition to the bills.
On Saturday, these companies got a major win.
With Government budget cuts, grounded shuttles and a nation who is no longer interested in any kind of “space race,” instead of turning tail and run, NASA went “open.”
Just this past week, NASA launched code.nasa.gov, the latest member of the open NASA web family.
That’s right, web family.
Through code.NASA, they will continue to unify, and expand NASA’s open source activities. The site will serve to bring existing projects to light, provide a forum to discuss projects and processes, and guide internal and external groups in open development, release, and contribution.
This also includes NASA’s Nebula Cloud Computing Platform.
As a web and graphic designer, author or any other Creative, where do you draw the line with copyright and when do you pull those strings to control the content?
Here are two examples:
According to ChurchMag readers and further confirmed by Tyndale’s recent survey on Church and Technology, the two biggest obstacles facing Church IT (and perhaps the Church in general) is having enough volunteers and funding.
Yesterday, I shared my thoughts on a solution for the lack of volunteers — Digital Discipleship – and shared my personal experience building a Church A/V team.
Today, I’m really looking forward to your input, as we begin to formulate some practical solutions when it comes to the second Church IT obstacle facing Church Technologists: Funding.
Historically, the entity known as the Church hasn’t always been a patron of sound scientific principles.
It is pretty nice, though, when you hear about Churches doing things that count, particularly when it is related to conservation. Myers Park Baptist Church in Charlotte, NC is doing just that.
It’s easy to have a narrow perspective of the world wide web. In the United States, the world wide web is pretty much wide open, however, there are plenty of other places in the world where that simply isn’t the case.
I watched this infographic video, this weekend, that speaks more specifically to something called, “The Soft War.”
I’ve been going over some of the key pitfalls and mistakes Church-IT should be sure to avoid. These are certainly not things that needed to be committed to memory, but they are certainly things that may help you notice blind spots and become more mindful of common IT mistakes. All in all, I hope these are things that will help you become a better and more dynamic Church-IT member.
As always, be sure to weigh-in with your own insights and experiences!
Here are 5 Church-IT mistakes you should try to avoid:
Have you ever used pirated software? Downloaded or installed a cracked program?
With programs that can cost an arm and a leg, I know there are many people who justify their actions. I believe it’s straight-up stealing. How about you?
From 1966 to today, the history of software piracy: