View MR for information: !617



Approved-by: dakkar <dakkar@thenautilus.net>
Approved-by: Tess K <me@thvxl.se>

View MR for information: !614



Approved-by: Marie <github@yuugi.dev>
Approved-by: dakkar <dakkar@thenautilus.net>

View MR for information: !608



Closes #612

Approved-by: dakkar <dakkar@thenautilus.net>
Approved-by: Marie <github@yuugi.dev>

added event to detect when control and enter are pressed to confirm it. Also escape now escapes the window

View MR for information: !603



Approved-by: Marie <github@yuugi.dev>
Approved-by: fEmber <acomputerdog@gmail.com>

View MR for information: !607



Closes #631

Approved-by: fEmber <acomputerdog@gmail.com>
Approved-by: Marie <github@yuugi.dev>

View MR for information: !606



Approved-by: Amelia Yukii <amelia.yukii@shourai.de>
Approved-by: Marie <github@yuugi.dev>

karilaa.app seems down, and I've not heard from them

plasmatrap has been running our release candidate for a few days

View MR for information: !604



Closes #626

Approved-by: fEmber <acomputerdog@gmail.com>
Approved-by: Marie <github@yuugi.dev>
Approved-by: Amelia Yukii <amelia.yukii@shourai.de>

that Japanese string exactly matches that i18n key

this prevents generating promises we don't use, which would get logged
by the node vm and spam the logs

I have no clue why I wrote that code 😭

View MR for information: !583



Approved-by: Marie <github@yuugi.dev>
Approved-by: Julia Johannesen <julia@insertdomain.name>

View MR for information: !602



Approved-by: Julia Johannesen <julia@insertdomain.name>
Approved-by: Amelia Yukii <amelia.yukii@shourai.de>
Approved-by: Marie <2-Marie@users.noreply.activitypub.software>

It's trivial to have more than 128 requests in flight: open a busy
timeline, scroll a bit down, wait for many notes to arrive, scroll to
the top. The frontend will send "subscribe to note" messages for each
new note that it accumulated, all at once. We don't want to shut down
the connection in those common cases!

View MR for information: !599



Closes #622

Approved-by: Marie <2-Marie@users.noreply.activitypub.software>
Approved-by: Julia Johannesen <julia@insertdomain.name>

View MR for information: !601



Approved-by: Julia Johannesen <julia@insertdomain.name>
Approved-by: Marie <2-Marie@users.noreply.activitypub.software>

* the frontend opens 2 websockets at startup (I'm not completely clear
  why), and that `minInterval:1sec` was breaking the second connection
* as the comment says, "catching up" generates many noteSubscribe
  messages

View MR for information: !594



Approved-by: Marie <2-Marie@users.noreply.activitypub.software>
Approved-by: Amelia Yukii <amelia.yukii@shourai.de>

View MR for information: !598



Approved-by: Marie <2-Marie@users.noreply.activitypub.software>
Approved-by: Amelia Yukii <amelia.yukii@shourai.de>

View MR for information: !600



Approved-by: dakkar <dakkar@thenautilus.net>
Approved-by: Marie <2-Marie@users.noreply.activitypub.software>

we're doing the same thing that Fastify does in the non-streaming
ServerService

Suggestions made by @Leah

3f73251d reworked the way `offsetMode`
is handled, to allow reactive `ComputedRef<boolean>` in addition to a
simple `boolean`, so that custom emoji search could easily switch
between the faster `sinceId`/`untilId` pagination and the slower
`offset` as needed.

Or it would have, if I had written the correct expression! I wrote
`props.offsetMode` instead of `props.pagination.offsetMode`, so it was
always `false`

I have *no idea* how I didn't notice, I swear I tested it ☹️

Anyway, factoring out the nested ternaries makes the whole thing
clearer and less prone to mistakes. And I have tested it, this time.