These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE Technology Lab

 
  • Topic is locked indefinitely.
 

zKillboard.com

First post
Author
Squizz Caphinator
WiNGSPAN Delivery Network
#201 - 2013-04-09 13:50:23 UTC
DingoGS wrote:
I have a API Request,

Could you add a option to show estimated ISK Value of the Kill? That could open up many interesting analysis to be pulled from the API :)

Also, it seems the endTime tag is broken, or I'm formatting the DateTime badly (But it works for startTime tho)

Something I really liked about the old API (Epic one) was the "Mask" attribute, which was really good to select the information you want.


We may, or may not do this. Yup, that's completely uncommittal :)

Reason being we are trying to keep this particular API as close to CCP's API as possible by not adding any fields that CCP wouldn't include themselves. I'm not saying this is how it will always be, but that's just the reasoning we have for it today.

Various projects I enjoy putting my free time into:

https://zkillboard.com | https://evewho.com

Karbowiak
The League Of Unwanted Capsuleers
#202 - 2013-04-09 17:00:32 UTC
Squizz Caphinator wrote:
DingoGS wrote:
I have a API Request,

Could you add a option to show estimated ISK Value of the Kill? That could open up many interesting analysis to be pulled from the API :)

Also, it seems the endTime tag is broken, or I'm formatting the DateTime badly (But it works for startTime tho)

Something I really liked about the old API (Epic one) was the "Mask" attribute, which was really good to select the information you want.


We may, or may not do this. Yup, that's completely uncommittal :)

Reason being we are trying to keep this particular API as close to CCP's API as possible by not adding any fields that CCP wouldn't include themselves. I'm not saying this is how it will always be, but that's just the reasoning we have for it today.


The XML call for the zKB API, actually looks like the CCP API so much, you could fool Pheal into eating it without much modification (you'd need to alter the URL, that's it)

So lovely Lol
Squizz Caphinator
WiNGSPAN Delivery Network
#203 - 2013-04-10 14:29:14 UTC
We have finally made the code public:

https://github.com/EVE-KILL/zKillboard

Disclaimer: if it looks like crap code, we call that karbocode <3

Feel free to fork yourselves and have fun contributing!

Various projects I enjoy putting my free time into:

https://zkillboard.com | https://evewho.com

Karbowiak
The League Of Unwanted Capsuleers
#204 - 2013-04-10 14:37:49 UTC
Squizz Caphinator wrote:
We have finally made the code public:

https://github.com/EVE-KILL/zKillboard

Disclaimer: if it looks like crap code, we call that karbocode <3

Feel free to fork yourselves and have fun contributing!


Well, that escalated quickly..

Also, damn you CCP for now allowing images being embedded ! X
Captain Thunk
Ministry of War
Amarr Empire
#205 - 2013-04-10 14:44:32 UTC
Played around with the zKillboard feed XML and it's probably the widest ranging one I've encountered. It goes through PLs custom API parser with no modification which makes things nice and easy, it also allows for unusual requests of particular use to us due to its scope.
Karbowiak
The League Of Unwanted Capsuleers
#206 - 2013-04-10 14:48:09 UTC
Captain Thunk wrote:
Played around with the zKillboard feed XML and it's probably the widest ranging one I've encountered. It goes through PLs custom API parser with no modification which makes things nice and easy, it also allows for unusual requests of particular use to us due to its scope.


Did i read "We can use it to win fights, mehehe" ?

Sneaky PL is sneaky! Lol
Bagehi
Habitual Euthanasia
Pandemic Legion
#207 - 2013-04-10 15:05:47 UTC
Karbowiak wrote:
Captain Thunk wrote:
Played around with the zKillboard feed XML and it's probably the widest ranging one I've encountered. It goes through PLs custom API parser with no modification which makes things nice and easy, it also allows for unusual requests of particular use to us due to its scope.


Did i read "We can use it to win fights, mehehe" ?

Sneaky PL is sneaky! Lol

Killboards are fantastic tools to help you win. If you are just using it for chest beating, you are wasting their utility potential!
Karbowiak
The League Of Unwanted Capsuleers
#208 - 2013-04-10 15:15:25 UTC
Bagehi wrote:
Karbowiak wrote:
Captain Thunk wrote:
Played around with the zKillboard feed XML and it's probably the widest ranging one I've encountered. It goes through PLs custom API parser with no modification which makes things nice and easy, it also allows for unusual requests of particular use to us due to its scope.


Did i read "We can use it to win fights, mehehe" ?

Sneaky PL is sneaky! Lol

Killboards are fantastic tools to help you win. If you are just using it for chest beating, you are wasting their utility potential!


Stop making sense, my head can't handle it ! Cry
Allna
Aim High
SWAG Co
#209 - 2013-04-11 17:12:54 UTC
Squizz Caphinator wrote:
We have finally made the code public:

https://github.com/EVE-KILL/zKillboard

Disclaimer: if it looks like crap code, we call that karbocode <3

Feel free to fork yourselves and have fun contributing!



Heyo -- firstly, thanks for the awesomeness of releasing the code to the public to start tinkering with, much appreciated!

I got things up and running for the most part, and was able to successfully add a corp-level API key to my self-hosted copy, however it doesn't appear to be feeding (it lists no errors in the API info page, but also no date that it actually parsed anything).

I then tried posting a mail manually, and get unknown corp ID, unknown alliance name, and other "unknown" stuff which caused the mail to not post.

After a bit of digging in the database I see that zz_corporations and zz_alliances tables aren't populated with any data, and none of the included SQL's contain that information. If memory serves, EDK came with a 'data dump' from CCP that contained a lot of this information, and I think EDK just kind of "adds as it sees new alliances/corps" in a mail.

Am a bit stumped at how zKB handles this (not a PHP expert by any stretch of the imagination!), but I'm starting to wonder if I can just do a dump of my EDK tables for corps, alliances, etc, and munge the data to match the column layout for zKB and import.

Before going to that length though I figured I'd post and see if I was missing something stupid. :)

Thanks!
Karbowiak
The League Of Unwanted Capsuleers
#210 - 2013-04-11 18:18:18 UTC
First up, everyone has to use the Forgot Password feature ( https://zkillboard.com/forgotpassword/ ) since we/i changed the password hashing stuff, and autologin. So all old passwords are now invalid and won't get you anywhere. Sorry.

Second, lost of people have begun forking and contributing to zKB. Which is very much appreciated! thank you all so much <3

Allna wrote:
Squizz Caphinator wrote:
We have finally made the code public:

https://github.com/EVE-KILL/zKillboard

Disclaimer: if it looks like crap code, we call that karbocode <3

Feel free to fork yourselves and have fun contributing!



Heyo -- firstly, thanks for the awesomeness of releasing the code to the public to start tinkering with, much appreciated!

I got things up and running for the most part, and was able to successfully add a corp-level API key to my self-hosted copy, however it doesn't appear to be feeding (it lists no errors in the API info page, but also no date that it actually parsed anything).

I then tried posting a mail manually, and get unknown corp ID, unknown alliance name, and other "unknown" stuff which caused the mail to not post.

After a bit of digging in the database I see that zz_corporations and zz_alliances tables aren't populated with any data, and none of the included SQL's contain that information. If memory serves, EDK came with a 'data dump' from CCP that contained a lot of this information, and I think EDK just kind of "adds as it sees new alliances/corps" in a mail.

Am a bit stumped at how zKB handles this (not a PHP expert by any stretch of the imagination!), but I'm starting to wonder if I can just do a dump of my EDK tables for corps, alliances, etc, and munge the data to match the column layout for zKB and import.

Before going to that length though I figured I'd post and see if I was missing something stupid. :)

Thanks!


Atm zKB uses a multitude of Cronjobs to fill up tables, if you look at util/cron.php you can see multiple functions which are to be called from a cronjob. Some parse kills, some fill up the char/ally/corp tables with info, others fetches from the API etc. etc.
It's a clusterfuck of commands atm.

And no, you can't take data from EDK and directly into zKB, wont work at all P

If you need some more direct help, do come by IRC and chat with us.

THAT SAID, zKB atm is very beta - and should obv. be treated as such Smile
Allna
Aim High
SWAG Co
#211 - 2013-04-11 18:51:40 UTC
Karbowiak wrote:

Atm zKB uses a multitude of Cronjobs to fill up tables, if you look at util/cron.php you can see multiple functions which are to be called from a cronjob. Some parse kills, some fill up the char/ally/corp tables with info, others fetches from the API etc. etc.
It's a clusterfuck of commands atm.

And no, you can't take data from EDK and directly into zKB, wont work at all P

If you need some more direct help, do come by IRC and chat with us.

THAT SAID, zKB atm is very beta - and should obv. be treated as such Smile



Indeed, am definitely only testing now, in fact our purpose for deploying was just to stay "current" with what the killboard community is up to in anticipation of someday going live with zKB, and also to help report bugs/problems/whatever. When I was talking about feeding the data from EDK, I meant actually after changing the data to be correct for the columns in zKB, not just a 1-to-1 copy. :)

That said, I did look at cron.php as well as the cron jobs that are laid out in the README, but didn't realize it would be feeding all that static data in through the cron jobs. I'll hack away a bit and see what I can figure out. Thanks for the response, much appreciated!

Karbowiak
The League Of Unwanted Capsuleers
#212 - 2013-04-11 18:58:35 UTC
Allna wrote:
Karbowiak wrote:

Atm zKB uses a multitude of Cronjobs to fill up tables, if you look at util/cron.php you can see multiple functions which are to be called from a cronjob. Some parse kills, some fill up the char/ally/corp tables with info, others fetches from the API etc. etc.
It's a clusterfuck of commands atm.

And no, you can't take data from EDK and directly into zKB, wont work at all P

If you need some more direct help, do come by IRC and chat with us.

THAT SAID, zKB atm is very beta - and should obv. be treated as such Smile



Indeed, am definitely only testing now, in fact our purpose for deploying was just to stay "current" with what the killboard community is up to in anticipation of someday going live with zKB, and also to help report bugs/problems/whatever. When I was talking about feeding the data from EDK, I meant actually after changing the data to be correct for the columns in zKB, not just a 1-to-1 copy. :)

That said, I did look at cron.php as well as the cron jobs that are laid out in the README, but didn't realize it would be feeding all that static data in through the cron jobs. I'll hack away a bit and see what I can figure out. Thanks for the response, much appreciated!



Ah, i must have misunderstood what you ment then, appoligies Smile
The easiest way to actually fill data into your board, is to fire up stomp, and leave it running for a while. Since we push out new mails continuously.

Anyway, keep up the good work Smile
DingoGS
We are not bad. Just unlucky
#213 - 2013-04-14 15:26:55 UTC
Squizz Caphinator wrote:
DingoGS wrote:
I have a API Request,

Could you add a option to show estimated ISK Value of the Kill? That could open up many interesting analysis to be pulled from the API :)

Also, it seems the endTime tag is broken, or I'm formatting the DateTime badly (But it works for startTime tho)

Something I really liked about the old API (Epic one) was the "Mask" attribute, which was really good to select the information you want.


We may, or may not do this. Yup, that's completely uncommittal :)

Reason being we are trying to keep this particular API as close to CCP's API as possible by not adding any fields that CCP wouldn't include themselves. I'm not saying this is how it will always be, but that's just the reasoning we have for it today.


I hope you reconsider this, ISK value adds a whole new dimension of analysis for kill data, which is also a pretty damn interesting dimension.

My current project it's http://raynor.cl/eve/displayResults.php?brId=3 (Doctoring BRs) and without the ISK input it looses sense so fast (Who cares how many rifters died, I want to know how I did on the ISK war!)

So far I'm still using the old API as it provides the ISK field :(
Karbowiak
The League Of Unwanted Capsuleers
#214 - 2013-04-14 15:54:16 UTC
DingoGS wrote:
Squizz Caphinator wrote:
DingoGS wrote:
I have a API Request,

Could you add a option to show estimated ISK Value of the Kill? That could open up many interesting analysis to be pulled from the API :)

Also, it seems the endTime tag is broken, or I'm formatting the DateTime badly (But it works for startTime tho)

Something I really liked about the old API (Epic one) was the "Mask" attribute, which was really good to select the information you want.


We may, or may not do this. Yup, that's completely uncommittal :)

Reason being we are trying to keep this particular API as close to CCP's API as possible by not adding any fields that CCP wouldn't include themselves. I'm not saying this is how it will always be, but that's just the reasoning we have for it today.


I hope you reconsider this, ISK value adds a whole new dimension of analysis for kill data, which is also a pretty damn interesting dimension.

My current project it's http://raynor.cl/eve/displayResults.php?brId=3 (Doctoring BRs) and without the ISK input it looses sense so fast (Who cares how many rifters died, I want to know how I did on the ISK war!)

So far I'm still using the old API as it provides the ISK field :(


If you want to use it for Battle Reports, you should wait doing too much, since we'll be redoing the entire relatedKills page, to work much like BRDoc.

But doing that involves us making a JSON API that the JS for the related page loads. You could just load the same JSON and do your stuff to it.
DingoGS
We are not bad. Just unlucky
#215 - 2013-04-14 15:57:12 UTC
Karbowiak wrote:
If you want to use it for Battle Reports, you should wait doing too much, since we'll be redoing the entire relatedKills page, to work much like BRDoc.

But doing that involves us making a JSON API that the JS for the related page loads. You could just load the same JSON and do your stuff to it.


All I'm saying it's that ISK it's a pretty interesting dimension and I (and I bet more people) would love having it on the API, as it opens a whole new dimension for analysis.
Squizz Caphinator
WiNGSPAN Delivery Network
#216 - 2013-04-16 21:21:21 UTC
We are progressing right along and getting a lot done. If anyone finds anything wrong or would like to request an enhancement please stop by and make an Issue of it!

https://github.com/EVE-KILL/zKillboard/issues

Various projects I enjoy putting my free time into:

https://zkillboard.com | https://evewho.com

Poetic Stanziel
The Scope
Gallente Federation
#217 - 2013-04-16 21:29:25 UTC
For people that might want to ease up on the API hits every 60 seconds ... have you thought about releasing a daily XML of a complete days worth of KMs (API-only)? I could download on May 10, for instance, the May 9 killmail file in XML format.

(You could also offer a JSON version for those people that prefer to work in that format.)
Squizz Caphinator
WiNGSPAN Delivery Network
#218 - 2013-04-17 14:32:02 UTC
Poetic Stanziel wrote:
For people that might want to ease up on the API hits every 60 seconds ... have you thought about releasing a daily XML of a complete days worth of KMs (API-only)? I could download on May 10, for instance, the May 9 killmail file in XML format.

(You could also offer a JSON version for those people that prefer to work in that format.)


We did some discussion on your request and decided that between the API and Stomp we already have the tools in place for everyone to get ahold of as many killmails as they like.

If you aren't familiar with Stomp, check the README section on zkb's github page.

Various projects I enjoy putting my free time into:

https://zkillboard.com | https://evewho.com

Shellac Brookdale
Cutting Edge Incorporated
RAZOR Alliance
#219 - 2013-04-17 19:11:37 UTC
Squizz Caphinator wrote:

We did some discussion on your request and decided that between the API and Stomp we already have the tools in place for everyone to get ahold of as many killmails as they like.


Wrote a simple python client one or two weeks ago to test the stomp push. It seems to work fine, but got killmails aged years ago which I'm not interested in. How can I only consume kms as they happen?
Poetic Stanziel
The Scope
Gallente Federation
#220 - 2013-04-17 19:18:25 UTC
Squizz Caphinator wrote:
If you aren't familiar with Stomp, check the README section on zkb's github page.
I have no idea what STOMP is (other than being a PHP module), and the following description doesn't say much about its purpose or what functionality it is providing:

https://github.com/EVE-KILL/zKillboard#stomp