Share

FurthurNet

File Release Notes and Changelog

Release Name: 1.7.2Beta

Notes:
*****************************************
* Furthur v1.7.2 Release Notes          *
*                                       *
* April 20, 2003                        *
*****************************************

If you have not already read the README.txt file that announces this release, please do so first.

This document describes some of the changes and features that you will
find when using this new version of Furthurnet.  We hope you will consider
them useful and provide us any feedback you may have on anything that
is broken, suggestions you may have, or flat-out praise  ;-)

Major issues addressed since version 1.7.1:

1. Implemented a naming convention to eliminate improper file types in
   audio and video shares, and to ensure complete and quality filesets.

2. Implemented additional security features to prevent sharing of
   official releases and other filsesets containing copyrighted material.

3. Implemented compression of network messages that can reduce network
   overhead by as much as 50% or more.

4. Added support for users behind proxy servers.

5. Improved accuracy and transfer speed calcuations and display.

6. Added "last activity" column to shares and partials lists

7. Allowed selection of multiple files for searching and downloading.

8. Fixed bugs that prevented columns from sorting correctly.

9. Combined Settings into a single menu and reorganized them.

10. Began implementation of support for FLAC.

11. Restored Phish to the network and updated trading policies for many
    artists.


Best regards,

The Furthurnet team
---------------------------------------------------------------------


THE URL for this document is 
https://sourceforge.net/project/shownotes.php?release_id=154090

---------------------------------------------------------------------


I. NEW .FURTHUR DIRECTORY

Furthur now expects to find certain files in a directory called 
".furthur".  The Furthur installer should create the directory, if 
necessary, and move the right files into it if you are doing an
upgrade. If, when you first start Furthur, you discover that all of
your old shares have disappeared, the problem may be that the file
sharing.cfg is not located in .furthur.  You can usually solve this
problem by finding sharing.cfg and moving it into .furthur, and then
restarting the Furthur program.

The location of .furthur varies, depending on your operating system

- On a PC running Win2000 or WinXP: 
                        c:\Documents and Settings\[your user name]\.furthur

- On a PC running Win98 or Win95:
                        c:\windows\.furthur 

- On a Mac running OSX: 
                        ~/furthur (a/k/a /users/[your user name]/furthur)

*** In OSX, the .furthur directory will be hidden b/c it begins with a 
"."  When you install Furthur, the installer will create a link to a 
visible directory called ~/furthur.  Everything that appears 
in ~/furthur is, in fact, really within ~/.furthur.

- On Unix or Linux, you should find ~/.furthur.  The directory may be 
invisible, too.  The command "ls -la" will make sure that you can see 
everything.

Also, the new Furthur install will update the location of your download 
and temp directories to underneath .furthur.  If you want to use a
different location, you must move the directories and 
then change their location in the Settings > Configure Furthur > 
Downloads.  

---------------------------------------------------------------------

II. FILE NAMING CONVENTIONS

Furthur 1.7.2 enforces a naming convention for all shares, as a method 
of quality control.  It does this each time you start Furthur, each time 
you share a new fileset, and each time a partial completes.  

This means three things.  First - when you start 1.7.2 for the first 
time, you will probably see a cascade of error messages, informing you 
that your shares are not correctly named.  When you click "ok", each bad 
share will be deactivated and removed from your shares list.  DO NOT 
PANIC - the files are still on your hard drive.  Second - you will not 
be able to add new shares unless they conform to the naming convention.  
Third, any incoming partials that complete will produce an error message 
if they do not conform to the naming convention, and will not move over 
to the share tab when you clear the error message.  Again, don't panic, 
the files are still on your hard drive.

If you need to rename files to share or re-share them, file-renaming 
software is a big help.  You can find a list of freeware here:  
http://forums.furthurnet.org/viewtopic.php?t=8601.  Don't forget that 
any Furthur shares are "read only" - you may have to change that 
setting to rename files.

The Naming Convention Rules

In order to share a fileset, every file in the fileset must conform to 
the following naming convention.  Here are the rules that a fileset must 
follow, and then a detailed description of each rule. 

****************************
Rule #1 - Only the correct filetypes are allowed in a fileset.  If you 
include additional filetypes, the fileset cannot be shared.  Other 
filetypes are optional - they are allowed but not required.

Share Type    Allowable File Types        Optional File Types

SHN           .shn   .md5   .txt          .skt
FLAC *        .flac  .txt
MP3           .mp3   .txt                 .md5
OGG           .ogg   .txt                 .md5
AVI           .avi   .txt                 .md5
Quicktime     .mov   .txt                 .md5
MPEG          .mpeg/.mpg        .txt      .md5
VCD           .mpeg/.mpg/.dat   .txt      .md5
SVCD          .mpeg/.mpg/.dat   .txt      .md5
DiVX          .avi   .txt                 .md5

This means:

No .jpg, .gif., .doc, .clb or .pdf files.
No .mkw files
No .ds_store files

Rename .info and .nfo >>> .txt or .info.txt
Rename .ffp >>> .ffp.txt

* Note: FLAC IS NOT SUPPORTED IN 1.7.2.  Do not share Flac filesets or 
you will crash Furthur.  

****************************
Rule #2 - Each fileset must have a .txt file and at least one other file 
of the correct file type.

Each fileset must have a .txt file.  Each fileset must also have at 
least one file of each data filetype.  For example, an MP3 share must 
have at least one .mp3 file.  Other than SHN filesets, .md5 files are 
optional.  .skt files are also optional.  In either case, if those files 
are present, that's OK.  If not, that's OK, too.

****************************
Rule #3 - Each file in the fileset must start with the correct band 
abbreviation, and then the date, correctly formatted.

Part 1 - The first characters of each file must be the official Furthur 
band abbreviation.  The official Furthur band abbreviations can be found 
in parentheses following the band name (1) in the drop down list in the 
Search window, (2) in the "attributes" tab of the File Set Editor that 
appears when you add a fileset, and (3) here:  
http://furthurnet.org/bandlist/  Please note that bands with numbers in 
their names, e.g., "b47-" have a "-" following their abbreviations.  
Band abbreviations should be lower case, but can by upper case (or a mix 
of the two), also.  

Part 2 - The date format is as follows:  yyyy-mm-dd or yy-mm-dd.  YOU 
MUST USE HYPHENS between year, month and date.  Dashes, periods, spaces, 
or anything else are invalid.  Also, when you add a new fileset, you 
must tell Furthur the date of the show - if that date doesn't match the 
filenames, Furthur will give you an error:  "the name of the file xxxxx 
does not match the name of the fileset xxxx yyyy-dd-mm."

Part 3 - Any extra information can then follow the date, so long as it 
comes before the file extension.

This means:

    INCORRECT                      REASON                  CORRECT
allmans2000-08-10.md5          Wrong abbreviation    abb2000-08-10.md5
skb11-24-02.txt                Date in wrong order       skb02-11.24.txt
b472002-12-31.md5	Wrong abbreviation (missing "-") b47-2002-12-31.md5
abb2000/08/10d1t01.shn  "/" = invalid.  Replace w/ "-" abb2000-08-10d1t01.shn
abb2000.08.10d1t01.shn  "." = invalid.  Replace w/ "-" abb2000-08-10d1t01.shn
abb 02-08-10d1t01.shn     Space between abb and date     abb02-08-10d1t01.shn
skb+sears2002-11-24.txt    +sears goes at the end    skb2002-11-24+sears.txt
ph1999-12-31-FOB-mk4.txt                OK                  
ph1999-12-31d1t01-fixed.mp3             OK                  
ph1999-12-31-hi mom.shn                 OK                  
ph1999-12-31.eac.log.txt                OK  


When filenames are wrong, you will see an error when you try to add a 
fileset that says ".md5 mismatch."

****************************
Rule #4 If the fileset has .md5s in it, then each .md5 checksum must 
verify with the files in the filesets; every file in the fileset (except 
.txt files) must have an .md5 checksum. 

This means:  

- The filenames inside each md5 file must match names of the audio and 
video files, no .md5 checksums can be missing, and there can be no extra 
checksums, either.  Furthur does not expect a checksum for .txt files.  

- The names of the checksums listed inside the .md5 must match the names 
of the .shn, .mp3, and other files in your fileset.  If you have to 
change filenames to get the fileset to share, you must also update the 
filenames listed in the .md5 file itself, to match the new filenames. 
You can use any simple text editor, like Notepad, to edit the .md5 files.

- Each .md5 checksum must verify against the files in the fileset.  No 
defective files.  And, there cannot be any .md5 checksums for files that 
are not in the fileset.  There can be no missing files.

- If the checksum names do not match the filenames or do not verify, 
Furthur will report that one or more of the files listed "had an .md5 
mismatch".

- If there are too many or two few .md5 checksums, Furthur will report 
that "X files present but Y .md5 values found."

Here's an example:

If the fileset contains:  Then the .md5 file(s) must include:

abb2000-08-10d1t01.shn    xxxxxxxxxxxxxxxxxxxxxxxx *abb2000-08-10d1t01.shn 
abb2000-08-10d1t02.shn    xxxxxxxxxxxxxxxxxxxxxxxx *abb2000-08-10d1t02.shn 
etc.                         etc.
abb2000-08-10d1t01.skt    xxxxxxxxxxxxxxxxxxxxxxxx *abb2000-08-10d1t01.skt 
abb2000-08-10d1t02.skt    xxxxxxxxxxxxxxxxxxxxxxxx *abb2000-08-10d1t02.skt 
etc.                         etc.
abb2000-08-10.txt         <<< No checksum required.

****************************
Rule #5 - You must fill out at least some of the "attributes" fields 
when you add a new share.  Leave 'em blank, and the share won't go 
through.  Furthur will prompt you if you omit a necessary field.

---------------------------------------------------------------------

III.  HOW TO GET HELP

If you need help running or installing Furthur, join us in Furthur Chat, 
using the Furthur program, or post your question in the help forum, 
http://forums.furthurnet.org/viewforum.php?f=7

Also, please read the FAQ at forums.furthurnet.org, as many of your 
questions will be answered there.


Changes: Changes between 1.7.1 and 1.7.2: - Better autodetection of external programs (things like music players, flac decoders, etc.). - Added the error console. - Added much stricter seeding standards (at boot time for existing shares, at initial share time, and as partials move to shares). Now the file names and types are checked for consistency with the file set name. Also, the mechanism for controlling banned material has been improved. - Fixed bug that could cause Furthur to either incorrectly disallow you from removing a shared fileset, or allow you to remove one that was still active. - Modified the settings menu. It is now all on one screen and tabbed. - Added "Last Activity" column to partials and share tabs so users can track activity on their file sets. - Fixed bug that would cause a partial to be lost if Furthur was shut down before the first time the partial had ever attempted to begin downloading. - Don't run identd all the time, only when connected to the chat server. - Added proxy support to the Furthur Network Setup menu. - Implemented compression to reduce network utilization. - Allow multiple selections in the Search, Share, and Partials tabs. - Fix bug where an update in the Share tab caused the current selection to go away.