Hollo :hollo:'s avatar

Hollo :hollo:

@hollo@hollo.social

200 following871 followers

:hollo: A federated single-user microblogging software.

Website

https://hollo.social/

GitHub

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

Fedify

https://fedify.dev/

Pinned

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

洪 民憙 (Hong Minhee) :nonbinary:
@hongminhee@hollo.social

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

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

hachyderm.io

Emelia 👸🏻 (@thisismissem@hachyderm.io)

Extended my previous contribution to @hollo@hollo.social tonight with some tests for the `GET /api/v1/accounts/verify_credentials` route: https://github.com/fedify-dev/hollo/pull/126/files#diff-944986dc760a778a36a291dd17b1e234ece1252336b9eefed1032e64a468601e There's some magic going on here, but I'm pretty happy with the results. Though, node.js's test runner seems really slow at times and I've no idea why, like some of these are taking 1-4 seconds, whereas other tests are 54ms. I've tried instrumenting the code to find slownesses and I can't, everything's taking only milliseconds.

Emelia 👸🏻
@thisismissem@hachyderm.io

Extended my previous contribution to @hollo tonight with some tests for the `GET /api/v1/accounts/verify_credentials` route:

github.com/fedify-dev/hollo/pu

There's some magic going on here, but I'm pretty happy with the results.

Though, node.js's test runner seems really slow at times and I've no idea why, like some of these are taking 1-4 seconds, whereas other tests are 54ms. I've tried instrumenting the code to find slownesses and I can't, everything's taking only milliseconds.

github.com

Refactor OAuth logic for improved testability by ThisIsMissEm · Pull Request #126 · fedify-dev/hollo

Overview This pull request aims to improve the ability to write tests for the OAuth routes & middleware by extracting out helpers to create authorization codes, access tokens and client credent...

Emelia 👸🏻
@thisismissem@hachyderm.io · Reply to Emelia 👸🏻

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.

Emelia 👸🏻
@thisismissem@hachyderm.io · Reply to Emelia 👸🏻

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

Emelia 👸🏻
@thisismissem@hachyderm.io

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?

github.com/fedify-dev/hollo/pu

github.com

Refactor OAuth logic for improved testability by ThisIsMissEm · Pull Request #126 · fedify-dev/hollo

Overview This pull request aims to improve the ability to write tests for the OAuth routes & middleware by extracting out helpers to create authorization codes, access tokens and client credent...

Emelia 👸🏻
@thisismissem@hachyderm.io · Reply to Emelia 👸🏻

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:
- github.com/fedify-dev/hollo/is
- github.com/fedify-dev/hollo/is
- github.com/fedify-dev/hollo/is
- github.com/fedify-dev/hollo/is

github.com

Automated tests · Issue #14 · fedify-dev/hollo

Surprisingly, Hollo does not have any automated tests at all. It currently only relies on type checker. We need unit tests at least for the core logic.

洪 民憙 (Hong Minhee) :nonbinary:
@hongminhee@hollo.social

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

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

hachyderm.io

Emelia 👸🏻 (@thisismissem@hachyderm.io)

Wooo! I have tests running for @hollo@hollo.social 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

Emelia 👸🏻
@thisismissem@hachyderm.io

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.

github.com/fedify-dev/hollo/pu

github.com

Refactor storage to use DriveManager, enabling testing by ThisIsMissEm · Pull Request #121 · fedify-dev/hollo

This implements #115, and also adds some initial test coverage to the route for saving a new custom emoji. Breaking Changes Replaces FS_ASSET_PATH with FS_STORAGE_PATH Replaces ASSET_URL_BASE with...

Emelia 👸🏻
@thisismissem@hachyderm.io

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.

github.com/fedify-dev/hollo/pu

github.com

Refactor storage to use DriveManager, enabling testing by ThisIsMissEm · Pull Request #121 · fedify-dev/hollo

This implements #115, and also adds some initial test coverage to the route for saving a new custom emoji. Breaking Changes Replaces FS_ASSET_PATH with FS_STORAGE_PATH Replaces ASSET_URL_BASE with...

Emelia 👸🏻
@thisismissem@hachyderm.io

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

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

github.com

Feat: setup testing infrastructure by ThisIsMissEm · Pull Request #114 · fedify-dev/hollo

This changes src/index.tsx to not directly start the application, but instead to just create it, such that it can be required in different scenarios. The entrypoint bin/server.ts is now used instea...

Hollo :hollo:
@hollo@hollo.social

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.

The profile page of @botkit@hollo.social with a lime color.
ALT text

The profile page of @botkit@hollo.social with a lime color.

The profile page of @fedify@hollo.social with a blue color.
ALT text

The profile page of @fedify@hollo.social with a blue color.

The profile page of @hollo@hollo.social with a slate color.
ALT text

The profile page of @hollo@hollo.social with a slate color.

The profile page of @hongminhee@hollo.social with an amber color.
ALT text

The profile page of @hongminhee@hollo.social with an amber color.

wakest ⁂
@liaizon@wake.st · Reply to Hollo :hollo:

@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

洪 民憙 (Hong Minhee) :nonbinary:
@hongminhee@hollo.social

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

noc.social

noim (@noim@noc.social)

Attached: 1 image Coming soon™℠®© to @hollo@hollo.social as PR

noim
@noim@noc.social

Coming soon™℠®© to @hollo as PR

Work in progress relay management screen in hollo. Shows relay add input and table of added relays.
ALT text

Work in progress relay management screen in hollo. Shows relay add input and table of added relays.

noim
@noim@noc.social

Coming soon™℠®© to @hollo as PR

Work in progress relay management screen in hollo. Shows relay add input and table of added relays.
ALT text

Work in progress relay management screen in hollo. Shows relay add input and table of added relays.

Hollo :hollo:
@hollo@hollo.social · Reply to Hollo :hollo:

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

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

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

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

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

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

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

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

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

hollo.social

#Hollo everyone! :hollo: We'd…

#Hollo 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@opencollective.com. 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:
@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!

  • 1️⃣ Great idea! I'd be interested in supporting and using the hosted service.26 (45%)
  • 2️⃣ Sounds good! I'll stick to self-hosting but support the initiative.29 (50%)
  • 3️⃣ I think we should explore other ways to increase support.2 (3%)
  • 4️⃣ I prefer Hollo to remain purely self-hosted.1 (2%)
Hollo :hollo:
@hollo@hollo.social · Reply to Hollo :hollo:

안녕하세요! :hollo:

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

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

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

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

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

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

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

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

hollo.social

#Hollo everyone! :hollo: We'd…

#Hollo 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@opencollective.com. 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:
@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!

  • 1️⃣ Great idea! I'd be interested in supporting and using the hosted service.26 (45%)
  • 2️⃣ Sounds good! I'll stick to self-hosting but support the initiative.29 (50%)
  • 3️⃣ I think we should explore other ways to increase support.2 (3%)
  • 4️⃣ I prefer Hollo to remain purely self-hosted.1 (2%)
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!

  • 1️⃣ Great idea! I'd be interested in supporting and using the hosted service.26 (45%)
  • 2️⃣ Sounds good! I'll stick to self-hosting but support the initiative.29 (50%)
  • 3️⃣ I think we should explore other ways to increase support.2 (3%)
  • 4️⃣ I prefer Hollo to remain purely self-hosted.1 (2%)
Hollo :hollo:
@hollo@hollo.social · Reply to Hollo :hollo:

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

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

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

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

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

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

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

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

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

hollo.social

#Hollo everyone! :hollo: We'd…

#Hollo 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@opencollective.com. 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:
@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!

  • 1️⃣ Great idea! I'd be interested in supporting and using the hosted service.26 (45%)
  • 2️⃣ Sounds good! I'll stick to self-hosting but support the initiative.29 (50%)
  • 3️⃣ I think we should explore other ways to increase support.2 (3%)
  • 4️⃣ I prefer Hollo to remain purely self-hosted.1 (2%)
Hollo :hollo:
@hollo@hollo.social · Reply to Hollo :hollo:

안녕하세요! :hollo:

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

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

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

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

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

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

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

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

hollo.social

#Hollo everyone! :hollo: We'd…

#Hollo 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@opencollective.com. 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:
@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!

  • 1️⃣ Great idea! I'd be interested in supporting and using the hosted service.26 (45%)
  • 2️⃣ Sounds good! I'll stick to self-hosting but support the initiative.29 (50%)
  • 3️⃣ I think we should explore other ways to increase support.2 (3%)
  • 4️⃣ I prefer Hollo to remain purely self-hosted.1 (2%)
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!

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