
tkgka
hollo는 캐싱 정책 설정하기 매우 편하다
되게 간단하게 설정했는데 이정도라니
#hollo
hollo는 캐싱 정책 설정하기 매우 편하다
되게 간단하게 설정했는데 이정도라니
#hollo
hollo는 캐싱 정책 설정하기 매우 편하다
되게 간단하게 설정했는데 이정도라니
#hollo
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
Fedifyの関連プロジェクトをご紹介したいと思います。ActivityPubアプリケーション開発をより簡単にするツール群です:
Fedify(@fedify)はActivityPubやその他のフェディバース標準を活用する連合型サーバーアプリケーションを構築するためのTypeScriptライブラリです。Activity Vocabularyの型安全なオブジェクト、WebFingerクライアント・サーバー、HTTP Signaturesなどを提供し、ボイラープレートコードを削減してアプリケーションロジックに集中できるようにします。
Hollo(@hollo)はFedifyで動作するお一人様用マイクロブログサーバーです。個人向けに設計されていますが、ActivityPubを通じて完全に連合化されており、フェディバース全体のユーザーと交流することができます。HolloはMastodon互換APIを実装しているため、独自のウェブインターフェースがなくても、ほとんどのMastodonクライアントと互換性があります。
Holloはまた、正式リリース前の最新Fedify機能をテストする実験場としても活用されています。
BotKit(@botkit)は私たちの最も新しいメンバーで、ActivityPubボットを作成するために特別に設計されたフレームワークです。従来のMastodonボットとは異なり、BotKitはプラットフォーム固有の制限(文字数制限など)に縛られない独立したActivityPubサーバーを作成します。
BotKitのAPIは意図的にシンプルに設計されており、単一のTypeScriptファイルで完全なボットを作成できます!
これら三つのプロジェクトはすべて@fedify-dev GitHubオーガニゼーションでオープンソースとして公開されています。それぞれ異なる目的を持っていますが、ActivityPub開発をより身近にし、フェディバースのエコシステムを拡大するという共通の目標を共有しています。
これらのプロジェクトを試してみたり、開発に貢献したりすることに興味がある場合は、以下をご覧ください:
#Fedify #ActivityPub #フェディバース #fediverse #Hollo #BotKit #fedidev
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
#Fedify 자매 프로젝트들을 소개해 드리고자 합니다. #ActivityPub 애플리케이션 개발을 더 쉽게 만들어주는 관련 도구들입니다:
Fedify(@fedify)는 ActivityPub와 다른 #연합우주(#fediverse) 표준을 기반으로 연합 서버 애플리케이션을 구축하기 위한 #TypeScript 라이브러리입니다. Activity Vocabulary를 위한 타입 안전한 객체, WebFinger 클라이언트·서버, HTTP Signatures 등를 제공하여 반복적인 코드를 줄이고 애플리케이션 로직에 집중할 수 있게 해줍니다.
Hollo(@hollo)는 Fedify로 구동되는 1인 사용자용 마이크로블로깅 서버입니다. 1인 사용자를 위해 설계되었지만, ActivityPub를 통해 완전히 연합되어 연합우주 전체의 사용자들과 상호작용할 수 있습니다. Hollo는 Mastodon 호환 API를 구현하여 자체 웹 인터페이스 없이도 대부분의 Mastodon 클라이언트와 호환됩니다.
Hollo는 또한 정식 출시 전에 최신 Fedify 기능을 테스트하는 실험장으로도 활용되고 있습니다.
BotKit(@botkit)은 저희의 가장 새로운 구성원으로, ActivityPub 봇을 만들기 위해 특별히 설계된 프레임워크입니다. 전통적인 Mastodon 봇과 달리, BotKit은 플랫폼별 제한(글자 수 제한 등)에 구애받지 않는 독립적인 ActivityPub 서버를 만듭니다.
BotKit의 API는 의도적으로 단순하게 설계되어 단일 TypeScript 파일로 완전한 봇을 만들 수 있습니다!
세 프로젝트 모두 @fedify-dev GitHub 조직에서 오픈 소스로 공개되어 있습니다. 각기 다른 목적을 가지고 있지만, ActivityPub 개발을 더 접근하기 쉽게 만들고 연합우주 생태계를 확장한다는 공통된 목표를 공유합니다.
이러한 프로젝트를 사용해보거나 개발에 기여하는 데 관심이 있으시다면, 다음을 확인해보세요:
We'd like to introduce the #Fedify project family—a set of related tools that make building #ActivityPub applications more accessible:
Fedify (@fedify) is a #TypeScript library for building federated server applications powered by ActivityPub and other #fediverse standards. It provides type-safe objects for Activity Vocabulary, WebFinger client/server, HTTP Signatures, and more—eliminating boilerplate code so you can focus on your application logic.
Hollo (@hollo) is a single-user microblogging server powered by Fedify. While designed for individual users, it's fully federated through ActivityPub, allowing interaction with users across the fediverse. #Hollo implements Mastodon-compatible APIs, making it compatible with most Mastodon clients without needing its own web interface.
Hollo also serves as our testing ground for bleeding-edge Fedify features before they're officially released.
BotKit (@botkit) is our newest family member—a framework specifically designed for creating ActivityPub bots. Unlike traditional Mastodon bots, #BotKit creates standalone ActivityPub servers that aren't constrained by platform-specific limitations (like character counts).
BotKit's API is intentionally simple—you can create a complete bot in a single TypeScript file!
All three projects are open source and hosted under the @fedify-dev GitHub organization. While they serve different purposes, they share common goals: making ActivityPub development more accessible and expanding the fediverse ecosystem.
If you're interested in trying any of these projects or contributing to their development, check out:
Just released #Hollo 0.5.4 (ghcr.io/fedify-dev/hollo:0.5.4
), 0.4.10 (ghcr.io/fedify-dev/hollo:0.4.10
), and 0.3.9 (ghcr.io/fedify-dev/hollo:0.3.9
), which fix interoperability issues with some software including @mitra. (Thanks for @silverpill's bug report.)
Just released #Hollo 0.5.4 (ghcr.io/fedify-dev/hollo:0.5.4
), 0.4.10 (ghcr.io/fedify-dev/hollo:0.4.10
), and 0.3.9 (ghcr.io/fedify-dev/hollo:0.3.9
), which fix interoperability issues with some software including @mitra. (Thanks for @silverpill's bug report.)
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
Fedifyの関連プロジェクトをご紹介したいと思います。ActivityPubアプリケーション開発をより簡単にするツール群です:
Fedify(@fedify)はActivityPubやその他のフェディバース標準を活用する連合型サーバーアプリケーションを構築するためのTypeScriptライブラリです。Activity Vocabularyの型安全なオブジェクト、WebFingerクライアント・サーバー、HTTP Signaturesなどを提供し、ボイラープレートコードを削減してアプリケーションロジックに集中できるようにします。
Hollo(@hollo)はFedifyで動作するお一人様用マイクロブログサーバーです。個人向けに設計されていますが、ActivityPubを通じて完全に連合化されており、フェディバース全体のユーザーと交流することができます。HolloはMastodon互換APIを実装しているため、独自のウェブインターフェースがなくても、ほとんどのMastodonクライアントと互換性があります。
Holloはまた、正式リリース前の最新Fedify機能をテストする実験場としても活用されています。
BotKit(@botkit)は私たちの最も新しいメンバーで、ActivityPubボットを作成するために特別に設計されたフレームワークです。従来のMastodonボットとは異なり、BotKitはプラットフォーム固有の制限(文字数制限など)に縛られない独立したActivityPubサーバーを作成します。
BotKitのAPIは意図的にシンプルに設計されており、単一のTypeScriptファイルで完全なボットを作成できます!
これら三つのプロジェクトはすべて@fedify-dev GitHubオーガニゼーションでオープンソースとして公開されています。それぞれ異なる目的を持っていますが、ActivityPub開発をより身近にし、フェディバースのエコシステムを拡大するという共通の目標を共有しています。
これらのプロジェクトを試してみたり、開発に貢献したりすることに興味がある場合は、以下をご覧ください:
#Fedify #ActivityPub #フェディバース #fediverse #Hollo #BotKit #fedidev
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
#Fedify 자매 프로젝트들을 소개해 드리고자 합니다. #ActivityPub 애플리케이션 개발을 더 쉽게 만들어주는 관련 도구들입니다:
Fedify(@fedify)는 ActivityPub와 다른 #연합우주(#fediverse) 표준을 기반으로 연합 서버 애플리케이션을 구축하기 위한 #TypeScript 라이브러리입니다. Activity Vocabulary를 위한 타입 안전한 객체, WebFinger 클라이언트·서버, HTTP Signatures 등를 제공하여 반복적인 코드를 줄이고 애플리케이션 로직에 집중할 수 있게 해줍니다.
Hollo(@hollo)는 Fedify로 구동되는 1인 사용자용 마이크로블로깅 서버입니다. 1인 사용자를 위해 설계되었지만, ActivityPub를 통해 완전히 연합되어 연합우주 전체의 사용자들과 상호작용할 수 있습니다. Hollo는 Mastodon 호환 API를 구현하여 자체 웹 인터페이스 없이도 대부분의 Mastodon 클라이언트와 호환됩니다.
Hollo는 또한 정식 출시 전에 최신 Fedify 기능을 테스트하는 실험장으로도 활용되고 있습니다.
BotKit(@botkit)은 저희의 가장 새로운 구성원으로, ActivityPub 봇을 만들기 위해 특별히 설계된 프레임워크입니다. 전통적인 Mastodon 봇과 달리, BotKit은 플랫폼별 제한(글자 수 제한 등)에 구애받지 않는 독립적인 ActivityPub 서버를 만듭니다.
BotKit의 API는 의도적으로 단순하게 설계되어 단일 TypeScript 파일로 완전한 봇을 만들 수 있습니다!
세 프로젝트 모두 @fedify-dev GitHub 조직에서 오픈 소스로 공개되어 있습니다. 각기 다른 목적을 가지고 있지만, ActivityPub 개발을 더 접근하기 쉽게 만들고 연합우주 생태계를 확장한다는 공통된 목표를 공유합니다.
이러한 프로젝트를 사용해보거나 개발에 기여하는 데 관심이 있으시다면, 다음을 확인해보세요:
We'd like to introduce the #Fedify project family—a set of related tools that make building #ActivityPub applications more accessible:
Fedify (@fedify) is a #TypeScript library for building federated server applications powered by ActivityPub and other #fediverse standards. It provides type-safe objects for Activity Vocabulary, WebFinger client/server, HTTP Signatures, and more—eliminating boilerplate code so you can focus on your application logic.
Hollo (@hollo) is a single-user microblogging server powered by Fedify. While designed for individual users, it's fully federated through ActivityPub, allowing interaction with users across the fediverse. #Hollo implements Mastodon-compatible APIs, making it compatible with most Mastodon clients without needing its own web interface.
Hollo also serves as our testing ground for bleeding-edge Fedify features before they're officially released.
BotKit (@botkit) is our newest family member—a framework specifically designed for creating ActivityPub bots. Unlike traditional Mastodon bots, #BotKit creates standalone ActivityPub servers that aren't constrained by platform-specific limitations (like character counts).
BotKit's API is intentionally simple—you can create a complete bot in a single TypeScript file!
All three projects are open source and hosted under the @fedify-dev GitHub organization. While they serve different purposes, they share common goals: making ActivityPub development more accessible and expanding the fediverse ecosystem.
If you're interested in trying any of these projects or contributing to their development, check out:
If you ever happen to see a hosted offer for #Hollo, please let us know!
Just released #Hollo 0.5.3 (ghcr.io/fedify-dev/hollo:0.5.3
), 0.4.9 (ghcr.io/fedify-dev/hollo:0.4.9
), and 0.3.8 (ghcr.io/fedify-dev/hollo:0.3.8
), which fix interoperability issues with some software including @mitra. (Thanks for @silverpill's bug report.)
If you ever happen to see a hosted offer for #Hollo, please let us know!
If you ever happen to see a hosted offer for #Hollo, please let us know!
Just released #Hollo 0.5.3 (ghcr.io/fedify-dev/hollo:0.5.3
), 0.4.9 (ghcr.io/fedify-dev/hollo:0.4.9
), and 0.3.8 (ghcr.io/fedify-dev/hollo:0.3.8
), which fix interoperability issues with some software including @mitra. (Thanks for @silverpill's bug report.)
Just released #Hollo 0.5.3 (ghcr.io/fedify-dev/hollo:0.5.3
), 0.4.9 (ghcr.io/fedify-dev/hollo:0.4.9
), and 0.3.8 (ghcr.io/fedify-dev/hollo:0.3.8
), which fix interoperability issues with some software including @mitra. (Thanks for @silverpill's bug report.)
Just released #Hollo 0.5.3 (ghcr.io/fedify-dev/hollo:0.5.3
), 0.4.9 (ghcr.io/fedify-dev/hollo:0.4.9
), and 0.3.8 (ghcr.io/fedify-dev/hollo:0.3.8
), which fix interoperability issues with some software including @mitra. (Thanks for @silverpill's bug report.)
#Hollo v0.6.0, the next minor release, will have theme colors on your profile pages. Powered by Pico CSS, see the list of all available colors in the Colors section from their docs.
Want to give it a try in advance? Try v0.6.0-dev.397, an unstable release, at your own risk.
#Hollo v0.6.0, the next minor release, will have theme colors on your profile pages. Powered by Pico CSS, see the list of all available colors in the Colors section from their docs.
Want to give it a try in advance? Try v0.6.0-dev.397, an unstable release, at your own risk.
#Hollo v0.6.0, the next minor release, will have theme colors on your profile pages. Powered by Pico CSS, see the list of all available colors in the Colors section from their docs.
Want to give it a try in advance? Try v0.6.0-dev.397, an unstable release, at your own risk.
#Hollo v0.6.0, the next minor release, will have theme colors on your profile pages. Powered by Pico CSS, see the list of all available colors in the Colors section from their docs.
Want to give it a try in advance? Try v0.6.0-dev.397, an unstable release, at your own risk.
#Hollo v0.6.0, the next minor release, will have theme colors on your profile pages. Powered by Pico CSS, see the list of all available colors in the Colors section from their docs.
Want to give it a try in advance? Try v0.6.0-dev.397, an unstable release, at your own risk.
Just released #Hollo 0.5.2 (ghcr.io/fedify-dev/hollo:0.5.2
) and 0.4.8 (ghcr.io/fedify-dev/hollo:0.4.8
), which fix several minor bugs! (Thanks for @ntek's bug reports.)
Just released #Hollo 0.5.2 (ghcr.io/fedify-dev/hollo:0.5.2
) and 0.4.8 (ghcr.io/fedify-dev/hollo:0.4.8
), which fix several minor bugs! (Thanks for @ntek's bug reports.)
Just released #Hollo 0.5.2 (ghcr.io/fedify-dev/hollo:0.5.2
) and 0.4.8 (ghcr.io/fedify-dev/hollo:0.4.8
), which fix several minor bugs! (Thanks for @ntek's bug reports.)
Just released #Hollo 0.5.2 (ghcr.io/fedify-dev/hollo:0.5.2
) and 0.4.8 (ghcr.io/fedify-dev/hollo:0.4.8
), which fix several minor bugs! (Thanks for @ntek's bug reports.)
Just released #Hollo 0.5.2 (ghcr.io/fedify-dev/hollo:0.5.2
) and 0.4.8 (ghcr.io/fedify-dev/hollo:0.4.8
), which fix several minor bugs! (Thanks for @ntek's bug reports.)
@[email protected] · Reply to Hollo :hollo:'s post
みなさん、こんにちは!
Holloの新しい計画について、みなさんのご意見をお聞かせください。
これまでHolloは、セルフホスティングを基本原則としてきました。これは今後も変わることなく維持され、ソースコードは引き続きAGPLv3ライセンスで公開されます。
最近、プロジェクトの持続可能な発展のため、Open Collective (@opencollective )を通じて一定額以上を定期的にご支援いただいている方々向けに、ホスティングサービスの提供を検討しています。
これは、技術的な部分を気にすることなくHolloを利用したい方のための追加オプションとなります。もちろん、現在のように自身でインストールして運用することも引き続き可能です。
引用させていただいた英語の投稿のアンケートにご参加ください!📊
💭 追加のご意見やご提案がございましたら、コメントでお寄せください!
https://hollo.social/@hollo/01950344-1c55-7f43-8afc-b0a1ee8b4abf
#Hollo everyone!
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!
Option | Voters |
---|---|
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%) |
@[email protected] · Reply to Hollo :hollo:'s post
안녕하세요!
Hollo의 새로운 계획에 대해 여러분의 의견을 듣고자 합니다.
지금까지 Hollo는 셀프 호스팅을 기본 원칙으로 삼아왔습니다. 이는 앞으로도 변함없이 유지될 것이며, 소스 코드는 계속해서 AGPLv3 라이선스로 공개됩니다.
최근 저희는 프로젝트의 지속 가능한 발전을 위해, Open Collective(@opencollective)를 통해 일정 금액 이상을 정기적으로 후원해 주시는 분들을 위한 호스팅 서비스 제공을 검토하고 있습니다.
이는 기술적인 부분에 신경 쓰지 않고도 Hollo를 이용하고 싶으신 분들을 위한 추가 옵션이 될 것입니다. 물론 지금처럼 직접 설치하고 운영하시는 것도 계속 가능합니다.
아래 인용된 영어 게시물의 투표에 참여해 주시면 감사하겠습니다! 📊
💭 추가 의견이나 제안이 있으시다면 댓글로 남겨주세요!
https://hollo.social/@hollo/01950344-1c55-7f43-8afc-b0a1ee8b4abf
#Hollo everyone!
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!
Option | Voters |
---|---|
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 everyone!
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!
Option | Voters |
---|---|
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 everyone!
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!
Option | Voters |
---|---|
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 everyone!
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!
Option | Voters |
---|---|
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%) |
@[email protected] · Reply to Hollo :hollo:'s post
みなさん、こんにちは!
Holloの新しい計画について、みなさんのご意見をお聞かせください。
これまでHolloは、セルフホスティングを基本原則としてきました。これは今後も変わることなく維持され、ソースコードは引き続きAGPLv3ライセンスで公開されます。
最近、プロジェクトの持続可能な発展のため、Open Collective (@opencollective )を通じて一定額以上を定期的にご支援いただいている方々向けに、ホスティングサービスの提供を検討しています。
これは、技術的な部分を気にすることなくHolloを利用したい方のための追加オプションとなります。もちろん、現在のように自身でインストールして運用することも引き続き可能です。
引用させていただいた英語の投稿のアンケートにご参加ください!📊
💭 追加のご意見やご提案がございましたら、コメントでお寄せください!
https://hollo.social/@hollo/01950344-1c55-7f43-8afc-b0a1ee8b4abf
#Hollo everyone!
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!
Option | Voters |
---|---|
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%) |
@[email protected] · Reply to Hollo :hollo:'s post
みなさん、こんにちは!
Holloの新しい計画について、みなさんのご意見をお聞かせください。
これまでHolloは、セルフホスティングを基本原則としてきました。これは今後も変わることなく維持され、ソースコードは引き続きAGPLv3ライセンスで公開されます。
最近、プロジェクトの持続可能な発展のため、Open Collective (@opencollective )を通じて一定額以上を定期的にご支援いただいている方々向けに、ホスティングサービスの提供を検討しています。
これは、技術的な部分を気にすることなくHolloを利用したい方のための追加オプションとなります。もちろん、現在のように自身でインストールして運用することも引き続き可能です。
引用させていただいた英語の投稿のアンケートにご参加ください!📊
💭 追加のご意見やご提案がございましたら、コメントでお寄せください!
https://hollo.social/@hollo/01950344-1c55-7f43-8afc-b0a1ee8b4abf
#Hollo everyone!
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!
Option | Voters |
---|---|
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%) |
@[email protected] · Reply to Hollo :hollo:'s post
안녕하세요!
Hollo의 새로운 계획에 대해 여러분의 의견을 듣고자 합니다.
지금까지 Hollo는 셀프 호스팅을 기본 원칙으로 삼아왔습니다. 이는 앞으로도 변함없이 유지될 것이며, 소스 코드는 계속해서 AGPLv3 라이선스로 공개됩니다.
최근 저희는 프로젝트의 지속 가능한 발전을 위해, Open Collective(@opencollective)를 통해 일정 금액 이상을 정기적으로 후원해 주시는 분들을 위한 호스팅 서비스 제공을 검토하고 있습니다.
이는 기술적인 부분에 신경 쓰지 않고도 Hollo를 이용하고 싶으신 분들을 위한 추가 옵션이 될 것입니다. 물론 지금처럼 직접 설치하고 운영하시는 것도 계속 가능합니다.
아래 인용된 영어 게시물의 투표에 참여해 주시면 감사하겠습니다! 📊
💭 추가 의견이나 제안이 있으시다면 댓글로 남겨주세요!
https://hollo.social/@hollo/01950344-1c55-7f43-8afc-b0a1ee8b4abf
#Hollo everyone!
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!
Option | Voters |
---|---|
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 everyone!
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!
Option | Voters |
---|---|
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%) |
@[email protected] · Reply to Hollo :hollo:'s post
#Hollo 0.5.0이 릴리스되었습니다! 이번 업데이트는 여러분의 Hollo 사용 경험을 더욱 개선하는 다양한 변화를 담고 있습니다.
게시물의 공유 수와 좋아요 수를 더 정확하게 집계하도록 개선했습니다. 이제 각 게시물의 공유 수와 좋아요 수가 정확하게 유지되며, 다른 서버로 공유되었을 때도 이 수치가 올바르게 보존됩니다.
@yamanoku 님의 기여로 프로필 페이지가 크게 개선되었습니다:
이 밖에도 시스템의 라이트·다크 모드에 따라 파비콘이 자동으로 전환되며, 새로운 ALLOW_HTML
환경 변수로 Markdown 안에 HTML 사용이 가능해졌습니다(보안을 위해 허용되는 HTML 요소는 제한됩니다).
또한 뮤트와 차단 목록을 위한 API 엔드포인트를 추가하여 Mastodon API 호환성을 강화했습니다.
S3를 사용하시는 분들은 이제 S3_REGION
환경 변수 설정이 필수가 되었으니 참고해 주시기 바랍니다.
0.5.0으로 업데이트하는 방법:
docker pull ghcr.io/fedify-dev/hollo:0.5.0
git pull origin stable
후 pnpm install
전체 변경 사항: https://github.com/fedify-dev/hollo/releases/tag/0.5.0.
@[email protected] · Reply to Hollo :hollo:'s post
#Hollo 0.5.0をリリースしました!今回のアップデートでは、皆様のHollo体験をより良くする様々な改善が含まれています。
投稿のシェア数といいね数の集計がより正確になりました。各投稿のシェア数といいね数が正確に維持され、他のサーバーでシェアされた場合でもこれらの数値が適切に保持されるようになりました。
@yamanoku さんの貢献により、プロフィールページが大幅に改善されました:
alt
属性を活用した画像のアクセシビリティ向上その他、システムのライト/ダークモードに応じてファビコンが自動的に切り替わるようになり、新しいALLOW_HTML
環境変数でMarkdown内でのHTML使用が可能になりました。(セキュリティのため、使用可能なHTML要素は制限されています)
また、ミュートとブロックリストのためのAPIエンドポイントを追加し、Mastodon APIとの互換性を強化しました。
S3をご利用の方は、S3_REGION
環境変数の設定が必須となりましたのでご注意ください。
0.5.0へのアップデート方法:
docker pull ghcr.io/fedify-dev/hollo:0.5.0
git pull origin stable
の後pnpm install
を実行変更の詳細:https://github.com/fedify-dev/hollo/releases/tag/0.5.0.
@[email protected] · Reply to Hollo :hollo:'s post
#Hollo 0.5.0をリリースしました!今回のアップデートでは、皆様のHollo体験をより良くする様々な改善が含まれています。
投稿のシェア数といいね数の集計がより正確になりました。各投稿のシェア数といいね数が正確に維持され、他のサーバーでシェアされた場合でもこれらの数値が適切に保持されるようになりました。
@yamanoku さんの貢献により、プロフィールページが大幅に改善されました:
alt
属性を活用した画像のアクセシビリティ向上その他、システムのライト/ダークモードに応じてファビコンが自動的に切り替わるようになり、新しいALLOW_HTML
環境変数でMarkdown内でのHTML使用が可能になりました。(セキュリティのため、使用可能なHTML要素は制限されています)
また、ミュートとブロックリストのためのAPIエンドポイントを追加し、Mastodon APIとの互換性を強化しました。
S3をご利用の方は、S3_REGION
環境変数の設定が必須となりましたのでご注意ください。
0.5.0へのアップデート方法:
docker pull ghcr.io/fedify-dev/hollo:0.5.0
git pull origin stable
の後pnpm install
を実行変更の詳細:https://github.com/fedify-dev/hollo/releases/tag/0.5.0.
@[email protected] · Reply to Hollo :hollo:'s post
#Hollo 0.5.0をリリースしました!今回のアップデートでは、皆様のHollo体験をより良くする様々な改善が含まれています。
投稿のシェア数といいね数の集計がより正確になりました。各投稿のシェア数といいね数が正確に維持され、他のサーバーでシェアされた場合でもこれらの数値が適切に保持されるようになりました。
@yamanoku さんの貢献により、プロフィールページが大幅に改善されました:
alt
属性を活用した画像のアクセシビリティ向上その他、システムのライト/ダークモードに応じてファビコンが自動的に切り替わるようになり、新しいALLOW_HTML
環境変数でMarkdown内でのHTML使用が可能になりました。(セキュリティのため、使用可能なHTML要素は制限されています)
また、ミュートとブロックリストのためのAPIエンドポイントを追加し、Mastodon APIとの互換性を強化しました。
S3をご利用の方は、S3_REGION
環境変数の設定が必須となりましたのでご注意ください。
0.5.0へのアップデート方法:
docker pull ghcr.io/fedify-dev/hollo:0.5.0
git pull origin stable
の後pnpm install
を実行変更の詳細:https://github.com/fedify-dev/hollo/releases/tag/0.5.0.
@[email protected] · Reply to Hollo :hollo:'s post
#Hollo 0.5.0이 릴리스되었습니다! 이번 업데이트는 여러분의 Hollo 사용 경험을 더욱 개선하는 다양한 변화를 담고 있습니다.
게시물의 공유 수와 좋아요 수를 더 정확하게 집계하도록 개선했습니다. 이제 각 게시물의 공유 수와 좋아요 수가 정확하게 유지되며, 다른 서버로 공유되었을 때도 이 수치가 올바르게 보존됩니다.
@yamanoku 님의 기여로 프로필 페이지가 크게 개선되었습니다:
이 밖에도 시스템의 라이트·다크 모드에 따라 파비콘이 자동으로 전환되며, 새로운 ALLOW_HTML
환경 변수로 Markdown 안에 HTML 사용이 가능해졌습니다(보안을 위해 허용되는 HTML 요소는 제한됩니다).
또한 뮤트와 차단 목록을 위한 API 엔드포인트를 추가하여 Mastodon API 호환성을 강화했습니다.
S3를 사용하시는 분들은 이제 S3_REGION
환경 변수 설정이 필수가 되었으니 참고해 주시기 바랍니다.
0.5.0으로 업데이트하는 방법:
docker pull ghcr.io/fedify-dev/hollo:0.5.0
git pull origin stable
후 pnpm install
전체 변경 사항: https://github.com/fedify-dev/hollo/releases/tag/0.5.0.
#Hollo 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:
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 pull ghcr.io/fedify-dev/hollo:0.5.0
git pull origin stable
and pnpm install
Full changelog: https://github.com/fedify-dev/hollo/releases/tag/0.5.0.
So far, Phanpy is my favorite Hollo client. Enafore gives me emoji reacts, so I find myself jumping back and forth.
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.
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.
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!
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.
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!
@[email protected] · Reply to Hollo :hollo:'s post
@[email protected] · Reply to Hollo :hollo:'s post
Introducing #Hollo. Hollo is an #ActivityPub-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 #Mastodon 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 #Markdown in the content of your posts and you can quote another post.
Oh, and Hollo is built using #Bun and #Fedify.