Hollo :hollo:'s avatar

Hollo :hollo:

@hollo@hollo.social · 198 following · 821 followers

:hollo: A federated single-user microblogging software.

WebsiteGitHubFedify

https://hollo.social/

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

https://fedify.dev/

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

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to Woojin Kim's post

@me 네, 직접 이슈 등록해 주시면 더욱 감사하지요!

Hollo :hollo:'s avatar
Hollo :hollo:

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

@me 늦었지만 이 문제도 GitHub에 이슈로 등록했습니다.

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

ruru's avatar
ruru

@ruru@mi.ruruke.moe

holloはいいですよ。

피존's avatar
피존

@pijon@buttersc.one

홀로 유저 알음알음 많이 보여서 좋아보여

Buachi's avatar
Buachi

@b@techniclip.com

PleromaよりHollo気になってます

Buachi's avatar
Buachi

@b@techniclip.com

Holloを立てようと計画中なのだわ

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

@hongminhee@hollo.social

參考(참고)로 Hollo에는 저만 쓰려고 具顯(구현)한 SEONBI_URL이라는 文書化(문서화)되지 않은 設定(설정)이 있습니다. Seonbi API 서버의 URL을 設定(설정)하면 韓國語(한국어)로 글을 쓸 때 Seonbi가 後處理機(후처리기)로 作動(작동)하게 됩니다. 國漢文(국한문)을 쓰면 한글 讀音(독음)이 <ruby>로 달린다는 것이죠.

dai's avatar
dai

@dai@mastodon.social

@esurio1673 blog.esurio1673.net/posts/holl
変更項目もこまめに更新されていて素晴らしいです。
時間できたらこちらを参考にholloを試してみたいです。 cc @hongminhee

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to 염산하's post

@ysh 답변이 늦어져서 죄송합니다! 잘 찾으셨다니 다행입니다!

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 · 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: ActivityPub server framework's avatar
Fedify: ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: 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: ActivityPub server framework's avatar
Fedify: ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: 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: ActivityPub server framework's avatar
Fedify: ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: 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.

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

@fedify@hollo.social · Reply to Fedify: 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 Woojin Kim's post

@me 보고 감사합니다!

Hollo :hollo:'s avatar
Hollo :hollo:

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

@me GitHub에 이슈도 생성해 두었습니다.

https://github.com/dahlia/hollo/issues/98

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to Woojin Kim's post

@me 410 응답을 주는 서버에 대한 요청을 하다가 오류가 나는 것으로 보이네요. 조만간 패치를 릴리스하겠습니다!

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to Woojin Kim's post

@me 보고 감사합니다! 혹시 원래 쓰시던 계정 서버를 셧다운하셨나요?

Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to Björn Þór Jónsson's post

@bthj Sorry, we currently don't support split-domain configuration yet.

SorairoLake's avatar
SorairoLake

@sorairolake@misskey.io

Holloの公式サイトって日本語のページもあるんだ

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

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

Okay, since we couldn't get in touch with the @fedify account owner, we need a new name for our GitHub organization. Which alternative do you prefer?

Your suggestions for other names are welcome in the comments! We'll make the final decision based on your feedback.

OptionVoters
fedify-js16 (11%)
fedify-sdk14 (10%)
fedify-framework15 (11%)
fedify-dev48 (34%)
fedify-org48 (34%)
newflow's avatar
newflow

@newflow@uri.life

1인용 연합우주 소프트웨어
hollo.social/@hollo

やまのく's avatar
やまのく

@yamanoku@mastodon.social

Holloアカウント作ってみた
hollo.yamanoku.net/@yamanoku

ストレージ周りの連携が失敗してるっぽく連合ができない状態なのでまだ完了ではない…

치즈군★ 🧀's avatar
치즈군★ 🧀

@cheesekun@ppiy.ac

hollo 인스턴스를 세울까 싶은데 아직 자세히 알아보진 않아서 모르겠지만 플레로마처럼 마스토돈 FE를 사용하거나 할 수는 없을려나...

やまのく's avatar
やまのく

@yamanoku@mastodon.social

画像投稿ができるようになったので本格的にHolloで活動していこうと思います

Buachi's avatar
Buachi

@b@techniclip.com

Hollo、気になってる

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: ActivityPub server framework's avatar
Fedify: 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)
ALT text detailsDear 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)
Fedify: ActivityPub server framework's avatar
Fedify: 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)
ALT text detailsDear 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)
Hollo :hollo:'s avatar
Hollo :hollo:

@hollo@hollo.social · Reply to Markus 🌱:fosse:'s post

@markus We're looking into it! Thanks for reporting!

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

@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

← Newer
Older →