also forgot, but I am going to have a website soon, to show my love for all of this. If you all were probably not aware, I haven't had A computer in a long time. In that time, I managed to talk to some cool people in the chiptunescene, one that just happened to be A big influence in my chip archival today. If you all don't like getting sync, I strongly recommend that you hold for the website as I am working on it with some friends, but if you want to know what it's going to be, it's chiparchive.cf
In other chip related news, I, along with BGT lover have started to try and help some developers with chiptune tracker accessibility, so we can try to get screen readers working with chiptune trackers, and we did get a nice developer working with us, for A multy system tracker called Deflemask,  that can make music for the gameboy, turbografcs/pc engine, Sega megadrive, and more! I also am talking to superdisk, an awesome fello who is making a tracker for making music on the gameboy, called Hugetracker.
as to why you should have this folder, more music, more things for making music for various computers and consoles, more everything! it has music by some blind artists that don't get the love they should get like Daniel keeshelovsky, *sorry for the spelling,* his name is poalish, and Evangelosz Nagy, who did an awesome Goemon thing in the mck2ch archive. His other awesome works are there too!  BTw, look at his sequence storm stuff they're good!
Q and A.
Q. Is this folder like ultrabit?
A. while this folder and ultrabit may have some things alike, they're not the same, and shouldn't be treated as such.
Q. Why go through all this effort with trackers, rather than just using midi to make music?
A. It's called chiptune, not fakebit.
Q. do you still have A high passion to make music?
A. Yes I do!
If there's anything elce, let me know.

what is the difference between this and ultrabit chips archive, thats allready 30 gb in size.
Its got mostly chiptunes, not interested in tools as such.

Can there be a changelog.txt in the folder for any changes and have a rule that everyone that changes the folder updates it?
This has helped on other chip folders for when its updated for backup purposes.
Thanks

Your BTSync link is invalid. Is that on purpose?

Well keybase wouldn't do for the client side, it just sucks access wize.
However you could 7z the archive up to a public folder and then share the link I guess as long as it didn't take over your space.
I have managed to get and extract the many zip files in the archive and winamp can play the files.
A few notes for users.
1.  the .lha file in the folder can be extracted with 7zip.

There will be many ahx files withh .ahx filename as in ahx.filename or .ahx.filename.
If you turn that round to filename.ext you will be able to play them.
Gripes, nsf.7z and nsf.zip are the same name even though their content is different, same as nsfs.rar could these files be renamed to something discriptive.
You did a good job with archives.
You however may better serve the folder in the long run by taking the archives which are allready archived out of the folder.
keygenmusic archive hasn't been updated in ages, but can be gotten from the net, it could be daunting for some to brouse a directory so you can leave it in maybe though with my own downloads, ultrabit and this folder I have at least 3 coppies of the hvsc and keygenmusic alone on here.
For archives with zipps or lzh files in small files inside files it may be better if the archive was zipped but with the smaller files extracted, it took me a while to extract these and put these where they needed to go.
Notes on winamp, not all gbc files play and a few othhers but most do.

For those that have it, do not combine inyansf and nosefart together else winamp will not start.
Decide what you want and kill the other, I killed nosefart and it worked.
I am also looking for a shell replacement when working with small files.
Windows explorer is mostly ok with large files to some extent but files like chips or mids being a few kb in size will choak it.
I don't always encounter the shittyness of explorer as I don't predominantly work with the shell on a daily basis to a large extent anyway but I had to heavily work with it yesterday as well as doing backups and the like and yeah small files and loads of data just don't mix.
I have to keep restarting the shell every few minutes, and eventually windows after I am done, its not a showstopper as most opperations don't need me to be in a folder but it can be a real time lengthener.

I use keybase a lot. This might be a bit off topic, is 2TB of google drive storage worth getting for $10 a month?

Okay, so some misconceptions/misunderstandings to clear up:

1. Keybase does not use keys like BTSync does. Keybase works on invites.

2. A Keybase team has members which can have different roles. These roles, in order from highest to lowest, are:
   

   • Owner: allows full access to a team

   • Admin: allows slightly less permissions to a team. Similar to an owner, but an admin cannot delete a team.

   • Writers: allows members to write and read chat messages; view, edit, and save files; and create chat channels.

   • Readers: lowest level of privilege. Only allowed to read and write chat messages and view files.

3. Keybase has invite tokens, but these are one-time, cryptographically secure tokens that can be shared via things like iMessage or SMS.

To create a keybase team from the command line:

1. Install keybase and sign in.

2. Type keybase team create <team name> where <team name> is the name of the team you'd like to create.

3. Optionally, modify team settings with keybase team settings. This command accepts a team name and then a list of options:
   

   • The --description option sets the description of the team

   • The --open-team converts this team into an 'open team' and optionally sets the role that a user will assume when they join. This can be changed later of desired. The role can be either 'reader', 'writer', or 'off' to disable the function.

   • The --profile-promote option promotes this team on your profile so that when keybase users view your profile they see this team there. This accepts either 'yes' or 'no.

   • The --allow-profile-promote option enables members of the team to promote the team on their profile. This option accepts 'yes' or 'no'.

   • The --showcase option determines whether this team shows up on the Keybase popular teams list at https://keybase.io/popular-teams. This accepts 'yes' or 'no.

   • The --disable-access-requests option determines whether normal keybase users can request access to this team with the keybase team request-access command. If yes, then this permission is denied and members must be invited; if no, anyone can join the team without needing an invite.

4. Finally, add members to the team. This is doable via the keybase team add-member or keybase team add-members-bulk command. Use the --help option to these commands for full usage information.

Hope this helps! Teams will appear under KBFS/teams/teamname. To enable KBFS:

• Open the keybase GUI app

• Locate 'files' and click on it

• Click 'enable'

KBFS will then appear under k:\ on windows.