Free sharing dee software for linux

Web Sharing is a small tray applet for sharing files on the web.

Publish anything on the Internet or your local area network at home, office or school from a folder on your hard disk with just a few clicks of a mouse!

MUTE File Sharing is a peer-to-peer network that provides easy search-and-download functionality while also protecting your privacy.
It compiles as a fast, native application for many platforms (no Java, no Python, etc.).
MUTE protects your privacy by avoiding direct connections with your sharing partners in the network. Most other file sharing programs use direct connections to download or upload, making your identity available to spies from the RIAA and other unscrupulous organizations.
MUTE is based on research, and experiments show that it works quite well. MUTEs ant-inspired routing is light-weight, robust, and adaptive. Results from experiments in real MUTE networks show that the collective behavior of MUTE nodes quickly finds the shortest (or fastest) routing path between two nodes on the network.
Enhancements:
- This release fixes bugs in MUTEs initial connection to the network upon startup.
- MUTE has also been upgraded to Crypto++ 5.4, so it should now compile using GCC 4.1.

Snark is a client for downloading and sharing files distributed with the BitTorrent protocol. It is mainly used for exploring the BitTorrent protocol and experimenting with the the GNU Compiler for Java (gcj). But it can also be used as a regular BitTorrent Client.

Snark can also act as a torrent creator an http server.

When given the option --share Snark will automatically create a .torrent file, start a very simple webserver to distribute the metainfo.torrent file and a local tracker that other BitTorrent clients can connect to.

Money Share is an expense management tool that can be used keep track of expenses among several people.
Expenses made on behalf of people can be kept track of and recovered when balancing accounts. The utility also reduces the number of exchanges required in order to balance the accounts.
Enhancements:
Improvements
- Specify which file is selected in the dropdown box
- Change password option functionality is now available
- Transactions page now has a summary of expenses by description

SharedAppVnc is a remote collaboration tool. SharedAppVnc project allows sharing of applications between remote participants. In a typical usage scenario, two or more remote collaborators would run SharedAppVnc on their desktop computers while participating in a phone or conference call.

After establishing SharedAppVnc connections, possibly through ssh-tunnels, they would be able to share (replicate) windows between the remote desktops. The shared windows could optionally be controlled by the remote viewers, or they could be set to view-only.

SharedAppVNC is based on VNC (Virtual Network Computer), but with a modified VNC protocol that allows for window sharing. The main advantage of SharedAppVnc over traditional VNC is its ability to share individual windows rather than the entire desktop. Users typically have some applications which should remain private, such as email, and some applications they would like to share. Normal VNC is only able to share a users entire desktop and thus does not lend itself well to a combination of shared and private data.

SharedAppVnc has two components: a server for sharing windows and a client for viewing windows. The SharedAppVnc Server runs on a collaborators desktop computer and allows them to select which windows from the desktop to share. Only windows they select will be visible to the other collaborators.

The SharedAppVnc Viewer runs on the other collaborators computers and allows them to receive the shared windows. Typically collaborators will run both the Server and Viewer so that they can share and receive windows. One nice feature of the SharedAppVnc Viewer is that it puts each received window in its own frame which can be resized or positioned independently of the size or position of windows on the server or the other clients. Both the Server and Viewer can listen for or initiate connections.

SharedAppVnc versions are currently available for Linux and Mac OS X platforms. We are in the process of adding support for Windows OS.

Usage:

The Linux version of SharedAppVnc requires running three pieces of software: the server, viewer and control applet. The server, which allows windows to be shared, will be started automatically when the X11 server starts (X11 must first be configured to use SharedAppVnc).

The viewer is a java application that is started from the command line. It receives and displays shared windows. The control applet is a GUI that lets the user control the server. It lets the user select which windows to share or hide, or which viewers to connect to.

Shared Mime Library is my implementation for libsharedmime. It reads the Shared Mime Info database and returns you the MIME-TYPE of a file. Freedesktop make this database freely available, but they dont seem to be distributing a library to read it anymore (Its no where in their CVS that I can find).
It is different to the freedesktop version in the following ways:
- Licensed under LGPL instead of the GPL at aid all developers. *sigh*
- Has NO dependencies. Which is an important feature in this world of tangled packages all depending on each other.
- Probably not as fast?
- Not as complete (yet)?
To install the package firstly you need the Shared Mime data files. Which you can get from here. Then download and unpack libsharedmime and:
% make
# make install
Enhancements:
- Added code to check for a text file if the content lookup fails, if it matches it gets a text/plain type.
- Stopped the content lookup being performed on directories.
- Fixed a bug in the magic matching code that caused valid matches to fail. This means that some files will now return the correct mime type as opposed to a default "not found" type.

Apache Xindice is a database designed from the ground up to store XML data or what is more commonly referred to as a native XML database. The name is pronounced zeen-dee-chay in your best faux Italian accent. Dont worry if you get it wrong though, we wont mind. We just care that you spell it correctly.
You might be wondering what a native XML database is good for? Well it pretty much has one purpose, storing XML data. If you dont have any XML data, dont want any XML data or think XML is the most over-hyped technology of the new millennium, then Xindice is not for you. Were not out to change the way data in general is stored, only to provide a good solution for storing XML data. If you survey your projects and see XML popping out of every corner, then Xindice might be a real help for storing that XML.
The benefit of a native solution is that you dont have to worry about mapping your XML to some other data structure. You just insert the data as XML and retrieve it as XML. You also gain a lot of flexibility through the semi-structured nature of XML and the schema independent model used by Xindice. This is especially valuable when you have very complex XML structures that would be difficult or impossible to map to a more structured database.
At the present time Xindice uses XPath for its query language and XML:DB XUpdate for its update language. We provide an implementation of the XML:DB API for Java development and it is possible to access Xindice from other languages using built in XML-RPC API. As standards in the XML database area mature Xindice will include support for those that are most important.
Xindice is the continuation of the project that used to be called the dbXML Core. The dbXML source code was donated to the Apache Software Foundation in December of 2001.
Native XML database technology is a very new area and Xindice is very much a project still in development. The server currently supports storing well formed XML documents. This means it does not have any schema that constrains what can be placed into a document collection. This makes Xindice a semi-structured database and provides tremendous flexiblity in how you store your data, but, also means you give up some common database functionality such as data types. In its current state Xindice is already a powerful tool for managing XML data. However, there is still much that needs to be done. Feedback and contributions are actively encouraged.
This document attempts to describe those features that are working and can be used today. You should review the README file that is part of the Xindice distribution for the most current status on the project.
Main features:
- Document Collections: Documents are stored in collections that can be queried as a whole. You can create collections that contain just documents of the same type or you can create a collection to store all your documents together. The database doesnt care.
- XPath Query Engine: To query the Document Collections you use XPath as defined by the W3C. This provides a reasonably flexible mechanism for querying documents by navigating and restricting the result tree that is returned.
- XML Indexing: In order to improve the performance of queries over large numbers of documents you can define indexes on element and attribute values. This can dramatically speed up query response time.
- XML:DB XUpdate Implementation: When you store XML in the database you may want to be able to change that data without retrieving the entire document. XUpdate is the mechanism to use when you want to do server side updates of the data. It is an XML based language for specifying XML modifications and allows those modifications to be applied to entire document collections as well as single documents.
- Java XML:DB API Implementation: For Java programmers Xindice provides an implementation of the XML:DB API. This API is intended to bring portability to XML database applications just as JDBC has done for relational databases. Most applications developed for Xindice will use the XML:DB API.
- Command Line Management Tools: To aid the administrator Xindice provides a full suite of command line driven management tools. Just about everything you can do through the XML:DB API can also be done from the command line.
- Modular Architecture: The Xindice server is constructed in a very modular manner. This makes it easy to add and remove components to tailor the server to a particular environment or to embed it into another application.
- Database Structure
- The Xindice server is designed to store collections of XML documents. Collections can be arranged in a hierarchy similar to that of a typical UNIX or Windows file system.
- In Xindice the data store is rooted in a database instance that can also be used as a document collection. This database instance can then contain any number of child collections. In a default install of Xindice the database instance is called db and all collection paths will begin with /db. It is possible to rename the database instance if desired though it is not necessary to do so.

Whamb Sharing Protocol Daemon (WSD) is a perl script that allows you to share MP3 or OGG on a Unix/Linux or windows system.WSD needs perl 5.7.3 or later (5.8.0 recommended) and some modules (HTML::Entities, Encode, MP3::Info), you will find any instructions you need in the readme, so please read it ! WSD also needs RendezVous from Apple, its opensource and runs on lots of platform including linux/*BSD/Windows/Solaris and all Posix OSes

Installation is simple but depends by your operating system:
make os=linux on linux
make os=opensd on openbsd
make os=osx on macosx
make os=solaris on solaris

if you are running NetBSD or FreeBSD edit the makefile you will see:
ifeq ($(os),openbsd)
CFLAGS_OS = -DHAVE_SOCKADDR_SA_LEN -DHAVE_DAEMON -DHAVE_SOCKLEN_T -DHAVE_BROKEN_RECVDSTADDR
change it to
ifeq ($(os),bsd)
CFLAGS_OS = -DHAVE_SOCKADDR_SA_LEN -DHAVE_DAEMON -DHAVE_SOCKLEN_T

and use make os=bsd

You can start it with something like: build/mDNSResponderPosix -n "`hostname`" -t _whamb._tcp. -p 7603 -d
You may also want to copy mDNSResponderPosix to your /usr/bin directory