@razorpop: That's good to know for one thing and very sad on the other hand, because you don't give it back to the community that way.

Always remember you wouldn't have been able to start up without the community and open-source. Allow others to do the same.

It is like the old truck driver, who teaches a youngster how the biz goes, because there also was an old truckdriver for him once, who taught him how to survive out there.

Re: TrustyFiles legal status
 

Well, some of the people who are/were a little more involved with the GiFT project (e.g. J. Ashton) already stated on Slyck that they could prove this is a lie - and I tend to believe them.
That aside there were announcements from Razorpop - while they were working on TrustyFiles 2.2 - that it would be open-source like the GPL required it to be. A few weeks later they release their client and state the code in this version is all theirs they just rewrote a couple of thousand lines of code. - Really, you don't cough up a Gnutella implementation just like that.

I wish someone from the FSF or so would offer some money to sue those Razorpop people because ripping of OS technology is not a respectable business modell and people should be warned not to use TrustyFiles. You can have the same features from people who don't steal other people's work (like BearShare, LimeWire or even Shareaza).

Marc and Razorpop are a*shol*s. Really. You do not respect GPL and LGPL and then you are making unstainable big lies... Marc, there was a thread at slyck.com when TFS 2 went live, you participated and left once we asked you legal questions about the legitimicy of TFS. You said you knew nothing, as it was some kind of employee that was writing TFS. This is bullshit, I'm sure by your forums at razorpop that you are the programmer. I know you use gift and gnucdna, I just don't know what you did rip as opensource software for bittorrent support (gift?).

PS: for those who don't understand what the fuss is all about: AVOID trustyfiles!

Ciao

Regarding the original topic of the thread:

There will be bittorrent support in LimeWire. It will not happen in LimeWire 4.2 but possibly in 4.4.

Some LimeWire versions with early (but nontheless already working) bittorrent support already exist.

Authenticated RSS/torrent as a trusted show-season-episode delivery mechanism
 

On a slightly differnt track

The objective is to set up a torrent based publishing mechanism where the audience can be sure the source is trusted while removing the need for the RSS feed or a tracker to be hosted on a public server.

The question is which bits don't exist yet and how could they be achieved?
1. It starts off with the generation of a strong PGP key that is held by, the publisher (or moderator);
2. Next an "authenticated" RSS "feed" is generated as a container for torrents related to the show;
3. The first episode of the show is added as a torrent to the RSS feed;
4. The feed is published over a gnutella style of hosting/propagation so people can go to “the search engine” and do a search of "the show name" (this means that once published into the network the host would not need to exist any more). This takes the role of the tracker and makes the definition of the torrent un-shut-down-able;
5. The search would return the list of season/episodes for the authenticated feed and automatically start downloading the listed torrents;
6. As new shows are developed they are converted into a torrent file and the "authenticated" RSS "feed" is updated with a new version number in the title and uploaded to the network;
7. The client would “become aware” of the new episode through the "authenticated" RSS "feed" and automatically download the torrent to the targeted directory. This would allow the new episodes to just appear in the directory for the show;
8. If necessary the publisher should have the facility to delete and replace an episode. This would allow an early version of an episode to be replaced with a better quality version;
9. If at the end of the show’s run the "authenticated" RSS "feed" available on the network would contain all the torrents for the show and when added to the client the torrents would be downloaded in the correct sequence.

The above steps should be automatic i.e. aside from coming up with a unique show name and the content of the show itself all the published should have to do is direct the client at a watched directory where new content is placed for publishing.

An option would be useful to allow for restricted publishing of the "authenticated" RSS "feed" by switching the public/private key pair. In this way the key could be shared with a family member to allow sharing in a restricted format.

An additional component would be the synergy of operating this in combination with an IP masking tool.

This sounds useful, but why would you want to use torrents?

A magnet-link with a working first source and/or an ip-cache libe the one at freebase works quite well.

For a first model of trusted lists, you don't need cryptography, but simply a web-address which gives you the security, that the owner of the website is the publisher (which lacks a web of trust, but works as first step).

And when you're at that, you can just use the decentral content distribution of Phex: http://wiki.phex.org/Decentral_Content_Distribution

It downloads new files with every start of the program (because downloading more often didn't seem necessary, yet).

For download it uses magnet-links and Gnutella.

You can try it out by downloading one of the Polar-Skulk programs (modified Phex'):

http://www.phex.org/wiki/index.php/D...s_into_the_Den

Besides: We need people who search for free files and publish them decentrally via Phex.
What you need is a flatrate, a dyndns-host and a 24/7 Phex.

More infos:
- FAQ: http://www.gnutellaforums.com/showthread.php?t=62814
- Forum: https://www.gnutellaforums.com/polar-skulk/

What you need to do as of yet to publish a show is:

- Sharing only your shows.
- Putting the new show into your share along with the others.
- Click "export" in the Phex Libraray and choose "include your IP".
- upload the exported file to your server.

When you're uploading for the first time, you also need to inform us, that you're publishing the files and that you'd like to have them included in the Decentral Content Subscription.

If you instead want to create your own feed of content, you need to tell your visitors to add the URL of your uploaded magma-list to their Phex' (this needs fairly copetent users as of now, but if you ask in our forum, if that could be made easier, our main dev might add an easier way to subscribe to a new feed. It's been discussed for some time, but there never seemed to be enough need of easy adding of feeds to include it _now_ - instead of other features).

All the possibilities of doing this are there (except direct FTP-access via Phex, but that shouldn't be too hard either), it just isn't polished, yet.