Yeah that would be better but it seems that the twitter search
engine does not recognize curly brackets and dots in search
queries, so searching for either of them returns random results
with the word "play" in them. I haven't yet had the luxury of using
#supercollider in my codes, all of them so far are barely 140
characters. This concept is quite addictive, having seemingly
stupid limitations makes you addictive and feel creative. :)
Btw twitter is experiencing difficulties for quite a few days and
tweets are disappearing at random. I've also been a victim of this,
but they say they will re-appear back eventually. Missing some code
already. Anyway...
B.B.
On Apr 8, 2009, at 4:22 AM, Michael G. Cox wrote:
This is great.
I just posted one on
http://twitter.com/themonkeyfist
one thought though:
if this is going to be added to the main distro then
how about searching for just 'play{' OR '}.play'
instead of '#supercollider'. Them's an awful lot of characters
that could be used for sctwitting. I'm pretty sure that there
won't be too many non-sc posts containing 'play{' OR '}.play'
-mgc
twitterpated with #supercollider overload?
jonesin' for a 140-char-max fix in your ear?
--
View this message in context: http://www.nabble.com/sctwitt-tp22745438p22941914.html
Sent from the Supercollider - User mailing list archive at
Nabble.com.
_______________________________________________
sc-users mailing list
info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: https://listarc.bham.ac.uk/marchives/sc-users/
search: https://listarc.bham.ac.uk/lists/sc-users/search/
_______________________________________________
sc-users mailing list
info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: https://listarc.bham.ac.uk/marchives/sc-users/
search: https://listarc.bham.ac.uk/lists/sc-users/search/