We are currently experiencing payment processing issues. Our team is working to resolve the problem as quickly as possible. Thank you for your patience
General API Questions
0
Okay, so after about an hour of looking through Google searches and forum posts, I finally found the mention of the API being a possibility here: link.
Now, Jacob mentions that people should email him at jacob@fakku.net if they are interested... but I've never really liked this whole private system when dealing with such things. In my opinion, people should really be more open about testing APIs and such, especially based on the amount of people interested, if that idea is too absurd I guess this thread can be locked or taken down.
So with that basic rambling out of the way, I do have some general questions I (and probably some others) would like answered about this:
1. What languages will it be available in?
Will there be separate APIs for say PHP or JAVA, or will it be based on HTTP requests like tumblr's API? I would assume either way that the calls would return an object, preferably JSON for convenience sake.
2. Will OAuth keys be required? If so, for what requests?
This also counts for just API keys in general. If there's anything for users' accounts or posting I would assume there would be OAuth requirements, but for things like getting a recent list of uploads I wouldn't think it would be necessary (then again I don't know to what extent Fakku! wants to keep data secure).
3. Will User info be accessible?
This would just be basic things like reputation or amount of forum posts, but could possibly be bold enough to extend to lists of favorites (or at the farthest extreme actual comments on manga)
4. Will there be a call restriction?
A lot of APIs do this and I find it rather annoying to be honest, but I can see why they would have it. An API does extend the user market and thus the workload to whatever server hosts it, but if an app were to be popular enough to constantly hit the cap on this sort of thing it would become an issue (of course you could always have a system of extending it for exceptions or a fee).
Those are just my general questions, other can chime in if they want. If this post is breaking any rule (I'm fairly sure it isn't though it may be a double post) I'd appreciate someone making me aware, but I don't think I'd care too much if this is locked (whenever I actually get to developing what I was planning I might actually be in the mood for emailing people).
Now, Jacob mentions that people should email him at jacob@fakku.net if they are interested... but I've never really liked this whole private system when dealing with such things. In my opinion, people should really be more open about testing APIs and such, especially based on the amount of people interested, if that idea is too absurd I guess this thread can be locked or taken down.
So with that basic rambling out of the way, I do have some general questions I (and probably some others) would like answered about this:
1. What languages will it be available in?
Will there be separate APIs for say PHP or JAVA, or will it be based on HTTP requests like tumblr's API? I would assume either way that the calls would return an object, preferably JSON for convenience sake.
2. Will OAuth keys be required? If so, for what requests?
This also counts for just API keys in general. If there's anything for users' accounts or posting I would assume there would be OAuth requirements, but for things like getting a recent list of uploads I wouldn't think it would be necessary (then again I don't know to what extent Fakku! wants to keep data secure).
3. Will User info be accessible?
This would just be basic things like reputation or amount of forum posts, but could possibly be bold enough to extend to lists of favorites (or at the farthest extreme actual comments on manga)
4. Will there be a call restriction?
A lot of APIs do this and I find it rather annoying to be honest, but I can see why they would have it. An API does extend the user market and thus the workload to whatever server hosts it, but if an app were to be popular enough to constantly hit the cap on this sort of thing it would become an issue (of course you could always have a system of extending it for exceptions or a fee).
Those are just my general questions, other can chime in if they want. If this post is breaking any rule (I'm fairly sure it isn't though it may be a double post) I'd appreciate someone making me aware, but I don't think I'd care too much if this is locked (whenever I actually get to developing what I was planning I might actually be in the mood for emailing people).
0
waterflame
FAKKUDL.NET
xeonexodus wrote...
Okay, so after about an hour of looking through Google searches and forum posts, I finally found the mention of the API being a possibility here: link -snip-As I am not Jacob I can't provide you with exact answers but...
1. What languages will it be available in?
There github has several SDK(Javascript, python, and php) but the API is HTTP based and returns JSON.
2. Will OAuth keys be required? If so, for what requests?
From what I've looked through it's all public info so no auth needed.
3. Will User info be accessible?
Everything on there public profile is able to be called by the API.
4. Will there be a call restriction?
An over call restriction I don't think is set(I didn't see it anywhere I've read through) but I remember reading somewhere that there is a limit on return(10 pages of content I think..) I think this is mostly for doujin/manga search's but may also be for forum post searches.
As I am not Jacob I can't provide you with exact answers but...
0
So it shouldn't be too hard to build an application on it (since it's like every other api ever), that's nice.
I was actually thinking of making an embedded version of the manga viewer, for posts and such on a social network type thing (my main project). Once I get to that point an API like this would be the best possible solution so I look forward to it.
I was actually thinking of making an embedded version of the manga viewer, for posts and such on a social network type thing (my main project). Once I get to that point an API like this would be the best possible solution so I look forward to it.
0
It returns data through JSON, if your language understands JSON you should be fine. The rest of your question is in the main page of the API.
Cheers,
Cheers,
0
I"m trying to make a mobile webapp using angular.js, polymer and such. I'm getting a Cross-origin-resource-sharing error.
Is there anyway around this, or any chance of CORS being enabled?
No 'Access-Control-Allow-Origin' header is present on the requested resource
Is there anyway around this, or any chance of CORS being enabled?
0
_yuri wrote...
I"m trying to make a mobile webapp using angular.js, polymer and such. I'm getting a Cross-origin-resource-sharing error.No 'Access-Control-Allow-Origin' header is present on the requested resource
Is there anyway around this, or any chance of CORS being enabled?
Good catch! This has been fixed.
0
Well to be honest, I'm not that familiar with HTTP Requests, JSON and the WWW in its whole. So I'm having some problems using the Fakku API, as I need to always add header information. If I just wget for example api.fakku.net, I just get an 403 access denied error. If I wget with for example a firefox header, I get 200 OK and can load the site just fine. I've the same problem using any program language I tested so far. Opening a HTTP-Stream seems to be not enough, I've to always add a legal and known browser header to get access.
So here I'm wondering whether this is intentionally that way or not.
So here I'm wondering whether this is intentionally that way or not.
0
Is that...dicks?
In the header of the response object, there is a dicks field...and its set US.
{ date: 'Wed, 15 Oct 2014 17:24:30 GM
'content-type': 'application/json',
'content-length': '8653',
connection: 'keep-alive',
'set-cookie': [ '__cfduid=d10c1706f; HttpOnly' ],
'access-control-allow-origin': '*',
'accept-ranges': 'bytes',
'x-varnish': '848214440 848208284',
age: '33',
via: '1.1 varnish',
'x-cache': 'HIT',
dicks: 'US', <-----------------------------hahaha WHAT IS THIS for?
server: 'cloudflare-nginx',
'cf-ray': '179db5eb6fa80719-SJC' }
also where's the mono font :(
In the header of the response object, there is a dicks field...and its set US.
{ date: 'Wed, 15 Oct 2014 17:24:30 GM
'content-type': 'application/json',
'content-length': '8653',
connection: 'keep-alive',
'set-cookie': [ '__cfduid=d10c1706f; HttpOnly' ],
'access-control-allow-origin': '*',
'accept-ranges': 'bytes',
'x-varnish': '848214440 848208284',
age: '33',
via: '1.1 varnish',
'x-cache': 'HIT',
dicks: 'US', <-----------------------------hahaha WHAT IS THIS for?
server: 'cloudflare-nginx',
'cf-ray': '179db5eb6fa80719-SJC' }
also where's the mono font :(