misskey fixed this properly, and we know the code works because it's
in our stable release

this is also fixed in the `future` branch

View MR for information: TransFem-org/Sharkey!506



Approved-by: Tess K <me@thvxl.se>
Approved-by: Marie <marie@kaifa.ch>

View MR for information: TransFem-org/Sharkey!522



Closes #528

Approved-by: Marie <marie@kaifa.ch>
Approved-by: fEmber <acomputerdog@gmail.com>

View MR for information: TransFem-org/Sharkey!521



Closes #512

Approved-by: Marie <marie@kaifa.ch>
Approved-by: fEmber <acomputerdog@gmail.com>

View MR for information: TransFem-org/Sharkey!520



Approved-by: Marie <marie@kaifa.ch>
Approved-by: fEmber <acomputerdog@gmail.com>

View MR for information: TransFem-org/Sharkey!530



Approved-by: Marie <marie@kaifa.ch>
Approved-by: dakkar <dakkar@thenautilus.net>

View MR for information: TransFem-org/Sharkey!515



Approved-by: dakkar <dakkar@thenautilus.net>
Approved-by: Marie <marie@kaifa.ch>
Approved-by: Leah <kevinlukej@gmail.com>
Approved-by: Amelia Yukii <amelia.yukii@shourai.de>

View MR for information: TransFem-org/Sharkey!523



Approved-by: dakkar <dakkar@thenautilus.net>
Approved-by: Marie <marie@kaifa.ch>
Approved-by: Leah <kevinlukej@gmail.com>

View MR for information: TransFem-org/Sharkey!483



Approved-by: Marie <marie@kaifa.ch>
Approved-by: fEmber <acomputerdog@gmail.com>

View MR for information: TransFem-org/Sharkey!514



Approved-by: dakkar <dakkar@thenautilus.net>
Approved-by: Marie <marie@kaifa.ch>

View MR for information: TransFem-org/Sharkey!508



Approved-by: dakkar <dakkar@thenautilus.net>
Approved-by: Marie <marie@kaifa.ch>

View MR for information: TransFem-org/Sharkey!528



Approved-by: dakkar <dakkar@thenautilus.net>
Approved-by: Amelia Yukii <amelia.yukii@shourai.de>

View MR for information: TransFem-org/Sharkey!527



Approved-by: dakkar <dakkar@thenautilus.net>
Approved-by: Amelia Yukii <amelia.yukii@shourai.de>

View MR for information: TransFem-org/Sharkey!114



Approved-by: dakkar <dakkar@thenautilus.net>
Approved-by: Leah <kevinlukej@gmail.com>

View MR for information: TransFem-org/Sharkey!526



Closes #535

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

View MR for information: TransFem-org/Sharkey!478



Closes #472

Approved-by: Luna <her@mint.lgbt>
Approved-by: Leah <kevinlukej@gmail.com>

View MR for information: TransFem-org/Sharkey!455



Approved-by: fEmber <acomputerdog@gmail.com>
Approved-by: Leah <kevinlukej@gmail.com>
Approved-by: Amelia Yukii <amelia.yukii@shourai.de>

View MR for information: TransFem-org/Sharkey!525



Approved-by: dakkar <dakkar@thenautilus.net>
Approved-by: Amelia Yukii <amelia.yukii@shourai.de>

View MR for information: TransFem-org/Sharkey!524



Approved-by: dakkar <dakkar@thenautilus.net>
Approved-by: Luna <her@mint.lgbt>
Approved-by: Amelia Yukii <amelia.yukii@shourai.de>

there is no `tlWithBots` setting, it's inside `tl.filter` and we need
more complicated code to set it

The previous assertion that:

> if it's a complicated thing and the `activity.id` doesn't match, I
> think we're fine rejecting the activity

was wrong: at least peertube sends activities that have `url` as an
array of objects.

Notice that this does *not*, in fact, fix #512: the peertube activity
does not contain its short URL (`https://example.com/w/someid`), so
there's no way to confirm that it is the activity we requested.

my recent changes to allow overrides from the environment had bad types

View MR for information: TransFem-org/Sharkey!476



Closes #465

Approved-by: Marie <marie@kaifa.ch>
Approved-by: Luna <her@mint.lgbt>

a server replied to, renoted or reacted to a note knows about a note,
and as such it should get notified about it being edited.

this matches similar logic in mastodon.

View MR for information: TransFem-org/Sharkey!512



Approved-by: Marie <marie@kaifa.ch>
Approved-by: Tess K <me@thvxl.se>