|
Top-level
 @pixel I wasn’t expecting this, and even though it violates our ToS, I do believe that APIs should be open. Officially I’m not impressed, unofficially I am impressed and won’t hinder unauthorized 3rd party access. Btw, you and @h should help me define the v1 schema, I’m aware of 3 devs who plan to build 3rd party clients and would love your help in an official fashion! This would normally lead to legal action, but here in the fediverse, you are doing my work for me ✨ 5 comments
@pixel @h ngl, there was an initial temptation to block 3rd party access, but then I remembered I'm building this for the fediverse. I'm kinda honoured that 3 different groups reverse engineered the API so quickly, and that's what the fediverse is all about! I'm not trying to get rich quick with a TikTok clone, rather, I want to revive the magic of Vine and give the whole platform to the people so they can do it on their own terms. And you're playing an important part, so thank you @dansup @h I guess blocking would be really tough, but making the API harder to use with something like request signing would add a significant challenge (that's what most mobile apps tend to do) in the end, for reverse engineering folks it just tends to be an additional challenge :P and I'm sure you'll put out an officially endorsed (to use) API at some point, so this is just some fun poking and a head start for the community to build things around Loops. |
Gregory's Server
@dansup @h added a disclaimer to the repository to at least make others aware of the ToS.