
yamanoku
HolloをRailwayにデプロイする時の作業ログをZenn Scrapsにまとめました。躓いた個所もあったのでこれからデプロイしてやってみたい人に届け~ #Hollo https://zenn.dev/yamanoku/scraps/546b887da013d9
HolloをRailwayにデプロイする時の作業ログをZenn Scrapsにまとめました。躓いた個所もあったのでこれからデプロイしてやってみたい人に届け~ #Hollo https://zenn.dev/yamanoku/scraps/546b887da013d9
Eg har nett støtta @fedify ! Dei har fleire kule prosjekt. @[email protected] køyrer på deira teneste @hollo.
English:
I've just contributed to #Fedify They have several cool projects. @[email protected] runs on their service #Hollo.
@[email protected] · Reply to Hollo :hollo:'s post
Eg har nett støtta @fedify ! Dei har fleire kule prosjekt. @[email protected] køyrer på deira teneste @hollo.
English:
I've just contributed to #Fedify They have several cool projects. @[email protected] runs on their service #Hollo.
HolloをRailwayにデプロイする時の作業ログをZenn Scrapsにまとめました。躓いた個所もあったのでこれからデプロイしてやってみたい人に届け~ #Hollo https://zenn.dev/yamanoku/scraps/546b887da013d9
@[email protected] · 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
이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다.
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
We've just moved the #Fedify 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!
New GitHub organization: https://github.com/fedify-dev.
@[email protected] · 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 #fediverse #フェディバース #Docker #ドッカー
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
We've just moved the #Fedify 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!
New GitHub organization: https://github.com/fedify-dev.
The #Hollo repository has moved from @dahlia/hollo to @fedify-dev/hollo! Along with this move, our #Docker 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:
ghcr.io/dahlia/hollo:latest
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!
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
We've just moved the #Fedify 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!
New GitHub organization: https://github.com/fedify-dev.
Hei!
Eg er forfattar Markus Pedersen. Eg har tidlegare gjeve ut ein teikneserietrilogi om nokre udugelege superheltar kalla #UdugelegeHeltar (https://www.uberpress.no/collections/udugeleg-collection).
For tida prøvar eg meg i heilt andre banar enn superheltar med dikt og anna kortprosa. Eg er i ein prosess med å sende nokre samlingar rundt til forlag.
På denne kontoen har eg tenkt å leggje ut nokre av desse tekstane eg skriv. Dei kan gjerne vera litt for lange for ein vanleg #Mastodon-konto, og difor nyttar eg #Hollo til dette.
Det kjem til å vera ein del tekstar med tung tematikk, eg skal prøve å vera flink med innhaldsfilter på dei aller tyngste.
Min kvardagslege konto er @markus. Eg nyttar den som ein småblogg, så der finn du allslags tankar om allslags greiar.
Eg vonar du vil følgje meg her sjølv om du følgjar meg annastads allereie!
Hollo 0.4.0 released! #Hollo is a single-user federated microblogging software which is #ActivityPub-enabled and powered by #Fedify.
The key changes of this release include:
Hollo is now powered by Node.js 23+ instead of Bun for more efficient memory usage.
Added an experimental feature flag TIMELINE_INBOXES
to store all posts visible to your timeline in the database, rather than filtering them in real-time as they are displayed. This is useful for relatively larger instances with many incoming posts, but as of now it may have several bugs. It is expected to be the default behavior in the future after it is stabilized.
Now you can import and export your data from the administration dashboard in CSV format: follows, lists, accounts you muted, accounts you blocked, and bookmarks.
You can now make your profile discoverable
.
The profile page now shows an account's cover image if it has one.
Many bug fixes.
For the details, see also the full changelog.
You can upgrade to Hollo 0.4.0 using the following ways:
To Railway users: Just redeploy the Hollo service!
To Docker users: Switch your Hollo image to ghcr.io/dahlia/hollo:0.4.0
or simply latest
!
To manual installers:
Install Node.js 23 or higher.
Fetch the stable
branch and switch over to it.
Run pnpm install
.
Run pnpm run prod
to start the Hollo server.
#Hollo is currently testing #Node.js instead of #Bun. (In fact, the hollo.social server is already running on Node.js!) If this test is successful, starting with the next release, Hollo will be powered by Node.js instead of Bun.
The main reason for switching to Node.js is to optimize memory usage. As you can see in the graph image below, Node.js uses significantly less memory than Bun. With this switch, Hollo is expected to be even more lightweight than before!
Are you interested in trying out the Node.js version of Hollo early? Try to pull ghcr.io/dahlia/hollo:0.4.0-dev.290
!
Hollo 0.4.0 released! #Hollo is a single-user federated microblogging software which is #ActivityPub-enabled and powered by #Fedify.
The key changes of this release include:
Hollo is now powered by Node.js 23+ instead of Bun for more efficient memory usage.
Added an experimental feature flag TIMELINE_INBOXES
to store all posts visible to your timeline in the database, rather than filtering them in real-time as they are displayed. This is useful for relatively larger instances with many incoming posts, but as of now it may have several bugs. It is expected to be the default behavior in the future after it is stabilized.
Now you can import and export your data from the administration dashboard in CSV format: follows, lists, accounts you muted, accounts you blocked, and bookmarks.
You can now make your profile discoverable
.
The profile page now shows an account's cover image if it has one.
Many bug fixes.
For the details, see also the full changelog.
You can upgrade to Hollo 0.4.0 using the following ways:
To Railway users: Just redeploy the Hollo service!
To Docker users: Switch your Hollo image to ghcr.io/dahlia/hollo:0.4.0
or simply latest
!
To manual installers:
Install Node.js 23 or higher.
Fetch the stable
branch and switch over to it.
Run pnpm install
.
Run pnpm run prod
to start the Hollo server.
#Hollo is currently testing #Node.js instead of #Bun. (In fact, the hollo.social server is already running on Node.js!) If this test is successful, starting with the next release, Hollo will be powered by Node.js instead of Bun.
The main reason for switching to Node.js is to optimize memory usage. As you can see in the graph image below, Node.js uses significantly less memory than Bun. With this switch, Hollo is expected to be even more lightweight than before!
Are you interested in trying out the Node.js version of Hollo early? Try to pull ghcr.io/dahlia/hollo:0.4.0-dev.290
!
One hidden feature of #Hollo: You can also quote another post while replying to someone else's post.
We'll be releasing #Hollo 0.4.0 before the year is out. Stay tuned!
@[email protected] · Reply to Hollo :hollo:'s post
#Hollo is currently testing #Node.js instead of #Bun. (In fact, the hollo.social server is already running on Node.js!) If this test is successful, starting with the next release, Hollo will be powered by Node.js instead of Bun.
The main reason for switching to Node.js is to optimize memory usage. As you can see in the graph image below, Node.js uses significantly less memory than Bun. With this switch, Hollo is expected to be even more lightweight than before!
Are you interested in trying out the Node.js version of Hollo early? Try to pull ghcr.io/dahlia/hollo:0.4.0-dev.290
!
For the sake of dogfooding #Hollo, which I'm working on, I'm moving to @[email protected], a new account created with Hollo. My follower list will automatically be handed over, so there's nothing you need to do, and I wish you well with my new account!
@[email protected] · Reply to KazukyAkayashi's post
@KazukyAkayashi visiblement depuis iceshrimp y a des problèmes de mise en page avec des messages publié sur #Moshidon depuis mon compte #Hollo, avec des double saut de ligne
Et chez vous ça donne quoi?
@[email protected] · Reply to KazukyAkayashi's post
C'est vraiment dommage du coup que #Hollo ne fonctionne pas avec #Mangane car je suis pas fan de #Phanpy ou de #Elk
Quand a #Moshidon avec Hollo sur Android ça bug un peu, y a des doubles publication, des images en double dans des publication alors qu'il n'y a qu'une image de base.
Puis en globalité ça manque d'un client qui gère toutes les fonctionnalités disponible ... parce que bon ce limité a ce que peut faire Mastodon merci mais c'est merdique.
@[email protected] · Reply to KazukyAkayashi's post
Du coup le stockage local fonctionne nickel 👍
@[email protected] · Reply to KazukyAkayashi's post
Hmm bon #Hollo ne démarre plus depuis la 0.2.x et le passage a la 0.3.0 ne change rien, même sur une fresh install j'ai les même problème PostgresError
Hollo 0.3.0 released! #Hollo is a single-user federated microblogging software which is #ActivityPub-enabled and powered by #Fedify.
The key changes of this release include:
DRIVE_DISK=fs
and FS_ASSET_PATH
to store media files in the local filesystem. For users who've used S3, no further action is required—but, it's recommended to configure DRIVE_DISK=s3
as DRIVE_DISK
will be required in the future releases.SENTRY_DSN
.You can upgrade to Hollo 0.3.0 using the following ways:
ghcr.io/dahlia/hollo:0.3.0
or simply latest
!stable
branch and switch over to it!working on #Hollo support
The #Hollo v0.2.3 has been released, which fixes a few bugs and brings #Fedify to the latest version, v1.2.7. If you are using the Docker image, you can upgrade by using the ghcr.io/dahlia/hollo:0.2.3
.
#hollo タニタのページを貼るとエラー出るの、まじでバグっぽい https://gist.github.com/ntsklab/3bb1c72fc6dda82a54f6171ff4c8c679
#logtape #hollo #package Simple logging library with zero dependencies for Deno, Node.js, Bun, browsers, and edge functions https://logtape.org/
#fedify #hollo #package ActivityPub server framework in TypeScript https://fedify.dev/
Star History of #Fedify, #Hollo, and #LogTape:
https://star-history.com/#dahlia/fedify&dahlia/logtape&dahlia/hollo&Date
Yeah the hollo.service
works 👍
All that's left now is to wait for local storage support (because at the moment there's only support for storage on S3).
#Hollo #Fediverse
@hongminhee お疲れ様です。HolloとFedifyのチラシが無事届きました〜
KOFなどで配布しますね
@[email protected] · Reply to Kazuky Akayashi ฅ^•ﻌ•^ฅ's post
Hmm I can't start Hollo with systemd, I don't really understand why.
I've tried the example given on the Bun website, I think the problem comes from this line :
ExecStart=/home/my_user/.bun/bin/bun run index.ts
@[email protected] · Reply to Kazuky Akayashi ฅ^•ﻌ•^ฅ's post
Bon bah j'ai n'y les moyens financier, ni matériel (en plus d'y connaitre quedale) de faire du S3 du coup ça bloque totalement l'utilisation de Hollo
En espérant que le stockage local soit rajouté dans les prochaines versions.
#Hollo #Fediverse
@[email protected] · Reply to Kazuky Akayashi ฅ^•ﻌ•^ฅ's post
Bon bah ça fonctionne pas mal du tout
Va juste falloir mettre un truc de stockage en place pour tester bien la chose.
#Hollo #Fediverse
RE: hollo.zarchbox.fr/@KazukyAkayashi/0192fda2-f090-7c21-9a15-4d1896aa573f
Hello world 👋
Hello world 👋
@[email protected] · Reply to Kazuky Akayashi ฅ^•ﻌ•^ฅ's post
Ah bah zut alors Mangane ça marche pas avec Hollo
#Hollo #Mangane #Fediverse
@[email protected] · Reply to Kazuky Akayashi ฅ^•ﻌ•^ฅ's post
Aie gros points noir :
- une dépendance a cdn.jsdelivr.net sur l'interface web.
- et visiblement l'obligation d'avoir un S3 compatible pour les medias
Je vais tester le reste mais ça semble pas mal foutu dans la même veine que GotoSocial mais qui fonctionne mieux
#Hollo #Fediverse
주말부터 #hollo 를 #nixos 모듈로 작성하고 있는데 어느 정도 마무리가 된 듯하다. 지금은 개발이 빠르게 진행되고 있어서 nixpkgs에 올리는 건 나중에 생각해 보는 걸로..
패키지: https://github.com/honnip/dotfiles/blob/3e52a09afc680ecaff6c0d7dfff414f507af3f8a/pkgs/hollo/default.nix 모듈: https://github.com/honnip/dotfiles/blob/3e52a09afc680ecaff6c0d7dfff414f507af3f8a/modules/nixos/hollo.nix
Hollo 0.2.0 released! #Hollo is a single-user federated microblogging software which is #ActivityPub-enabled and powered by #Fedify.
The key changes of this release include:
Thanks to @thisismissem, now you can report remote accounts and posts.
Added two-factor authentication support.
Thanks again to @thisismissem, Hollo improved alignment on Mastodon API changes about OAuth and apps.
Thanks again to @thisismissem, RFC 8414 for OAuth Authorization Server metadata endpoint. It will improve interoperability between Hollo and Mastodon-compatible client apps.
Renamed the Data menu from the administration dashboard to Federation, and:
Custom emojis now can be deleted from the administration dashboard.
Thanks to @helge, PORT
and ALLOW_PRIVATE_ADDRESS
environment variables are introduced.
Added a favicon.
Dropped support for Redis, which was an optional dependency.
You can upgrade to Hollo 0.2.0 using the following ways:
To Railway users: Just redeploy the Hollo service!
To Docker users: Switch your Hollo image to ghcr.io/dahlia/hollo:0.2.0
or simply latest
!
To manual installers: Fetch the stable
branch and switch over to it!
In the next version of #Hollo, you'll see the number of messages stacked in your task queue in the administration dashboard. This gives you an idea of how busy your instance is.
The next version of #Hollo's administration dashboard will have a Federation menu instead of a Data menu, and will allow you to force refresh posts as well as accounts.
If you'd like to support the development of #Fedify or #Hollo, you can sponsor me on GitHub!
10月26日(土)に開催されるOSC 2024 Tokyo/FallにFedify/Hollo合同で出展します!可愛いFedifyのロゴのシールと『自分だけのフェディバースのマイクロブログを作ろう!』日本語版の紙の本を持って行く予定です。よろしくお願いします。
#Hollo 0.2.0 will have two-factor authentication support using time-based OTP!
If you want to give it a try right now, you can get it in ghcr.io/dahlia/hollo:0.2.0-dev.183
or just canary
.
#Hollo's GitHub repository now has 200 stars!
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.
#Hollo is a headless microblogging software that implements the Mastodon API. This means that you can use any Mastodon-compatible client to interact with it. However, in practice, some clients may not work as expected due to differences in the way they implement the Mastodon API. Here are some of the clients that have been tested with Hollo:
#Hollo finally has #Misskey/#Threads-style quotes! It's easy to use. Just paste the link to the post you want to quote into your post! It will automatically recognize a link to an ActivityPub post (supports Article
, Note
, and Question
) and turn it into a quote.
FYI, if you're using #Phanpy, you can use the Quote button that appears when you press the boost icon!
https://hollo.social/@fedify/0191d67c-a300-786e-8395-2020ac47ebc7
@[email protected] · Reply to Hollo :hollo:'s post
From your view, what are the top priorities for future #Hollo development?
Option | Voters |
---|---|
Polls | 0 (0%) |
Lists | 3 (33%) |
Search | 6 (67%) |
Custom emojis | 0 (0%) |
#Hollo now supports sharing posts (reblogs)!
@[email protected] · Reply to 洪 民憙 (Hong Minhee) 🤏🏼's post
@[email protected] · Reply to 洪 民憙 (Hong Minhee) 🤏🏼's post
Here's the #Hollo source code in progress:
@[email protected] · Reply to 洪 民憙 (Hong Minhee) 🤏🏼's post
What image comes to mind when you hear the word “#Hollo” (not “hello”)?
The max_id, since_id, and min_id parameters in #Mastodon's Timeline API assume that the post ID is a sortable number. (Is this correct?) #Hollo, the #ActivityPub implementation I'm building, uses UUIDs for post IDs internally, so I'm stuck on how to implement a Mastodon-compatible API.