Hollo

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.

https://github.com/dahlia/hollo

#fedidev

We'd like to introduce the #Fedify project family—a set of related tools that make building #ActivityPub applications more accessible:

Fedify

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 (@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 (@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:

• Fedify: https://fedify.dev/
• Hollo: https://docs.hollo.social/
• BotKit: https://botkit.fedify.dev/

#fedidev

@deadsuperhero @fedify

The developer of Fedify has built Hollo with it. This is intended as a single-user instance for microblogging.

github.com/fedify-dev/hollo

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.)

@esurio1673 ご指摘ありがとうございます！先ほど更新しました！

#Fediverseサーバープロフ帳 でプロフィールカードを作成しました！ https://purofu.y-zu.org/view/server?id=142 #サーバープロフ帳 #サーバープロフィール帳 #サーバー紹介

@julian @fedify Probably. Stay tuned!

I have great respect for @thisismissem's tremendous work on @hollo.😲

https://hachyderm.io/@thisismissem/114056333638591578

Found the slowness! It was because each account that was created for the tests generated two keypairs for activitypub usage. We don't need those for these tests.

Now they run in like 150ms each, or a 10x increase in speed.

One of the things I'm wanting to do is also implement some of the **planned** OAuth functionality for Mastodon in @hollo first to get a feel for how it works — I'm way better at writing typescript compared to ruby.

So things like Device Code Grant Flow for input constrained devices (sign-in to hollo on your TV or retro computer), or supporting access token expiration and Client ID Metadata Documents (which removes the need for a client to pre-register with a given server before doing an oauth flow).

Another @hollo pull request for this weekend: improving the testability of the OAuth related code.

I was supposed to be having a "me" day and relaxing, but I started having a coughing fit and needing to focus on something to help calm my system down, and what better than a refactor?

https://github.com/fedify-dev/hollo/pull/126

This is part of the work to improve how @hollo does OAuth and to bring it up to par with Mastodon 4.3

However, one of those next steps requires a rather major refactor of how we do authorization grants and access tokens. Before we make those changes it would be great to be able to have some baseline test coverage in place.

Related issues:
- https://github.com/fedify-dev/hollo/issues/125
- https://github.com/fedify-dev/hollo/issues/49
- https://github.com/fedify-dev/hollo/issues/44
- https://github.com/fedify-dev/hollo/issues/14

I am overwhelmed with joy to receive @thisismissem's gift of patches to @hollo!

https://hachyderm.io/@thisismissem/114048984038803235

Wooo! I have tests running for @hollo that interact with the site as a logged in user, and uploads a custom emoji and verifies that it was uploaded using fake storage driver for testing.

https://github.com/fedify-dev/hollo/pull/121

만약 Hollo의 호스팅 서비스를 보신 분이 계시다면, 저희에게 알려주세요!

Holloのホスティングサービスを見かけた場合は、是非お知らせください！

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.)

Have been working on a few things for @hollo today, one of the public things is setting up testing for the codebase: https://github.com/fedify-dev/hollo/pull/114

There's still some work to do, but it's a start.

@hollo @hongminhee When's the FEP for a custom actor property for the profile accent color? 😇

#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 0.5.2！なおった！

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.)

@hollo464 That's really a good idea! We're considering to package Hollo for those platforms.

@hollo I this this would be a great initiative, something that would quell any concerns I might have is designing a way to migrate to another host without any technical knowledge from the get-go. Maybe you could work out a system so something like @fedihost or @spacehost etc could support an automatic transfer of a hosted server and configure that all so that the user doesn't need to know any command line stuff in order to move away from your hosting but still have a path to keep their instance

Really looking forward to shipping @noim's this patch, which implements FEP-ae0c-compliant relays support!

Thank you very much, @noim!

https://noc.social/@noim/114009749110355059

Coming soon™℠®© to @hollo as PR

みなさん、こんにちは！

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

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

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

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

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

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

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

#Hollo #アンケート #フェディバース

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

안녕하세요!

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

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

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

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

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

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

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

#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!

#poll #fediverse

みなさん、こんにちは！

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

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

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

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

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

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

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

#Hollo #アンケート #フェディバース

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