jodel_api
jodel_api copied to clipboard
nborrmann
Jodel is not happy about this
Maybe you received an email as well. The Jodel Team is not happy about me doing this, so they contacted me, and I'd like to let you know, that you should also stop your work on this, until I find a solution with them.
They told me to close all repos regarding my JodelAPI and all it's sub projects, because they were used to spam on jodel. That's pretty much the short version.
Thank you for the fast reply. :) They should offer at least an offical read only api. :D
I don't think that deleting (what does "closing" even mean?) the repos makes any sense, there's too many forks and they won't be able to remove all of them.
They told me that they're mostly fine with read-only functions, the problem is the verify() function that I built, and I kinda agree.
I guess I will move the gcmhack stuff to a different repo and remove all the Jodel specific stuff. That should stop most script kiddies from spamming, because they'll have to decompile the app themselves to get the IDs and keys for GCM.
Yeah, that won't solve anything. all the forks can still be found via google or github search.
They can request a DMCA takedown notice to disable this repo and forks. But the internet never forgets and I think many of us have a local copy :P
They told me all that aswell, I've been invited to Berlin and I will meet them there. I will definitely discuss this with them. I made a few plans/concepts for the API and it's security, so I hope that we will find a great solution for this.
@anaseqal Sounds cool, join me on Gitter and shoot me a PM: https://gitter.im/JodelAPI/Lobby?utm_source=share-link&utm_medium=link&utm_campaign=share-link
I've been invited to Berlin and I will meet them there.
@ioncodes Any updates on here?
What is the offical statement from the jodel hq? Is there a way of developing "good" bots (like a daily weather bot or some cool things) for jodel which are using the api with the agreement of jodel?
@cpyix We are allowed to use read endpoints. We need to wait for them to create a public API.
so I'm not sure does this mean this api will not be updated with the new signing key? and we have to wait until the release of an official api?
