Ignas Kiela 296c40c5b4 fix: stop sending pings on every pong ... This resulted in endless ping-pong traffic on the websocket, happening every interval of network latency to the server (e.g. for me, with 40ms latency to my server, it was about every 40ms). On my server this ended up taking about 20% of foundkey's CPU usage. Now, just send pings every 30s, and check if we have received any pong's in last 60 seconds to check that the connection is still alive. Changelog: Fixed		2023-05-23 18:08:08 +02:00
..
.vscode	Update settings.json	2022-04-15 21:33:00 +09:00
assets	client: display move notification	2023-03-23 21:10:17 +01:00
migration	add "nobody" follower visibility	2023-05-20 23:18:57 +02:00
src	fix: stop sending pings on every pong	2023-05-23 18:08:08 +02:00
test	try to fix tests	2023-05-15 20:14:51 +02:00
.eslintignore	migrate to Yarn 3.2.3	2022-08-26 15:24:29 -04:00
.eslintrc.cjs	enhance typeorm-prefer-count lint rule	2023-01-03 02:41:53 +01:00
.mocharc.json	fix broken mocha tests v2	2022-07-13 12:49:58 +02:00
jsconfig.json	use eslint	2021-11-12 10:35:41 +09:00
ormconfig.js	refactor: migrate to typeorm 3.0 (#8443)	2022-03-26 15:34:00 +09:00
package.json	remove syslog	2023-05-19 23:15:24 +02:00
tsconfig.json	BREAKING: Remove support for Node 16.x and upgrade to TypeScript 4.9	2022-11-25 02:07:21 -05:00
watch.mjs	implement dev command	2021-11-19 14:48:59 +09:00