When loading the content (after a paste or by ID) the site does not indicate to the user it's busy processing the request. A loading cue or animation would be great!

Invalid report IDs (not found) are rendering an empty table. Instead they should redirect to root with a notification, or render a message akin to "not found".

Match <url=infotype://13\d\d/.+?>(.+?)</url> (not actually tested); group 1 is the character's name.

Remember to update the instructions in Welcome screen.

Some browsers and systems might not recognize or not support pasting on the window. For these and other cases it might be a good idea to have a "compatible mode" where we display a textarea to have content pasted in.

What's your idea?

Display loading states to summary and table.

Why do you think it's a good idea?

Looks cool and cues the user that something is happening while we have no or too few data.

Right now it's possible to post a huge payload to paste creation endpoint and no validation would take place. There should be a limit and an appropriate message on the front-end.

How can I change the default port from 8080 to something else?

You know, responsive design.

• Possibly smaller font-size.
• Smaller paddings in the body.
• Hide columns in the table.

I am gonna check this out but.. fantabulous.. if this is still being maintained this is awesome.

Copy/paste Jita local to see what I mean.

Also let the user know the paste has be truncated to avoid confusion.

• Add credit to ESI and zKillboard
• Fix legal notice mentioning zKillboard

See https://github.com/bvaughn/react-virtualized

• Save a history of visited reports
• Add a side panel that shows this history
• List date and time of the report and also stats such as number of characters

Given the time it takes to fetch all the information it would be helpful to add a cache layer on top of either the App's state or the API response.

I'm leaning into caching the state, so the components are free to revalidate the data.

As you can see here -- easylist/easylist#1529 -- we have a problem with Ad Blockers blocking the affiliations endpoint of ESI. It was supposed to be fixed but it's still an issue. I hope to have it sorted out soon.

In the meantime it would be great to have a banner explaining the situation.

Plus how members of each are present in the paste.

Since the API is publicly writable it should have some safety measures in place.

• https://github.com/didip/tollbooth

Updates are not available until you clear your browser's cache.

There should be an appropriate message if no names were derived from CTRL+V.

Help panel needs a review, with the perspective of the user needing actual help (information is secondary).

With a single call for translating names to IDs: https://esi.tech.ccp.is/latest/#!/Universe/post_universe_ids

Suggested settings controls:

• Switch color scheme (#32).
• Compatible mode (#50).
• Toggle between extending current report or creating new report on Paste.

What were you doing?

I loaded a report and then clicked on New Report to change the page.

What did you expect to happen?

I expected the remote requests of the report to halt after I changed the page.

What happened instead?

They continued, needlessly.

Support dscan format on paste.

Looking into the data I noticed the API is failing at detecting a chat transcript when there's no character links and defaulting to members list format. We should be more strict when detecting the paste content format, for instance, we could follow the game's policy on character names to detect an invalid paste:

Valid player character names:

• Must be at least 3 characters.
• Cannot exceed 37 characters. (This limit includes one space between the characters name and family name.)
  • Name cannot exceed 24 characters. The name can include a middle name separated by a space.
  • Family name cannot exceed 12 characters.
• May contain the characters A-Z, a-z, 0-9, hyphen-minus and single quotation. (Corporation names may also include the dot character.)
• Space, hyphen-minus and single quotation characters are not allowed as the first or last character in a name.
• Must be unique.

— https://community.eveonline.com/support/policies/naming-policy-en/

https://developers.eveonline.com/blog/article/sso-to-authenticated-calls

Hi, first of all: great tool! worked fine until now. i can get no results - nothing is displayed. there's is also nothing shown, when i click through my history.

Regards!

We could loop over the killmails and calculate the average length of the attackers property.

Sample: https://zkillboard.com/api/characterID/95036967/kills/

• Share
• New Report
• History

Consider adding cues to the UI to suggest the support for keyboard shortcuts. Also list them in the Help panel (#36).

1. Display player count (somehow) in the affiliation summary panels.
2. When there are few items we could inline corporation and alliances names.
3. When there are a lot of items we should move the names to a tooltip.

You can get corporation and alliance information from the zKillboard API instead of having to make 3 extra requests to ESI (affiliation, corporation, and alliance).

As of right now, the tool doesn't appear to be fetching corp/alliance IDs/info.

1. Generate an unique ID for each paste
2. Append it to the URL
3. Save both ID and paste content into some back-end (Firebase?)
4. Save a history of pastes for current user (browser storage, cookies, etc.)
5. Load the paste content when visiting a URL with an existing ID

A useful piece of information to see would be the "Top Ship" field from zKill for searched characters. It would also be possible to link to a zKill result showing the characters losses for this ship type, allowing you to quickly check for an expected fit.

Mockup:
https://i.imgur.com/AaRfmao.png

See #35. Like that, but for Q&A.

• What is localthreat?
• How does it work?
• Does it cost anything?
• Does it collect my information?
• I like it.
• I have other questions.

Example:

• Lords Servant
• Lord's Servant

Both searches return the same result: IDs for both characters.

As to increase browser compatibility and make it more resilient to changes:

1. Wrap img in div for styling
2. Rename CSS classes with hierarchy (BEM style)

Something changed recently on zKill's side of things that's unearthed a bit of an issue in the code here. The links to zKill being generated by localthreat are generating errors because they're missing trailing slashes in the URLs.

I haven't been able to test it, but tweaking the getEntityURL code in entity.js should probably help fix the problem (the code below has the slashes added in):

const getEntityURL = (type, id) => {
  switch (type) {
    case "char":
      return `https://zkillboard.com/character/${id}/`;
    case "ally":
      return `https://zkillboard.com/alliance/${id}/`;
    case "corp":
      return `https://zkillboard.com/corporation/${id}/`;
    case "ship":
      return `https://zkillboard.com/character/${id[1]}/shipTypeID/${id[0]}/`;
  }
};

Apologies if this is a known issue or something local to me, but about a week ago I became unable to paste into the page, even though I verified the clipboard held the pilot list. No-adblocker. Incognito mode doesn't work, either. Tried Chrome and Edge.

A communication channel with the site users would be helpful. Things like known issues, change log and what not could be posted over there and help foster the community.

The panel itself can be a drawer, pretty much like the History panel but on the left site.

Probably the sorting mechanism is causing each <Row /> to mount twice.

Change it to accept a post to /reports with the data. There you go https://github.com/matoous/go-nanoid

zKillboard has an aggressive throttling in place in which I can only make a single request every second. Right now I have a regular interval of 1 second, where I dispatch a request on very tick. The problem is when a request takes too long the next one might come too soon and then it gets throttled.

The pattern I've seen is that the first few dozen requests takes about 50ms. But then this time begins to increase with each request, taking up to 1–1.5s. That's when the cascading failures start. Once a request takes more than the, all the following ones fail as well.

• One option is to put 1 second between requests, instead of dispatching in a regular interval of 1 second. i.e. dispatch a request, wait for it to finish, dispatch the next one. But this would really ramp up the time it takes to fill the stats.
• Another option is to apply a dynamic interval between them, increasing as the requests take longer and decreasing otherwise.