Open yuberee opened 6 months ago
Lets build a checklist of the data you want to query?
Sure, let me know if there's an end point for some of these already:
News
[x] Access to all news feeds (https://sbox.game/news Both official and community news)
[x] Access to news from a single org
[x] Access to news from a single package
Insights (These might require a form of authentification)
[ ] Access to the errors page (https://sbox.game/fish/deathcard/errors)
[ ] Access to the sessions page (https://sbox.game/fish/deathcard/sessions)
Stats
[ ] Access to the stats
[ ] Access to the leaderboards
[ ] Access to the achievements
Analytics
[ ] Hook this up and make it public https://sbox.game/fish/~analytics
That's it for now, this is how I have it set up: https://github.com/Small-Fish-Dev/Fishley/tree/main/Code/Sbox.Game
Mainly what we're interested in is the news and errors feed.
I'm not gonna lie, I'd be fine with no auth for errors and insights page, not like there's much for others to see. But will have to see what others think about it, they might not want it exposed.
For?
Other
What can't you do?
I'd like for a public game to have feeds for the news page, errors page, and insights page. This way I am able to fetch and and report any new errors to my team, keep track of the stats outside of asset.party, and automatically post news for the community to view. All without wasting valuable bandwidth for both me and Facepunch.
How would you like it to work?
Similar to the existing feed: https://services.facepunch.com/sbox/package/ A way to fetch specific packages and their pages, if public. Better yet if you can just specify an entire org and it combines the feeds of all their packages, but that's a stretch goal.
What have you tried?
The existing feed already has a some user stats such as reviews and player count (daily, weekly, monthly) for any package, I can use this in alternative to the "Insights Page". I wasn't able to find the news feed of a package/org, and the errors tab is private so I'm unable to access it without any authentification.
Additional context
I understand if others wouldn't want their errors feed public but personally I don't mind, it could contain "semi-private" informations such as the player's computer name but it shouldn't be a problem as long as the steamid isn't provided. The alternative would be an authentification key for developers to use on their own org, which I think was planned already if I remember correctly.