Hollo

Hollo公式サイト兼ドキュメントに日本語が追加されました！

https://docs.hollo.social/ja/

Hollo 공식 웹사이트 겸 문서에 한국어가 추가되었습니다!

https://docs.hollo.social/ko/

@helianthropy We don't support per-domain blocking yet, but it's on the roadmap!

@esther We don't support account migration yet, but it's coming this month!

@steve Looks like the Docker Compose file is outdated, we'll fix it!

Unfortunately, Hollo doesn't support customizing permalink formats like WordPress. If you want to keep permalinks, you'll need to maintain a separate redirection service.

Hollo supports multiple accounts. However, all accounts are logged in with a single credential (you will be prompted to select an account after logging in).

@steve Oh, this is the first I've heard of snac2, thanks for letting me know.

Hollo used to rely on Redis, but we don't anymore. In the long run, we'll remove the dependency on S3-compatible storage as well (or make it an optional dependency).

I don't know much about snac2, but at first glance it looks like Hollo has a bit more functionality: quotes, emoji reactions, Markdown, etc.

@julian Fixed now!

@julian Thanks for reporting! We're going to fix it soon!

개인용 ActivityPub 서버를 운영하고 싶지만, Mastodon나 Misskey을 설치하기에는 서버 사양이 넉넉치 않아서 고민이신가요? 그럼 개인용 경량 ActivityPub 서버인 Hollo를 써 보세요!

https://docs.hollo.social/

個人用ActivityPubサーバーを運営したいけど、MastodonやMisskeyをインストールするにはサーバーの仕様が足りないので悩んでいますか？それなら、個人用の軽量ActivityPubサーバーであるHolloを使ってみてください！

https://docs.hollo.social/

Want to run your own personal #ActivityPub server, but don't have the server specs to install Mastodon? Try #Hollo, a lightweight personal ActivityPub server!

https://docs.hollo.social/

@dmitri We use ngrok or fedify tunnel for local development!

@dmitri We recommend @phanpy!

MinIO使わずに外部のオブジェクトストレージ使えばRAM512MBとかで動くと思う

Hollo、Misskeyのメモリ使用量の1/3くらいでいいね

何か書いた

https://blog.esurio1673.net/posts/hollo/

You can now see #emoji #reactions in #Hollo (but you can't leave emoji reactions yet). We've implemented the FEP-c0e0 spec and tested it on #Misskey, #Akkoma, and #Fedibird.

#ActivityPub #fedidev

@silverpill As it turns out, this was a bug on @fedify's end. It's been fixed in the Fedify 1.0.2 release, and has also been applied to Hollo!

Fixed a bug that caused #hashtags attached to posts on #Hollo to be treated as regular links in #Misskey and other #Forkeys!

Fedify, an ActivityPub framework, has finally released its first stable version, 1.0.0! Here are key changes:

Deprecation of the term handle

From this version, the term handle across Fedify will only be used to refer to fediverse handles (e.g., @[email protected]). An actor's internal unique ID (e.g., b379dbdc-3b4f-4ef4-88c2-fc25632d1c22) is referred to as an identifier, and the WebFinger name (e.g., hongminhee) is referred to as a username.

The term handle in the API will be maintained for a while for backward compatibility, but deprecation warnings will be logged, and it is planned to be removed in the future.

For more details, please refer to the related documentation.

Linked Data Signatures

Linked Data Signatures is an outdated standard, but it's still relied upon by major fediverse implementations such as Mastodon.

In addition to HTTP Signatures and Object Integrity Proofs, Fedify now supports Linked Data Signatures from this version, thus supporting all types of signature methods used in the fediverse. This makes Fedify an ActivityPub implementation with the best interoperability.

However, Fedify users don't need to do anything special to use Linked Data Signatures. If an incoming activity has Linked Data Signatures, it automatically verifies the signature, and all outgoing activities will have signatures in three formats: HTTP Signatures, Linked Data Signatures, and Object Integrity Proofs.

For more details, please refer to the related documentation.

Activity forwarding

From this version, you can forward activities received in the inbox to other actors using the InboxContext.forwardActivity() method.

At first glance, you might think that you could just resend an activity received in the inbox using the Context.sendActivity() method. However, if you do this, the original signature is removed before the activity is delivered to the inbox, and when sending it, the signature of the forwarding actor is attached instead, causing the receiving side of the forwarded activity to not trust it.

On the other hand, when using the InboxContext.forwardActivity() method, the activity is forwarded with the original signature preserved, avoiding this problem. (Of course, the original activity itself must be signed with Linked Data Signatures or Object Integrity Proofs.)

For more details, please refer to the related documentation.

Sending Delete(Application) on fedify inbox termination

From this version, fedify inbox will send a Delete(Application) activity to all peer servers it encountered when terminated. This is typically an activity sent when deleting an account, which will help prevent residual data related to temporary actors from remaining on other servers.

PostgreSQL drivers

The @fedify/postgres package, which implements PostgreSQL drivers for the KvStore and MessageQueue interfaces, has been released alongside this version.

The PostgreSQL driver is a backend that can be sufficiently used in production, especially recommended for projects already using PostgreSQL.

Additionally, an option to select the PostgreSQL driver has been added to the fedify init command.

Celebrating Fedify 1.0.0

With the release of version 1.0.0, Fedify will now maintain API backward compatibility as much as possible. (Of course, in the long term, there may be a 2.0.0 that breaks backward compatibility.) This should be good news for those who have been hesitant to use Fedify because there hasn't been a stable version until now!

So, hoping that more services will support ActivityPub in the future, I conclude this post!

#Fedify #ActivityPub #fedidev

@gekidasa Oh, you also need to remove the Redis service!

@gekidasa You can apply the new default configuration by redeploying the Hollo service and removing REDIS_URL from the environment variables!

#Hollo now uses PostgreSQL for caching and message queue by default (unless the REDIS_URL environment variable is present)! It's quite performant and scalable when it's compared to Redis, so we've decided to make it the default configuration.

#Hollo now can work without #Redis. It uses Redis as a cache and queue backend if the REDIS_URL environment variable is provided, but if not given, it caches in memory and works without a queue. This is an option to consider if you have a few following/followers.

#Hollo now implements FEP-e232 as well for incoming and outgoing activities!

https://hollo.social/@hollo/0191d68a-3ba7-7f2f-9836-fe8664fb51b0

#Hollo now has its own website with docs.

https://docs.hollo.social/

HolloについにMisskey/Threads風の引用機能が追加されました！使い方は簡単です。引用する投稿のリンクを投稿内容に貼り付けてください！ActivityPubの投稿（Article、Note、そしてQuestionに対応）のリンクを自動で認識して引用に変えてくれます。

ちなみに、Phanpyを使う場合は、ブーストアイコンを押すと出てくるQuoteボタンを使ってください。

#Hollo #Misskey #Threads #引用
QT: https://hollo.social/@hollo/0191d68a-3ba7-7f2f-9836-fe8664fb51b0 [参照]

one more niche software better than mastodon whee 🎉

RE: https://hollo.social/@hollo/0191d68a-3ba7-7f2f-9836-fe8664fb51b0

#Hollo finally has #Misskey/#Threads-style quotes! It's easy to use. Just paste the link to the post you want to quote into your post! It will automatically recognize a link to an ActivityPub post (supports Article, Note, and Question) and turn it into a quote.

FYI, if you're using #Phanpy, you can use the Quote button that appears when you press the boost icon!

https://hollo.social/@fedify/0191d67c-a300-786e-8395-2020ac47ebc7

@gekidasa Yes, redeploy to update!