#hollo

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to Hollo :hollo:'s post

みなさん、こんにちは! :hollo:

Holloの新しい計画について、みなさんのご意見をお聞かせください。

これまでHolloは、セルフホスティングを基本原則としてきました。これは今後も変わることなく維持され、ソースコードは引き続きAGPLv3ライセンスで公開されます。

最近、プロジェクトの持続可能な発展のため、Open Collective (@opencollective )を通じて一定額以上を定期的にご支援いただいている方々向けに、ホスティングサービスの提供を検討しています。

これは、技術的な部分を気にすることなくHolloを利用したい方のための追加オプションとなります。もちろん、現在のように自身でインストールして運用することも引き続き可能です。

引用させていただいた英語の投稿のアンケートにご参加ください!📊

  1. 良いアイデアです!ホスティングサービスを利用したいです。
  2. いいですね!私はセルフホスティングを続けますが、応援しています。
  3. 他の方法でサポートを増やすのが良いと思います。
  4. 現状通り純粋なセルフホスティングのままが良いです。

💭 追加のご意見やご提案がございましたら、コメントでお寄せください!

https://hollo.social/@hollo/01950344-1c55-7f43-8afc-b0a1ee8b4abf

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

everyone! :hollo:

We'd like to hear your thoughts on something we've been considering.

As you know, Hollo has always been focused on self-hosting—this won't change, and our source code will continue to be available under the AGPLv3 license.

We're exploring ways to make the project more sustainable, and we're considering offering a hosting service for those who regularly support us with a certain amount through @opencollective.

This would be an additional option for those who want to use Hollo without managing the technical aspects themselves. Of course, you'll still be able to self-host just like you do now.

What are your thoughts on this idea? Please vote below! 📊

💭 Have additional thoughts or suggestions? Feel free to share them in the comments!

OptionVoters
1️⃣ Great idea! I'd be interested in supporting and using the hosted service.25 (44%)
2️⃣ Sounds good! I'll stick to self-hosting but support the initiative.29 (51%)
3️⃣ I think we should explore other ways to increase support.2 (4%)
4️⃣ I prefer Hollo to remain purely self-hosted.1 (2%)
Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to Hollo :hollo:'s post

안녕하세요! :hollo:

Hollo의 새로운 계획에 대해 여러분의 의견을 듣고자 합니다.

지금까지 Hollo는 셀프 호스팅을 기본 원칙으로 삼아왔습니다. 이는 앞으로도 변함없이 유지될 것이며, 소스 코드는 계속해서 AGPLv3 라이선스로 공개됩니다.

최근 저희는 프로젝트의 지속 가능한 발전을 위해, Open Collective(@opencollective)를 통해 일정 금액 이상을 정기적으로 후원해 주시는 분들을 위한 호스팅 서비스 제공을 검토하고 있습니다.

이는 기술적인 부분에 신경 쓰지 않고도 Hollo를 이용하고 싶으신 분들을 위한 추가 옵션이 될 것입니다. 물론 지금처럼 직접 설치하고 운영하시는 것도 계속 가능합니다.

아래 인용된 영어 게시물의 투표에 참여해 주시면 감사하겠습니다! 📊

  1. 좋은 생각입니다! 호스팅 서비스를 이용하고 싶어요.
  2. 괜찮네요! 전 셀프 호스팅을 계속하지만 응원합니다.
  3. 다른 방식으로 후원을 늘리는 게 좋겠어요.
  4. 현재처럼 순수 셀프 호스팅으로 남았으면 좋겠어요.

💭 추가 의견이나 제안이 있으시다면 댓글로 남겨주세요!

https://hollo.social/@hollo/01950344-1c55-7f43-8afc-b0a1ee8b4abf

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

everyone! :hollo:

We'd like to hear your thoughts on something we've been considering.

As you know, Hollo has always been focused on self-hosting—this won't change, and our source code will continue to be available under the AGPLv3 license.

We're exploring ways to make the project more sustainable, and we're considering offering a hosting service for those who regularly support us with a certain amount through @opencollective.

This would be an additional option for those who want to use Hollo without managing the technical aspects themselves. Of course, you'll still be able to self-host just like you do now.

What are your thoughts on this idea? Please vote below! 📊

💭 Have additional thoughts or suggestions? Feel free to share them in the comments!

OptionVoters
1️⃣ Great idea! I'd be interested in supporting and using the hosted service.25 (44%)
2️⃣ Sounds good! I'll stick to self-hosting but support the initiative.29 (51%)
3️⃣ I think we should explore other ways to increase support.2 (4%)
4️⃣ I prefer Hollo to remain purely self-hosted.1 (2%)
Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

everyone! :hollo:

We'd like to hear your thoughts on something we've been considering.

As you know, Hollo has always been focused on self-hosting—this won't change, and our source code will continue to be available under the AGPLv3 license.

We're exploring ways to make the project more sustainable, and we're considering offering a hosting service for those who regularly support us with a certain amount through @opencollective.

This would be an additional option for those who want to use Hollo without managing the technical aspects themselves. Of course, you'll still be able to self-host just like you do now.

What are your thoughts on this idea? Please vote below! 📊

💭 Have additional thoughts or suggestions? Feel free to share them in the comments!

OptionVoters
1️⃣ Great idea! I'd be interested in supporting and using the hosted service.25 (44%)
2️⃣ Sounds good! I'll stick to self-hosting but support the initiative.29 (51%)
3️⃣ I think we should explore other ways to increase support.2 (4%)
4️⃣ I prefer Hollo to remain purely self-hosted.1 (2%)
Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

everyone! :hollo:

We'd like to hear your thoughts on something we've been considering.

As you know, Hollo has always been focused on self-hosting—this won't change, and our source code will continue to be available under the AGPLv3 license.

We're exploring ways to make the project more sustainable, and we're considering offering a hosting service for those who regularly support us with a certain amount through @opencollective.

This would be an additional option for those who want to use Hollo without managing the technical aspects themselves. Of course, you'll still be able to self-host just like you do now.

What are your thoughts on this idea? Please vote below! 📊

💭 Have additional thoughts or suggestions? Feel free to share them in the comments!

OptionVoters
1️⃣ Great idea! I'd be interested in supporting and using the hosted service.25 (44%)
2️⃣ Sounds good! I'll stick to self-hosting but support the initiative.29 (51%)
3️⃣ I think we should explore other ways to increase support.2 (4%)
4️⃣ I prefer Hollo to remain purely self-hosted.1 (2%)
Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

everyone! :hollo:

We'd like to hear your thoughts on something we've been considering.

As you know, Hollo has always been focused on self-hosting—this won't change, and our source code will continue to be available under the AGPLv3 license.

We're exploring ways to make the project more sustainable, and we're considering offering a hosting service for those who regularly support us with a certain amount through @opencollective.

This would be an additional option for those who want to use Hollo without managing the technical aspects themselves. Of course, you'll still be able to self-host just like you do now.

What are your thoughts on this idea? Please vote below! 📊

💭 Have additional thoughts or suggestions? Feel free to share them in the comments!

OptionVoters
1️⃣ Great idea! I'd be interested in supporting and using the hosted service.25 (44%)
2️⃣ Sounds good! I'll stick to self-hosting but support the initiative.29 (51%)
3️⃣ I think we should explore other ways to increase support.2 (4%)
4️⃣ I prefer Hollo to remain purely self-hosted.1 (2%)
Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to Hollo :hollo:'s post

みなさん、こんにちは! :hollo:

Holloの新しい計画について、みなさんのご意見をお聞かせください。

これまでHolloは、セルフホスティングを基本原則としてきました。これは今後も変わることなく維持され、ソースコードは引き続きAGPLv3ライセンスで公開されます。

最近、プロジェクトの持続可能な発展のため、Open Collective (@opencollective )を通じて一定額以上を定期的にご支援いただいている方々向けに、ホスティングサービスの提供を検討しています。

これは、技術的な部分を気にすることなくHolloを利用したい方のための追加オプションとなります。もちろん、現在のように自身でインストールして運用することも引き続き可能です。

引用させていただいた英語の投稿のアンケートにご参加ください!📊

  1. 良いアイデアです!ホスティングサービスを利用したいです。
  2. いいですね!私はセルフホスティングを続けますが、応援しています。
  3. 他の方法でサポートを増やすのが良いと思います。
  4. 現状通り純粋なセルフホスティングのままが良いです。

💭 追加のご意見やご提案がございましたら、コメントでお寄せください!

https://hollo.social/@hollo/01950344-1c55-7f43-8afc-b0a1ee8b4abf

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

everyone! :hollo:

We'd like to hear your thoughts on something we've been considering.

As you know, Hollo has always been focused on self-hosting—this won't change, and our source code will continue to be available under the AGPLv3 license.

We're exploring ways to make the project more sustainable, and we're considering offering a hosting service for those who regularly support us with a certain amount through @opencollective.

This would be an additional option for those who want to use Hollo without managing the technical aspects themselves. Of course, you'll still be able to self-host just like you do now.

What are your thoughts on this idea? Please vote below! 📊

💭 Have additional thoughts or suggestions? Feel free to share them in the comments!

OptionVoters
1️⃣ Great idea! I'd be interested in supporting and using the hosted service.25 (44%)
2️⃣ Sounds good! I'll stick to self-hosting but support the initiative.29 (51%)
3️⃣ I think we should explore other ways to increase support.2 (4%)
4️⃣ I prefer Hollo to remain purely self-hosted.1 (2%)
Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to Hollo :hollo:'s post

みなさん、こんにちは! :hollo:

Holloの新しい計画について、みなさんのご意見をお聞かせください。

これまでHolloは、セルフホスティングを基本原則としてきました。これは今後も変わることなく維持され、ソースコードは引き続きAGPLv3ライセンスで公開されます。

最近、プロジェクトの持続可能な発展のため、Open Collective (@opencollective )を通じて一定額以上を定期的にご支援いただいている方々向けに、ホスティングサービスの提供を検討しています。

これは、技術的な部分を気にすることなくHolloを利用したい方のための追加オプションとなります。もちろん、現在のように自身でインストールして運用することも引き続き可能です。

引用させていただいた英語の投稿のアンケートにご参加ください!📊

  1. 良いアイデアです!ホスティングサービスを利用したいです。
  2. いいですね!私はセルフホスティングを続けますが、応援しています。
  3. 他の方法でサポートを増やすのが良いと思います。
  4. 現状通り純粋なセルフホスティングのままが良いです。

💭 追加のご意見やご提案がございましたら、コメントでお寄せください!

https://hollo.social/@hollo/01950344-1c55-7f43-8afc-b0a1ee8b4abf

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

everyone! :hollo:

We'd like to hear your thoughts on something we've been considering.

As you know, Hollo has always been focused on self-hosting—this won't change, and our source code will continue to be available under the AGPLv3 license.

We're exploring ways to make the project more sustainable, and we're considering offering a hosting service for those who regularly support us with a certain amount through @opencollective.

This would be an additional option for those who want to use Hollo without managing the technical aspects themselves. Of course, you'll still be able to self-host just like you do now.

What are your thoughts on this idea? Please vote below! 📊

💭 Have additional thoughts or suggestions? Feel free to share them in the comments!

OptionVoters
1️⃣ Great idea! I'd be interested in supporting and using the hosted service.25 (44%)
2️⃣ Sounds good! I'll stick to self-hosting but support the initiative.29 (51%)
3️⃣ I think we should explore other ways to increase support.2 (4%)
4️⃣ I prefer Hollo to remain purely self-hosted.1 (2%)
Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to Hollo :hollo:'s post

안녕하세요! :hollo:

Hollo의 새로운 계획에 대해 여러분의 의견을 듣고자 합니다.

지금까지 Hollo는 셀프 호스팅을 기본 원칙으로 삼아왔습니다. 이는 앞으로도 변함없이 유지될 것이며, 소스 코드는 계속해서 AGPLv3 라이선스로 공개됩니다.

최근 저희는 프로젝트의 지속 가능한 발전을 위해, Open Collective(@opencollective)를 통해 일정 금액 이상을 정기적으로 후원해 주시는 분들을 위한 호스팅 서비스 제공을 검토하고 있습니다.

이는 기술적인 부분에 신경 쓰지 않고도 Hollo를 이용하고 싶으신 분들을 위한 추가 옵션이 될 것입니다. 물론 지금처럼 직접 설치하고 운영하시는 것도 계속 가능합니다.

아래 인용된 영어 게시물의 투표에 참여해 주시면 감사하겠습니다! 📊

  1. 좋은 생각입니다! 호스팅 서비스를 이용하고 싶어요.
  2. 괜찮네요! 전 셀프 호스팅을 계속하지만 응원합니다.
  3. 다른 방식으로 후원을 늘리는 게 좋겠어요.
  4. 현재처럼 순수 셀프 호스팅으로 남았으면 좋겠어요.

💭 추가 의견이나 제안이 있으시다면 댓글로 남겨주세요!

https://hollo.social/@hollo/01950344-1c55-7f43-8afc-b0a1ee8b4abf

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

everyone! :hollo:

We'd like to hear your thoughts on something we've been considering.

As you know, Hollo has always been focused on self-hosting—this won't change, and our source code will continue to be available under the AGPLv3 license.

We're exploring ways to make the project more sustainable, and we're considering offering a hosting service for those who regularly support us with a certain amount through @opencollective.

This would be an additional option for those who want to use Hollo without managing the technical aspects themselves. Of course, you'll still be able to self-host just like you do now.

What are your thoughts on this idea? Please vote below! 📊

💭 Have additional thoughts or suggestions? Feel free to share them in the comments!

OptionVoters
1️⃣ Great idea! I'd be interested in supporting and using the hosted service.25 (44%)
2️⃣ Sounds good! I'll stick to self-hosting but support the initiative.29 (51%)
3️⃣ I think we should explore other ways to increase support.2 (4%)
4️⃣ I prefer Hollo to remain purely self-hosted.1 (2%)
Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

everyone! :hollo:

We'd like to hear your thoughts on something we've been considering.

As you know, Hollo has always been focused on self-hosting—this won't change, and our source code will continue to be available under the AGPLv3 license.

We're exploring ways to make the project more sustainable, and we're considering offering a hosting service for those who regularly support us with a certain amount through @opencollective.

This would be an additional option for those who want to use Hollo without managing the technical aspects themselves. Of course, you'll still be able to self-host just like you do now.

What are your thoughts on this idea? Please vote below! 📊

💭 Have additional thoughts or suggestions? Feel free to share them in the comments!

OptionVoters
1️⃣ Great idea! I'd be interested in supporting and using the hosted service.25 (44%)
2️⃣ Sounds good! I'll stick to self-hosting but support the initiative.29 (51%)
3️⃣ I think we should explore other ways to increase support.2 (4%)
4️⃣ I prefer Hollo to remain purely self-hosted.1 (2%)
Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to Hollo :hollo:'s post

0.5.0이 릴리스되었습니다! 이번 업데이트는 여러분의 Hollo 사용 경험을 더욱 개선하는 다양한 변화를 담고 있습니다.

게시물의 공유 수와 좋아요 수를 더 정확하게 집계하도록 개선했습니다. 이제 각 게시물의 공유 수와 좋아요 수가 정확하게 유지되며, 다른 서버로 공유되었을 때도 이 수치가 올바르게 보존됩니다.

@yamanoku 님의 기여로 프로필 페이지가 크게 개선되었습니다:

  • 이전 게시물뿐 아니라 최신 게시물로도 이동할 수 있는 페이지네이션
  • 대체 텍스트를 활용한 이미지 접근성 개선
  • 화면 크기가 작아져도 커스텀 필드가 잘 표시되도록 수정

이 밖에도 시스템의 라이트·다크 모드에 따라 파비콘이 자동으로 전환되며, 새로운 ALLOW_HTML 환경 변수로 Markdown 안에 HTML 사용이 가능해졌습니다(보안을 위해 허용되는 HTML 요소는 제한됩니다).

또한 뮤트와 차단 목록을 위한 API 엔드포인트를 추가하여 Mastodon API 호환성을 강화했습니다.

S3를 사용하시는 분들은 이제 S3_REGION 환경 변수 설정이 필수가 되었으니 참고해 주시기 바랍니다.

0.5.0으로 업데이트하는 방법:

  • Docker 사용자: docker pull ghcr.io/fedify-dev/hollo:0.5.0
  • 수동 설치 사용자: git pull origin stablepnpm install
  • Railway 사용자: Railway 대시보드에서 서비스 재배포

전체 변경 사항: https://github.com/fedify-dev/hollo/releases/tag/0.5.0.

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to Hollo :hollo:'s post

0.5.0をリリースしました!今回のアップデートでは、皆様のHollo体験をより良くする様々な改善が含まれています。

投稿のシェア数といいね数の集計がより正確になりました。各投稿のシェア数といいね数が正確に維持され、他のサーバーでシェアされた場合でもこれらの数値が適切に保持されるようになりました。

@yamanoku さんの貢献により、プロフィールページが大幅に改善されました:

  • 新しい投稿へ移動できる逆方向のページネーション機能を追加
  • alt属性を活用した画像のアクセシビリティ向上
  • 画面サイズが小さくなってもカスタムフィールドが正しく表示されるように修正

その他、システムのライト/ダークモードに応じてファビコンが自動的に切り替わるようになり、新しいALLOW_HTML環境変数でMarkdown内でのHTML使用が可能になりました。(セキュリティのため、使用可能なHTML要素は制限されています)

また、ミュートとブロックリストのためのAPIエンドポイントを追加し、Mastodon APIとの互換性を強化しました。

S3をご利用の方は、S3_REGION環境変数の設定が必須となりましたのでご注意ください。

0.5.0へのアップデート方法:

  • Dockerをご利用の場合:docker pull ghcr.io/fedify-dev/hollo:0.5.0
  • 手動インストールの場合:git pull origin stableの後pnpm installを実行
  • Railwayをご利用の場合:Railwayダッシュボードからサービスを再デプロイ

変更の詳細:https://github.com/fedify-dev/hollo/releases/tag/0.5.0.

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to Hollo :hollo:'s post

0.5.0をリリースしました!今回のアップデートでは、皆様のHollo体験をより良くする様々な改善が含まれています。

投稿のシェア数といいね数の集計がより正確になりました。各投稿のシェア数といいね数が正確に維持され、他のサーバーでシェアされた場合でもこれらの数値が適切に保持されるようになりました。

@yamanoku さんの貢献により、プロフィールページが大幅に改善されました:

  • 新しい投稿へ移動できる逆方向のページネーション機能を追加
  • alt属性を活用した画像のアクセシビリティ向上
  • 画面サイズが小さくなってもカスタムフィールドが正しく表示されるように修正

その他、システムのライト/ダークモードに応じてファビコンが自動的に切り替わるようになり、新しいALLOW_HTML環境変数でMarkdown内でのHTML使用が可能になりました。(セキュリティのため、使用可能なHTML要素は制限されています)

また、ミュートとブロックリストのためのAPIエンドポイントを追加し、Mastodon APIとの互換性を強化しました。

S3をご利用の方は、S3_REGION環境変数の設定が必須となりましたのでご注意ください。

0.5.0へのアップデート方法:

  • Dockerをご利用の場合:docker pull ghcr.io/fedify-dev/hollo:0.5.0
  • 手動インストールの場合:git pull origin stableの後pnpm installを実行
  • Railwayをご利用の場合:Railwayダッシュボードからサービスを再デプロイ

変更の詳細:https://github.com/fedify-dev/hollo/releases/tag/0.5.0.

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to Hollo :hollo:'s post

0.5.0をリリースしました!今回のアップデートでは、皆様のHollo体験をより良くする様々な改善が含まれています。

投稿のシェア数といいね数の集計がより正確になりました。各投稿のシェア数といいね数が正確に維持され、他のサーバーでシェアされた場合でもこれらの数値が適切に保持されるようになりました。

@yamanoku さんの貢献により、プロフィールページが大幅に改善されました:

  • 新しい投稿へ移動できる逆方向のページネーション機能を追加
  • alt属性を活用した画像のアクセシビリティ向上
  • 画面サイズが小さくなってもカスタムフィールドが正しく表示されるように修正

その他、システムのライト/ダークモードに応じてファビコンが自動的に切り替わるようになり、新しいALLOW_HTML環境変数でMarkdown内でのHTML使用が可能になりました。(セキュリティのため、使用可能なHTML要素は制限されています)

また、ミュートとブロックリストのためのAPIエンドポイントを追加し、Mastodon APIとの互換性を強化しました。

S3をご利用の方は、S3_REGION環境変数の設定が必須となりましたのでご注意ください。

0.5.0へのアップデート方法:

  • Dockerをご利用の場合:docker pull ghcr.io/fedify-dev/hollo:0.5.0
  • 手動インストールの場合:git pull origin stableの後pnpm installを実行
  • Railwayをご利用の場合:Railwayダッシュボードからサービスを再デプロイ

変更の詳細:https://github.com/fedify-dev/hollo/releases/tag/0.5.0.

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to Hollo :hollo:'s post

0.5.0이 릴리스되었습니다! 이번 업데이트는 여러분의 Hollo 사용 경험을 더욱 개선하는 다양한 변화를 담고 있습니다.

게시물의 공유 수와 좋아요 수를 더 정확하게 집계하도록 개선했습니다. 이제 각 게시물의 공유 수와 좋아요 수가 정확하게 유지되며, 다른 서버로 공유되었을 때도 이 수치가 올바르게 보존됩니다.

@yamanoku 님의 기여로 프로필 페이지가 크게 개선되었습니다:

  • 이전 게시물뿐 아니라 최신 게시물로도 이동할 수 있는 페이지네이션
  • 대체 텍스트를 활용한 이미지 접근성 개선
  • 화면 크기가 작아져도 커스텀 필드가 잘 표시되도록 수정

이 밖에도 시스템의 라이트·다크 모드에 따라 파비콘이 자동으로 전환되며, 새로운 ALLOW_HTML 환경 변수로 Markdown 안에 HTML 사용이 가능해졌습니다(보안을 위해 허용되는 HTML 요소는 제한됩니다).

또한 뮤트와 차단 목록을 위한 API 엔드포인트를 추가하여 Mastodon API 호환성을 강화했습니다.

S3를 사용하시는 분들은 이제 S3_REGION 환경 변수 설정이 필수가 되었으니 참고해 주시기 바랍니다.

0.5.0으로 업데이트하는 방법:

  • Docker 사용자: docker pull ghcr.io/fedify-dev/hollo:0.5.0
  • 수동 설치 사용자: git pull origin stablepnpm install
  • Railway 사용자: Railway 대시보드에서 서비스 재배포

전체 변경 사항: https://github.com/fedify-dev/hollo/releases/tag/0.5.0.

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

0.5.0 has been released! This update brings several improvements to make your Hollo experience even better.

We've enhanced the accuracy of sharing and liking counts, giving you a clearer picture of post engagement. Posts now maintain precise counts of shares and likes, which persist even when shared across different servers.

Thanks to contributions from @yamanoku, the profile page has received several enhancements:

  • You can now navigate to newer posts with backward pagination
  • Images are more accessible with improved alt text handling
  • Custom fields display better on smaller screens

The favicon now automatically adapts to your light/dark mode preference, and you can enable raw HTML in Markdown using the new ALLOW_HTML environment variable (with secure limitations on allowed HTML elements).

We've also expanded our Mastodon API compatibility by adding endpoints for muted and blocked accounts, making it easier to manage your social boundaries.

Important note for S3 users: The S3_REGION environment variable is now required when using S3 storage.

To update to 0.5.0:

  • Docker users: docker pull ghcr.io/fedify-dev/hollo:0.5.0
  • Manual installation: git pull origin stable and pnpm install
  • Railway users: Redeploy your service from the Railway dashboard

Full changelog: https://github.com/fedify-dev/hollo/releases/tag/0.5.0.

Jeff Sikes's avatar
Jeff Sikes

@box464@mastodon.social

Had some fun today installing @hollo because you can never have enough fediverse accounts, right? I'm definitely not avoiding the real world with this distraction. 👀

Hollo is a single / low user platform for the fediverse. It runs on the @fedify framework and supports quote posts, markdown, and emoji reactions.

I went off the beaten path a bit and customized the composer file. Here's my notes on the install process.

box464.com/posts/hollo-install/

Jeff Sikes's avatar
Jeff Sikes

@box464@mastodon.social

This has been on my weekend project list for a long while. Setup a @hollo instance in my homelab. NGINX Proxy Manager, Portainer, External Storage in the mix. Can’t wait to tinker around with it!

hollo.box464.social/@hollo464

Jeff Sikes's avatar
Jeff Sikes

@box464@mastodon.social

Had some fun today installing @hollo because you can never have enough fediverse accounts, right? I'm definitely not avoiding the real world with this distraction. 👀

Hollo is a single / low user platform for the fediverse. It runs on the @fedify framework and supports quote posts, markdown, and emoji reactions.

I went off the beaten path a bit and customized the composer file. Here's my notes on the install process.

box464.com/posts/hollo-install/

Jeff Sikes's avatar
Jeff Sikes

@box464@mastodon.social

This has been on my weekend project list for a long while. Setup a @hollo instance in my homelab. NGINX Proxy Manager, Portainer, External Storage in the mix. Can’t wait to tinker around with it!

hollo.box464.social/@hollo464

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to Hollo :hollo:'s post

supports 's full spec with Hollo's own extended syntax (mentions and hashtags).

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to Hollo :hollo:'s post

supports 's full spec with Hollo's own extended syntax (mentions and hashtags).

fedicat's avatar
fedicat

@fedicat@pc.cafe

quote posts are supported on platforms that support quote posts ( )

iphone screenshot of the context menu for a post showing a quote option in a link submenua post composer titled Quote followed by a snippet of the quoted post then the visibility then the text composition area prefilled with a mention of the quoted author a home timeline showing the published quote post with the quoted list and under the author mention and in its own border

Detected text:

7:32Hometechnicattechnicattesting quote postfrom @ycombinatorRT:https://rss-mstdn.studiofreesia.com/users/ycombinator/statuses/113942146481288788@ycombinator@rss-mstdn.studiofreesia.com7:26 PMHacker News (bot)ycombinator@rss-mstdn.studiofreesia.com2:46 PMThe Cantonese Scrolls (EE) - A CantoneseLanguage Learning Mental RPGhttps://cantoscrolls.com/#ycombinator #Cantonese #Chinese#Preservation #Language #Education#Culture #Identity #Traditional #Game#RPG #Mental #Mind#cantonese#chinese#culture#education#game#identity#language#mental#mind#preservation#rpg#traditional#combinator
fedicat's avatar
fedicat

@fedicat@pc.cafe

quote posts are supported on platforms that support quote posts ( )

iphone screenshot of the context menu for a post showing a quote option in a link submenua post composer titled Quote followed by a snippet of the quoted post then the visibility then the text composition area prefilled with a mention of the quoted author a home timeline showing the published quote post with the quoted list and under the author mention and in its own border

Detected text:

7:32Hometechnicattechnicattesting quote postfrom @ycombinatorRT:https://rss-mstdn.studiofreesia.com/users/ycombinator/statuses/113942146481288788@ycombinator@rss-mstdn.studiofreesia.com7:26 PMHacker News (bot)ycombinator@rss-mstdn.studiofreesia.com2:46 PMThe Cantonese Scrolls (EE) - A CantoneseLanguage Learning Mental RPGhttps://cantoscrolls.com/#ycombinator #Cantonese #Chinese#Preservation #Language #Education#Culture #Identity #Traditional #Game#RPG #Mental #Mind#cantonese#chinese#culture#education#game#identity#language#mental#mind#preservation#rpg#traditional#combinator
Markus 🌱:fosse:'s avatar
Markus 🌱:fosse:

@markus@skvip.lol

Eg har nett støtta @fedify ! Dei har fleire kule prosjekt. @markus@prosa.skvip.lol køyrer på deira teneste @hollo.

English:
I've just contributed to They have several cool projects. @markus@prosa.skvip.lol runs on their service .

opencollective.com/fedify

Markus 🌱:fosse:'s avatar
Markus 🌱:fosse:

@markus@skvip.lol

Eg har nett støtta @fedify ! Dei har fleire kule prosjekt. @markus@prosa.skvip.lol køyrer på deira teneste @hollo.

English:
I've just contributed to They have several cool projects. @markus@prosa.skvip.lol runs on their service .

opencollective.com/fedify

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to Hollo :hollo:'s post

저장소가 @dahlia/hollo에서 @fedify-dev/hollo로 이전되었습니다. 이에 따라 이미지 레지스트리도 ghcr.io/dahlia/hollo에서 ghcr.io/fedify-dev/hollo로 이전되었습니다.

기존 이미지 레지스트리는 계속 접근 가능하지만, 새로운 태그는 더 이상 추가되지 않을 예정입니다. Hollo를 사용 중이신 모든 분들은 새로운 레지스트리 주소로 업데이트해 주시기 바랍니다.

Docker 설정을 다음과 같이 변경해 주세요:

  • 기존 이미지 주소: ghcr.io/dahlia/hollo:latest
  • 새 이미지 주소: ghcr.io/fedify-dev/hollo:latest

이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다. :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

Fedify: an ActivityPub server framework's avatar
Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

yamanoku's avatar
yamanoku

@yamanoku@hollo.yamanoku.net

HolloをRailwayにデプロイする時の作業ログをZenn Scrapsにまとめました。躓いた個所もあったのでこれからデプロイしてやってみたい人に届け~ https://zenn.dev/yamanoku/scraps/546b887da013d9

yamanoku's avatar
yamanoku

@yamanoku@hollo.yamanoku.net

HolloをRailwayにデプロイする時の作業ログをZenn Scrapsにまとめました。躓いた個所もあったのでこれからデプロイしてやってみたい人に届け~ https://zenn.dev/yamanoku/scraps/546b887da013d9

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

The repository has moved from @dahlia/hollo to @fedify-dev/hollo! Along with this move, our image registry has also been relocated from ghcr.io/dahlia/hollo to ghcr.io/fedify-dev/hollo.

While the old image registry will remain accessible, it won't receive any new tags. We recommend all Hollo users to update their Docker image references to the new registry address.

To update your Docker configurations, please change:

  • From: ghcr.io/dahlia/hollo:latest
  • To: ghcr.io/fedify-dev/hollo:latest

The migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

Fedify: an ActivityPub server framework's avatar
Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to Hollo :hollo:'s post

저장소가 @dahlia/hollo에서 @fedify-dev/hollo로 이전되었습니다. 이에 따라 이미지 레지스트리도 ghcr.io/dahlia/hollo에서 ghcr.io/fedify-dev/hollo로 이전되었습니다.

기존 이미지 레지스트리는 계속 접근 가능하지만, 새로운 태그는 더 이상 추가되지 않을 예정입니다. Hollo를 사용 중이신 모든 분들은 새로운 레지스트리 주소로 업데이트해 주시기 바랍니다.

Docker 설정을 다음과 같이 변경해 주세요:

  • 기존 이미지 주소: ghcr.io/dahlia/hollo:latest
  • 새 이미지 주소: ghcr.io/fedify-dev/hollo:latest

이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다. :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

Fedify: an ActivityPub server framework's avatar
Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

The repository has moved from @dahlia/hollo to @fedify-dev/hollo! Along with this move, our image registry has also been relocated from ghcr.io/dahlia/hollo to ghcr.io/fedify-dev/hollo.

While the old image registry will remain accessible, it won't receive any new tags. We recommend all Hollo users to update their Docker image references to the new registry address.

To update your Docker configurations, please change:

  • From: ghcr.io/dahlia/hollo:latest
  • To: ghcr.io/fedify-dev/hollo:latest

The migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

Fedify: an ActivityPub server framework's avatar
Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to Hollo :hollo:'s post

Holloのリポジトリが@dahlia/holloから@fedify-dev/holloに移行いたしました。これに伴い、Dockerイメージレジストリもghcr.io/dahlia/holloからghcr.io/fedify-dev/holloに移行しております。

旧イメージレジストリは引き続きアクセス可能ですが、新しいタグの追加は行われません。Holloをご利用の皆様には、新しいレジストリアドレスへの更新をお願いいたします。

Dockerの設定を以下のように更新してください:

  • 旧アドレス:ghcr.io/dahlia/hollo:latest
  • 新アドレス:ghcr.io/fedify-dev/hollo:latest

この移行はプロジェクトのより良い運営と継続的な開発のために行われました。円滑な移行にご協力いただき、誠にありがとうございます。 :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

Fedify: an ActivityPub server framework's avatar
Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to Hollo :hollo:'s post

Holloのリポジトリが@dahlia/holloから@fedify-dev/holloに移行いたしました。これに伴い、Dockerイメージレジストリもghcr.io/dahlia/holloからghcr.io/fedify-dev/holloに移行しております。

旧イメージレジストリは引き続きアクセス可能ですが、新しいタグの追加は行われません。Holloをご利用の皆様には、新しいレジストリアドレスへの更新をお願いいたします。

Dockerの設定を以下のように更新してください:

  • 旧アドレス:ghcr.io/dahlia/hollo:latest
  • 新アドレス:ghcr.io/fedify-dev/hollo:latest

この移行はプロジェクトのより良い運営と継続的な開発のために行われました。円滑な移行にご協力いただき、誠にありがとうございます。 :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

Fedify: an ActivityPub server framework's avatar
Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to Hollo :hollo:'s post

저장소가 @dahlia/hollo에서 @fedify-dev/hollo로 이전되었습니다. 이에 따라 이미지 레지스트리도 ghcr.io/dahlia/hollo에서 ghcr.io/fedify-dev/hollo로 이전되었습니다.

기존 이미지 레지스트리는 계속 접근 가능하지만, 새로운 태그는 더 이상 추가되지 않을 예정입니다. Hollo를 사용 중이신 모든 분들은 새로운 레지스트리 주소로 업데이트해 주시기 바랍니다.

Docker 설정을 다음과 같이 변경해 주세요:

  • 기존 이미지 주소: ghcr.io/dahlia/hollo:latest
  • 새 이미지 주소: ghcr.io/fedify-dev/hollo:latest

이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다. :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

Fedify: an ActivityPub server framework's avatar
Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to Hollo :hollo:'s post

Holloのリポジトリが@dahlia/holloから@fedify-dev/holloに移行いたしました。これに伴い、Dockerイメージレジストリもghcr.io/dahlia/holloからghcr.io/fedify-dev/holloに移行しております。

旧イメージレジストリは引き続きアクセス可能ですが、新しいタグの追加は行われません。Holloをご利用の皆様には、新しいレジストリアドレスへの更新をお願いいたします。

Dockerの設定を以下のように更新してください:

  • 旧アドレス:ghcr.io/dahlia/hollo:latest
  • 新アドレス:ghcr.io/fedify-dev/hollo:latest

この移行はプロジェクトのより良い運営と継続的な開発のために行われました。円滑な移行にご協力いただき、誠にありがとうございます。 :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

Fedify: an ActivityPub server framework's avatar
Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

The repository has moved from @dahlia/hollo to @fedify-dev/hollo! Along with this move, our image registry has also been relocated from ghcr.io/dahlia/hollo to ghcr.io/fedify-dev/hollo.

While the old image registry will remain accessible, it won't receive any new tags. We recommend all Hollo users to update their Docker image references to the new registry address.

To update your Docker configurations, please change:

  • From: ghcr.io/dahlia/hollo:latest
  • To: ghcr.io/fedify-dev/hollo:latest

The migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

Fedify: an ActivityPub server framework's avatar
Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

In related news, has also released updates: 0.3.6 & 0.4.4. Update now!

https://hollo.social/@fedify/01948487-87b2-709d-953f-8799b78433ed

Fedify: an ActivityPub server framework's avatar
Fedify: an ActivityPub server framework

@fedify@hollo.social

We have released updates (1.0.14, 1.1.11, 1.2.11, 1.3.4) to address CVE-2025-23221, a in 's implementation. We recommend all users update to the latest version of their respective release series immediately.

The Vulnerability

A security researcher identified multiple security issues in Fedify's lookupWebFinger() function that could be exploited to:

  • Perform denial of service attacks through infinite redirect loops
  • Execute server-side request forgery () attacks via redirects to private network addresses
  • Access unintended URL schemes through redirect manipulation

Fixed Versions

  • 1.3.x series: Update to 1.3.4
  • 1.2.x series: Update to 1.2.11
  • 1.1.x series: Update to 1.1.11
  • 1.0.x series: Update to 1.0.14

Changes

The security updates implement the following fixes:

  1. Added a maximum redirect limit (5) to prevent infinite redirect loops
  2. Restricted redirects to only follow the same scheme as the original request (HTTP/HTTPS)
  3. Blocked redirects to private network addresses to prevent SSRF attacks

How to Update

To update to the latest secure version:

# For npm users
npm update @fedify/fedify

# For Deno users
deno add jsr:@fedify/fedify

We thank the security researcher who responsibly disclosed this vulnerability, allowing us to address these issues promptly.

For more details about this vulnerability, please refer to our security advisory.


If you have any questions or concerns, please don't hesitate to reach out through our GitHub Discussions, join our Matrix chat space, or our Discord server.

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

Once we have a @fedify org account, we'll be moving 's repository there as well.

https://hollo.social/@fedify/01949657-262f-78f4-a9a0-97643682ea70

Fedify: an ActivityPub server framework's avatar
Fedify: an ActivityPub server framework

@fedify@hollo.social

We're planning to move our GitHub repository to an organization account for better project management. We've requested GitHub support to help us acquire the inactive @fedify username for this purpose. (The attached screenshot is our formal request to GitHub support.)

If we successfully acquire @fedify, that will be our new organization name. If not, we'll choose an alternative name. We'll keep you updated on the progress!

In any case, we'll ensure a smooth transition with proper redirects from the current repository. Stay tuned for updates!

Dear GitHub Support,

I am writing to request the takeover of the inactive GitHub username “@fedify”. This username is currently held by an account that shows no activity since its creation—no repositories, contributions, or any other engagement.

I am the maintainer of the Fedify project (https://github.com/dahlia/fedify), which is an open source ActivityPub server framework. We would like to use this username as an organization account to host our project and related repositories.

The reasons for this request are:

1. The current “@fedify” account has been completely inactive with no public contributions or repositories
2. The name directly relates to our project's name and purpose
3. We need an organization account to better manage our growing open source project
4. The username would help us maintain consistent branding across different platforms (@fedify on npm, JSR, etc.)

If possible, we would greatly appreciate if you could help us acquire this username. We believe this would benefit the GitHub community by putting the inactive username to active use for an open source project.

Please let me know if you need any additional information to process this request.

Thank you for your time and consideration.

Best regards,
Hong Minhee (@dahlia)
洪 民憙 (Hong Minhee)'s avatar
洪 民憙 (Hong Minhee)

@hongminhee@hollo.social

If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!

https://github.com/sponsors/dahlia

洪 民憙 (Hong Minhee)'s avatar
洪 民憙 (Hong Minhee)

@hongminhee@hollo.social · Reply to 洪 民憙 (Hong Minhee)'s post

제 프로젝트인 @fedify, @hollo, @botkit ()開發(개발)後援(후원)하고 싶으신 분들께서는, GitHub에서 제 스폰서가 되어 주세요!

https://github.com/sponsors/dahlia

洪 民憙 (Hong Minhee)'s avatar
洪 民憙 (Hong Minhee)

@hongminhee@hollo.social · Reply to 洪 民憙 (Hong Minhee)'s post

@fedify」や「@hollo」や「@botkit」の開発を支援したい方は、GitHubでスポンサーになってください!

https://github.com/sponsors/dahlia

洪 民憙 (Hong Minhee)'s avatar
洪 民憙 (Hong Minhee)

@hongminhee@hollo.social

If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!

https://github.com/sponsors/dahlia

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to Hollo :hollo:'s post

この件に関連して、Holloもセキュリティアップデートをリリースしました。0.3.6または0.4.4バージョンに今すぐアップデートしてください!

https://hollo.social/@fedify/0194848e-7cac-7af3-941b-c93999a51274

Fedify: an ActivityPub server framework's avatar
Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

FedifyのWebFinger実装における脆弱性CVE-2025-23221に対するセキュリティアップデート(1.0.141.1.111.2.111.3.4)をリリースいたしました。すべてのユーザー様におかれましては、お使いのバージョンに応じた最新版への速やかなアップデートを推奨いたします。

脆弱性の詳細

セキュリティ研究者により、FedifyのlookupWebFinger()関数において以下のセキュリティ上の問題が発見されました:

  • 無限リダイレクトループによるサービス拒否攻撃(DoS)の可能性
  • プライベートネットワークアドレスへのリダイレクトを利用したSSRF(サーバーサイドリクエストフォージェリ)攻撃の可能性
  • リダイレクト操作による意図しないURLスキームへのアクセスの可能性

修正されたバージョン

  • 1.3.xシリーズ:1.3.4へアップデート
  • 1.2.xシリーズ:1.2.11へアップデート
  • 1.1.xシリーズ:1.1.11へアップデート
  • 1.0.xシリーズ:1.0.14へアップデート

変更内容

本セキュリティアップデートでは、以下の修正が実施されました:

  1. 無限リダイレクトループを防ぐため、最大リダイレクト回数(5回)の制限を導入
  2. 元のリクエストと同じスキーム(HTTP/HTTPS)のみにリダイレクトを制限
  3. SSRFを防止するため、プライベートネットワークアドレスへのリダイレクトをブロック

アップデート方法

以下のコマンドで最新のセキュアバージョンにアップデートできます:

# npmユーザーの場合
npm update @fedify/fedify

# Denoユーザーの場合
deno add jsr:@fedify/fedify

この脆弱性を責任を持って報告していただいたセキュリティ研究者の方に感謝申し上げます。迅速な対応が可能となりました。

本脆弱性の詳細については、セキュリティ勧告をご参照ください。


ご質問やご懸念がございましたら、GitHub DiscussionsMatrixチャットスペース、またはDiscordサーバーまでお気軽にご連絡ください。

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

In related news, has also released updates: 0.3.6 & 0.4.4. Update now!

https://hollo.social/@fedify/01948487-87b2-709d-953f-8799b78433ed

Fedify: an ActivityPub server framework's avatar
Fedify: an ActivityPub server framework

@fedify@hollo.social

We have released updates (1.0.14, 1.1.11, 1.2.11, 1.3.4) to address CVE-2025-23221, a in 's implementation. We recommend all users update to the latest version of their respective release series immediately.

The Vulnerability

A security researcher identified multiple security issues in Fedify's lookupWebFinger() function that could be exploited to:

  • Perform denial of service attacks through infinite redirect loops
  • Execute server-side request forgery () attacks via redirects to private network addresses
  • Access unintended URL schemes through redirect manipulation

Fixed Versions

  • 1.3.x series: Update to 1.3.4
  • 1.2.x series: Update to 1.2.11
  • 1.1.x series: Update to 1.1.11
  • 1.0.x series: Update to 1.0.14

Changes

The security updates implement the following fixes:

  1. Added a maximum redirect limit (5) to prevent infinite redirect loops
  2. Restricted redirects to only follow the same scheme as the original request (HTTP/HTTPS)
  3. Blocked redirects to private network addresses to prevent SSRF attacks

How to Update

To update to the latest secure version:

# For npm users
npm update @fedify/fedify

# For Deno users
deno add jsr:@fedify/fedify

We thank the security researcher who responsibly disclosed this vulnerability, allowing us to address these issues promptly.

For more details about this vulnerability, please refer to our security advisory.


If you have any questions or concerns, please don't hesitate to reach out through our GitHub Discussions, join our Matrix chat space, or our Discord server.

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to Hollo :hollo:'s post

이와 관련하여, 역시 업데이트가 이뤄졌습니다. 0.3.6 또는 0.4.4 버전으로 바로 업데이트하시기 바랍니다!

https://hollo.social/@fedify/0194848b-3b9e-7da1-b631-c011db2f4c43

Fedify: an ActivityPub server framework's avatar
Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

프레임워크의 구현에서 발견된 보안 취약점 CVE-2025-23221을 해결하기 위한 보안 업데이트(1.0.14, 1.1.11, 1.2.11, 1.3.4)를 배포했습니다. 모든 사용자께서는 각자 사용 중인 버전에 해당하는 최신 버전으로 즉시 업데이트하시기를 권장합니다.

취약점 내용

보안 연구자가 Fedify의 lookupWebFinger() 함수에서 다음과 같은 보안 문제점들을 발견했습니다:

  • 무한 리다이렉트 루프를 통한 서비스 거부 공격 가능
  • 내부 네트워크 주소로의 리다이렉트를 통한 SSRF (서버측 요청 위조) 공격 가능
  • 리다이렉트 조작을 통한 의도하지 않은 URL 스킴 접근 가능

수정된 버전

  • 1.3.x 시리즈: 1.3.4로 업데이트
  • 1.2.x 시리즈: 1.2.11로 업데이트
  • 1.1.x 시리즈: 1.1.11로 업데이트
  • 1.0.x 시리즈: 1.0.14로 업데이트

변경 사항

이번 보안 업데이트에는 다음과 같은 수정 사항이 포함되어 있습니다:

  1. 무한 리다이렉트 루프를 방지하기 위해 최대 리다이렉트 횟수 제한(5회) 도입
  2. 원래 요청과 동일한 스킴(HTTP/HTTPS)으로만 리다이렉트 허용하도록 제한
  3. SSRF 공격 방지를 위해 내부 네트워크 주소로의 리다이렉트 차단

업데이트 방법

다음 명령어로 최신 보안 버전으로 업데이트하실 수 있습니다:

# npm 사용자의 경우
npm update @fedify/fedify

# Deno 사용자의 경우
deno add jsr:@fedify/fedify

이 취약점을 책임감 있게 보고해 주신 보안 연구자께 감사드립니다. 덕분에 신속하게 문제를 해결할 수 있었습니다.

이 취약점에 대한 자세한 내용은 보안 권고문을 참고해 주시기 바랍니다.


문의 사항이나 우려 사항이 있으시다면 GitHub DiscussionsMatrix 채팅방, 또는 Discord 서버를 통해 언제든 연락해 주시기 바랍니다.

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

In related news, has also released updates: 0.3.6 & 0.4.4. Update now!

https://hollo.social/@fedify/01948487-87b2-709d-953f-8799b78433ed

Fedify: an ActivityPub server framework's avatar
Fedify: an ActivityPub server framework

@fedify@hollo.social

We have released updates (1.0.14, 1.1.11, 1.2.11, 1.3.4) to address CVE-2025-23221, a in 's implementation. We recommend all users update to the latest version of their respective release series immediately.

The Vulnerability

A security researcher identified multiple security issues in Fedify's lookupWebFinger() function that could be exploited to:

  • Perform denial of service attacks through infinite redirect loops
  • Execute server-side request forgery () attacks via redirects to private network addresses
  • Access unintended URL schemes through redirect manipulation

Fixed Versions

  • 1.3.x series: Update to 1.3.4
  • 1.2.x series: Update to 1.2.11
  • 1.1.x series: Update to 1.1.11
  • 1.0.x series: Update to 1.0.14

Changes

The security updates implement the following fixes:

  1. Added a maximum redirect limit (5) to prevent infinite redirect loops
  2. Restricted redirects to only follow the same scheme as the original request (HTTP/HTTPS)
  3. Blocked redirects to private network addresses to prevent SSRF attacks

How to Update

To update to the latest secure version:

# For npm users
npm update @fedify/fedify

# For Deno users
deno add jsr:@fedify/fedify

We thank the security researcher who responsibly disclosed this vulnerability, allowing us to address these issues promptly.

For more details about this vulnerability, please refer to our security advisory.


If you have any questions or concerns, please don't hesitate to reach out through our GitHub Discussions, join our Matrix chat space, or our Discord server.

Forfattar Markus Pedersen 📚🌱's avatar
Forfattar Markus Pedersen 📚🌱

@markus@prosa.skvip.lol

Introduksjon

Hei!

Eg er forfattar Markus Pedersen. Eg har tidlegare gjeve ut ein teikneserietrilogi om nokre udugelege superheltar kalla (https://www.uberpress.no/collections/udugeleg-collection).

For tida prøvar eg meg i heilt andre banar enn superheltar med dikt og anna kortprosa. Eg er i ein prosess med å sende nokre samlingar rundt til forlag.

På denne kontoen har eg tenkt å leggje ut nokre av desse tekstane eg skriv. Dei kan gjerne vera litt for lange for ein vanleg -konto, og difor nyttar eg til dette.

Det kjem til å vera ein del tekstar med tung tematikk, eg skal prøve å vera flink med innhaldsfilter på dei aller tyngste.

Min kvardagslege konto er @markus. Eg nyttar den som ein småblogg, så der finn du allslags tankar om allslags greiar.

Eg vonar du vil følgje meg her sjølv om du følgjar meg annastads allereie!

Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@KazukyAkayashi@social.zarchbox.fr

Une chose que je trouve intéressante sur Hollo et que j'ai vu nul par ailleurs :

## The number of recent public posts to fetch from remote actors when they are encountered first time.
REMOTE_ACTOR_FETCH_POSTS=10

Dans les faits ça fonctionne pas mal mais ça met un peu de temps a charger

Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@KazukyAkayashi@social.zarchbox.fr

Une chose que je trouve intéressante sur Hollo et que j'ai vu nul par ailleurs :

## The number of recent public posts to fetch from remote actors when they are encountered first time.
REMOTE_ACTOR_FETCH_POSTS=10

Dans les faits ça fonctionne pas mal mais ça met un peu de temps a charger

洪 民憙 (Hong Minhee)'s avatar
洪 民憙 (Hong Minhee)

@hongminhee@hollo.social

does not currently cache media attached to remote posts or avatars from remote accounts. Do you think we should cache them?

OptionVoters
It's fine the way it is.1 (8%)
They should be cached.5 (38%)
It would be nice to be configurable.7 (54%)
Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

does not currently cache media attached to remote posts or avatars from remote accounts (except for thumbnails). Do you think we should cache them?

OptionVoters
It's fine the way it is.1 (50%)
They should be cached.0 (0%)
It would be nice to be configurable.1 (50%)
Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

In 0.5.0, the number of likes and shares will be more accurate.

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

Have you been having trouble fetching accounts or posts from that have custom emojis in ?

This is because they represent an Emoji object as an invalid JSON-LD object. Fortunately, this patch fixes that issue, so keep an eye out for it.

https://hollo.social/@fedify/01941dab-e4c3-7ce0-9307-b5b8c095d521

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

Did you know? supports /-style . You can quote another post by adding a link to it. If a post contains any link to an object of Article/Note/Question, Hollo quotes it in the post.

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

Hollo 0.4.0 released! is a single-user federated microblogging software which is -enabled and powered by .

The key changes of this release include:

  • Hollo is now powered by Node.js 23+ instead of Bun for more efficient memory usage.

  • Added an experimental feature flag TIMELINE_INBOXES to store all posts visible to your timeline in the database, rather than filtering them in real-time as they are displayed. This is useful for relatively larger instances with many incoming posts, but as of now it may have several bugs. It is expected to be the default behavior in the future after it is stabilized.

  • Now you can import and export your data from the administration dashboard in CSV format: follows, lists, accounts you muted, accounts you blocked, and bookmarks.

  • You can now make your profile discoverable.

  • The profile page now shows an account's cover image if it has one.

  • Many bug fixes.

For the details, see also the full changelog.

You can upgrade to Hollo 0.4.0 using the following ways:

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

is currently testing .js instead of . (In fact, the hollo.social server is already running on Node.js!) If this test is successful, starting with the next release, Hollo will be powered by Node.js instead of Bun.

The main reason for switching to Node.js is to optimize memory usage. As you can see in the graph image below, Node.js uses significantly less memory than Bun. With this switch, Hollo is expected to be even more lightweight than before!

Are you interested in trying out the Node.js version of Hollo early? Try to pull ghcr.io/dahlia/hollo:0.4.0-dev.290!

Hollo's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

One hidden feature of : You can also quote another post while replying to someone else's post.

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

We'll be releasing 0.4.0 before the year is out. Stay tuned!

洪 民憙 (Hong Minhee)'s avatar
洪 民憙 (Hong Minhee)

@hongminhee@hollo.social

Just released 0.3.5, which contains small minor bug fixes.

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

Starting with 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.

In the profile settings, you can see the new option labeled with “Allow your account to be discovered in the public directory.”
洪 民憙 (Hong Minhee)'s avatar
洪 民憙 (Hong Minhee)

@hongminhee@hollo.social · Reply to 洪 民憙 (Hong Minhee)'s post

I wrote a blog post to wrap up the year 2024: A year with the fediverse.

https://writings.hongminhee.org/2024/12/a-year-with-the-fediverse/index.en.html

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to Hollo :hollo:'s post

Okay, testing with .js is cruising along. It's consuming up to 3 GB of memory at peak times, but that's a huge improvement over Hollo with , which was consuming over 8 GB of memory at peak times.

So, yes, starting with Hollo 0.4.0, we'll use Node.js instead of Bun!

Memory usage chart for the hollo.social server. You can see that before December 18th, the point at which we switched to Node.js, the memory usage fluctuated between 1 GB and 8 GB, but since then, it's been mostly stable around 1 GB. It did spike to 3 GB at peak times, but only briefly during the entire test period.
Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

is currently testing .js instead of . (In fact, the hollo.social server is already running on Node.js!) If this test is successful, starting with the next release, Hollo will be powered by Node.js instead of Bun.

The main reason for switching to Node.js is to optimize memory usage. As you can see in the graph image below, Node.js uses significantly less memory than Bun. With this switch, Hollo is expected to be even more lightweight than before!

Are you interested in trying out the Node.js version of Hollo early? Try to pull ghcr.io/dahlia/hollo:0.4.0-dev.290!

Hollo's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

For those who want to use on @ivory: evolved from the Tweetbot codebase, which was a third-party Twitter client, so it assumes that object IDs are integers. Hollo uses UUIDs for object IDs, so it can't be used with Ivory at this time. We hope that Ivory will support non-integer object IDs in the future!

洪 民憙 (Hong Minhee)'s avatar
洪 民憙 (Hong Minhee)

@hongminhee@fosstodon.org

For the sake of dogfooding , which I'm working on, I'm moving to @hongminhee@hollo.social, a new account created with Hollo. My follower list will automatically be handed over, so there's nothing you need to do, and I wish you well with my new account!

Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@KazukyAkayashi@social.zarchbox.fr

Hmm bon ne démarre plus depuis la 0.2.x et le passage a la 0.3.0 ne change rien, même sur une fresh install j'ai les même problème PostgresError :nko_curious:

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

Hollo 0.3.0 released! is a single-user federated microblogging software which is -enabled and powered by .

The key changes of this release include:

  • Thanks to @joschi, Hollo now support local filesystem storage for media files. You can configure DRIVE_DISK=fs and FS_ASSET_PATH to store media files in the local filesystem. For users who've used S3, no further action is required—but, it's recommended to configure DRIVE_DISK=s3 as DRIVE_DISK will be required in the future releases.
  • Added support for Sentry. If you want to see error reports and instrumented traces in Sentry, please configure SENTRY_DSN.
  • Added pagination to the profile page.
  • Minor performance improvements and bug fixes due to upgrading Fedify to 1.3.0.

You can upgrade to Hollo 0.3.0 using the following ways:

fedicat's avatar
fedicat

@fedicat@pc.cafe

I don’t have my test instance completely set up with S3 for media but pretty sure is working with now.

screenshot of home feed with test posts and image placeholders in teal

Detected text:

12:35Homehollo.fedifolio.comtechtechnicat12:34 AMalt texttechtechnicat12:13 AMtechtechnicat11/28/20241technicattechtechnicatТ 11/27/202411/27/2024trst112
fedicat's avatar
fedicat

@fedicat@pc.cafe

working on support

screenshot of a home feed with just a few test posts

Detected text:

9:50Homeo introvert (public, not in timelines)Phil Chutechnicattest introPhil ChutechnicattestingPhil Chutechnicattesthollo.fedifolio.com6:03 PM6:03 PM12:59 AM
Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

The v0.2.3 has been released, which fixes a few bugs and brings to the latest version, v1.2.7. If you are using the Docker image, you can upgrade by using the ghcr.io/dahlia/hollo:0.2.3.

anno189

@anno189@hollo.1dian.site

Simple logging library with zero dependencies for Deno, Node.js, Bun, browsers, and edge functions https://logtape.org/

anno189

@anno189@hollo.1dian.site

ActivityPub server framework in TypeScript https://fedify.dev/

洪 民憙 (Hong Minhee)'s avatar
洪 民憙 (Hong Minhee)

@hongminhee@fosstodon.org

Star History of , , and :

star-history.com/#dahlia/fedif

Star History of Fedify, Hollo, and LogTape.
Fedify: an ActivityPub server framework's avatar
Fedify: an ActivityPub server framework

@fedify@hollo.social

Flyers for and to be used at an open source event in Japan!

https://mstdn.y-zu.org/@Yohei_Zuho/113440544215822210

Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@KazukyAkayashi@social.zarchbox.fr · Reply to Kazuky Akayashi ฅ^•ﻌ•^ฅ's post

Hmm I can't start Hollo with systemd, I don't really understand why.

I've tried the example given
on the Bun website, I think the problem comes from this line :

ExecStart=/home/my_user/.bun/bin/bun run index.ts

Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@KazukyAkayashi@social.zarchbox.fr · Reply to Kazuky Akayashi ฅ^•ﻌ•^ฅ's post

Bon bah j'ai n'y les moyens financier, ni matériel (en plus d'y connaitre quedale) de faire du S3 du coup ça bloque totalement l'utilisation de Hollo :pikasad:
En espérant que le stockage local soit rajouté dans les prochaines versions.

Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@KazukyAkayashi@social.zarchbox.fr · Reply to Kazuky Akayashi ฅ^•ﻌ•^ฅ's post

Bon bah ça fonctionne pas mal du tout :nko_okay:
Va juste falloir mettre un truc de stockage en place pour tester bien la chose.



RE:
hollo.zarchbox.fr/@KazukyAkayashi/0192fda2-f090-7c21-9a15-4d1896aa573f

KazukyAkayashi

@KazukyAkayashi@hollo.zarchbox.fr

Hello world 👋

Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@KazukyAkayashi@social.zarchbox.fr · Reply to Kazuky Akayashi ฅ^•ﻌ•^ฅ's post

Ah bah zut alors Mangane ça marche pas avec Hollo :pikathinknothappy:

Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@KazukyAkayashi@social.zarchbox.fr · Reply to Kazuky Akayashi ฅ^•ﻌ•^ฅ's post

Aie gros points noir :

- une dépendance a
cdn.jsdelivr.net sur l'interface web.
- et visiblement l'obligation d'avoir un S3 compatible pour les medias
:pikaneutral: :pikascream:

Je vais tester le reste mais ça semble pas mal foutu dans la même veine que GotoSocial mais qui fonctionne mieux
:pikasmilesweat:

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

Hollo 0.2.0 released! is a single-user federated microblogging software which is -enabled and powered by .

The key changes of this release include:

  1. Thanks to @thisismissem, now you can report remote accounts and posts.

  2. Added two-factor authentication support.

  3. Thanks again to @thisismissem, Hollo improved alignment on Mastodon API changes about OAuth and apps.

  4. Thanks again to @thisismissem, RFC 8414 for OAuth Authorization Server metadata endpoint. It will improves interoperability between Hollo and Mastodon-compatible client apps.

  5. Renamed the Data menu from the administration dashboard to Federation, and:

    • Now posts also can be force-refreshed.
    • Now the number of messages in the task queue is shown.
  6. Custom emojis now can be deleted from the administration dashboard.

  7. Thanks @helge, PORT and ALLOW_PRIVATE_ADDRESS environment variables are introduced.

  8. Added a favicon.

  9. Dropped support for Redis, which was an optional dependency.

You can upgrade to Hollo 0.2.0 using the following ways:

5-a. Now posts also can be force-refreshed.5-b. Now the number of messages in the task queue is shown.6. Custom emojis now can be deleted from the administration dashboard.2. Added two-factor authentication support.
Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

In the next version of , you'll see the number of messages stacked in your task queue in the administration dashboard. This gives you an idea of how busy your instance is.

The number of messages in the task queue as seen in Hollo's administration dashboard.
poes 🇵🇸's avatar
poes 🇵🇸

@poes@kauaku.us

I'm in waiting for someone create fedi app using fedify and deno (#Hollo like app).

Doesn't using Bun, sorry.

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

The next version of 's administration dashboard will have a Federation menu instead of a Data menu, and will allow you to force refresh posts as well as accounts.

The administration dashboard in the next version of Hollo. There is a Federation menu instead of a Data menu.
洪 民憙(ホン・ミンヒ)'s avatar
洪 民憙(ホン・ミンヒ)

@hongminhee@fedibird.com · Reply to 洪 民憙(ホン・ミンヒ)'s post

今日Fedify/Holloのブースに訪問してくれた皆様、本当にありがとうございました‼️機会があれば是非またお会いましょう!

洪 民憙(ホン・ミンヒ)'s avatar
洪 民憙(ホン・ミンヒ)

@hongminhee@fedibird.com · Reply to 洪 民憙(ホン・ミンヒ)'s post

FedifyとHolloのブースです!

洪 民憙(ホン・ミンヒ)'s avatar
洪 民憙(ホン・ミンヒ)

@hongminhee@fedibird.com

今週土曜日に開催されるOSC 2024 Tokyo/FallにFedify/Hollo合同で出展します!可愛いFedifyのロゴのシールと『自分だけのフェディバースのマイクロブログを作ろう!』日本語版の紙の本を持って行く予定です。よろしくお願いします。

event.ospn.jp/osc2024-fall/

촛불에 구어진🔥잉어구이🔥's avatar
촛불에 구어진🔥잉어구이🔥

@everclear@hollo.ingyeo.net

헉 이모지 훔쳐오기 기능이 있었어...

Daniel Finsler's avatar
Daniel Finsler

@insl@tooting.ch

github.com/dahlia/hollo

촛불에 구어진🔥잉어구이🔥's avatar
촛불에 구어진🔥잉어구이🔥

@everclear@hollo.ingyeo.net

minio에서 클플r2로 옮기니 이미지 잘 뜨네요.

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

0.2.0 will have two-factor authentication support using time-based OTP!

If you want to give it a try right now, you can get it in ghcr.io/dahlia/hollo:0.2.0-dev.183 or just canary.

Two-factor authentication settings on the Hollo administration dashboard.
Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

Finally, Hollo 0.1.0 released! is a single-user federated microblogging software which is -enabled and powered by .

Hollo has the most of features that Mastodon has except for moderation tools, and also include:

  • CommonMark (a.k.a. Markdown) and up to 4,096 characters per post
  • Misskey-style quotes (compatible with Misskey, Akkoma, Fedibird, etc)
  • Misskey-style emoji reactions (both Unicode emojis and custom emojis are supported; compatible with Misskey, Akkoma, kmyblue, etc)
  • Generally much relaxed limitations (more poll options, more attachments, and so on)
  • … and many more!

If you're interested in Hollo, please give it a try! There are several ways to install it: using Railway, using Docker (and Docker Compose), or manually.

If you're already using Hollo, please upgrade it to v0.1.0:

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

is a headless microblogging software that implements the Mastodon API. This means that you can use any Mastodon-compatible client to interact with it. However, in practice, some clients may not work as expected due to differences in the way they implement the Mastodon API. Here are some of the clients that have been tested with Hollo:

https://docs.hollo.social/clients/

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

The most common pitfall for first-time users is deploying Hollo behind a reverse proxy and forgetting to set BEHIND_PROXY=true, which causes federation issues and wasted time trying to resolve them.

To help users avoid this common pitfall, we've introduced a warning on Hollo's setup page when Hollo is behind a reverse proxy and the BEHIND_PROXY is off.

The warning message seen on Hollo's setup page.
촛불에 구어진🔥잉어구이🔥's avatar
촛불에 구어진🔥잉어구이🔥

@everclear@hollo.ingyeo.net

오라클 클라우드 프리티어에서 홀로 잘 도네요.

洪 民憙 (Hong Minhee)'s avatar
洪 民憙 (Hong Minhee)

@hongminhee@fosstodon.org

1人 인스턴스를 만드시고 싶은가요? 무거운 Mastodon이나 Misskey 말고 써 보세요!

docs.hollo.social/ko/

洪 民憙 (Hong Minhee)'s avatar
洪 民憙 (Hong Minhee)

@hongminhee@fosstodon.org

The development speed of is itself an advertisement for . :ablobcatbongo:

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

finally lets you move your old account to new one! (FEP-7628 compliant.) It's bidirectional, which is basically equivalent to and interoperable with Mastodon's account move:

  • You can prepare to move your old account to Hollo by adding aliases (setting alsoKnownAs).
  • You can start to move your Hollo account to new one by setting movedTo property and sending Move activities to the followers.

It enables your new account to have the same existing followers after you've moved your account.

Hollo's new migration panel.
@everclear@hollo.ingyeo.net's avatar
@everclear@hollo.ingyeo.net

@everclear@kolektiva.social · Reply to @everclear@hollo.ingyeo.net's post

@hongminhee 님 도움으로 docker container 내부에서 외부로 통신이 안되는 것 같은 증상을 발견.
stackoverflow.com/questions/39 적용하니 느리긴 하지만 팔로잉은 된 것 같습니다. 이제 minio랑 통신이 안되는 것 같은 증상을 해결해야..

@everclear@hollo.ingyeo.net's avatar
@everclear@hollo.ingyeo.net

@everclear@kolektiva.social · Reply to @everclear@hollo.ingyeo.net's post

방화벽 문제인가...

@everclear@hollo.ingyeo.net's avatar
@everclear@hollo.ingyeo.net

@everclear@kolektiva.social · Reply to @everclear@hollo.ingyeo.net's post

<Error>
<Code>AccessDenied</Code>
<Message>Access Denied.</Message>
<BucketName>setup</BucketName>
<Resource>/setup</Resource>
<RequestId>17FFD8BD59068C45</RequestId>
<HostId>dd9025bab4ad464b049177c95eb6ebf374d3b3fd1af9251148b658df7ac2e3e8</HostId>
</Error>
흑흑....

@everclear@hollo.ingyeo.net's avatar
@everclear@hollo.ingyeo.net

@everclear@kolektiva.social · Reply to @everclear@hollo.ingyeo.net's post

환경변수 그냥 세팅하고 돌리는...건가? 3000번 포트로 캐디 연결하면 될 것 같긴 한데..

Fedify: an ActivityPub server framework's avatar
Fedify: an ActivityPub server framework

@fedify@hollo.social

10月26日(土)に開催されるOSC 2024 Tokyo/FallにFedify/Hollo合同で出展します!可愛いFedifyのロゴのシールと『自分だけのフェディバースのマイクロブログを作ろう!』日本語版の紙の本を持って行く予定です。よろしくお願いします。

https://event.ospn.jp/osc2024-fall/

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

finally has /-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 , you can use the Quote button that appears when you press the boost icon!

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

The menu that appears when you press the boost icon in Phanpy. The menu items are Boost and Quote.
洪 民憙 (Hong Minhee)'s avatar
洪 民憙 (Hong Minhee)

@hongminhee@fosstodon.org

If you'd like to support the development of or , you can sponsor me on GitHub!

github.com/sponsors/dahlia

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to Hollo :hollo:'s post

You can get started with your own Hollo in just a few clicks with the official template for :

https://railway.app/template/eopPyH?referralCode=qeEK5G

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social

Introducing . Hollo is an -enabled single-user microblogging software. Although it's for a single user, it also supports creating and running multiple accounts for different topics.

It's headless, meaning you can use existing client apps instead, with its Mastodon-compatible APIs. It has most feature parity with Mastodon. Two big differences with Mastodon is that you can use in the content of your posts and you can quote another post.

Oh, and Hollo is built using and .

https://github.com/dahlia/hollo