Notices by 洪 民憙 (Hong Minhee) (hongminhee@fosstodon.org), page 2

According to the Activity Vocabulary specification, the summary property should be HTML encoded, but #Mastodon is putting plain text in the summary property. #Hollo is putting #HTML in the summary, but should I change Hollo's behavior? :blobcatthink:

https://www.w3.org/TR/activitystreams-vocabulary/#dfn-summary

#ActivityPub #fedidev

If you've been avoiding #JavaScript & #TypeScript due to the complexity of the #Node.js ecosystem, give #Deno a try. Everything is simplified and you can start coding right away without having to set up a development environment.

Okay, #Fedify is now ready for #Deno 2.0!

#Fedify is now preparing for #Deno 2.0…

I'm adding the #EmojiReact (FEP-c0e0) class to #Fedify… It will be coming in Fedify 1.1.0.

https://w3id.org/fep/c0e

#ActivityPub #fedidev

#Fedify is built in #Deno for ease of development, but it also supports #Node.js and #Bun using #dnt. Deno's DX is so good that I don't regret this decision, and I'm looking forward to Deno 2.0 as well.

Looks like #Fedify v1.0.0 will be released this week! Is there anything you'd like to see added or fixed before then?

#fedidev #ActivityPub

Quick question: would it be okay to embed a collection object in the `as:replies` property of `as:Note` & `as:Article` objects instead of putting the URL to the collection in the `as:replies` property? In theory, it would be okay, but would the actual implementations handle it well?

#fedidev #ActivityPub

@julian Ghost already represents posts as `as:Article` objects. Interestingly, they put `as:Note` into the `as:preview` property of `as:Article` objects, which I don't think Mastodon utilizes.

https://github.com/TryGhost/ActivityPub/blob/46ef68e2c79ec9e8e3fb8d9e5ebbd0729c6bae72/src/handlers.ts#L58-L70

@renchap @pfefferle @mike @michael

As the creator of Fedify, I'd like to see either ActivityPub implementations all deal with JSON-LD properly, or the ActivityPub spec gives up on JSON-LD. 😩

I received a request from @ghost today to add #LDSignatures to @fedify for compatibility with #Mastodon, as Mastodon does not plan to implement Object Integrity Proofs (FEP-8b32) for the near future. 😩

However, Mastodon's implementation of LD Signatures does not even use valid JSON-LD properties (despite the name), so I'm not sure how to make it compatible with Mastodon since #Fedify does JSON-LD processing. 🤔

#ActivityPub #fedidev

@liaizon I have no idea either, but I learned it from @tesaguri (if I recall correctly).

I wish #Mastodon would just implement FEP-8b32 instead of the LD Signatures which is obsolete.

https://w3id.org/fep/8b32

#ActivityPub #LDSignatures #fedidev

うちのサーバーで日本側のサーバーのアイコンだけをブロックしているのだろうか？（欧米圏のサーバーは日本サーバーをブロックすることが多い）

何故か日本側のサーバーのアカウントはアイコンが表示されないことが多い。🤔

Hello, I'm an open source software engineer in my late 30s living in #Seoul, #Korea, and an avid advocate of #FLOSS and the #fediverse.

I'm the creator of @fedify, an #ActivityPub server framework in #TypeScript, and @hollo, a fediverse microblog for single users.

I'm also very interested in East Asian languages (so-called #CJK) and #Unicode. Feel free to talk to me in #English, #Korean (#한국어), or #Japanese (#日本語), or even in Literary Chinese (#文言文/#漢文)!

#introduction

こんにちは、私はソウルに住んでいる30代後半のオープンソースソフトウェアエンジニアで、自由・オープンソースソフトウェアとフェディバースの熱烈な支持者です。名前は洪 民憙（ホン・ミンヒ）です。

私はTypeScript用のActivityPubサーバーフレームワークである「@fedify」と、1人用フェディバースのマイクロブログである 「@hollo」の作成者でもあります。

私は東アジア言語（いわゆるCJK）とUnicodeにも興味が多いです。日本語、英語、韓国語で話しかけてください。（または、漢文でも！）

#自己紹介 #CJK #Unicode #日本語 #英語 #韓国語

安寧하세요, 저는 서울에 살고 있는 30代 後半 오픈 소스 소프트웨어 엔지니어이며, 自由·오픈 소스 소프트웨어와 聯合宇宙의 熱烈한 支持者입니다.

저는 TypeScript用 ActivityPub 서버 프레임워크인 @fedify 프로젝트와 싱글 유저用 聯合宇宙 마이크로블로그인 @hollo 프로젝트의 製作者이기도 합니다.

저는 東아시아 언어(이른바 #CJK)와 유니코드에도 關心이 많습니다. Mastodon에서는 國漢文混用體를 쓰고 있어요! 제게 韓國語나 英語, 日本語로 말을 걸어주세요. (아니면, 漢文으로도!)

#툿친소 #연친소 #별친소 #國漢文 #國漢文混用 #國漢文混用體 #국한문 #국한문혼용 #국한문혼용체 #한국어 #일본어 #영어 #한문 #연합우주

@satomuch 最近、韓国では「#国有化」の反対を「#民営化」と呼ぶのは保守派のフレームに過ぎないので、「#私有化」と呼ぶべきだという動きが起きています。

@songyuka_ 韓国鉄道公社が民営企業ではなく、国有公営企業だからです！