Slashdot Mirror
OpenDJ UNIX-based P2P Streamer
hardcorejon writes "I found the Streamer software interesting, particularly because I've also written a remarkably similar piece of software, called OPENdj. Because Streamer requires
Windows, I thought my fellow Slashdot readers would be interested in
OPENdj, which is an open source
Java/Linux-based distributed streamer. Development on OPENdj began over a year ago, with version 1.0.0 appearing this past May. It has some slick features, including
automatic archiving, archive search, stream meta-tagging, listener
counts and chat rooms. Download it, bang on it, send me patches :)"
Dear developer: :)
OpenDJ doesn't crash!
Is this a bug or a feature?
Will you be putting the crash thingee back in so as to make it comparable to its closed source Windows counterpart?
--- Grow a pair, liberals... stop letting the Republicans bully you!
Hello slashdot folk.
I'm really interested in getting as much feedback on OPENdj as I can. Towards that end, if you have any questions, comments, concerns that you'd like to direct towards me, please let me know.
Thanks,
- jonathan.
question: how will you avoid getting killed by the fees on internet radio broadcasting? Don't you have to keep a log of exactly who is listening, what is broadcast, etc etc?
There's no need to actually invent new P2P-stream-distribution techniques: a better approach would be to merge live, refreshing station playlists with existing P2P file-sharing networks, like Gnutella, ED2K, FastTrack, etc.
You can think of this as as "Judo Radio" because it uses a tiny, smart control channel to throw around a giant amount of content that lives and travels on outside networks.
I wrote more about it here:
It's not quite the same as typical P2P-webcasting proposals because it leverages open, ownerless content-distribution networks that are already in place, and in fact the "stations" can be agnostic about how the data arrives to audiences. They just say, "get and listen to this next", ad infinitum.Whether the "stations" need any licenses whatsoever to the tracks they "recommend" seems a debatable point to me: the stations themselves make no copies of copyrighted material at all, instead leaving that completely up to the audience to do on their own.
This approach thus has the same resiliency (or weakness) of the underlying P2P file-sharing networks themselves.
Theres not a single good java app for peer to peer, name one.
Err...Limewire??
Why Java?
Because server side networking code is REALLY easy in Java. Writing multithreaded code is REALLY easy in Java.
That said, OPENdj is really built on top of open wire-level protocols. The current client and server are in Java. I'm working on a C client right now. If someone wants to reimplement the server in C, go for it!
- jonathan.
Offer a download button which downloads all the file in one tar or zip, have some instructions on how to install it on your website.
If you use Linux, please help development of Autopac
I do sidestep the CARP issue by requiring the DJ to take care of all that. If the DJ wants to broadcast original material, or do a talk show, then there are no copyright restrictions on that. If they want to broadcast copyrighted material, it's their responsibility to pay any associated fees.
The broadcasting software that DJs use tells them how many listeners they have, so if they need to use that to calculate what they owe, the can use it.
On the bandwidth side, a 24 or 32Kbps upstream signal is about all a 56k modem can do. I've tested it with PacBell dialup anyway, and it works OK.
Which brings me to another thought: I hope the RIAA realizes that these low-quality streams are not really worth prosecuting. They are listenable, but certainly won't infringe on album sales - the difference in quality is just too huge. Now if I were streaming at 128k, then you might have a different story.
- jonathan.