|7 months later.....
||[Aug. 31st, 2006|02:58 pm]
This is now this:|
Yes, seven months to allocate two wimpy boxes and draw some turn-tables. :-)
oh, I forgot about this! so much fun...
I was about to suggest that some robot voice could speak the username of the phonepost playing (just before it started) but just realized it would spoil much of the fun ;-)
2006-08-31 10:30 pm (UTC)
If you've got a player that supports it, you should see the username and the post time in the stream title as each entry starts playing.
heh, yeah, quite a change from the rather much longer one before it
2006-08-31 10:31 pm (UTC)
Wow. I thought everyone got bored of phoneposts about a month after they were added.
2006-08-31 10:57 pm (UTC)
It doesn't show up as a continuous stream in iTunes (Windows, admittedly for the moment, Macs in the shop). The play progress bar just runs "off the end" as it plays the next voice post and then stops if it runs out of voice posts (assuming that it actually ran out).
Needs hold music between posts.
Do you lay awake at night worrying about the evil you unleash on the world?
2006-09-01 02:10 am (UTC)
So, I'm totally puzzled where iTunes is getting that spurious content length -- because as far as I can tell, the server isn't sending a content-length header! I was going to suggest "just hack your copy of mod_mp3 to comment out the length header, and it should all work fine", but I don't see it there at all. I think the exchange between iTunes and the server looks like this:
>> GET / HTTP/1.1
>> Accept: */*
>> Cache-Control: no-cache
>> User-Agent: iTunes/6.0.5 (Macintosh; N; Intel)
>> Icy-Metadata: 1
>> Connection: close
>> Proxy-Connection: close
>> Host: frnk.livejournal.com
<< ICY 200 OK
<< icy-notice1:<BR>This stream requires a shoutcast compatible player.<BR>
<< icy-name:LiveJournal Voice Posts
<< ...mpeg data...
And there's no content-length in there! (Nor x-audiocast-streamlength.) But, maybe I got the headers slightly wrong, because mod_mp3 seems to send different responses depending on whether it sees the various Icy headers... and there doesn't seem to be any documentation for its behavior anywhere.
LOL. I can't wait for the usual people to whine about this one, complaining about their privacy being violated when they're the ones to make it public to begin with.
2006-09-01 05:29 am (UTC)
Sad, but oh so true.
Three people so far, and counting!
*cries* people talk such crap.
How does it queue up what call gets played next? Is it all based like, you connect and it queues up the last recorded one? After it ends does it queue the next in line from being recorded or what?
can we filter the crappy ones?