洪 民憙 (Hong Minhee)

Starting with #Hollo 0.4.0, you can allow your profile to be discovered in the public directory. Under the hood, this option corresponds to Mastodon's toot:discoverable property.

へぇ、となった記事

パイプライン演算子の歴史 - まめめも https://mametter.hatenablog.com/entry/2019/06/15/192311

@reiver @anze3db Hmm, looks like I need to implement the discoverable property in Hollo. 🤔

@monaco_koukoku お疲れ様でした！

ActivityPub Relay v0.8.0 has been released🎉

https://github.com/S-H-GAMELINKS/activity-pub-relay/releases/tag/v0.8.0

The main changes are
・Support for Pleroma and Akkoma relays.
・Support for domain blocking as an anti-spam measure.
・Temporary delivery stop functionality has been added.
・REPOSITORY_NAME environment variable added to allow multiple relay servers to be built.

#ActivityPub_Relay

亦是 辛拉麵은 맛이 없어…

修正してみた
QT: https://fedibird.com/@dampuzakura/113719383739676842 [参照]

You will soon be able to run your own federated, self-hosted TikTok alternative with first class support for ActivityPub and a rich API with a vibrant 3rd party ecosystem.

https://loops.video

#loops

@aslakr Yes, this is a hidden feature of Hollo for Korean! (Ruby characters are automatically attached.) However, it's not yet available for other languages.

A Call for Better Activity Signatures in the Fediverse

Why Major ActivityPub Implementations Should Adopt Object Integrity Proofs

Let's say you have accounts named alice@bar and bob@baz that don't follow each other, but they both follow john@foo. When alice@bar replies to john@foo's post, how can bob@baz see this reply?

This problem applies not only to replies, but also to things like likes and emoji reactions. One of the ways that ActivityPub implementations solve this problem is through inbox forwarding. The idea is to forward the reply received by john@foo to bob@baz as well.

Fedify makes inbox forwarding easy and convenient with its forwardActivity() method. But the question is, can bob@baz trust the activity forwarded by john@foo?

Because HTTP Signatures sign the HTTP request that contains the activity, not the activity itself, john@foo can't sign an activity created by alice@bar when it's forwarded by him, because forwarding requires creating a new HTTP request. (The HTTP request includes things like the Host header, so a new signature is required for each new recipient.)

So, alice@bar needs to sign her activity in a way that allows john@foo to forward it. In the fediverse, there are two ways to do this: Linked Data Signatures and Object Integrity Proofs. Fedify automatically attaches all three types of signatures (HTTP Signatures, Linked Data Signatures, and Object Integrity Proofs) to every activity it sends, so activities are free to be forwarded between ActivityPub software created with Fedify.

However, major ActivityPub implementations such as Mastodon and Misskey still sign activities with HTTP Signatures only, or only some activities with Linked Data Signatures. (Note that Linked Data Signatures is an outdated standard, and Object Integrity Proofs are recommended.)

So, why are we talking about this at length? We strongly urge major ActivityPub implementations to adopt Object Integrity Proofs, or at minimum Linked Data Signatures, for activity signing!

しかし、インボックスフォワーディングをする為には元のアクティビティが署名される必要が有りますよね。HTTP Signaturesだけで署名するとフォワーディングが出来ないので、Mastodon, Misskeyなど主要なActivityPubの実装がLinked Data SignaturesでもObject Integrity Proofsでもどちらでも良いので、署名して欲しいです。

インボックスフォワーディング（inbox forwarding）、実装が面倒なので、多くのActivityPubの実装が省略したり、一部のアクティビティにのみ実装しているみたいです。Fedifyを使うとインボックスフォワーディングをとても簡単に実装する事が出来ます。

https://fedify.dev/manual/inbox#forwarding-activities-to-another-server

@tirr 안 그래도 저도 개발하면서 그게 필요해서 스크립트를 하나 만들게 되더라고요! (pnpx run rebuild-timelines 커맨드로 실행 가능.)

미스키에는 없지만 마스토돈에는 타임라인 캐시 재생성하는 명령도 있었던것같다

RE: https://hollo.social/@hollo/01940231-1d29-7810-953b-c2336976966d

┏━━┓┏━━┓┏━━┓┗━┓┃
┗━┓┃┃┏┓┃┗━┓┃　　┗┛
┏━┛┃┃┃┃┃┏━┛┃┏━━┓
┃┏━┛┃┃┃┃┃┏━┛┃┏━┛
┃┗━┓┃┗┛┃┃┗━┓┃┗━┓
┗━━┛┗━━┛┗━━┛┗━┓┃

Pleromaの投稿を見ると自サーバの誰もがフォローしていない人によるものも含めてやたらと絵文字リアクションが付いているような印象を受けがちだけど、あれも恐らくinbox forwardingの実装状況の違いによるものなのだろうな

Inbox forwarding、確かMisskeyとかは実装していないのだったよな。あと規格通りなら`Create(Note)`に限らず`Like`などを含む任意のアクティビティに適用されるはずだけど、Mastodonの場合は恐らく（署名済みの）リプライや`Update(Note)`、`Delete(Note)`などしか転送しないっぽい。一方でFedibirdはリアクションも転送するらしいね

Loops web progress ⚡️

Hollo 0.4.0からTIMELINE_INBOXESという実験的なオプションが追加されます。このオプションをtrueにすると、ホームタイムラインとリストタイムラインが要請されるたびに投稿がリアルタイムでフィルタリングされる代わりに、データベースに各タイムラインごとにインボックスが作成され、そこに投稿が入ります。その為、このオプションをオンにした直後は、タイムラインが空っぽに見える事が有ります。

このオプションをオンにすると、多くのアカウントをフォローしているアカウントでパフォーマンスが向上しますが、まだバグが有る可能性が有ります。しかし、機能が安定化したら、このオプションがデフォルトの動作に成る予定です。

Hollo 0.4.0부터는 TIMELINE_INBOXES라는 실험적인 옵션이 추가됩니다. 이 옵션을 true로 하면 여러분의 홈 타임라인과 리스트 타임라인이 요청할 때마다 게시물들이 실시간으로 필터링되는 대신, 데이터베이스에 각 타임라인별 인박스가 생기고 거기에 게시물들이 들어가게 됩니다. 따라서, 이 옵션을 켠 직후에는 타임라인이 비어 보일 수 있습니다.

이 옵션을 켜면 많은 사람을 팔로하고 있는 계정에서 성능이 향상되지만, 아직 버그가 있을 수 있습니다. 하지만 기능이 안정화되고 나서는 이 옵션이 디폴트 동작이 될 예정입니다.

Starting with Hollo 0.4.0, we're adding an experimental option called TIMELINE_INBOXES.

If this option is set to true, instead of your home timeline and list timelines filtering posts in real-time whenever they are requested, the database will create an inbox for each timeline and put posts into it. As a result, your timelines may appear empty immediately after turning this option on.

Turning this option on will improve performance for accounts that follow a lot of accounts, but it may still be buggy. However, once the feature is stabilized, this will be the default behavior.

@gnh1201 @druidesse 祝賀(축하)드립니다!

@yamanoku 『11ぴきのねこ』、私も子供の頃よく観ましたね。大好きです！

妻（@tokolovesme）からクリスマスのプレゼントして貰った『11ぴきのねこ』の縫い包み！ 🥰

FediLUG（@fedilug）の技術書第0号に掲載される私の原稿を今日脱稿した！タイトルは「国漢文混用体からHolloまで」。私がどの様にしてFedifyとHolloを作る事に成ったか、その旅路を共有する内容です。

来年1月25日に横浜産貿ホールマリネリアで開催される第十一回技術書同人誌博覧会で頒布される予定ですので、よろしくお願いします！

나는 비슷하게 韓國人(한국인)·中國(중국) 朝鮮族(조선족)·在日朝鮮人(재일조선인)·高麗人(고려인) 等(등)을 아울러 民族(민족)을 指稱(지칭)하는 말로 「韓國人(한국인)」 乃至(내지)는 「韓民族(한민족)」을 쓰는 것이 뭔가 께름직하다. 民族(민족)의 代表性(대표성)을 韓國(한국)이라는 國家(국가)가 獨佔(독점)하는 것 같아서. 個人的(개인적)으로는 「朝鮮人(조선인)」이나 「朝鮮民族(조선민족)」이라는 말을 쓰는 게 더 中立的(중립적)이지 않나 싶기도 하다. 뭐, 그게 좋은 代案(대안)인지는 나도 잘 모르겠지만… 아니면 아예 「코리안」이 나을 수도 있고.

비슷하게 ko-KR이 아닌 ko를 指稱(지칭)하는 말로 「韓國語(한국어)」가 適切(적절)하지 않다는 느낌을 받음. 亦是(역시)나 여기서도 뚜렷한 代案(대안)은 잘 모르겠다. 個人的(개인적)으로는 「朝鮮語(조선어)」라는 말을 쓰는 便(편). 마찬가지로 「코리안」이 더 나을지도 모르겠다…

https://uri.life/@mola/113712493891626073

@ysh 그러게 말입니다…

This year's Christmas cake!

@georgberky 仁川（インチョン）は韓国のソウルの隣に有る都市です。仁川国際空港がある所です。楽しく旅行してきますね〜！