| Pages: [1] :: one page |
|
|
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
velocity7
   |
Posted - 2007.08.27 02:47:00 -
[1]
Edited by: velocity7 on 27/08/2007 02:48:46
To my understanding, there was talk among the developers about having killmails being brought into their own section rather than having CONCORD EVE mail the details to the player. I was just thinking that, with the limited-use API key, would it be possible to incorporate the killmails into there as well? Basically, a client would be able to queue up the kills/losses of a player and grab all necessary information from it.
For an PHP killboard system (which we all know and commonly use), this could be extended so a user can register with that killboard, enter his limited-use API key, and from there the killboard can grab killboard data, cache it, and check for new data (using an extra parameter with the request) every once so often. Advantage with this is that people don't have to go and post up killmails any longer; the PHP killboards will be responsible for that and grab the data directly from EVE.
Of course, there is the issue of killboards intentionally designed to queue data very very fast (aka, DDoSing?), so it's probably also a good idea to have some sort of limit; kinda like, can only update new data once every 5 minutes, can only grab all killboard data once every 60 minutes, and so on.
As for what information will be displayed by the killboard, that is up to whoever programs the killboard PHP code. I'm merely suggesting a possible alternative to posting killmails onto the killboards. :)
|
velocity7
|
Posted - 2007.08.27 15:24:00 -
[2]
bump
|
Ricky1989
Curse Alliance
|
Posted - 2007.08.27 17:03:00 -
[3]
I like this idea.
|
Gus Morgan
Genos Occidere
|
Posted - 2007.08.27 20:57:00 -
[4]
yes please.
|
Torndeco
Minmatar
Kingpins
|
Posted - 2007.08.27 22:05:00 -
[5]
Edited by: Torndeco on 27/08/2007 22:09:07
Love the idea.
Small minor implenmentation suggestion
Just add it to current full / limited api as it is.
API could log last killmails in last 24 hours.
Could get eve servers database scanned every dt to remove old killmails that are over 24 hours old.
And have 3rd party client update killmails to the board
i.e
eve mon checks every hour i believe (allow user to force and update so can get kill straight away)
would check every hour & notice new killmail
then it would send the killmail to the server hosting the killboard in question
also would allow 3rd party for clients to remove your lost modules if u lost a ship. For those corps that like secrets, and yes u know how u are 
Also no point having killboard constantly checking for new kills, if the user isnt online. And if there are online they can update via killmails or from 3rd party app that is prob running already. |
ghosttr
Amarr
ARK-CORP
FREGE Alliance
|
Posted - 2007.08.27 22:30:00 -
[6]
I thick CCP should keep a reasonable record of them because many people never delete thier mails anyways. It would also be nice if the new marketing stuff they are doing could also be made an api to make prices correct, and they could be used together to provide accurate stats.
.
Do not read this thread!!!
|
Miss KillSome
Caldari
School of Applied Knowledge
|
Posted - 2007.08.28 07:49:00 -
[7]
or just give us another button like export on market, to gather killmail to API queue which is then shifted to killboard, when killboard asks for it..
|
Jack Paladin
Gladiators of Rage
Chaos Incarnate.
|
Posted - 2007.08.28 11:29:00 -
[8]
I support this idea. It can be helpful for non-pvp corps to keep statistic and what the members are realy doing. Like spy alt killed in 0.0. Also no screens woul be needed. And pvp corps would have their ranking system that is not manipulated. After all nearly all 0.0 entities use already killboard same with empire corps. So this would be very nice improvement widely used. |
velocity7
|
Posted - 2007.08.28 15:06:00 -
[9]
Edited by: velocity7 on 28/08/2007 15:12:24
I'm more curious as to what the killboard programmers think of the idea, actually. :)
I would think that assisted kills (e.g., you didn't get the final blow) could also be added into the API in this way... of course, up to killboard systems to figure out which kills are the same or not. Maybe create a unique kill ID# for each kill? (that way, if three people get a kill on someone, and they all have the same kill ID# in the EVE API, the killboard can filter that out)
|
Atasy Huopian
|
Posted - 2007.08.28 15:32:00 -
[10]
This is an awesome idea. I really hope this makes it to the table.
|
|
|
Turix
Interstellar eXodus
R0ADKILL
|
Posted - 2007.08.29 00:00:00 -
[11]
THe main problem i see if backlogging to killmails.
I know for a fact theres a good few people who would hate to start from scratch with their kill stats, so maybe the first couple of weeks of running it allows killboards to grab all kills for a character during say downtime, so the DB server doesnt get nailed?
But i basically love the idea.
| Image Hosting | My Movies | |
Stephannus Calimben
|
Posted - 2007.08.29 08:47:00 -
[12]
maybe it'd be easier to just have an option in the "my character" tab of the website where you can set a killboard url to have your kills uploaded to, so that when you get a new kill it sends an update to your killboard, or maybe just have the guts for the killboard itself be part of the api, so that rather than having killboards repeatedly hit the server for updates, it's only hit when someone views the killboard
(written at 2 in the morning, may make a minimum of sense)
|
velocity7
|
Posted - 2007.08.31 14:48:00 -
[13]
bump
|
TomParad0x
Caldari
Caldari Provisions
|
Posted - 2007.08.31 19:10:00 -
[14]
Edited by: TomParad0x on 31/08/2007 19:12:28
This would be great. If implemented, and the killboard programmers jumped on, it would make getting accurate kill / lose mails easy (/easier) for alliances / corps who like to keep track.
/Signed.
edit: Also, if they do implement this, please provide a way to output the text and XML form of the killmail - this way parsing the killmail can be done via XML (In the form of say, <victum name='someonme' ship='something' corp='somecorp' etc>) for quite a bit easier parsing.
|
xCyno Girlx
|
Posted - 2007.09.01 19:47:00 -
[15]
/Signed
Having this would be great for anyone having a killboard.
Each day leader of a corp or alliance can see where they stand where they need to improve, and not have to worry about someone not posting killmails gimping the stats. For the good for the bad. Most leaders want accuracy. Right now because of people not wanting to post lossmail you cant see where you stand.
|
Gane Green
Gallente
Digital Foundry
|
Posted - 2007.09.01 19:47:00 -
[16]
Damn alt hehe that was me :)
|
Jurgen Cartis
Caldari
Interstellar Corporation of Exploration
|
Posted - 2007.09.02 07:13:00 -
[17]
Sounds good. Still want the mails themselves though, preferably delayed so they aren't lagbombs in your inbox.
--------------------------------------------------
ICE Blueprint Sales
FIRST!! -Yipsilanti
Pfft. Never such a thing as a "last chance". ;) -Rauth |
Una D
Ex Coelis
Hydra Alliance
|
Posted - 2007.09.02 14:18:00 -
[18]
This would be great thing just to lower the amount of lag. Just send the info to server that can than take it's time posting it to API and perhaps send an mail to with say 12 hours delay or so.
|
Erotic Irony
0bsession
|
Posted - 2007.09.11 01:51:00 -
[19]
hey guys what's going on this thread
___
Support Killmail Overhaul
|
Blazde
4S Corporation
Morsus Mihi
|
Posted - 2007.09.11 02:43:00 -
[20]
Garthagk said on eve-tv he was looking at killmails, hopefully this suggestion and my previous ones get implemented.
_
|
|
|
velocity7
|
Posted - 2007.09.11 18:40:00 -
[21]
 Originally by: CCP Chronotis
There is intention to add in API access for the kill log in the future but it is not part of Kali 3 and will be developed separately to hopefully be added at some future point.
Better than nothing! :)
|
Tenshiin
|
Posted - 2007.10.06 14:53:00 -
[22]
Edited by: Tenshiin on 06/10/2007 14:57:26
I don't think this is a viable option for CCP. Consider this scenario:
Killboard X has 300 users registered with their API key.
Say Killboard X updates its killboard cache every hour.
Killboard X Effectively needs to connect 300 times, one time per user.
Now take into account all the OTHER killboards, and you have a fine DDOS system implemented.
The only solution I see that would be viable is something as presented in this topic. That is, a kill-tracker implemented and run by CCP.
|
Tonto Auri
|
Posted - 2007.10.06 15:24:00 -
[23]
Originally by: Tenshiin
Killboard X has 300 users registered with their API key.
Say Killboard X updates its killboard cache every hour.
Killboard X Effectively needs to connect 300 times, one time per user.
Now take into account all the OTHER killboards, and you have a fine DDOS system implemented.
This forum have some millions of registered users. At any given time, about 300 of 'em browsing forum, polling (roughly) 3 pages in minute each.
You still think that this is DDoS ?
Speaking about polling all 300 accounts every hour, there's a much more load-friendly way than stupidly re-request kills for each user.
It is about including already taken kills in request for next kills.
Say, You have last kill Nr 101 for acc 1, 102 for Acc 2 and 102 (again) for Acc 3, yep, two men involved in last kill. (one killing another or they both killing someone else - doesn't matter)
You start polling new kills.
Request is as follows:
GiveMeKills
ID=1
Key=....
SeeAfter=101
You'll get kills 105,112,115
Well, You see that there's some holes, but ok... Next request:
GiveMeKills
ID=2
Key=...
SeeAfter=102
Exclude=105,112,115
You'll get two kills - 103 and 104. Good news, we have filled the gap 102-105.
Let we try to get last kills.
GiveMeKills
ID=3
Key=...
SeeAfter=105
Exclude=112,115
See?
--
Thanks CCP for cu<end of sig> |
Tenshiin
|
Posted - 2007.10.06 16:13:00 -
[24]
I see your point, but that's still quite a load of requests to be made one after another.
Surely there would be a more efficient solution.
Still, an API would be pretty nice for us players, notwithstanding the load issue (or non-issue).
|
Xealot
ECP Rogues
The Reckoning.
|
Posted - 2007.12.06 20:38:00 -
[25]
I hear directors can see all corp members kills/losses in Trinity,
if this is true, then just make that info exportable so that killboards only need an API key from a corp director, or from each director/CEO per corp in an alliance.
Perfect way to get all kills/losses with 100% accuracy |
achoura
|
Posted - 2007.12.07 00:20:00 -
[26]
Edited by: achoura on 07/12/2007 00:20:34
Originally by: Xealot
I hear directors can see all corp members kills/losses in Trinity,
if this is true, then just make that info exportable so that killboards only need an API key from a corp director, or from each director/CEO per corp in an alliance.
Perfect way to get all kills/losses with 100% accuracy
Genius A corp api exclusivly for killmails would be gold 
|
SN3263827
The Black Rabbits
The Gurlstas Associates
|
Posted - 2007.12.07 00:26:00 -
[27]
Threadomancy, and to post an "idea" that the Devs have already said is being worked on for a future update no less!
Fail++
_____________________________________________
My Wishlist
|
|
|
| |
|
| Pages: [1] :: one page |
| First page | Previous page | Next page | Last page |