>U.S. prosecutors pointed out that wget was not on the list of “approved” programs for use in facility where Manning worked.
I know it sounds trivial but it was an unauthorized tool run on a system that was supposed to be secure as that system was talking to SIPRNET. Above all the other things PFC Manning has shown the world, he's also shown that security standards & procedures around some of the most damning secrets the DOD & State department could stupidly put on one fileshare was unprotected. Ironically this stuff might have shown up in foreign intelligence circles even without the PFC's actions.
Taking a page from something I learned from MySQL replication tricks, have you thought about trying a master -> inner slaves -> slaves out peers? Where there's one inner slave per datacenter/region.
I know atleast with 1.2.6 a slave can be a slave of a slave but I never measured the latency of a write at master, through the inner peers, out to the fan out slaves. Admittedly a more complicated topology but it would circumvent the stampede's against a master instance and also makes it easier to spin up larger numbers of slaves without wiping out the entire platform.
I have a widget like this for AWS+Virtualbox, it sorts all instances across all regions into tag name groups, by ip, by region, and by instance type. Unfortunately I know it only works for Windows and linux at the moment and my company hasn't given me a green flag to release it.
Still this project is a lot prettier and appears to have been more refined while mine was hobbled together in a hour or two and fit in one Python file ( reasonably, its not 10 files in one ).
Just got a client off a container based provider and it wasn't too great an experience ( dramatically slow networking, unreliable file I/O ). Granted I could, and can continue to, say the same thing about virtualization but virtualization is here and reliable enough that it seems like a hard sell to want to try something that is even less performant.
Funny memory, at a startup weekend in a team as the only technical resource. Had my headset on but wasn't listening to music... was somewhat amusing as everyone passed out C letter titles for an idea that wasn't even implemented. Took my headset off when someone claimed CTO "CTO huh? What am I doing right now?... Oh you don't actually know? You want to be the CTO but you don't know what your only engineer is doing?" Walked off after that.
Startup weekend is probably one of the last places on earth to find legit entrepreneurs/founders. I've been to 2 and never will be going again- such a mental drain to accomplish so little.
The API client just let you search, get popular songs, and get individual song info. There was no downloading included in the API client - if you wanted to download a song based on the info from their APIs you would have to write your own code to do that
It provides only basic search functions of course, but it is publicly documented and I'm sure Grooveshark can't complain if you use it.
I wrote a Go package for it years ago (literally, 2010 I think) and it still works fine. You get tinysong.com shortlinks, which lead to the song on Grooveshark.
I am not in anyway affiliated with GS/Escape and have 0 influence on their operations, but given what I know of them and that it only replicates what several other API libs provide, this DMCA seems really odd or a mistake?
From someone elses comment, looked at the google cache of your github repo,
.url is a part of the meta info from the api - there is no downloading functionality in the api library itself. The song url is just the culmination of the song id and your session
Gizmodo will just summarize mashable. Eventually AOL will decide they should be the #1 search term for 'python' and 'sendgrid' and their content mill will start working those phrases and beat them all.
Then they'll all congratulate themselves for raising the journalistic bar one cheap SEO trick and even cheaper "I can't believe it's not plagiarism" rewording at a time.
>U.S. prosecutors pointed out that wget was not on the list of “approved” programs for use in facility where Manning worked.
I know it sounds trivial but it was an unauthorized tool run on a system that was supposed to be secure as that system was talking to SIPRNET. Above all the other things PFC Manning has shown the world, he's also shown that security standards & procedures around some of the most damning secrets the DOD & State department could stupidly put on one fileshare was unprotected. Ironically this stuff might have shown up in foreign intelligence circles even without the PFC's actions.