Nikita Vilunov nikita
  • Joined on 2023-08-25
nikita commented on pull request lavina/lavina#60 2024-05-04 10:52:28 +00:00
Implement Message Archive Management stub for XEP-0313

delete commented out code?

nikita pushed to cluster at nikita/lavina 2024-05-03 20:36:24 +00:00
5377b4c96a config
8a14a4d687 cluster
9a09ff717e management api endpoints for rooms
a87f7c9d73 xmpp: extract common fragments of integration tests into functions
25605322a0 player shutdown API (#58)
Compare 10 commits »
nikita created branch cluster in nikita/lavina 2024-05-03 20:36:24 +00:00
nikita pushed to clustering at nikita/lavina 2024-05-03 20:35:53 +00:00
9cd088ef78 config
nikita commented on pull request lavina/lavina#43 2024-05-03 16:25:49 +00:00
implement WHOIS command

[T; 20] is an array of 20 elements exactly, and there might be fewer that 20 elements?

nikita commented on pull request lavina/lavina#43 2024-05-03 16:24:40 +00:00
implement WHOIS command

All protocol types like any other network-transmitted types are plain data, they have no encapsulation of data and no behavior other than [de]serialization. This concerns all that kind of types,…

nikita pushed to main at lavina/lavina 2024-05-01 15:30:37 +00:00
9a09ff717e management api endpoints for rooms
nikita opened issue lavina/lavina#59 2024-05-01 11:16:17 +00:00
IRC echo-message capability
nikita commented on pull request lavina/lavina#43 2024-04-30 14:04:23 +00:00
implement WHOIS command

it's better to move this entire module to proto-irc, make all fields public and remove new methods

nikita commented on pull request lavina/lavina#43 2024-04-30 13:33:44 +00:00
implement WHOIS command

probably rename this to IrcConnection just like we already have an XmppConnection

nikita commented on pull request lavina/lavina#43 2024-04-30 13:33:44 +00:00
implement WHOIS command
nikita commented on pull request lavina/lavina#43 2024-04-30 13:33:44 +00:00
implement WHOIS command

&self

nikita commented on pull request lavina/lavina#43 2024-04-30 13:33:44 +00:00
implement WHOIS command

I would prefer that all player-related queries would go through PlayerConnection and then the player actor, Storage should not be exposed to projections. Even if the method in PlayerConnection does nothing except calling storage. This is important because 1) the player actor serializes all incoming commands and acts as a sort of anti-dos protection layer; 2) it's not guaranteed in the future that all players will be stored on the same node, and the core services will handle routing requests to other nodes.

nikita suggested changes for lavina/lavina#43 2024-04-30 13:33:44 +00:00
implement WHOIS command
nikita pushed to main at lavina/lavina 2024-04-29 21:56:22 +00:00
a87f7c9d73 xmpp: extract common fragments of integration tests into functions
nikita deleted branch player-shutdown from nikita/lavina 2024-04-29 17:24:45 +00:00
nikita pushed to main at lavina/lavina 2024-04-29 17:24:45 +00:00
25605322a0 player shutdown API (#58)
nikita merged pull request lavina/lavina#58 2024-04-29 17:24:44 +00:00
player shutdown API
nikita pushed to player-shutdown at nikita/lavina 2024-04-29 17:13:54 +00:00
51fd90d95a Merge branch 'main' into player-shutdown
31f9da9b05 xmpp: fix incorrect auth test
Compare 2 commits »
nikita pushed to main at lavina/lavina 2024-04-29 17:13:39 +00:00
31f9da9b05 xmpp: fix incorrect auth test