Notices by 洪 民憙 (Hong Minhee) (hongminhee@todon.eu), page 13

The #SocialHub forum now has the #Fedify category!

https://socialhub.activitypub.rocks/c/software/fedify/85

「成功したオタク」(성덕)、性被害者を思いやる心は見えず、推しが墮落してしまった自分への自己憐憫ばかりが露呈してしまい、最低な映畫だった。😩

Always bet on the #web. That's why I bet on #ActivityPub and #fediverse, not Bluesky.

@0x0 @erlend Although Fedify already implements HTTP Signatures, relying on Kitsune's implementation for performance might be an option. However, I'm not sure how much of a performance gain it would be, since Fedify already relies on Deno's Web Cryptography API, which is implemented in Rust. 🤔

@mariusor Unfortunately, that's the official installation method that the Deno documentation says. 😥

#Fedify finally has a step-by-step tutorial! It's perfectly fine if you're not familiar with the #ActivityPub protocol or the #Deno runtime. Here's the link for beta readers:

https://unstable.fedify.dev/tutorial/

Unlike #Deno CLI, Deno Deploy apparently doesn't support Web Worker API yet. Disappointing. Maybe someday it will support it?

日本에서는 디지털 器機가 甓돌이 되는 걸 「文鎭化」라고 하는 模樣.

@crepels Good. Thank you for the fast fix!

@crepels Do you have any idea what happened?

Oh no, ActivityPub.Academy seems to be down?

The ACM, the IEEE, and other professional organizations have really dropped the ball on this because it shouldn't be up to some random individual with no policy experience to suggest this. This is the sort of thing that industry groups are supposed to help inform policymakers about.

Groups like those should be asking questions like "How big would the tax writeoff have to be to prevent Redis from moving from open-source to source-available?" and "How do we get governments to sign off on that?"

Today's Redis news is an unfortunate reminder that while open source itself is a public benefit to society, within our economic system if you are the _provider_ of a public benefit to society, that's an inefficiency in your business that there will be constant pressure to eliminate. The more capital investment the provider accepts from others, the more pressure there will be on management to remove that inefficiency.

I made a fedi badge generator, which shows the number of your following/followers/posts. You can embed this on your project README.

Under the hood, it's powered by #Hono and #Fedify, and deployed to #Deno Deploy.

https://github.com/dahlia/fedi-badge

@lamikennel 네, 둘 다 「육십일」로 같습니다! 비슷하게 「10日」과 「11」 둘 다 「십일」로 같습니다. 그래서 電話 通話할 때 「십일? 십일일? 열 하나? 열?」처럼 말하기도 해요. 😅

I just added one more small example to the #Fedify repository, a simple CLI program that looks up an actor by their fediverse handle (e.g. @user@host) and prints out their name, bio, stats, etc. It uses Fedify as a client library of ActivityPub, not as a server framework here.

https://github.com/dahlia/fedify/tree/main/examples/actor-lookup-cli

#Fedify now has getActorHandle() function. It will be shipped with the next release…

https://jsr.io/@fedify/fedify@0.4.0-dev.62+1e878003/doc/vocab/~/getActorHandle

One workaround I've found is to query WebFinger with an actor IRI and then look at the subject and aliases.

I should probably add a utility function to #Fedify to get an actor's handle…

I believed that to get a handle of the form “@username@domain” from an actor object, I could just combine the preferredUsername and the host part of the id IRI, but I realized that this is not always the case. For example, in Mastodon, if you configure LOCAL_DOMAIN and WEB_DOMAIN differently, the handle can be “@username@domain” and the profile URL can be “sub.domain/@username”” at a time. #fedidev

https://docs.joinmastodon.org/admin/config/#web_domain