Getting Started with SparkleShare
If you follow Linux-related news, you've probably heard about SparkleShare, a promising open source alternative to the popular Dropbox service. SparkleShare has been under active development for some time, but the latest 0.2.2 release is actually the first version suitable for practical use. Mind you, it's far from ready for production use, so install it only if you want to satisfy your curiosity, or if you enjoy using bleeding edge releases.
While you can find .deb SparkShare packages in the wild, your best bet is to compile the software from source. This is a rather straightforward thing to do. First off, you need to install the required dependencies. On Ubuntu, this can be done by executing the following command:
sudo apt-get install gtk-sharp2 mono-runtime mono-devel monodevelop libndesk-dbus1.0-cil-dev nant libnotify-cil-dev libgtk2.0-cil-dev libwebkit-cil-dev intltool libtool python-nautilus libndesk-dbus-glib1.0-cil-dev libappindicator0.1-cil-dev
Grab then the latest source package from the project's website, unpack it, switch to the resulting directory in the terminal, and compile the software using three simple commands:
./configure --prefix=/usr make sudo make install
Next step is to set up a Git repository. Although SparkleShare can use GitHub and Gitorious as its file storage back-end, setting up a Git repository on your own server makes a lot of sense. It is also a rather straightforward process, and the How to set up your own server wiki page provides detailed instructions.
With all the pieces in place, launch SparkleShare using the sparkleshare start command. When prompted, specify your server's address in the following format: user@remotehost. Enter then the pass to the Git repository on your server like this: /path/to/dir/repositoryname.git. Press Finish and you are done. Repeat the setup process on other machines.
Don't encourage Mono usage. Mono is a legal risk and a patent threatI would appreciate it if Linux Magazine would show some serious restraint when it comes to writing about Mono or any apps that require Mono. Judging from the ton of information and analysis in techrights.org Microsoft has a legal basis to sue anyone using Mono & Mono based apps. Do you want to subject your readers to that risk? Not even De Icaza has been able to refute that Mono is a legal risk and patent threat. And Ubuntu or Canonical do not seem to provide any sort of indemnification against such a legal threat. Red Hat's decision with regards to Mono and Mono based apps should tell you something. In our Community Friends do not let Friends run legal risks, right?
Carnegie Mellon researchers say 3 million pages could fall down the phishing hole in the next year.
The US government rolls new best-practice rules for protecting SSH.
Klaus Knopper announces the latest version of his iconic Live Linux system.
All websites that use these popular CMS tools could be vulnerable to denial of service attacks if users don't install the updates.
According to a report, many potential victims of the Heartbleed attack have patched their systems, but few have cleaned up the crime scene to protect themselves from the effects of a previous intrusion.
DARPA and NICTA release the code for the ultra-secure microkernel system used in aerial drones.
Should you trust an online service to store your online passwords?
New B+ board lets you build cool things without the complication of a powered USB hub.
Redmond rushes in to root out alleged malware haven.
New initiative will bring futuristic virtual reality effects to the web surfing experience.