洪 民憙 (Hong Minhee)
If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!
If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!
If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!
If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!
If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!
If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!
If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!
If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!
If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!
If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!
If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!
If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!
If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!
If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!
@[email protected] · Reply to 洪 民憙 (Hong Minhee)'s post
「@fedify」や「@hollo」や「@botkit」の開発を支援したい方は、GitHubでスポンサーになってください!
https://github.com/sponsors/dahlia
#ActivityPub #fediverse #フェディバース #Fedify #Hollo #BotKit #スポンサー
If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!
If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!
@[email protected] · Reply to 洪 民憙 (Hong Minhee)'s post
「@fedify」や「@hollo」や「@botkit」の開発を支援したい方は、GitHubでスポンサーになってください!
https://github.com/sponsors/dahlia
#ActivityPub #fediverse #フェディバース #Fedify #Hollo #BotKit #スポンサー
@[email protected] · Reply to 洪 民憙 (Hong Minhee)'s post
「@fedify」や「@hollo」や「@botkit」の開発を支援したい方は、GitHubでスポンサーになってください!
https://github.com/sponsors/dahlia
#ActivityPub #fediverse #フェディバース #Fedify #Hollo #BotKit #スポンサー
@[email protected] · Reply to 洪 民憙 (Hong Minhee)'s post
제 프로젝트인 @fedify, @hollo, @botkit 等의 開發을 後援하고 싶으신 분들께서는, GitHub에서 제 스폰서가 되어 주세요!
https://github.com/sponsors/dahlia
#ActivityPub #fediverse #페디버스 #聯合宇宙 #연합우주 #Fedify #Hollo #BotKit #스폰서 #후원
If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!
@[email protected] · Reply to 洪 民憙 (Hong Minhee)'s post
「@fedify」や「@hollo」や「@botkit」の開発を支援したい方は、GitHubでスポンサーになってください!
https://github.com/sponsors/dahlia
#ActivityPub #fediverse #フェディバース #Fedify #Hollo #BotKit #スポンサー
If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!
@[email protected] · Reply to Kazuky Akayashi ฅ^•ﻌ•^ฅ's post
On verra bien ce qu'il en est, mais va falloir faire chauffer un peu l'instance
free -h
total used free shared buff/cache available
Mem: 973Mi 779Mi 67Mi 65Mi 267Mi 193Mi
Swap: 1.0Gi 0B 1.0Gi
@[email protected] · Reply to Kazuky Akayashi ฅ^•ﻌ•^ฅ's post
Bon j'ai rajouté 1Go de Swap, ce qui est pas une très bonne idée sur un SSD je pense, mais c'est pour voir si Hollo crash par manque de RAM quand il chauffe ou si c'est Hollo qui ce casse juste la tronche
#Hollo
So I updated my systemd service for Hollo.I'm not a master of systemd but it works very well.
[Unit]
Description=Hollo Social
After=network.target
[Service]
Type=simple
ExecStart=/usr/bin/pnpm run prod
WorkingDirectory=/your/hollo_path
User=YOUR_USER
Group=YOUR_USER_GROUP
Restart=on-failure
# Configures the time to wait before service is stopped forcefully.
TimeoutStopSec=5
[Install]
WantedBy=multi-user.target
So I updated my systemd service for Hollo.I'm not a master of systemd but it works very well.
[Unit]
Description=Hollo Social
After=network.target
[Service]
Type=simple
ExecStart=/usr/bin/pnpm run prod
WorkingDirectory=/your/hollo_path
User=YOUR_USER
Group=YOUR_USER_GROUP
Restart=on-failure
# Configures the time to wait before service is stopped forcefully.
TimeoutStopSec=5
[Install]
WantedBy=multi-user.target
@[email protected] · Reply to Hollo :hollo:'s post
この件に関連して、Holloもセキュリティアップデートをリリースしました。0.3.6または0.4.4バージョンに今すぐアップデートしてください!
https://hollo.social/@fedify/0194848e-7cac-7af3-941b-c93999a51274
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
FedifyのWebFinger実装における脆弱性CVE-2025-23221に対するセキュリティアップデート(1.0.14、1.1.11、1.2.11、1.3.4)をリリースいたしました。すべてのユーザー様におかれましては、お使いのバージョンに応じた最新版への速やかなアップデートを推奨いたします。
セキュリティ研究者により、FedifyのlookupWebFinger()
関数において以下のセキュリティ上の問題が発見されました:
本セキュリティアップデートでは、以下の修正が実施されました:
以下のコマンドで最新のセキュアバージョンにアップデートできます:
# npmユーザーの場合
npm update @fedify/fedify
# Denoユーザーの場合
deno add jsr:@fedify/fedify
この脆弱性を責任を持って報告していただいたセキュリティ研究者の方に感謝申し上げます。迅速な対応が可能となりました。
本脆弱性の詳細については、セキュリティ勧告をご参照ください。
ご質問やご懸念がございましたら、GitHub Discussions、Matrixチャットスペース、またはDiscordサーバーまでお気軽にご連絡ください。
@[email protected] · Reply to Hollo :hollo:'s post
この件に関連して、Holloもセキュリティアップデートをリリースしました。0.3.6または0.4.4バージョンに今すぐアップデートしてください!
https://hollo.social/@fedify/0194848e-7cac-7af3-941b-c93999a51274
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
FedifyのWebFinger実装における脆弱性CVE-2025-23221に対するセキュリティアップデート(1.0.14、1.1.11、1.2.11、1.3.4)をリリースいたしました。すべてのユーザー様におかれましては、お使いのバージョンに応じた最新版への速やかなアップデートを推奨いたします。
セキュリティ研究者により、FedifyのlookupWebFinger()
関数において以下のセキュリティ上の問題が発見されました:
本セキュリティアップデートでは、以下の修正が実施されました:
以下のコマンドで最新のセキュアバージョンにアップデートできます:
# npmユーザーの場合
npm update @fedify/fedify
# Denoユーザーの場合
deno add jsr:@fedify/fedify
この脆弱性を責任を持って報告していただいたセキュリティ研究者の方に感謝申し上げます。迅速な対応が可能となりました。
本脆弱性の詳細については、セキュリティ勧告をご参照ください。
ご質問やご懸念がございましたら、GitHub Discussions、Matrixチャットスペース、またはDiscordサーバーまでお気軽にご連絡ください。
@[email protected] · Reply to Hollo :hollo:'s post
この件に関連して、Holloもセキュリティアップデートをリリースしました。0.3.6または0.4.4バージョンに今すぐアップデートしてください!
https://hollo.social/@fedify/0194848e-7cac-7af3-941b-c93999a51274
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
FedifyのWebFinger実装における脆弱性CVE-2025-23221に対するセキュリティアップデート(1.0.14、1.1.11、1.2.11、1.3.4)をリリースいたしました。すべてのユーザー様におかれましては、お使いのバージョンに応じた最新版への速やかなアップデートを推奨いたします。
セキュリティ研究者により、FedifyのlookupWebFinger()
関数において以下のセキュリティ上の問題が発見されました:
本セキュリティアップデートでは、以下の修正が実施されました:
以下のコマンドで最新のセキュアバージョンにアップデートできます:
# npmユーザーの場合
npm update @fedify/fedify
# Denoユーザーの場合
deno add jsr:@fedify/fedify
この脆弱性を責任を持って報告していただいたセキュリティ研究者の方に感謝申し上げます。迅速な対応が可能となりました。
本脆弱性の詳細については、セキュリティ勧告をご参照ください。
ご質問やご懸念がございましたら、GitHub Discussions、Matrixチャットスペース、またはDiscordサーバーまでお気軽にご連絡ください。
@[email protected] · Reply to Hollo :hollo:'s post
이와 관련하여, #Hollo 역시 #보안 업데이트가 이뤄졌습니다. 0.3.6 또는 0.4.4 버전으로 바로 업데이트하시기 바랍니다!
https://hollo.social/@fedify/0194848b-3b9e-7da1-b631-c011db2f4c43
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
#Fedify 프레임워크의 #WebFinger 구현에서 발견된 보안 취약점 CVE-2025-23221을 해결하기 위한 보안 업데이트(1.0.14, 1.1.11, 1.2.11, 1.3.4)를 배포했습니다. 모든 사용자께서는 각자 사용 중인 버전에 해당하는 최신 버전으로 즉시 업데이트하시기를 권장합니다.
보안 연구자가 Fedify의 lookupWebFinger()
함수에서 다음과 같은 보안 문제점들을 발견했습니다:
이번 보안 업데이트에는 다음과 같은 수정 사항이 포함되어 있습니다:
다음 명령어로 최신 보안 버전으로 업데이트하실 수 있습니다:
# npm 사용자의 경우
npm update @fedify/fedify
# Deno 사용자의 경우
deno add jsr:@fedify/fedify
이 취약점을 책임감 있게 보고해 주신 보안 연구자께 감사드립니다. 덕분에 신속하게 문제를 해결할 수 있었습니다.
이 취약점에 대한 자세한 내용은 보안 권고문을 참고해 주시기 바랍니다.
문의 사항이나 우려 사항이 있으시다면 GitHub Discussions나 Matrix 채팅방, 또는 Discord 서버를 통해 언제든 연락해 주시기 바랍니다.
In related news, #Hollo has also released #security updates: 0.3.6 & 0.4.4. Update now!
https://hollo.social/@fedify/01948487-87b2-709d-953f-8799b78433ed
We have released #security updates (1.0.14, 1.1.11, 1.2.11, 1.3.4) to address CVE-2025-23221, a #vulnerability in #Fedify's #WebFinger implementation. We recommend all users update to the latest version of their respective release series immediately.
A security researcher identified multiple security issues in Fedify's lookupWebFinger()
function that could be exploited to:
The security updates implement the following fixes:
To update to the latest secure version:
# For npm users
npm update @fedify/fedify
# For Deno users
deno add jsr:@fedify/fedify
We thank the security researcher who responsibly disclosed this vulnerability, allowing us to address these issues promptly.
For more details about this vulnerability, please refer to our security advisory.
If you have any questions or concerns, please don't hesitate to reach out through our GitHub Discussions, join our Matrix chat space, or our Discord server.
In related news, #Hollo has also released #security updates: 0.3.6 & 0.4.4. Update now!
https://hollo.social/@fedify/01948487-87b2-709d-953f-8799b78433ed
We have released #security updates (1.0.14, 1.1.11, 1.2.11, 1.3.4) to address CVE-2025-23221, a #vulnerability in #Fedify's #WebFinger implementation. We recommend all users update to the latest version of their respective release series immediately.
A security researcher identified multiple security issues in Fedify's lookupWebFinger()
function that could be exploited to:
The security updates implement the following fixes:
To update to the latest secure version:
# For npm users
npm update @fedify/fedify
# For Deno users
deno add jsr:@fedify/fedify
We thank the security researcher who responsibly disclosed this vulnerability, allowing us to address these issues promptly.
For more details about this vulnerability, please refer to our security advisory.
If you have any questions or concerns, please don't hesitate to reach out through our GitHub Discussions, join our Matrix chat space, or our Discord server.
In related news, #Hollo has also released #security updates: 0.3.6 & 0.4.4. Update now!
https://hollo.social/@fedify/01948487-87b2-709d-953f-8799b78433ed
We have released #security updates (1.0.14, 1.1.11, 1.2.11, 1.3.4) to address CVE-2025-23221, a #vulnerability in #Fedify's #WebFinger implementation. We recommend all users update to the latest version of their respective release series immediately.
A security researcher identified multiple security issues in Fedify's lookupWebFinger()
function that could be exploited to:
The security updates implement the following fixes:
To update to the latest secure version:
# For npm users
npm update @fedify/fedify
# For Deno users
deno add jsr:@fedify/fedify
We thank the security researcher who responsibly disclosed this vulnerability, allowing us to address these issues promptly.
For more details about this vulnerability, please refer to our security advisory.
If you have any questions or concerns, please don't hesitate to reach out through our GitHub Discussions, join our Matrix chat space, or our Discord server.
@[email protected] · Reply to Hollo :hollo:'s post
この件に関連して、Holloもセキュリティアップデートをリリースしました。0.3.6または0.4.4バージョンに今すぐアップデートしてください!
https://hollo.social/@fedify/0194848e-7cac-7af3-941b-c93999a51274
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
FedifyのWebFinger実装における脆弱性CVE-2025-23221に対するセキュリティアップデート(1.0.14、1.1.11、1.2.11、1.3.4)をリリースいたしました。すべてのユーザー様におかれましては、お使いのバージョンに応じた最新版への速やかなアップデートを推奨いたします。
セキュリティ研究者により、FedifyのlookupWebFinger()
関数において以下のセキュリティ上の問題が発見されました:
本セキュリティアップデートでは、以下の修正が実施されました:
以下のコマンドで最新のセキュアバージョンにアップデートできます:
# npmユーザーの場合
npm update @fedify/fedify
# Denoユーザーの場合
deno add jsr:@fedify/fedify
この脆弱性を責任を持って報告していただいたセキュリティ研究者の方に感謝申し上げます。迅速な対応が可能となりました。
本脆弱性の詳細については、セキュリティ勧告をご参照ください。
ご質問やご懸念がございましたら、GitHub Discussions、Matrixチャットスペース、またはDiscordサーバーまでお気軽にご連絡ください。
In related news, #Hollo has also released #security updates: 0.3.6 & 0.4.4. Update now!
https://hollo.social/@fedify/01948487-87b2-709d-953f-8799b78433ed
We have released #security updates (1.0.14, 1.1.11, 1.2.11, 1.3.4) to address CVE-2025-23221, a #vulnerability in #Fedify's #WebFinger implementation. We recommend all users update to the latest version of their respective release series immediately.
A security researcher identified multiple security issues in Fedify's lookupWebFinger()
function that could be exploited to:
The security updates implement the following fixes:
To update to the latest secure version:
# For npm users
npm update @fedify/fedify
# For Deno users
deno add jsr:@fedify/fedify
We thank the security researcher who responsibly disclosed this vulnerability, allowing us to address these issues promptly.
For more details about this vulnerability, please refer to our security advisory.
If you have any questions or concerns, please don't hesitate to reach out through our GitHub Discussions, join our Matrix chat space, or our Discord server.
In related news, #Hollo has also released #security updates: 0.3.6 & 0.4.4. Update now!
https://hollo.social/@fedify/01948487-87b2-709d-953f-8799b78433ed
We have released #security updates (1.0.14, 1.1.11, 1.2.11, 1.3.4) to address CVE-2025-23221, a #vulnerability in #Fedify's #WebFinger implementation. We recommend all users update to the latest version of their respective release series immediately.
A security researcher identified multiple security issues in Fedify's lookupWebFinger()
function that could be exploited to:
The security updates implement the following fixes:
To update to the latest secure version:
# For npm users
npm update @fedify/fedify
# For Deno users
deno add jsr:@fedify/fedify
We thank the security researcher who responsibly disclosed this vulnerability, allowing us to address these issues promptly.
For more details about this vulnerability, please refer to our security advisory.
If you have any questions or concerns, please don't hesitate to reach out through our GitHub Discussions, join our Matrix chat space, or our Discord server.
@[email protected] · Reply to Hollo :hollo:'s post
이와 관련하여, #Hollo 역시 #보안 업데이트가 이뤄졌습니다. 0.3.6 또는 0.4.4 버전으로 바로 업데이트하시기 바랍니다!
https://hollo.social/@fedify/0194848b-3b9e-7da1-b631-c011db2f4c43
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
#Fedify 프레임워크의 #WebFinger 구현에서 발견된 보안 취약점 CVE-2025-23221을 해결하기 위한 보안 업데이트(1.0.14, 1.1.11, 1.2.11, 1.3.4)를 배포했습니다. 모든 사용자께서는 각자 사용 중인 버전에 해당하는 최신 버전으로 즉시 업데이트하시기를 권장합니다.
보안 연구자가 Fedify의 lookupWebFinger()
함수에서 다음과 같은 보안 문제점들을 발견했습니다:
이번 보안 업데이트에는 다음과 같은 수정 사항이 포함되어 있습니다:
다음 명령어로 최신 보안 버전으로 업데이트하실 수 있습니다:
# npm 사용자의 경우
npm update @fedify/fedify
# Deno 사용자의 경우
deno add jsr:@fedify/fedify
이 취약점을 책임감 있게 보고해 주신 보안 연구자께 감사드립니다. 덕분에 신속하게 문제를 해결할 수 있었습니다.
이 취약점에 대한 자세한 내용은 보안 권고문을 참고해 주시기 바랍니다.
문의 사항이나 우려 사항이 있으시다면 GitHub Discussions나 Matrix 채팅방, 또는 Discord 서버를 통해 언제든 연락해 주시기 바랍니다.
In related news, #Hollo has also released #security updates: 0.3.6 & 0.4.4. Update now!
https://hollo.social/@fedify/01948487-87b2-709d-953f-8799b78433ed
We have released #security updates (1.0.14, 1.1.11, 1.2.11, 1.3.4) to address CVE-2025-23221, a #vulnerability in #Fedify's #WebFinger implementation. We recommend all users update to the latest version of their respective release series immediately.
A security researcher identified multiple security issues in Fedify's lookupWebFinger()
function that could be exploited to:
The security updates implement the following fixes:
To update to the latest secure version:
# For npm users
npm update @fedify/fedify
# For Deno users
deno add jsr:@fedify/fedify
We thank the security researcher who responsibly disclosed this vulnerability, allowing us to address these issues promptly.
For more details about this vulnerability, please refer to our security advisory.
If you have any questions or concerns, please don't hesitate to reach out through our GitHub Discussions, join our Matrix chat space, or our Discord server.
In related news, #Hollo has also released #security updates: 0.3.6 & 0.4.4. Update now!
https://hollo.social/@fedify/01948487-87b2-709d-953f-8799b78433ed
We have released #security updates (1.0.14, 1.1.11, 1.2.11, 1.3.4) to address CVE-2025-23221, a #vulnerability in #Fedify's #WebFinger implementation. We recommend all users update to the latest version of their respective release series immediately.
A security researcher identified multiple security issues in Fedify's lookupWebFinger()
function that could be exploited to:
The security updates implement the following fixes:
To update to the latest secure version:
# For npm users
npm update @fedify/fedify
# For Deno users
deno add jsr:@fedify/fedify
We thank the security researcher who responsibly disclosed this vulnerability, allowing us to address these issues promptly.
For more details about this vulnerability, please refer to our security advisory.
If you have any questions or concerns, please don't hesitate to reach out through our GitHub Discussions, join our Matrix chat space, or our Discord server.
Une chose que je trouve intéressante sur Hollo et que j'ai vu nul par ailleurs :
## The number of recent public posts to fetch from remote actors when they are encountered first time.
REMOTE_ACTOR_FETCH_POSTS=10
Has anyone tested importing Follows from Hollo 0.4.3 ? It still doesn't work for me, it runs in a vacuum and sometimes crashes the server.
Just so I know if it's me or if I'm opening a new ticket on Github
Has anyone tested importing Follows from Hollo 0.4.3 ? It still doesn't work for me, it runs in a vacuum and sometimes crashes the server.
Just so I know if it's me or if I'm opening a new ticket on Github
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.
You will need a Pixelfed but single-user, like forking Hollo (for the backend) for its ease of installation and its lightness and Phanpy (for the frontend) by improving the view for the images a little.
You will need a Pixelfed but single-user, like forking Hollo (for the backend) for its ease of installation and its lightness and Phanpy (for the frontend) by improving the view for the images a little.
You will need a Pixelfed but single-user, like forking Hollo (for the backend) for its ease of installation and its lightness and Phanpy (for the frontend) by improving the view for the images a little.
Oups, Hollo it's stopped again, this time after adding a reaction from my Iceshrimp account on a message in a quote.
10:27:30.930 INF fedify·federation·http: 'HEAD' '/@KazukyAkayashi/01947e19-182a-79df-8a3b-9afae013980b': 200
10:27:31.036 INF fedify·federation·http: 'GET' '/@KazukyAkayashi/01947e19-182a-79df-8a3b-9afae013980b': 200
10:27:31.478 INF fedify·federation·http: 'OPTIONS' '/api/v1/statuses/01947e19-182a-79df-8a3b-9afae013980b/context': 204
10:27:31.493 INF fedify·federation·http: 'OPTIONS' '/api/v1/statuses/01947e19-182a-79df-8a3b-9afae013980b': 204
10:27:31.626 INF fedify·federation·http: 'GET' '/@KazukyAkayashi/01947e19-182a-79df-8a3b-9afae013980b': 200
10:27:32.237 DBG hollo·federation·post: The quote target is already persisted: '01947e19-182a-79df-8a3b-9afae013980b'
ELIFECYCLE Command failed with exit code 137.
You will need a Pixelfed but single-user, like forking Hollo (for the backend) for its ease of installation and its lightness and Phanpy (for the frontend) by improving the view for the images a little.
Une chose que je trouve intéressante sur Hollo et que j'ai vu nul par ailleurs :
## The number of recent public posts to fetch from remote actors when they are encountered first time.
REMOTE_ACTOR_FETCH_POSTS=10
You will need a Pixelfed but single-user, like forking Hollo (for the backend) for its ease of installation and its lightness and Phanpy (for the frontend) by improving the view for the images a little.
Hmmm étrange quand même le nombre de message donné par Iceshrimp 65 vs 69 sur le profil de mon compte Hollo
Hmmm étrange quand même le nombre de message donné par Iceshrimp 65 vs 69 sur le profil de mon compte Hollo
私も微力ながら『Thinking Penguin Magazine Vol.0』に「国漢文混用体からHolloまで」という拙稿を寄稿しました。興味の有る方は、第十一回技術書同人誌博覧会で手に入れる事が出来ます。
【技術書同人誌博覧会まであと1週間‼️】
#FediLUG は来週の今日、2025年1月25日に横浜産貿ホール マリネリアで開催される第11回技術書同人誌博覧会( #技書博 )に出展します。
#FediLUG 新刊として『Thinkng Penguin Magazine vol.0』を頒布します!(124ページ・500円)
委託として @[email protected] さんの『さばかんライフ!』も頒布いたします!
皆さんのお越しを心待ちにしています!!!
詳しくは技術書博の公式サイトおよび、サークル概要をご覧ください!
https://gishohaku.dev/gishohaku11/circles/LOmokXEikphsDCEG9OEb
私も微力ながら『Thinking Penguin Magazine Vol.0』に「国漢文混用体からHolloまで」という拙稿を寄稿しました。興味の有る方は、第十一回技術書同人誌博覧会で手に入れる事が出来ます。
【技術書同人誌博覧会まであと1週間‼️】
#FediLUG は来週の今日、2025年1月25日に横浜産貿ホール マリネリアで開催される第11回技術書同人誌博覧会( #技書博 )に出展します。
#FediLUG 新刊として『Thinkng Penguin Magazine vol.0』を頒布します!(124ページ・500円)
委託として @[email protected] さんの『さばかんライフ!』も頒布いたします!
皆さんのお越しを心待ちにしています!!!
詳しくは技術書博の公式サイトおよび、サークル概要をご覧ください!
https://gishohaku.dev/gishohaku11/circles/LOmokXEikphsDCEG9OEb
私も微力ながら『Thinking Penguin Magazine Vol.0』に「国漢文混用体からHolloまで」という拙稿を寄稿しました。興味の有る方は、第十一回技術書同人誌博覧会で手に入れる事が出来ます。
【技術書同人誌博覧会まであと1週間‼️】
#FediLUG は来週の今日、2025年1月25日に横浜産貿ホール マリネリアで開催される第11回技術書同人誌博覧会( #技書博 )に出展します。
#FediLUG 新刊として『Thinkng Penguin Magazine vol.0』を頒布します!(124ページ・500円)
委託として @[email protected] さんの『さばかんライフ!』も頒布いたします!
皆さんのお越しを心待ちにしています!!!
詳しくは技術書博の公式サイトおよび、サークル概要をご覧ください!
https://gishohaku.dev/gishohaku11/circles/LOmokXEikphsDCEG9OEb
私も微力ながら『Thinking Penguin Magazine Vol.0』に「国漢文混用体からHolloまで」という拙稿を寄稿しました。興味の有る方は、第十一回技術書同人誌博覧会で手に入れる事が出来ます。
【技術書同人誌博覧会まであと1週間‼️】
#FediLUG は来週の今日、2025年1月25日に横浜産貿ホール マリネリアで開催される第11回技術書同人誌博覧会( #技書博 )に出展します。
#FediLUG 新刊として『Thinkng Penguin Magazine vol.0』を頒布します!(124ページ・500円)
委託として @[email protected] さんの『さばかんライフ!』も頒布いたします!
皆さんのお越しを心待ちにしています!!!
詳しくは技術書博の公式サイトおよび、サークル概要をご覧ください!
https://gishohaku.dev/gishohaku11/circles/LOmokXEikphsDCEG9OEb
Une chose que je trouve intéressante sur Hollo et que j'ai vu nul par ailleurs :
## The number of recent public posts to fetch from remote actors when they are encountered first time.
REMOTE_ACTOR_FETCH_POSTS=10
私も微力ながら『Thinking Penguin Magazine Vol.0』に「国漢文混用体からHolloまで」という拙稿を寄稿しました。興味の有る方は、第十一回技術書同人誌博覧会で手に入れる事が出来ます。
【技術書同人誌博覧会まであと1週間‼️】
#FediLUG は来週の今日、2025年1月25日に横浜産貿ホール マリネリアで開催される第11回技術書同人誌博覧会( #技書博 )に出展します。
#FediLUG 新刊として『Thinkng Penguin Magazine vol.0』を頒布します!(124ページ・500円)
委託として @[email protected] さんの『さばかんライフ!』も頒布いたします!
皆さんのお越しを心待ちにしています!!!
詳しくは技術書博の公式サイトおよび、サークル概要をご覧ください!
https://gishohaku.dev/gishohaku11/circles/LOmokXEikphsDCEG9OEb
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.
私も微力ながら『Thinking Penguin Magazine Vol.0』に「国漢文混用体からHolloまで」という拙稿を寄稿しました。興味の有る方は、第十一回技術書同人誌博覧会で手に入れる事が出来ます。
【技術書同人誌博覧会まであと1週間‼️】
#FediLUG は来週の今日、2025年1月25日に横浜産貿ホール マリネリアで開催される第11回技術書同人誌博覧会( #技書博 )に出展します。
#FediLUG 新刊として『Thinkng Penguin Magazine vol.0』を頒布します!(124ページ・500円)
委託として @[email protected] さんの『さばかんライフ!』も頒布いたします!
皆さんのお越しを心待ちにしています!!!
詳しくは技術書博の公式サイトおよび、サークル概要をご覧ください!
https://gishohaku.dev/gishohaku11/circles/LOmokXEikphsDCEG9OEb
私も微力ながら『Thinking Penguin Magazine Vol.0』に「国漢文混用体からHolloまで」という拙稿を寄稿しました。興味の有る方は、第十一回技術書同人誌博覧会で手に入れる事が出来ます。
【技術書同人誌博覧会まであと1週間‼️】
#FediLUG は来週の今日、2025年1月25日に横浜産貿ホール マリネリアで開催される第11回技術書同人誌博覧会( #技書博 )に出展します。
#FediLUG 新刊として『Thinkng Penguin Magazine vol.0』を頒布します!(124ページ・500円)
委託として @[email protected] さんの『さばかんライフ!』も頒布いたします!
皆さんのお越しを心待ちにしています!!!
詳しくは技術書博の公式サイトおよび、サークル概要をご覧ください!
https://gishohaku.dev/gishohaku11/circles/LOmokXEikphsDCEG9OEb
#Hollo does not currently cache media attached to remote posts or avatars from remote accounts (except for thumbnails). Do you think we should cache them?
Option | Voters |
---|---|
It's fine the way it is. | 3 (9%) |
They should be cached. | 6 (18%) |
It would be nice to be configurable. | 24 (73%) |
#Hollo does not currently cache media attached to remote posts or avatars from remote accounts (except for thumbnails). Do you think we should cache them?
Option | Voters |
---|---|
It's fine the way it is. | 3 (9%) |
They should be cached. | 6 (18%) |
It would be nice to be configurable. | 24 (73%) |
#Hollo does not currently cache media attached to remote posts or avatars from remote accounts (except for thumbnails). Do you think we should cache them?
Option | Voters |
---|---|
It's fine the way it is. | 3 (9%) |
They should be cached. | 6 (18%) |
It would be nice to be configurable. | 24 (73%) |
#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
#Hollo now implements FEP-e232 as well for incoming and outgoing activities!
https://hollo.social/@hollo/0191d68a-3ba7-7f2f-9836-fe8664fb51b0
#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
#分散型SNSユーザー有志 のホームページを更新しました。
主な分散型SNSの欄に新たに #Hollo や #gotosocial を追加しました。
https://fediverse.pcgf.io
#分散型SNSユーザー有志 のホームページを更新しました。
主な分散型SNSの欄に新たに #Hollo や #gotosocial を追加しました。
https://fediverse.pcgf.io
#分散型SNSユーザー有志 のホームページを更新しました。
主な分散型SNSの欄に新たに #Hollo や #gotosocial を追加しました。
https://fediverse.pcgf.io
#分散型SNSユーザー有志 のホームページを更新しました。
主な分散型SNSの欄に新たに #Hollo や #gotosocial を追加しました。
https://fediverse.pcgf.io
#分散型SNSユーザー有志 のホームページを更新しました。
主な分散型SNSの欄に新たに #Hollo や #gotosocial を追加しました。
https://fediverse.pcgf.io
#分散型SNSユーザー有志 のホームページを更新しました。
主な分散型SNSの欄に新たに #Hollo や #gotosocial を追加しました。
https://fediverse.pcgf.io
#分散型SNSユーザー有志 のホームページを更新しました。
主な分散型SNSの欄に新たに #Hollo や #gotosocial を追加しました。
https://fediverse.pcgf.io
#分散型SNSユーザー有志 のホームページを更新しました。
主な分散型SNSの欄に新たに #Hollo や #gotosocial を追加しました。
https://fediverse.pcgf.io
#分散型SNSユーザー有志 のホームページを更新しました。
主な分散型SNSの欄に新たに #Hollo や #gotosocial を追加しました。
https://fediverse.pcgf.io
#分散型SNSユーザー有志 のホームページを更新しました。
主な分散型SNSの欄に新たに #Hollo や #gotosocial を追加しました。
https://fediverse.pcgf.io
Y a des fedigens qui on fait le chemin inverse Misskey/Iceshrimp vers mastodon ou Pleroma ? ça fonctionne ?
Le .csv
généré pour les abonnements sous Iceshrimp ne ressemble pas a celui de Mastodon ou Holo c'est un peu chiant quand même.
#Iceshrimp #Mastodon #Hollo #Fediverse
Bon théoriquement l'import d'abonnement est corrigé dans #Hollo du coup je vais refaire une essai, z'êtes pas obliger de me suivre vu que pour le moment c'est une instance de teste
RE: hollo.zarchbox.fr/@KazukyAkayashi/01945492-0ff4-7b5e-8095-c6614ffb3d5a
Update Hollo to 0.4.3
It lacks a lightweight single-user software dedicated to posting images, a kind of Hollo but for images, easy to install (and without docker ) and to update.
#Hollo #Pixelfed #Vernissage #Fediverse
In the next version of #Hollo, I'd like to improve search quality.
@[email protected] · Reply to Jcrabapple's post
@jcrabapple Just before the year ended I got a few fediverse test servers running: #snac, #mitra, and for a while, #hollo.
In #Hollo 0.5.0, the number of likes and shares will be more accurate.
In #Hollo 0.5.0, the number of likes and shares will be more accurate.
In #Hollo 0.5.0, the number of likes and shares will be more accurate.
In #Hollo 0.5.0, the number of likes and shares will be more accurate.
Found 11 new servers and 18 servers died off since 7 hours ago.
22,230 servers checked. 13,431,920 Total Users with 1,027,115 Active Users today. Check out the stats!
New #fediverse servers found:
hollo.ssig33.com a #hollo server from Private
diaspora.delaylama.de a #diaspora server from France
mastodon.mulesgaming.com a #mastodon server from Private
cabamacnagoya.harumaki2000.net a #misskey server from Private
pl.firelink.digital a #pleroma server from Private
kurage.homes a #sharkey server from Germany
social.seedoubleyou.me a #gotosocial server from United Arab Emirates
this-email-list.ispants.com a #wordpress server from United Kingdom
altair.nyoroooon.xyz a #nexkey server from Private
fedi.merta.xyz a #gotosocial server from United States
lvgaldieri.com a #wordpress server from United States
Help others find a home, send them to fediverse.observer
Found 11 new servers and 18 servers died off since 7 hours ago.
22,230 servers checked. 13,431,920 Total Users with 1,027,115 Active Users today. Check out the stats!
New #fediverse servers found:
hollo.ssig33.com a #hollo server from Private
diaspora.delaylama.de a #diaspora server from France
mastodon.mulesgaming.com a #mastodon server from Private
cabamacnagoya.harumaki2000.net a #misskey server from Private
pl.firelink.digital a #pleroma server from Private
kurage.homes a #sharkey server from Germany
social.seedoubleyou.me a #gotosocial server from United Arab Emirates
this-email-list.ispants.com a #wordpress server from United Kingdom
altair.nyoroooon.xyz a #nexkey server from Private
fedi.merta.xyz a #gotosocial server from United States
lvgaldieri.com a #wordpress server from United States
Help others find a home, send them to fediverse.observer
Have you been having trouble fetching accounts or posts from #Akkoma that have custom emojis in #Hollo?
This is because they represent an Emoji
object as an invalid JSON-LD object. Fortunately, this patch fixes that issue, so keep an eye out for it.
https://hollo.social/@fedify/01941dab-e4c3-7ce0-9307-b5b8c095d521
Are you getting the following error when trying to look up any Activity Streams objects from #Akkoma that contain custom emojis?
jsonld.SyntaxError: Invalid JSON-LD syntax; "@id" value must a string.
This is because they represent an Emoji
object as an invalid JSON-LD object. Fortunately, this patch fixes that issue, so keep an eye out for it.
Have you been having trouble fetching accounts or posts from #Akkoma that have custom emojis in #Hollo?
This is because they represent an Emoji
object as an invalid JSON-LD object. Fortunately, this patch fixes that issue, so keep an eye out for it.
https://hollo.social/@fedify/01941dab-e4c3-7ce0-9307-b5b8c095d521
Are you getting the following error when trying to look up any Activity Streams objects from #Akkoma that contain custom emojis?
jsonld.SyntaxError: Invalid JSON-LD syntax; "@id" value must a string.
This is because they represent an Emoji
object as an invalid JSON-LD object. Fortunately, this patch fixes that issue, so keep an eye out for it.
Have you been having trouble fetching accounts or posts from #Akkoma that have custom emojis in #Hollo?
This is because they represent an Emoji
object as an invalid JSON-LD object. Fortunately, this patch fixes that issue, so keep an eye out for it.
https://hollo.social/@fedify/01941dab-e4c3-7ce0-9307-b5b8c095d521
Are you getting the following error when trying to look up any Activity Streams objects from #Akkoma that contain custom emojis?
jsonld.SyntaxError: Invalid JSON-LD syntax; "@id" value must a string.
This is because they represent an Emoji
object as an invalid JSON-LD object. Fortunately, this patch fixes that issue, so keep an eye out for it.
Have you been having trouble fetching accounts or posts from #Akkoma that have custom emojis in #Hollo?
This is because they represent an Emoji
object as an invalid JSON-LD object. Fortunately, this patch fixes that issue, so keep an eye out for it.
https://hollo.social/@fedify/01941dab-e4c3-7ce0-9307-b5b8c095d521
Are you getting the following error when trying to look up any Activity Streams objects from #Akkoma that contain custom emojis?
jsonld.SyntaxError: Invalid JSON-LD syntax; "@id" value must a string.
This is because they represent an Emoji
object as an invalid JSON-LD object. Fortunately, this patch fixes that issue, so keep an eye out for it.
Have you been having trouble fetching accounts or posts from #Akkoma that have custom emojis in #Hollo?
This is because they represent an Emoji
object as an invalid JSON-LD object. Fortunately, this patch fixes that issue, so keep an eye out for it.
https://hollo.social/@fedify/01941dab-e4c3-7ce0-9307-b5b8c095d521
Are you getting the following error when trying to look up any Activity Streams objects from #Akkoma that contain custom emojis?
jsonld.SyntaxError: Invalid JSON-LD syntax; "@id" value must a string.
This is because they represent an Emoji
object as an invalid JSON-LD object. Fortunately, this patch fixes that issue, so keep an eye out for it.
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
!
Did you know? #Hollo supports #Misskey/#Pleroma-style #quotes. You can quote another post by adding a link to it. If a post contains any link to an #ActivityPub object of Article
/Note
/Question
, Hollo quotes it in the post.
Did you know? #Hollo supports #Misskey/#Pleroma-style #quotes. You can quote another post by adding a link to it. If a post contains any link to an #ActivityPub object of Article
/Note
/Question
, Hollo quotes it in the post.
Hmm je vais tester l'import des Follows dans #Hollo, si la moitié du fediverse casse vous saurez pourquoi
Did you know? #Hollo supports #Misskey/#Pleroma-style #quotes. You can quote another post by adding a link to it. If a post contains any link to an #ActivityPub object of Article
/Note
/Question
, Hollo quotes it in the post.
Did you know? #Hollo supports #Misskey/#Pleroma-style #quotes. You can quote another post by adding a link to it. If a post contains any link to an #ActivityPub object of Article
/Note
/Question
, Hollo quotes it in the post.
Did you know? #Hollo supports #Misskey/#Pleroma-style #quotes. You can quote another post by adding a link to it. If a post contains any link to an #ActivityPub object of Article
/Note
/Question
, Hollo quotes it in the post.
@[email protected] · Reply to 洪 民憙 (Hong Minhee)'s post
I wrote a blog post to wrap up the year 2024: A year with the fediverse.
https://writings.hongminhee.org/2024/12/a-year-with-the-fediverse/index.en.html
@[email protected] · Reply to 洪 民憙 (Hong Minhee)'s post
I wrote a blog post to wrap up the year 2024: A year with the fediverse.
https://writings.hongminhee.org/2024/12/a-year-with-the-fediverse/index.en.html
Update Hollo to v.0.4.0 🎉
But I will have to rewrite my hollo.service
for systemd
http://hollo.social/@hollo/01941325-8d0e-71e4-ad49-daef861c01d0
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 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
!
@[email protected] · Reply to KazukyAkayashi (Hollo)'s post
I also have the impression that some messages from my Iceshrimp account do not go through either, nothing in my Hollo TL, nor when I do a search (from Phanpy and Elk)
Note: these are unlisted messages.
20:48:52.136 ERR fedify·federation·inbox: Failed to process the incoming activity 'https://social.zarchbox.fr/notes/a2dn3k8kt5hm3gci/activity' (attempt #8); retry...:
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
!
@[email protected] · Reply to KazukyAkayashi (Hollo)'s post
Strange I can't see my Hollo post from my Iceshrimp instance and searching doesn't give anything.
I also don't see the release announcement for v0.4.0 from my Iceshrimp instance.
Update Hollo to v.0.4.0 🎉
But I will have to rewrite my hollo.service
for systemd
http://hollo.social/@hollo/01941325-8d0e-71e4-ad49-daef861c01d0
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 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
!
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
!
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
!
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
!
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
!
Dites les fédigens, y en a parmi vous qui on activé l'option pour rendre les abonné•e•s et les abonnement uniquement visible aux abonné•e•s ?
Peut importe le logiciel, Pleroma, Akkoma,Mastodon, Glicth-Soc ... mais sous Iceshrimp ça aurait été pas mal aussi.
C'est pour debug Hollo
#Hollo #Iceshrimp #Fediverse
One hidden feature of #Hollo: You can also quote another post while replying to someone else's post.
Just released #Hollo 0.3.5, which contains small minor bug fixes.
Just released #Hollo 0.3.5, which contains small minor bug fixes.
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.
Just released #Hollo 0.3.5, which contains small minor bug fixes.
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!
One hidden feature of #Hollo: You can also quote another post while replying to someone else's post.
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!
We'll be releasing #Hollo 0.4.0 before the year is out. Stay tuned!
Just released #Hollo 0.3.5, which contains small minor bug fixes.
Just released #Hollo 0.3.5, which contains small minor bug fixes.
Just released #Hollo 0.3.5, which contains small minor bug fixes.
Just released #Hollo 0.3.5, which contains small minor bug fixes.
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.
Starting with #Hollo 0.4.0, you can allow your profile to be discovered in the public directory. Under the hood, this option corresponds to Mastodon's toot:discoverable
property.
Starting with #Hollo 0.4.0, you can allow your profile to be discovered in the public directory. Under the hood, this option corresponds to Mastodon's toot:discoverable
property.
Starting with #Hollo 0.4.0, you can allow your profile to be discovered in the public directory. Under the hood, this option corresponds to Mastodon's toot:discoverable
property.
Starting with #Hollo 0.4.0, you can allow your profile to be discovered in the public directory. Under the hood, this option corresponds to Mastodon's toot:discoverable
property.
Starting with #Hollo 0.4.0, you can allow your profile to be discovered in the public directory. Under the hood, this option corresponds to Mastodon's toot:discoverable
property.
Starting with #Hollo 0.4.0, you can allow your profile to be discovered in the public directory. Under the hood, this option corresponds to Mastodon's toot:discoverable
property.
Starting with #Hollo 0.4.0, you can allow your profile to be discovered in the public directory. Under the hood, this option corresponds to Mastodon's toot:discoverable
property.
Starting with #Hollo 0.4.0, you can allow your profile to be discovered in the public directory. Under the hood, this option corresponds to Mastodon's toot:discoverable
property.
Starting with #Hollo 0.4.0, you can allow your profile to be discovered in the public directory. Under the hood, this option corresponds to Mastodon's toot:discoverable
property.
Dites les fédigens, y en a parmi vous qui on activé l'option pour rendre les abonné•e•s et les abonnement uniquement visible aux abonné•e•s ?
Peut importe le logiciel, Pleroma, Akkoma,Mastodon, Glicth-Soc ... mais sous Iceshrimp ça aurait été pas mal aussi.
C'est pour debug Hollo
#Hollo #Iceshrimp #Fediverse
@[email protected] · Reply to 洪 民憙 (Hong Minhee)'s post
I wrote a blog post to wrap up the year 2024: A year with the fediverse.
https://writings.hongminhee.org/2024/12/a-year-with-the-fediverse/index.en.html
@[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
!
Poupoupou Hollo update 0.3.1 🎉
For those who want to use #Hollo on @ivory: #Ivory evolved from the Tweetbot codebase, which was a third-party Twitter client, so it assumes that object IDs are integers. Hollo uses UUIDs for object IDs, so it can't be used with Ivory at this time. We hope that Ivory will support non-integer object IDs in the future!
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 Kazuky Akayashi ฅ^•ﻌ•^ฅ's post
@KazukyAkayashi I admit that I don't really know where to go for the bugs that occur in Moshidon with Hollo because it only affects the account with Hollo and as I'm not a techie I don't know if it's Hollo or Moshidon.
#Hollo #Moshidon
@[email protected] · Reply to KazukyAkayashi (Hollo)'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 (Hollo)'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 (Hollo)'s post
Du coup le stockage local fonctionne nickel 👍
@[email protected] · Reply to KazukyAkayashi (Hollo)'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!got my #hollo instance working again, turned out to be an nginx/certbot thing, I don't know how you server-side guys do it
working on #Hollo support
헛 이제 보니 썸네일 이미지들이 안보인다. 흠... 클라우드플레어 스토리지에는 파일이 있네? #hollo
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
.
모바일에서도 phanpy social 로 보는게 dawn 보다 훨씬 보기 좋네. #hollo
#hollo タニタのページを貼るとエラー出るの、まじでバグっぽい https://gist.github.com/ntsklab/3bb1c72fc6dda82a54f6171ff4c8c679
홀로 인스턴스 만들면서 처음 설정하는 관리 계정의 이메일이 인스턴스 연락 메일로도 사용된다. credentials 테이블에서 변경할 수 있다. #hollo
#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.
I'm in waiting for someone create fedi app using fedify and deno (#Hollo like app).
Doesn't using Bun, sorry.
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.
@[email protected] · Reply to 洪 民憙(ホン・ミンヒ)'s post
@[email protected] · Reply to 洪 民憙(ホン・ミンヒ)'s post
今週土曜日に開催されるOSC 2024 Tokyo/FallにFedify/Hollo合同で出展します!可愛いFedifyのロゴのシールと『自分だけのフェディバースのマイクロブログを作ろう!』日本語版の紙の本を持って行く予定です。よろしくお願いします。
#Hollo's GitHub repository now has 200 stars!
@[email protected] · Reply to Hollo :hollo:'s post
@hollo #hollo on #nextcloud, please
#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
.
Finally, Hollo 0.1.0 released! #Hollo is a single-user federated microblogging software which is #ActivityPub-enabled and powered by #Fedify.
Hollo has the most of features that Mastodon has except for moderation tools, and also include:
If you're interested in Hollo, please give it a try! There are several ways to install it: using Railway, using Docker (and Docker Compose), or manually.
If you're already using Hollo, please upgrade it to v0.1.0:
ghcr.io/dahlia/hollo:0.1.0
or simply latest
!stable
branch and switch over to it!#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:
The most common pitfall for first-time #Hollo users is deploying Hollo behind a reverse proxy and forgetting to set BEHIND_PROXY=true
, which causes federation issues and wasted time trying to resolve them.
To help users avoid this common pitfall, we've introduced a warning on Hollo's setup page when Hollo is behind a reverse proxy and the BEHIND_PROXY
is off.
1人 인스턴스를 만드시고 싶은가요? 무거운 Mastodon이나 Misskey 말고 #Hollo 써 보세요!
#Hollo also works great on Windows (if you want it to)!
WindowsでマニュアルインストールでHollo起動できた!
#Hollo finally lets you move your old account to new one! (FEP-7628 compliant.) It's bidirectional, which is basically equivalent to and interoperable with Mastodon's account move:
alsoKnownAs
).movedTo
property and sending Move
activities to the followers.It enables your new account to have the same existing followers after you've moved your account.
@[email protected] · Reply to @[email protected]'s post
방화벽 문제인가... #hollo
@[email protected] · Reply to @[email protected]'s post
<Error>
<Code>AccessDenied</Code>
<Message>Access Denied.</Message>
<BucketName>setup</BucketName>
<Resource>/setup</Resource>
<RequestId>17FFD8BD59068C45</RequestId>
<HostId>dd9025bab4ad464b049177c95eb6ebf374d3b3fd1af9251148b658df7ac2e3e8</HostId>
</Error>
흑흑.... #hollo
#Hollo now supports Atom syndication feed, i.e., RSS! Append /atom.xml to your profile link; for example, this account's feed is:
@[email protected] · Reply to @[email protected]'s post
환경변수 그냥 세팅하고 돌리는...건가? #hollo 3000번 포트로 캐디 연결하면 될 것 같긴 한데..
@[email protected] · Reply to Hollo :hollo:'s post
Previously #Hollo implemented only #Fedibird-style extension APIs for emoji reactions, but now Hollo implements #Pleroma-style extension APIs for emoji reactions too. So you can use this feature with more client apps, e.g., #Moshidon.
https://github.com/dahlia/hollo/issues/36#issuecomment-2423548150
I've only been on Fosstodon for a few months, but I plan to move my account over to #Hollo later this year for dogfooding. Not right now, though.
Now you can upload videos on #Hollo!
#Hollo now lets you block other accounts!
#Hollo now has per-account muting! Plus, you can set the duration as well.
We now have a Matrix room for #Hollo users: #hollo-users:matrix.org
. Join us now!
#Hollo now lets you leave emoji reactions!
#Hollo now allows you to write custom emojis!
According to the Activity Vocabulary specification, the summary property should be HTML encoded, but #Mastodon is putting plain text in the summary property. #Hollo is putting #HTML in the summary, but should I change Hollo's behavior?
https://www.w3.org/TR/activitystreams-vocabulary/#dfn-summary
10月26日(土)に開催されるOSC 2024 Tokyo/FallにFedify/Hollo合同で出展します!可愛いFedifyのロゴのシールと『自分だけのフェディバースのマイクロブログを作ろう!』日本語版の紙の本を持って行く予定です。よろしくお願いします。
Want to run your own personal #ActivityPub server, but don't have the server specs to install Mastodon? Try #Hollo, a lightweight personal ActivityPub server!
Found 23 new servers and 21 servers died off since 3 hours ago.
22,887 servers checked. 14,084,325 Total Users with 1,039,977 Active Users today. Check out the stats!
New #fediverse servers found:
thanetviews.com a #wordpress server from United Kingdom
cuteenby.gay a #akkoma server from Germany
filledblanks.com a #mastodon server from United States
anchasalamedas.org a #wordpress server from United States
social.frederico.me a #friendica server from United States
msk.kitamiss.com a #misskey server from Private
nyansukey.net a #misskey server from Private
toot.it.com a #mastodon server from United States
social.ainmosni.eu a #gotosocial server from Germany
hcs-miskey.skycat.io a #misskey server from Private
misskey.rockcutter.jp a #misskey server from Japan
karibu.social a #mastodon server from Private
italianchoco.com a #wordpress server from United States
thearkproject.llc a #wordpress server from United States
blackevil.net a #wordpress server from Germany
pixelone.org a #pixelfed server from Private
armpit.space a #misskey server from United States
social.iceflower.io a #mastodon server from France
xcornman.com a #wordpress server from United States
eat.bakedbea.nz a #sharkey server from Private
misskey.hotserver.meme a #misskey server from Australia
social.brendans-bits.com a #snac server from Australia
hollo.esurio1673.net a #hollo server from Private
Help others find a home, send them to fediverse.observer
@[email protected] · Reply to Hollo :hollo:'s post
#Hollo now uses PostgreSQL for caching and message queue by default (unless the REDIS_URL
environment variable is present)! It's quite performant and scalable when it's compared to Redis, so we've decided to make it the default configuration.
#Hollo now implements FEP-e232 as well for incoming and outgoing activities!
https://hollo.social/@hollo/0191d68a-3ba7-7f2f-9836-fe8664fb51b0
#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
#Hollo now has its own website with docs.
HolloについにMisskey/Threads風の引用機能が追加されました!使い方は簡単です。引用する投稿のリンクを投稿内容に貼り付けてください!ActivityPubの投稿(Article、Note、そしてQuestionに対応)のリンクを自動で認識して引用に変えてくれます。
ちなみに、Phanpyを使う場合は、ブーストアイコンを押すと出てくるQuoteボタンを使ってください。
#Hollo #Misskey #Threads #引用
QT: https://hollo.social/@hollo/0191d68a-3ba7-7f2f-9836-fe8664fb51b0 [参照]
#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
#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
Always good to see progress! Only a handful of features left on the roadmap. Hollo is an activitypub powered federated microblog app. Docker image was made available with the latest release
#activitypub #hollo #federated #fediverse #opensource #oss #foss #microblog #microblogging
Since #Hollo no more depends on #Meilisearch, you can run your Hollo server in more cost-efficient way by getting rid of the Meilisearch service!
If you deployed your Hollo server using #Railway, here's instructions to remove it:
MEILI_URL
and MEILI_MASTER_KEY
environment variables.That's all!
Today, #Hollo held an offline #sprint in #Seoul, and received several improvement patches:
Removed a dependency on Meilisearch, which makes Hollo easier to install. Thanks to @longfin!
In a post view, the number of likes and shares are displayed now. Thanks to @devtedlee!
Hollo now has a Docker Compose configuration, which lets users easily deploy it and lets contributors quickly set up the project. Thanks to @longfin, again!
The code formatter now works well with the Hollo project in the IntelliJ IDEs. Thanks to @kecan0406!
Thanks again to our contributors!
Hollo를 소개합니다!
Hollo는 개인을 위한 연합형 마이크로블로그 소프트웨어입니다. Fedify와 Bun으로 만들어졌으며, #ActivityPub 프로토콜을 통해 다른 인스턴스 및 서비스와 교류할 수 있습니다.
Hollo의 특징은 한 사용자를 위해 설계된 전용 인스턴스라는 점입니다. 이를 통해 사용자는 자신만의 공간을 가지면서도 #Mastodon, #Misskey 및 기타 ActivityPub 지원 서비스의 사용자들과 소통할 수 있습니다.
독자적인 웹 인터페이스는 없지만, Mastodon API와 호환되어 기존의 많은 Mastodon 클라이언트 앱을 사용하여 Hollo에 접근할 수 있습니다. 이로 인해 익숙한 인터페이스로 Hollo를 이용할 수 있습니다.
주요 기능으로는 게시물 작성·편집·삭제, 답글, 미디어 첨부, 투표, 좋아요, 북마크, 고정 등이 있습니다. 또한 프로필 편집, 팔로우/팔로워 관리, 리스트 생성 등도 가능합니다. 더불어 Markdown을 지원하여 게시물이나 프로필의 서식 설정을 쉽게 할 수 있습니다.
Hollo는 현재 개발 초기 단계에 있으며, 지속적으로 기능 추가와 개선이 이루어지고 있습니다. Bun을 사용함으로써 빠른 성능과 효율적인 개발이 이뤄지고 있답니다. 오픈 소스 프로젝트로 GitHub에 공개되어 있으며, 커뮤니티의 기여를 환영합니다.
개인 블로그와 소셜 미디어의 장점을 결합한 Hollo는 프라이버시를 중시하면서도 더 넓은 커뮤니티와의 연결을 원하는 사람들에게 적합한 플랫폼으로 거듭나고 있습니다.
Holloを紹介します!
Holloは、個人向けの連合型マイクロブログソフトウェアです。FedifyとBunを基盤に構築され、ActivityPubプロトコルを通じて他のインスタンスやサービスと連携することができます。
Holloの特徴は、一人のユーザーのために設計された専用のインスタンスという点です。これにより、ユーザーは自分だけのスペースを持ちながら、Mastodon、Misskey、その他のActivityPub対応サービスのユーザーとも交流できます。
独自のウェブインターフェースを持たない代わりに、MastodonのAPIと互換性があるため、既存の多くのMastodonクライアントアプリを使用してHolloにアクセスできます。これにより、使い慣れたインターフェースでHolloを利用することができます。
主な機能には、投稿の作成・編集・削除、返信、メディア添付、投票、お気に入り、ブックマーク、ピン留めなどがあります。また、プロフィール編集、フォロー/フォロワー管理、リスト作成なども可能です。さらに、Markdownをサポートしているため、投稿やプロフィールの書式設定が容易に行えます。
Holloは現在開発の初期段階にあり、継続的に機能の追加や改善が行われています。Bunを使用することで、高速なパフォーマンスと効率的な開発が実現されています。オープンソースプロジェクトとして、GitHubで公開されており、コミュニティからの貢献を歓迎しています。
個人のブログとソーシャルメディアの利点を組み合わせたHolloは、プライバシーを重視しながら、より広いコミュニティとのつながりを求める人々に適したプラットフォームとなっています。
https://github.com/dahlia/hollo
#Hollo #ActivityPub #Mastodon #Markdown #Bun #Fedify #fedidev
@[email protected] · Reply to 洪 民憙 (Hong Minhee)'s post
この記事を読むと、自分もHolloでBunの代わりにNode.jsを使うべきなのかなーと。
@[email protected] · Reply to wakest ⁂'s post
Added #Sublinks, #Buttondown, #ActivityPods, #Hollo, #Smilodon and #Patchwork icons to #FediverseIconography at https://fediverse.wake.st
Option | Voters |
---|---|
Just now? | 1 (5%) |
Finally! | 4 (20%) |
Awesome! | 15 (75%) |
#Hollo now supports lists!
A galera que gosta de self-host, ter sua própria instância etc. com alternativas exóticas pode ficar atenta ao #hollo: https://github.com/dahlia/hollo
https://hollo.social/@hollo/01904586-7b75-7ef6-ad31-bec40b8b1e66#webclip
The latest #PhanpyDev (@phanpy) now shows the preview of a permalink to a #Hollo post!
https://github.com/cheeaun/phanpy/commit/a72400febf62e34e0aaaeef86ae64ed6e373d492
To #Hollo users: please update your #Hollo to 0.1.0-dev.46, a #security patch which addresses @fedify's #vulnerability CVE-2024-39687, as soon as possible!
https://hollo.social/@fedify/019080c7-c784-755d-a6f2-d1f91f2c5709
#Hollo is using this @fedify/redis package for caching and queuing. Battle tested!
https://hollo.social/@fedify/01905e6b-deec-785a-9bda-b72883031f8f
@[email protected] · Reply to 洪 民憙 (Hong Minhee)'s post
#Fedify now has the official #Hollo account! Please follow @fedify!
https://hollo.social/@fedify/01905d6a-5d70-75bc-881e-d6c155a5051c
@[email protected] · Reply to joschi's post
Good news: #Hollo finally supports featured tags!
Bad news: There is no client app that supports featured tags.
#Hollo now lets you pin your posts to the top of your profile!
If you'd like to support the development of #Fedify or #Hollo, you can sponsor me on GitHub!
@[email protected] · Reply to Hollo :hollo:'s post
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.
@[email protected] · Reply to Hollo :hollo:'s post
#Hollo's search is implemented internally using #Meilisearch.
#Hollo finally has a search feature!
The name #Hollo is a Korean word 홀로, which means alone or solitary. It is named so because it is designed to be a single-user software.
Federated single user microblogging software through activitypub that is also compatible with mitra
Interact with users on Mastodon, Pixelfed, Misskey, etc
Github repo here: https://github.com/dahlia/hollo
#hollo #microblogging #federated #activitypub #opensource #foss #mastodon #fediverse #mitra #mastodon #pixelfed #misskey
Although #Hollo is a single-user microblogging software, you can manage multiple accounts with a single sign-on. Create and run multiple accounts for different topics!
#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