Earlier quoted context omitted.
What happened to the Soundcloud API?
You can read about it here: https://medium.com/@padschneider/r-i-p-soundflake-79f7cf5f9d... I was super bummed when it happened because I use Soundcloud a lot and their app has some serious issues. I was considering building my own client, but then saw that these guys built a really nice alternative. Sadly it got shutdown shortly after.
Genius API
21–30 of 31 posts
Re: Genius API
#22APIs can shut down, bummer. But it's more of a bummer to never use them in the first place. It'd be rad if you could integrate with Genius' API in such a way that if they ever shut it down, or you want to switch to another annotation service for any reason, you would only have to point to another annotation provider instead of rewriting all the syntax/semantics of the integration. Sound cool? Get involved with: * W3C…
Feel free to try an alternative, open annotation api, like ours: api.hypothes.is
Re: Genius API
#23Genius is really cool service (founders/owners aside) and I love it for song lyrics. An API into their backend sounds appealing but without some contract that keeps them from shutting down the API with little to no notice or pulling a twitter/soundcloud/netflix/etc I can't even begin to think about building on top of this (for anything but little fun side projects/POC's).
Which is exactly what they want. They don't want people scaling and running huge businesses off their API, they want lots of little experiments by people messing around. They can see what gains traction and then copy it. It's like a free startup incubator and your investment is the time your engineers spend keeping the API up.
Re: Genius API
#24Re: Genius API
#25Re: Genius API
#26APIs can shut down, bummer. But it's more of a bummer to never use them in the first place. It'd be rad if you could integrate with Genius' API in such a way that if they ever shut it down, or you want to switch to another annotation service for any reason, you would only have to point to another annotation provider instead of rewriting all the syntax/semantics of the integration. Sound cool? Get involved with: * W3C…
Thanks for this comment Ben! +1000 Feel free to try an alternative, open annotation api, like ours: api.hypothes.is
Re: Genius API
#27APIs can shut down, bummer. But it's more of a bummer to never use them in the first place. It'd be rad if you could integrate with Genius' API in such a way that if they ever shut it down, or you want to switch to another annotation service for any reason, you would only have to point to another annotation provider instead of rewriting all the syntax/semantics of the integration. Sound cool? Get involved with: * W3C…
Thanks for this comment Ben! +1000 Feel free to try an alternative, open annotation api, like ours: api.hypothes.is
What kind of tech stack do you run? Last time I check it was mostly Javascript (ugh).
Re: Genius API
#28Re: Genius API
#29APIs can shut down, bummer. But it's more of a bummer to never use them in the first place. It'd be rad if you could integrate with Genius' API in such a way that if they ever shut it down, or you want to switch to another annotation service for any reason, you would only have to point to another annotation provider instead of rewriting all the syntax/semantics of the integration. Sound cool? Get involved with: * W3C…
Re: Genius API
#30APIs can shut down, bummer. But it's more of a bummer to never use them in the first place. It'd be rad if you could integrate with Genius' API in such a way that if they ever shut it down, or you want to switch to another annotation service for any reason, you would only have to point to another annotation provider instead of rewriting all the syntax/semantics of the integration. Sound cool? Get involved with: * W3C…
Thanks for this comment Ben! +1000 Feel free to try an alternative, open annotation api, like ours: api.hypothes.is