kyren/eko.git/internal/server/api/helpers.go, branch master [no description] http://git.kyren.codes/kyren/eko.git/atom/internal/server/api/helpers.go?h=master 2025-08-09T07:47:41Z Fix writing a message to an offline user causes an error log on the 2025-08-09T07:47:41Z Kyren223 kyren223@proton.me 2025-08-09T07:47:41Z urn:sha1:959290d2ffcf14e0397e262b9a32435bc1a5dd3b backend Updated copyright 2025-08-04T08:38:07Z Kyren223 kyren223@proton.me 2025-08-04T08:38:07Z urn:sha1:e6e1b6f86b296df1678c7d71128c61b4ef82f127 Added copyright and AGPL notice to all source code files 2025-07-20T13:34:18Z Kyren223 Kyren223@proton.me 2025-07-20T13:34:18Z urn:sha1:aa1fab53af16ec1aba56cceafdef4a26911044de Added session duration metrics with device analytics along with device 2025-07-19T15:32:12Z Kyren223 Kyren223@proton.me 2025-07-17T15:45:43Z urn:sha1:f793203e043aaa2db38823c84500e82756348ac0 analytics metrics in the DB to aggregate and DeviceID abuse prevention Replaced most log statements with slog on the server 2025-07-19T15:32:12Z Kyren223 Kyren223@proton.me 2025-07-09T13:20:59Z urn:sha1:ba47118e5171a602e90d22951997bf220fd8deb1 Added better logging for packets and payloads and now the writer is 2025-07-06T15:20:46Z Kyren223 Kyren223@proton.me 2025-07-06T15:20:46Z urn:sha1:bbd4eae95fe7dec5b85e2124eb016c7a10a390fe responsible for packaging into a packet the payload (instead of everyone who sends to the writer) Implemented server-side authentication in accordance to the protocol 2025-07-06T11:40:32Z Kyren223 Kyren223@proton.me 2025-07-06T11:40:32Z urn:sha1:f80cb4a0fe26f5ebbb9658da671771dc79d416d6 When a user sends a message "signal" and the receiving user doesn't have 2025-02-05T17:41:34Z Kyren223 Kyren223@proton.me 2025-02-05T17:41:34Z urn:sha1:0bf5515629f1cfe1557dba4f8d588ac64b77d408 the signal already open, it will be added as the first signal Server now also sends the last_read column to the client so the client 2025-02-04T17:37:06Z Kyren223 Kyren223@proton.me 2025-02-04T17:37:06Z urn:sha1:f0607f16633d266f55a4b08f7edbbc13d08121ae so the client can use it to persist notifications Reverted back the removal of the logic in get notifications to check if 2025-02-04T17:08:22Z Kyren223 Kyren223@proton.me 2025-02-04T17:08:22Z urn:sha1:d9ae3018180e12c8b79361ef58c9e9e7114d80aa the user has access to the frequency, because it is needed for the is_admin ping type but also to prevent the case where someone was an admin, got demoted and can now monitor when new messages are sent there