---
title: "Discussion on \"Building a game server tracker: what I learned exposing a public JSON API\" | Hashnode"
description: "Discussion on \"Building a game server tracker: what I learned exposing a public JSON API\". Lessons from shipping a public JSON API for a Lineage 2 server tracker: mysql2 date gotchas, CORS decisions, and why giving data away wins."
url: "https://hashnode.com/posts/building-a-game-server-tracker-what-i-learned-exposing-a-public-json-api/6a9ce2bec282d735560bbc6a"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Building a game server tracker: what I learned exposing a public JSON API](https://l2calendar.hashnode.dev/building-a-game-server-tracker-what-i-learned-exposing-a-public-json-api?utm_source=hashnode&utm_medium=feed)

Lessons from shipping a public JSON API for a Lineage 2 server tracker: mysql2 date gotchas, CORS decisions, and why giving data away wins.

Sep 6 · 4 min read · l2calendar.hashnode.dev  
Read the article

-   [#mysql](https://hashnode.com/tag/mysql)
-   [#nodejs](https://hashnode.com/tag/nodejs)
-   [#gamedev](https://hashnode.com/tag/gamedev)
-   [#cors](https://hashnode.com/tag/cors)

## Written by

[Dreiev](https://hashnode.com/@dreiev)

@dreiev · Barcelona, Spain

  
[View profile](https://hashnode.com/@dreiev)

I code since I had 13 years old, now I have 44 and hope to continue coding for a very long time.

Love coding, security, performance, blockchain, IA, gaming developement

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
