In the comparison table, why peer.js for non-authoritative game server?

[bennlich]

Just curious, in this table, why do you recommend peer.js over geckos for a non-authoritative game server?

[yandeu]

I can't remember 😄 (This table is old)

You can of course use geckos.io in any of those cases.

I guess you should only use socket.io over geckos.io if you do not know how to deploy your own server and to forward the necessary ports. For instance if you want to use Heroku, then your only option is socket.io since the Node.js WebRTC implementation can't work on services like Heroku.

I think I should update the table.

[bennlich]

Ah, k. Gotcha :) I'll let you close this or use as a reminder to update the table.

I think I'm going to try using geckos shortly! I'm excited.

[jdspugh]

A central server can act as a "judge" (authority) to give the final word on scores, game states, etc. Peer-to-peer (peerjs) games don't rely on a central authority (non-authoritative) and need to vote between themselves to decide on mutual outcomes.

[github-actions]

This issue is stale because it has been open 300 days with no activity. Remove stale label or comment or this will be closed in 10 days.

[github-actions]

This issue was closed because it has been stalled for 10 days with no activity.