Tag Archives: sharing

nap and nap: Take a nap or two

Two-for-one today, and not just because it’s 02-02, but because I have two programs with the same name, and I don’t think either of them really warrants an entire post to itself.

If you search both Debian and Arch/AUR for “nap,” you’ll find two different programs. The first, from Arch, is a variation on the sleep command, that shows a progress bar as it ticks away.


What you see there is really the grandest example of what I could do with nap, but that isn’t meant to suggest that it has no potential. If you search through this site, you’ll see that in the past two years, I never bothered to make any notes about the sleep command itself, because it was hard to think up something about a program that just waits.

nap does the same thing, but this time tells you how close you are to the end. If you want to know how much longer you’ll have to do nothing, nap will tell you.

The other nap is out of Debian, and is a console client for the now-ancient Napster file sharing protocol.


Unfortunately, that’s as far as I ever got with nap. Its self-configuration routine works fine, and I imagine if you could somehow force-feed it a list of servers, it might get further into its process, but I didn’t have any luck. It sat for the better part of an hour trying to download the server list from GotNap.com, and after that I felt pity and turned it off.

In any case, I don’t know what would be left on the Napster channels. I understand there is still some legitimate content operating under the same name, but whether this program can access it, or if this application is just lost in the dark ages of peer-to-peer networking … I can’t say for sure.

But that’s all for today. I see that my list is getting a bit short. I shall have to go out and beat the bushes this week, and see what falls out. … 😈

ncdc: Direct connect in ncurses

I missed a step somwhere, around the turn of the century, when direct connect became a thing for file sharing. Somehow I went straight from the naivete of Napster to the vicious intricacy of Gnutella to the hideous maelstrom of malware and Kazaa, then popped out somewhere around rtorrent and youtube-dl. :\

I never received the memo about direct connect, and as a result I always manage to confuse that with direct cable connection, which is not only totally unrelated, but a nightmare of bad memories in its own right. 😯 And as luck would have it, I’m not really in the market much for peer-to-peer file sharing these days, unless it has to do with a newly released Linux ISO.

So ncdc, an ncurses client for direct connect, is pleasing … but about a dozen years late to really pique my interest.

2014-11-04-2sjx281-ncdc-01 2014-11-04-2sjx281-ncdc-02

I had no trouble building ncdc, and it connected without effort too. The quick instructions on the home page were enough to get me into ncdc as far as you see, plus a little more.

I didn’t actually download anything, but I did browse a few files just out of curiosity. ncdc never balked and never spat an error, unless I did something outside the bounds of normal.

What strikes me most about ncdc, strictly from an interface standpoint, is how much it resembles programs like irssi and some other IRC clients. ncdc includes a “tabbed” interface, and you bounce between tabs via the ALT key and the number of the tab. The main or original tab is a kind of system log. Connecting and searching and listing connected users is done with slash-commands. All very much like irssi (but not like rhapsody 😉 ).

So even if you don’t have much experience with direct connect, like me, you’ll probably be mostly comfortable getting ncdc started.

Beyond that I don’t have much advice for ncdc. Most of the basic commands are found on the home page or by triggering the help function to show in the main tab. If you’re still an avid file sharer and need something lightweight for direct connect transfers, ncdc could fill the bill. 🙂

mutella: Looking for signs of life

I’m going to cross my fingers, and this time hope against all odds that it’s my inability to configure something that is causing an apparent lack of function.

This time it is mutella, a rather old client for the Gnutella network that you might remember from a decade ago. And unfortunately, no screenshot. 😦

I may be able to brag as the only person to remember hearing about Gnutella before Napster or its ilk. It’s an odd badge of fame, but I wear it.

My distress today came at building mutella out of the AUR version, which was supposedly updated as recently as a year ago.

With so few dependencies, I was surprised that it crashed and burned when I tried to build it. A patch is included, and as a troubleshooting measure I tried commenting it out. But that wasn’t the issue.

Adding to my woes, I don’t see it in Debian. Or Fedora. Or Suse or Slackware. 😕

The question at this point becomes, does it still build? I’d like to think so; I’d like to think that whatever issues are holding it back are on my end, and that it will or could still work.

And all of this is done in the hopes that the console version is still functional. Screenshots on the home page look hopeful.

Of course, even if I could get it to build, I’d still have to get it configured, and that’s where I usually fall flat. So maybe it’s better this way. 🙄

Wikipedia insists the Gnutella network is still active; if mutella will build, connect and work as promised, please send us a screenshot. Science demands an answer.

And nobody wants to announce the time of death on an application. 😦