You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it'd be interesting to be usable as a Discord activity. Discord activities are easy for everyone to use and improve the games discoverability.
It's a hard requirement not to be bound to Discord though. Everything needs to function without it.
This means, we should avoid relying on their SDK or anything like that. Everything must be losely coupled.
AFAIK right now there are 2 issues.
The inline scripts need to be downloaded scripts instead, as per discord security policy ... god knows why
Inline event handlers need to be moved into the JS code
The websocket URL needs to be aware of the proxy. (iframe start location can be used)
Session management needs to be integrated somehow.
We need to make sure people at least automatically join the instance or can see them even if they are private. That way, we only need to make slight changes to the API.
The text was updated successfully, but these errors were encountered:
Session management is still missing. The cherry on top would be to properly integrate, however, that would require loading the discord sdk afaik. If it is a simple small file, I will consider it, otherwise we'll go for half-assed integration for now.
I think it'd be interesting to be usable as a Discord activity. Discord activities are easy for everyone to use and improve the games discoverability.
It's a hard requirement not to be bound to Discord though. Everything needs to function without it.
This means, we should avoid relying on their SDK or anything like that. Everything must be losely coupled.
AFAIK right now there are 2 issues.
Session Management
For this we need to use the instanceid discord provides: https://discord.com/developers/docs/activities/development-guides#using-instanceid
We need to make sure people at least automatically join the instance or can see them even if they are private. That way, we only need to make slight changes to the API.
The text was updated successfully, but these errors were encountered: