LD-Signatureの別途keyId探索いらない気がする

src/queue/processors/inbox.ts

@@ -40,7 +40,6 @@ export const tryProcessInbox = async (data: InboxJobData, ctx?: ApContext): Prom
 	const activity = data.activity;
 
 	const resolver = ctx?.resolver || new Resolver();
-	const dbResolver = ctx?.dbResolver || new DbResolver();
 
 	//#region Log
 	logger.debug(inspect(signature));
@@ -90,20 +89,13 @@ export const tryProcessInbox = async (data: InboxJobData, ctx?: ApContext): Prom
 	// また、http-signatureのsignerは、activity.actorと一致する必要がある
 	if (!httpSignatureValidated || user.uri !== activity.actor) {
 		// でもLD-Signatureがありそうならそっちも見る
-		if (!config.ignoreApForwarded && activity.signature) {
+		if (!config.ignoreApForwarded && activity.signature?.creator) {
 			if (activity.signature.type !== 'RsaSignature2017') {
 				return `skip: unsupported LD-signature type ${activity.signature.type}`;
 			}
 
-			// activity.signature.creator: https://example.oom/users/user#main-key
-			// みたいになっててUserを引っ張れば公開キーも入ることを期待する
-			if (activity.signature.creator) {
-				const candicate = activity.signature.creator.replace(/#.*/, '');
-				await resolvePerson(candicate).catch(() => null);
-			}
+			user = await resolvePerson(activity.signature.creator.replace(/#.*/, '')).catch(() => null) as IRemoteUser | null;
 
-			// keyIdからLD-Signatureのユーザーを取得
-			user = await dbResolver.getRemoteUserFromKeyId(activity.signature.creator);
 			if (user == null) {
 				return `skip: LD-Signatureのユーザーが取得できませんでした`;
 			}