Conversation
Notices
-
meso (meso@the.asbestos.cafe)'s status on Tuesday, 26-Dec-2023 05:12:55 JST meso @kirby @Pawlicker @lain @mint @Zergling_man @siina IS HTTP signatures the same as authorized fetches -
(mint@ryona.agency)'s status on Tuesday, 26-Dec-2023 05:12:54 JST @meso @Pawlicker @kirby @lain @Zergling_man @siina No, signatures are good since otherwise anyone with a copy of curl could impersonate anyone else on the network but sendoing out fake activities. When it gets shoehorned into object fetching, that's where I have a problem. There's simply no valid reason why I should be able to view a post in web frontend but not get the activity corresponsing to the same public post if some janny couldn't handle my rizz. -
LS (lain@lain.com)'s status on Tuesday, 26-Dec-2023 05:13:45 JST LS @mint @Pawlicker @kirby @Zergling_man @siina @meso it can make sense for activities with restricted audiences. -
(mint@ryona.agency)'s status on Tuesday, 26-Dec-2023 05:15:03 JST @lain @Pawlicker @kirby @Zergling_man @siina @meso Lockposts are defective by design, but they simply return "not found" in either case. -
:blank: (i@declin.eu)'s status on Tuesday, 26-Dec-2023 05:18:18 JST :blank: @lain @Pawlicker @kirby @mint @Zergling_man @siina @meso like C2S, anything but https://www.w3.org/ns/activitystreams#Public was a habitual mistake with the current S2S implementations likes this.
-