Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jodel is not happy about this #39

Open
ioncodes opened this issue Jun 24, 2017 · 19 comments
Open

Jodel is not happy about this #39

ioncodes opened this issue Jun 24, 2017 · 19 comments

Comments

@ioncodes
Copy link
Contributor

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
Copy link

KLVN commented Jun 26, 2017

:(

@MichaelHepp
Copy link

Are they threatening you with legal issues?

@aschaeufler
Copy link

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

@ioncodes
Copy link
Contributor Author

ioncodes commented Jul 3, 2017

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
Copy link

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

@nborrmann
Copy link
Owner

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
Copy link
Contributor Author

ioncodes commented Jul 4, 2017

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

@nborrmann
Copy link
Owner

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

@KLVN
Copy link

KLVN commented Jul 4, 2017

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
Copy link

KLVN commented Jul 11, 2017

Any news on this?

--- removed ---

@ioncodes
Copy link
Contributor Author

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
Copy link

KLVN commented Jul 11, 2017

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

@ioncodes
Copy link
Contributor Author

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

@ioncodes
Copy link
Contributor Author

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

@ioncodes
Copy link
Contributor Author

@bebehei
Copy link

bebehei commented Aug 13, 2017

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

@ioncodes Any updates on here?

@cpyix
Copy link

cpyix commented Mar 26, 2018

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
Copy link
Contributor Author

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

@m7ariri
Copy link

m7ariri commented Apr 9, 2018

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants