Sharing a blog post from a Japanese developer, re: #ActivityPub
General Discussion
1
Posts
1
Posters
0
Views
-
Sharing a blog post from a Japanese developer, re: #ActivityPub amase.cc/articles/en/...
Why don't recommend to impleme...
Gli ultimi otto messaggi ricevuti dalla Federazione
-
mstdn.jp や #fedibird では .mp3 の音声ファイルがインライン表示されるのに、mastodon.social でインライン表示されないのはどうしてだ？
贈る側のJSONの問題かな？
#WordPress のプラグイン #ActivityPub の抜粋ではなく全コンテンツを送る設定の投稿なんだけど…。
-
Sharing a blog post from a Japanese developer, re: #ActivityPub amase.cc/articles/en/...
Why don't recommend to impleme...
-
jdt@enigmatick.social thanks! Yeah it was important to me to get that right. That little highlight library has been chugging along all this time lol.
-
@julian@activitypub.space BTW, I love that your interface uses rich formatting for markdown code blocks - so many platforms just phone that bit in.
Enigmatick uses highlight.js too, so I tend to use that a lot.
-
@jdt@enigmatick.social Fixed. My code handles the Accept header per RFC specifications now (i.e., by explicit weight first and by order second).
-
@jdt@enigmatick.social It's actually in my application code:
if let Some(accept) = headers.get(header::ACCEPT) { if let Ok(accept_str) = accept.to_str() { if accept_str.contains("text/html") { log::debug!("Redirecting to presentation page"); return Ok(AbstractResponse::Redirect(Redirect::to(&format!( "/@{username}" )))); } if accept_str.contains("application/activity+json") { log::debug!("Returning application/activity+json"); return Ok(AbstractResponse::ActivityJson(ActivityJson(actor))); } if accept_str.contains("application/ld+json") { log::debug!("Returning application/ld+json"); return Ok(AbstractResponse::LdJson(LdJson(actor))); } } }Just a priority issue with the existence of text/html. I'll rearrange.
-
@julian@activitypub.space I see the issue clearly now and can reproduce it (thanks @snarfed). It's just the complexity of the Accept header - I'll dig into why my nginx configuration isn't handling that well.
-
@julian@activitypub.space I think I see the issue on @snarfed's post on your site (thanks @snarfed). I don't currently handle application/activity+json requests for the URL (i.e., https://enigmatick.social/@jdt). I only handle those on the ID (i.e., https://enigmatick.social/user/jdt).
I don't see any harm in adding that to the URL, so I'll add a 301 to redirect application/activity+json requests for /@jdt to /user/jdt.
It's odd, though - my logs seem to indicate that the bridge server is requesting /user/jdt already.
