search

nborrmann / jodel_api

Unoffical Python Interface to the Jodel API
MIT License
150 stars 33 forks source link

Jodel is not happy about this #39

Open ioncodes opened 7 years ago

ioncodes commented 7 years ago

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.

KLVN commented 7 years ago

:(

MichaelHepp commented 7 years ago

Are they threatening you with legal issues?

aschaeufler commented 7 years ago

Can you maybe explain more in detail what they have said?

ioncodes commented 7 years ago

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.

aschaeufler commented 7 years ago

Thank you for the fast reply. :) They should offer at least an offical read only api. :D

nborrmann commented 7 years ago

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.

ioncodes commented 7 years ago

Closing a repo means removing it or setting it to private.

nborrmann commented 7 years ago

Yeah, that won't solve anything. all the forks can still be found via google or github search.

KLVN commented 7 years ago

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

KLVN commented 7 years ago

Any news on this?

--- removed ---

ioncodes commented 7 years ago

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.

KLVN commented 7 years ago

I've been invited to Berlin and I will meet them there.

ioncodes commented 7 years ago

😂😂😂 Wasn't meant to be like a dick 😂

ioncodes commented 7 years ago

@anaseqal If you tell me why and who you are, yes.

ioncodes commented 7 years ago

@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

bebehei commented 7 years ago

I've been invited to Berlin and I will meet them there.

@ioncodes Any updates on here?

cpyix commented 6 years ago

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?

ioncodes commented 6 years ago

@cpyix We are allowed to use read endpoints. We need to wait for them to create a public API.

m7ariri commented 6 years ago

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?