From 70920985cfc0b453a95613d437afaf092f167c60 Mon Sep 17 00:00:00 2001
From: alemi <me@alemi.dev>
Date: Tue, 23 Apr 2024 05:46:48 +0200
Subject: [PATCH] fix: use hs2019 instead of rsa-sha256

im not sure why but apparently there's some bug somewhere? maybe some
instances are picky and want the new thing? should still be fine using
sha256 as signing tho
---
 src/server/fetcher.rs | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/server/fetcher.rs b/src/server/fetcher.rs
index a9687135..75e1a1af 100644
--- a/src/server/fetcher.rs
+++ b/src/server/fetcher.rs
@@ -51,7 +51,8 @@ impl Fetcher for Context {
 
 		let mut signer = HttpSignature::new(
 			format!("{from}#main-key"), // TODO don't hardcode #main-key
-			"rsa-sha256".to_string(),
+			"hs2019".to_string(),
+			//"rsa-sha256".to_string(),
 			&headers,
 		);