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

Oh! Also had another API added to Mastodon today: currently when you attach media there's no way to immediately get it deleted, this changes that by allowing clients to delete media not yet attached to any status: https://github.com/mastodon/mastodon/pull/33991

This came about because I was looking at the media upload handling in @hollo the other weekend

Fedifyの関連プロジェクトをご紹介したいと思います。ActivityPubアプリケーション開発をより簡単にするツール群です：

Fedify

Fedify（@fedify）はActivityPubやその他のフェディバース標準を活用する連合型サーバーアプリケーションを構築するためのTypeScriptライブラリです。Activity Vocabularyの型安全なオブジェクト、WebFingerクライアント・サーバー、HTTP Signaturesなどを提供し、ボイラープレートコードを削減してアプリケーションロジックに集中できるようにします。

Hollo

Hollo（@hollo）はFedifyで動作するお一人様用マイクロブログサーバーです。個人向けに設計されていますが、ActivityPubを通じて完全に連合化されており、フェディバース全体のユーザーと交流することができます。HolloはMastodon互換APIを実装しているため、独自のウェブインターフェースがなくても、ほとんどのMastodonクライアントと互換性があります。

Holloはまた、正式リリース前の最新Fedify機能をテストする実験場としても活用されています。

BotKit

BotKit（@botkit）は私たちの最も新しいメンバーで、ActivityPubボットを作成するために特別に設計されたフレームワークです。従来のMastodonボットとは異なり、BotKitはプラットフォーム固有の制限（文字数制限など）に縛られない独立したActivityPubサーバーを作成します。

BotKitのAPIは意図的にシンプルに設計されており、単一のTypeScriptファイルで完全なボットを作成できます！

これら三つのプロジェクトはすべて@fedify-dev GitHubオーガニゼーションでオープンソースとして公開されています。それぞれ異なる目的を持っていますが、ActivityPub開発をより身近にし、フェディバースのエコシステムを拡大するという共通の目標を共有しています。

これらのプロジェクトを試してみたり、開発に貢献したりすることに興味がある場合は、以下をご覧ください：

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

#Fedify #ActivityPub #フェディバース #fediverse #Hollo #BotKit #fedidev

#Fedify 자매 프로젝트들을 소개해 드리고자 합니다. #ActivityPub 애플리케이션 개발을 더 쉽게 만들어주는 관련 도구들입니다:

Fedify

Fedify(@fedify)는 ActivityPub와 다른 #연합우주(#fediverse) 표준을 기반으로 연합 서버 애플리케이션을 구축하기 위한 #TypeScript 라이브러리입니다. Activity Vocabulary를 위한 타입 안전한 객체, WebFinger 클라이언트·서버, HTTP Signatures 등를 제공하여 반복적인 코드를 줄이고 애플리케이션 로직에 집중할 수 있게 해줍니다.

Hollo

Hollo(@hollo)는 Fedify로 구동되는 1인 사용자용 마이크로블로깅 서버입니다. 1인 사용자를 위해 설계되었지만, ActivityPub를 통해 완전히 연합되어 연합우주 전체의 사용자들과 상호작용할 수 있습니다. Hollo는 Mastodon 호환 API를 구현하여 자체 웹 인터페이스 없이도 대부분의 Mastodon 클라이언트와 호환됩니다.

Hollo는 또한 정식 출시 전에 최신 Fedify 기능을 테스트하는 실험장으로도 활용되고 있습니다.

BotKit

BotKit(@botkit)은 저희의 가장 새로운 구성원으로, ActivityPub 봇을 만들기 위해 특별히 설계된 프레임워크입니다. 전통적인 Mastodon 봇과 달리, BotKit은 플랫폼별 제한(글자 수 제한 등)에 구애받지 않는 독립적인 ActivityPub 서버를 만듭니다.

BotKit의 API는 의도적으로 단순하게 설계되어 단일 TypeScript 파일로 완전한 봇을 만들 수 있습니다!

세 프로젝트 모두 @fedify-dev GitHub 조직에서 오픈 소스로 공개되어 있습니다. 각기 다른 목적을 가지고 있지만, ActivityPub 개발을 더 접근하기 쉽게 만들고 연합우주 생태계를 확장한다는 공통된 목표를 공유합니다.

이러한 프로젝트를 사용해보거나 개발에 기여하는 데 관심이 있으시다면, 다음을 확인해보세요:

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

#fedidev #Hollo #BotKit

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