It might have been possible for an API endpoint to exist when Team Analytics where a thing. Now that they’ve been deprecated/discontinued, I’m not sure. Maybe poking between pages with DevTools logging for XHR requests might find that endpoint.
Each container already has PROJECT_REMIX_CHAIN as an environment variable which is a list of project ID’s that make up a project’s ancestry. It’s not the same thing but it’s similar. It’s also not shown in the .env file but it is accessiable from the terminal.
I don’t think you understand how storage of such information works, what you see in the app status is data collected from another program (containerd or docker I think), storage of remix count would be stored in a database, information is collected from the database and served in an API, the client (end-user, us) will fetch that information and display such information in the proper area.
I thought so too, but no count is being made when the Remix button is clicked. The only requests that are being made is the link to the new project. Once you’re in a new project, another request is made to the project that was remixed to fetch its contents. Maybe for analytics, they might be using a third-party plugin instead of the Glitch API?
Yeah, I guess it would be pretty hard to use API and third-party tools/software may be pretty inneficient. I still think it would be nice for some form of remix counter.