#Hollo

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

@[email protected]

If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!

https://github.com/sponsors/dahlia

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

@[email protected]

If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!

https://github.com/sponsors/dahlia

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

@[email protected]

If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!

https://github.com/sponsors/dahlia

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

@[email protected]

If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!

https://github.com/sponsors/dahlia

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

@[email protected]

If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!

https://github.com/sponsors/dahlia

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

@[email protected]

If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!

https://github.com/sponsors/dahlia

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

@[email protected]

If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!

https://github.com/sponsors/dahlia

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

@[email protected]

If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!

https://github.com/sponsors/dahlia

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

@[email protected]

If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!

https://github.com/sponsors/dahlia

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

@[email protected]

If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!

https://github.com/sponsors/dahlia

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

@[email protected]

If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!

https://github.com/sponsors/dahlia

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

@[email protected]

If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!

https://github.com/sponsors/dahlia

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

@[email protected]

If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!

https://github.com/sponsors/dahlia

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

@[email protected] · Reply to 洪 民憙 (Hong Minhee)'s post

@fedify」や「@hollo」や「@botkit」の開発を支援したい方は、GitHubでスポンサーになってください!

https://github.com/sponsors/dahlia

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

@[email protected]

If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!

https://github.com/sponsors/dahlia

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

@[email protected]

If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!

https://github.com/sponsors/dahlia

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

@[email protected] · Reply to 洪 民憙 (Hong Minhee)'s post

@fedify」や「@hollo」や「@botkit」の開発を支援したい方は、GitHubでスポンサーになってください!

https://github.com/sponsors/dahlia

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

@[email protected] · Reply to 洪 民憙 (Hong Minhee)'s post

@fedify」や「@hollo」や「@botkit」の開発を支援したい方は、GitHubでスポンサーになってください!

https://github.com/sponsors/dahlia

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

@[email protected] · Reply to 洪 民憙 (Hong Minhee)'s post

제 프로젝트인 @fedify, @hollo, @botkit ()開發(개발)後援(후원)하고 싶으신 분들께서는, GitHub에서 제 스폰서가 되어 주세요!

https://github.com/sponsors/dahlia

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

@[email protected]

If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!

https://github.com/sponsors/dahlia

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

@[email protected] · Reply to 洪 民憙 (Hong Minhee)'s post

@fedify」や「@hollo」や「@botkit」の開発を支援したい方は、GitHubでスポンサーになってください!

https://github.com/sponsors/dahlia

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

@[email protected]

If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!

https://github.com/sponsors/dahlia

Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@[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 :blobPikaLaugh:

free -h
               total        used        free      shared  buff/cache   available
Mem:           973Mi       779Mi        67Mi        65Mi       267Mi       193Mi
Swap:          1.0Gi          0B       1.0Gi

Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@[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

KazukyAkayashi (Hollo)'s avatar
KazukyAkayashi (Hollo)

@[email protected]

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

KazukyAkayashi (Hollo)'s avatar
KazukyAkayashi (Hollo)

@[email protected]

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

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected] · Reply to Hollo :hollo:'s post

この件に関連して、Holloもセキュリティアップデートをリリースしました。0.3.6または0.4.4バージョンに今すぐアップデートしてください!

https://hollo.social/@fedify/0194848e-7cac-7af3-941b-c93999a51274

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

@[email protected] · Reply to Fedify: an ActivityPub server framework's post

FedifyのWebFinger実装における脆弱性CVE-2025-23221に対するセキュリティアップデート(1.0.141.1.111.2.111.3.4)をリリースいたしました。すべてのユーザー様におかれましては、お使いのバージョンに応じた最新版への速やかなアップデートを推奨いたします。

脆弱性の詳細

セキュリティ研究者により、FedifyのlookupWebFinger()関数において以下のセキュリティ上の問題が発見されました:

  • 無限リダイレクトループによるサービス拒否攻撃(DoS)の可能性
  • プライベートネットワークアドレスへのリダイレクトを利用したSSRF(サーバーサイドリクエストフォージェリ)攻撃の可能性
  • リダイレクト操作による意図しないURLスキームへのアクセスの可能性

修正されたバージョン

  • 1.3.xシリーズ:1.3.4へアップデート
  • 1.2.xシリーズ:1.2.11へアップデート
  • 1.1.xシリーズ:1.1.11へアップデート
  • 1.0.xシリーズ:1.0.14へアップデート

変更内容

本セキュリティアップデートでは、以下の修正が実施されました:

  1. 無限リダイレクトループを防ぐため、最大リダイレクト回数(5回)の制限を導入
  2. 元のリクエストと同じスキーム(HTTP/HTTPS)のみにリダイレクトを制限
  3. SSRFを防止するため、プライベートネットワークアドレスへのリダイレクトをブロック

アップデート方法

以下のコマンドで最新のセキュアバージョンにアップデートできます:

# npmユーザーの場合
npm update @fedify/fedify

# Denoユーザーの場合
deno add jsr:@fedify/fedify

この脆弱性を責任を持って報告していただいたセキュリティ研究者の方に感謝申し上げます。迅速な対応が可能となりました。

本脆弱性の詳細については、セキュリティ勧告をご参照ください。


ご質問やご懸念がございましたら、GitHub DiscussionsMatrixチャットスペース、またはDiscordサーバーまでお気軽にご連絡ください。

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected] · Reply to Hollo :hollo:'s post

この件に関連して、Holloもセキュリティアップデートをリリースしました。0.3.6または0.4.4バージョンに今すぐアップデートしてください!

https://hollo.social/@fedify/0194848e-7cac-7af3-941b-c93999a51274

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

@[email protected] · Reply to Fedify: an ActivityPub server framework's post

FedifyのWebFinger実装における脆弱性CVE-2025-23221に対するセキュリティアップデート(1.0.141.1.111.2.111.3.4)をリリースいたしました。すべてのユーザー様におかれましては、お使いのバージョンに応じた最新版への速やかなアップデートを推奨いたします。

脆弱性の詳細

セキュリティ研究者により、FedifyのlookupWebFinger()関数において以下のセキュリティ上の問題が発見されました:

  • 無限リダイレクトループによるサービス拒否攻撃(DoS)の可能性
  • プライベートネットワークアドレスへのリダイレクトを利用したSSRF(サーバーサイドリクエストフォージェリ)攻撃の可能性
  • リダイレクト操作による意図しないURLスキームへのアクセスの可能性

修正されたバージョン

  • 1.3.xシリーズ:1.3.4へアップデート
  • 1.2.xシリーズ:1.2.11へアップデート
  • 1.1.xシリーズ:1.1.11へアップデート
  • 1.0.xシリーズ:1.0.14へアップデート

変更内容

本セキュリティアップデートでは、以下の修正が実施されました:

  1. 無限リダイレクトループを防ぐため、最大リダイレクト回数(5回)の制限を導入
  2. 元のリクエストと同じスキーム(HTTP/HTTPS)のみにリダイレクトを制限
  3. SSRFを防止するため、プライベートネットワークアドレスへのリダイレクトをブロック

アップデート方法

以下のコマンドで最新のセキュアバージョンにアップデートできます:

# npmユーザーの場合
npm update @fedify/fedify

# Denoユーザーの場合
deno add jsr:@fedify/fedify

この脆弱性を責任を持って報告していただいたセキュリティ研究者の方に感謝申し上げます。迅速な対応が可能となりました。

本脆弱性の詳細については、セキュリティ勧告をご参照ください。


ご質問やご懸念がございましたら、GitHub DiscussionsMatrixチャットスペース、またはDiscordサーバーまでお気軽にご連絡ください。

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected] · Reply to Hollo :hollo:'s post

この件に関連して、Holloもセキュリティアップデートをリリースしました。0.3.6または0.4.4バージョンに今すぐアップデートしてください!

https://hollo.social/@fedify/0194848e-7cac-7af3-941b-c93999a51274

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

@[email protected] · Reply to Fedify: an ActivityPub server framework's post

FedifyのWebFinger実装における脆弱性CVE-2025-23221に対するセキュリティアップデート(1.0.141.1.111.2.111.3.4)をリリースいたしました。すべてのユーザー様におかれましては、お使いのバージョンに応じた最新版への速やかなアップデートを推奨いたします。

脆弱性の詳細

セキュリティ研究者により、FedifyのlookupWebFinger()関数において以下のセキュリティ上の問題が発見されました:

  • 無限リダイレクトループによるサービス拒否攻撃(DoS)の可能性
  • プライベートネットワークアドレスへのリダイレクトを利用したSSRF(サーバーサイドリクエストフォージェリ)攻撃の可能性
  • リダイレクト操作による意図しないURLスキームへのアクセスの可能性

修正されたバージョン

  • 1.3.xシリーズ:1.3.4へアップデート
  • 1.2.xシリーズ:1.2.11へアップデート
  • 1.1.xシリーズ:1.1.11へアップデート
  • 1.0.xシリーズ:1.0.14へアップデート

変更内容

本セキュリティアップデートでは、以下の修正が実施されました:

  1. 無限リダイレクトループを防ぐため、最大リダイレクト回数(5回)の制限を導入
  2. 元のリクエストと同じスキーム(HTTP/HTTPS)のみにリダイレクトを制限
  3. SSRFを防止するため、プライベートネットワークアドレスへのリダイレクトをブロック

アップデート方法

以下のコマンドで最新のセキュアバージョンにアップデートできます:

# npmユーザーの場合
npm update @fedify/fedify

# Denoユーザーの場合
deno add jsr:@fedify/fedify

この脆弱性を責任を持って報告していただいたセキュリティ研究者の方に感謝申し上げます。迅速な対応が可能となりました。

本脆弱性の詳細については、セキュリティ勧告をご参照ください。


ご質問やご懸念がございましたら、GitHub DiscussionsMatrixチャットスペース、またはDiscordサーバーまでお気軽にご連絡ください。

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected] · Reply to Hollo :hollo:'s post

이와 관련하여, 역시 업데이트가 이뤄졌습니다. 0.3.6 또는 0.4.4 버전으로 바로 업데이트하시기 바랍니다!

https://hollo.social/@fedify/0194848b-3b9e-7da1-b631-c011db2f4c43

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

@[email protected] · Reply to Fedify: an ActivityPub server framework's post

프레임워크의 구현에서 발견된 보안 취약점 CVE-2025-23221을 해결하기 위한 보안 업데이트(1.0.14, 1.1.11, 1.2.11, 1.3.4)를 배포했습니다. 모든 사용자께서는 각자 사용 중인 버전에 해당하는 최신 버전으로 즉시 업데이트하시기를 권장합니다.

취약점 내용

보안 연구자가 Fedify의 lookupWebFinger() 함수에서 다음과 같은 보안 문제점들을 발견했습니다:

  • 무한 리다이렉트 루프를 통한 서비스 거부 공격 가능
  • 내부 네트워크 주소로의 리다이렉트를 통한 SSRF (서버측 요청 위조) 공격 가능
  • 리다이렉트 조작을 통한 의도하지 않은 URL 스킴 접근 가능

수정된 버전

  • 1.3.x 시리즈: 1.3.4로 업데이트
  • 1.2.x 시리즈: 1.2.11로 업데이트
  • 1.1.x 시리즈: 1.1.11로 업데이트
  • 1.0.x 시리즈: 1.0.14로 업데이트

변경 사항

이번 보안 업데이트에는 다음과 같은 수정 사항이 포함되어 있습니다:

  1. 무한 리다이렉트 루프를 방지하기 위해 최대 리다이렉트 횟수 제한(5회) 도입
  2. 원래 요청과 동일한 스킴(HTTP/HTTPS)으로만 리다이렉트 허용하도록 제한
  3. SSRF 공격 방지를 위해 내부 네트워크 주소로의 리다이렉트 차단

업데이트 방법

다음 명령어로 최신 보안 버전으로 업데이트하실 수 있습니다:

# npm 사용자의 경우
npm update @fedify/fedify

# Deno 사용자의 경우
deno add jsr:@fedify/fedify

이 취약점을 책임감 있게 보고해 주신 보안 연구자께 감사드립니다. 덕분에 신속하게 문제를 해결할 수 있었습니다.

이 취약점에 대한 자세한 내용은 보안 권고문을 참고해 주시기 바랍니다.


문의 사항이나 우려 사항이 있으시다면 GitHub DiscussionsMatrix 채팅방, 또는 Discord 서버를 통해 언제든 연락해 주시기 바랍니다.

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

In related news, has also released updates: 0.3.6 & 0.4.4. Update now!

https://hollo.social/@fedify/01948487-87b2-709d-953f-8799b78433ed

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

@[email protected]

We have released updates (1.0.14, 1.1.11, 1.2.11, 1.3.4) to address CVE-2025-23221, a in 's implementation. We recommend all users update to the latest version of their respective release series immediately.

The Vulnerability

A security researcher identified multiple security issues in Fedify's lookupWebFinger() function that could be exploited to:

  • Perform denial of service attacks through infinite redirect loops
  • Execute server-side request forgery () attacks via redirects to private network addresses
  • Access unintended URL schemes through redirect manipulation

Fixed Versions

  • 1.3.x series: Update to 1.3.4
  • 1.2.x series: Update to 1.2.11
  • 1.1.x series: Update to 1.1.11
  • 1.0.x series: Update to 1.0.14

Changes

The security updates implement the following fixes:

  1. Added a maximum redirect limit (5) to prevent infinite redirect loops
  2. Restricted redirects to only follow the same scheme as the original request (HTTP/HTTPS)
  3. Blocked redirects to private network addresses to prevent SSRF attacks

How to Update

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.

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

In related news, has also released updates: 0.3.6 & 0.4.4. Update now!

https://hollo.social/@fedify/01948487-87b2-709d-953f-8799b78433ed

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

@[email protected]

We have released updates (1.0.14, 1.1.11, 1.2.11, 1.3.4) to address CVE-2025-23221, a in 's implementation. We recommend all users update to the latest version of their respective release series immediately.

The Vulnerability

A security researcher identified multiple security issues in Fedify's lookupWebFinger() function that could be exploited to:

  • Perform denial of service attacks through infinite redirect loops
  • Execute server-side request forgery () attacks via redirects to private network addresses
  • Access unintended URL schemes through redirect manipulation

Fixed Versions

  • 1.3.x series: Update to 1.3.4
  • 1.2.x series: Update to 1.2.11
  • 1.1.x series: Update to 1.1.11
  • 1.0.x series: Update to 1.0.14

Changes

The security updates implement the following fixes:

  1. Added a maximum redirect limit (5) to prevent infinite redirect loops
  2. Restricted redirects to only follow the same scheme as the original request (HTTP/HTTPS)
  3. Blocked redirects to private network addresses to prevent SSRF attacks

How to Update

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.

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

In related news, has also released updates: 0.3.6 & 0.4.4. Update now!

https://hollo.social/@fedify/01948487-87b2-709d-953f-8799b78433ed

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

@[email protected]

We have released updates (1.0.14, 1.1.11, 1.2.11, 1.3.4) to address CVE-2025-23221, a in 's implementation. We recommend all users update to the latest version of their respective release series immediately.

The Vulnerability

A security researcher identified multiple security issues in Fedify's lookupWebFinger() function that could be exploited to:

  • Perform denial of service attacks through infinite redirect loops
  • Execute server-side request forgery () attacks via redirects to private network addresses
  • Access unintended URL schemes through redirect manipulation

Fixed Versions

  • 1.3.x series: Update to 1.3.4
  • 1.2.x series: Update to 1.2.11
  • 1.1.x series: Update to 1.1.11
  • 1.0.x series: Update to 1.0.14

Changes

The security updates implement the following fixes:

  1. Added a maximum redirect limit (5) to prevent infinite redirect loops
  2. Restricted redirects to only follow the same scheme as the original request (HTTP/HTTPS)
  3. Blocked redirects to private network addresses to prevent SSRF attacks

How to Update

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.

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected] · Reply to Hollo :hollo:'s post

この件に関連して、Holloもセキュリティアップデートをリリースしました。0.3.6または0.4.4バージョンに今すぐアップデートしてください!

https://hollo.social/@fedify/0194848e-7cac-7af3-941b-c93999a51274

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

@[email protected] · Reply to Fedify: an ActivityPub server framework's post

FedifyのWebFinger実装における脆弱性CVE-2025-23221に対するセキュリティアップデート(1.0.141.1.111.2.111.3.4)をリリースいたしました。すべてのユーザー様におかれましては、お使いのバージョンに応じた最新版への速やかなアップデートを推奨いたします。

脆弱性の詳細

セキュリティ研究者により、FedifyのlookupWebFinger()関数において以下のセキュリティ上の問題が発見されました:

  • 無限リダイレクトループによるサービス拒否攻撃(DoS)の可能性
  • プライベートネットワークアドレスへのリダイレクトを利用したSSRF(サーバーサイドリクエストフォージェリ)攻撃の可能性
  • リダイレクト操作による意図しないURLスキームへのアクセスの可能性

修正されたバージョン

  • 1.3.xシリーズ:1.3.4へアップデート
  • 1.2.xシリーズ:1.2.11へアップデート
  • 1.1.xシリーズ:1.1.11へアップデート
  • 1.0.xシリーズ:1.0.14へアップデート

変更内容

本セキュリティアップデートでは、以下の修正が実施されました:

  1. 無限リダイレクトループを防ぐため、最大リダイレクト回数(5回)の制限を導入
  2. 元のリクエストと同じスキーム(HTTP/HTTPS)のみにリダイレクトを制限
  3. SSRFを防止するため、プライベートネットワークアドレスへのリダイレクトをブロック

アップデート方法

以下のコマンドで最新のセキュアバージョンにアップデートできます:

# npmユーザーの場合
npm update @fedify/fedify

# Denoユーザーの場合
deno add jsr:@fedify/fedify

この脆弱性を責任を持って報告していただいたセキュリティ研究者の方に感謝申し上げます。迅速な対応が可能となりました。

本脆弱性の詳細については、セキュリティ勧告をご参照ください。


ご質問やご懸念がございましたら、GitHub DiscussionsMatrixチャットスペース、またはDiscordサーバーまでお気軽にご連絡ください。

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

In related news, has also released updates: 0.3.6 & 0.4.4. Update now!

https://hollo.social/@fedify/01948487-87b2-709d-953f-8799b78433ed

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

@[email protected]

We have released updates (1.0.14, 1.1.11, 1.2.11, 1.3.4) to address CVE-2025-23221, a in 's implementation. We recommend all users update to the latest version of their respective release series immediately.

The Vulnerability

A security researcher identified multiple security issues in Fedify's lookupWebFinger() function that could be exploited to:

  • Perform denial of service attacks through infinite redirect loops
  • Execute server-side request forgery () attacks via redirects to private network addresses
  • Access unintended URL schemes through redirect manipulation

Fixed Versions

  • 1.3.x series: Update to 1.3.4
  • 1.2.x series: Update to 1.2.11
  • 1.1.x series: Update to 1.1.11
  • 1.0.x series: Update to 1.0.14

Changes

The security updates implement the following fixes:

  1. Added a maximum redirect limit (5) to prevent infinite redirect loops
  2. Restricted redirects to only follow the same scheme as the original request (HTTP/HTTPS)
  3. Blocked redirects to private network addresses to prevent SSRF attacks

How to Update

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.

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

In related news, has also released updates: 0.3.6 & 0.4.4. Update now!

https://hollo.social/@fedify/01948487-87b2-709d-953f-8799b78433ed

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

@[email protected]

We have released updates (1.0.14, 1.1.11, 1.2.11, 1.3.4) to address CVE-2025-23221, a in 's implementation. We recommend all users update to the latest version of their respective release series immediately.

The Vulnerability

A security researcher identified multiple security issues in Fedify's lookupWebFinger() function that could be exploited to:

  • Perform denial of service attacks through infinite redirect loops
  • Execute server-side request forgery () attacks via redirects to private network addresses
  • Access unintended URL schemes through redirect manipulation

Fixed Versions

  • 1.3.x series: Update to 1.3.4
  • 1.2.x series: Update to 1.2.11
  • 1.1.x series: Update to 1.1.11
  • 1.0.x series: Update to 1.0.14

Changes

The security updates implement the following fixes:

  1. Added a maximum redirect limit (5) to prevent infinite redirect loops
  2. Restricted redirects to only follow the same scheme as the original request (HTTP/HTTPS)
  3. Blocked redirects to private network addresses to prevent SSRF attacks

How to Update

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.

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected] · Reply to Hollo :hollo:'s post

이와 관련하여, 역시 업데이트가 이뤄졌습니다. 0.3.6 또는 0.4.4 버전으로 바로 업데이트하시기 바랍니다!

https://hollo.social/@fedify/0194848b-3b9e-7da1-b631-c011db2f4c43

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

@[email protected] · Reply to Fedify: an ActivityPub server framework's post

프레임워크의 구현에서 발견된 보안 취약점 CVE-2025-23221을 해결하기 위한 보안 업데이트(1.0.14, 1.1.11, 1.2.11, 1.3.4)를 배포했습니다. 모든 사용자께서는 각자 사용 중인 버전에 해당하는 최신 버전으로 즉시 업데이트하시기를 권장합니다.

취약점 내용

보안 연구자가 Fedify의 lookupWebFinger() 함수에서 다음과 같은 보안 문제점들을 발견했습니다:

  • 무한 리다이렉트 루프를 통한 서비스 거부 공격 가능
  • 내부 네트워크 주소로의 리다이렉트를 통한 SSRF (서버측 요청 위조) 공격 가능
  • 리다이렉트 조작을 통한 의도하지 않은 URL 스킴 접근 가능

수정된 버전

  • 1.3.x 시리즈: 1.3.4로 업데이트
  • 1.2.x 시리즈: 1.2.11로 업데이트
  • 1.1.x 시리즈: 1.1.11로 업데이트
  • 1.0.x 시리즈: 1.0.14로 업데이트

변경 사항

이번 보안 업데이트에는 다음과 같은 수정 사항이 포함되어 있습니다:

  1. 무한 리다이렉트 루프를 방지하기 위해 최대 리다이렉트 횟수 제한(5회) 도입
  2. 원래 요청과 동일한 스킴(HTTP/HTTPS)으로만 리다이렉트 허용하도록 제한
  3. SSRF 공격 방지를 위해 내부 네트워크 주소로의 리다이렉트 차단

업데이트 방법

다음 명령어로 최신 보안 버전으로 업데이트하실 수 있습니다:

# npm 사용자의 경우
npm update @fedify/fedify

# Deno 사용자의 경우
deno add jsr:@fedify/fedify

이 취약점을 책임감 있게 보고해 주신 보안 연구자께 감사드립니다. 덕분에 신속하게 문제를 해결할 수 있었습니다.

이 취약점에 대한 자세한 내용은 보안 권고문을 참고해 주시기 바랍니다.


문의 사항이나 우려 사항이 있으시다면 GitHub DiscussionsMatrix 채팅방, 또는 Discord 서버를 통해 언제든 연락해 주시기 바랍니다.

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

In related news, has also released updates: 0.3.6 & 0.4.4. Update now!

https://hollo.social/@fedify/01948487-87b2-709d-953f-8799b78433ed

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

@[email protected]

We have released updates (1.0.14, 1.1.11, 1.2.11, 1.3.4) to address CVE-2025-23221, a in 's implementation. We recommend all users update to the latest version of their respective release series immediately.

The Vulnerability

A security researcher identified multiple security issues in Fedify's lookupWebFinger() function that could be exploited to:

  • Perform denial of service attacks through infinite redirect loops
  • Execute server-side request forgery () attacks via redirects to private network addresses
  • Access unintended URL schemes through redirect manipulation

Fixed Versions

  • 1.3.x series: Update to 1.3.4
  • 1.2.x series: Update to 1.2.11
  • 1.1.x series: Update to 1.1.11
  • 1.0.x series: Update to 1.0.14

Changes

The security updates implement the following fixes:

  1. Added a maximum redirect limit (5) to prevent infinite redirect loops
  2. Restricted redirects to only follow the same scheme as the original request (HTTP/HTTPS)
  3. Blocked redirects to private network addresses to prevent SSRF attacks

How to Update

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.

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

In related news, has also released updates: 0.3.6 & 0.4.4. Update now!

https://hollo.social/@fedify/01948487-87b2-709d-953f-8799b78433ed

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

@[email protected]

We have released updates (1.0.14, 1.1.11, 1.2.11, 1.3.4) to address CVE-2025-23221, a in 's implementation. We recommend all users update to the latest version of their respective release series immediately.

The Vulnerability

A security researcher identified multiple security issues in Fedify's lookupWebFinger() function that could be exploited to:

  • Perform denial of service attacks through infinite redirect loops
  • Execute server-side request forgery () attacks via redirects to private network addresses
  • Access unintended URL schemes through redirect manipulation

Fixed Versions

  • 1.3.x series: Update to 1.3.4
  • 1.2.x series: Update to 1.2.11
  • 1.1.x series: Update to 1.1.11
  • 1.0.x series: Update to 1.0.14

Changes

The security updates implement the following fixes:

  1. Added a maximum redirect limit (5) to prevent infinite redirect loops
  2. Restricted redirects to only follow the same scheme as the original request (HTTP/HTTPS)
  3. Blocked redirects to private network addresses to prevent SSRF attacks

How to Update

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.

Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@[email protected]

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

Dans les faits ça fonctionne pas mal mais ça met un peu de temps a charger

KazukyAkayashi (Hollo)'s avatar
KazukyAkayashi (Hollo)

@[email protected]

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

KazukyAkayashi (Hollo)'s avatar
KazukyAkayashi (Hollo)

@[email protected]

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

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Introducing . Hollo is an -enabled single-user microblogging software. Although it's for a single user, it also supports creating and running multiple accounts for different topics.

It's headless, meaning you can use existing client apps instead, with its Mastodon-compatible APIs. It has most feature parity with Mastodon. Two big differences with Mastodon is that you can use in the content of your posts and you can quote another post.

Oh, and Hollo is built using and .

https://github.com/dahlia/hollo

KazukyAkayashi (Hollo)'s avatar
KazukyAkayashi (Hollo)

@[email protected]

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.

KazukyAkayashi (Hollo)'s avatar
KazukyAkayashi (Hollo)

@[email protected]

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.

KazukyAkayashi (Hollo)'s avatar
KazukyAkayashi (Hollo)

@[email protected]

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.

Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@[email protected]

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.

KazukyAkayashi (Hollo)'s avatar
KazukyAkayashi (Hollo)

@[email protected]

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.

Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@[email protected]

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

Dans les faits ça fonctionne pas mal mais ça met un peu de temps a charger

KazukyAkayashi (Hollo)'s avatar
KazukyAkayashi (Hollo)

@[email protected]

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.

KazukyAkayashi (Hollo)'s avatar
KazukyAkayashi (Hollo)

@[email protected]

Hmmm étrange quand même le nombre de message donné par Iceshrimp 65 vs 69 sur le profil de mon compte Hollo

screenshot du profil de mon compte Hollo (avec Phanpy) montrant 65 messages
screenshot du profil de mon compte Hollo (avec Phanpy) montrant 65 messages
screentshot de mon compte Hollo mais vu depuis mon compte sur mon instance Iceshrimp qui affiche 69 messages alors que Phanpy n'en compte que 65.
screentshot de mon compte Hollo mais vu depuis mon compte sur mon instance Iceshrimp qui affiche 69 messages alors que Phanpy n'en compte que 65.
KazukyAkayashi (Hollo)'s avatar
KazukyAkayashi (Hollo)

@[email protected]

Hmmm étrange quand même le nombre de message donné par Iceshrimp 65 vs 69 sur le profil de mon compte Hollo

screenshot du profil de mon compte Hollo (avec Phanpy) montrant 65 messages
screenshot du profil de mon compte Hollo (avec Phanpy) montrant 65 messages
screentshot de mon compte Hollo mais vu depuis mon compte sur mon instance Iceshrimp qui affiche 69 messages alors que Phanpy n'en compte que 65.
screentshot de mon compte Hollo mais vu depuis mon compte sur mon instance Iceshrimp qui affiche 69 messages alors que Phanpy n'en compte que 65.
洪 民憙 (Hong Minhee)'s avatar
洪 民憙 (Hong Minhee)

@[email protected]

私も微力ながら『Thinking Penguin Magazine Vol.0』に「国漢文混用体からHolloまで」という拙稿を寄稿しました。興味の有る方は、第十一回技術書同人誌博覧会で手に入れる事が出来ます。

https://msky.ospn.jp/notes/a35ankd6m2p80nev

Fediverse Linux Users Group @ 技書博 き-02's avatar
Fediverse Linux Users Group @ 技書博 き-02

@[email protected]

【技術書同人誌博覧会まであと1週間‼️
は来週の今日、2025年1月25日に横浜産貿ホール マリネリアで開催される第11回技術書同人誌博覧会( )に出展します。
新刊として『Thinkng Penguin Magazine vol.0』を頒布します!(124ページ・500円)
委託として
@[email protected] さんの『さばかんライフ!』も頒布いたします!

皆さんのお越しを心待ちにしています!!!

詳しくは技術書博の公式サイトおよび、サークル概要をご覧ください!
https://gishohaku.dev/gishohaku11/circles/LOmokXEikphsDCEG9OEb

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

@[email protected]

私も微力ながら『Thinking Penguin Magazine Vol.0』に「国漢文混用体からHolloまで」という拙稿を寄稿しました。興味の有る方は、第十一回技術書同人誌博覧会で手に入れる事が出来ます。

https://msky.ospn.jp/notes/a35ankd6m2p80nev

Fediverse Linux Users Group @ 技書博 き-02's avatar
Fediverse Linux Users Group @ 技書博 き-02

@[email protected]

【技術書同人誌博覧会まであと1週間‼️
は来週の今日、2025年1月25日に横浜産貿ホール マリネリアで開催される第11回技術書同人誌博覧会( )に出展します。
新刊として『Thinkng Penguin Magazine vol.0』を頒布します!(124ページ・500円)
委託として
@[email protected] さんの『さばかんライフ!』も頒布いたします!

皆さんのお越しを心待ちにしています!!!

詳しくは技術書博の公式サイトおよび、サークル概要をご覧ください!
https://gishohaku.dev/gishohaku11/circles/LOmokXEikphsDCEG9OEb

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

@[email protected]

私も微力ながら『Thinking Penguin Magazine Vol.0』に「国漢文混用体からHolloまで」という拙稿を寄稿しました。興味の有る方は、第十一回技術書同人誌博覧会で手に入れる事が出来ます。

https://msky.ospn.jp/notes/a35ankd6m2p80nev

Fediverse Linux Users Group @ 技書博 き-02's avatar
Fediverse Linux Users Group @ 技書博 き-02

@[email protected]

【技術書同人誌博覧会まであと1週間‼️
は来週の今日、2025年1月25日に横浜産貿ホール マリネリアで開催される第11回技術書同人誌博覧会( )に出展します。
新刊として『Thinkng Penguin Magazine vol.0』を頒布します!(124ページ・500円)
委託として
@[email protected] さんの『さばかんライフ!』も頒布いたします!

皆さんのお越しを心待ちにしています!!!

詳しくは技術書博の公式サイトおよび、サークル概要をご覧ください!
https://gishohaku.dev/gishohaku11/circles/LOmokXEikphsDCEG9OEb

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

@[email protected]

私も微力ながら『Thinking Penguin Magazine Vol.0』に「国漢文混用体からHolloまで」という拙稿を寄稿しました。興味の有る方は、第十一回技術書同人誌博覧会で手に入れる事が出来ます。

https://msky.ospn.jp/notes/a35ankd6m2p80nev

Fediverse Linux Users Group @ 技書博 き-02's avatar
Fediverse Linux Users Group @ 技書博 き-02

@[email protected]

【技術書同人誌博覧会まであと1週間‼️
は来週の今日、2025年1月25日に横浜産貿ホール マリネリアで開催される第11回技術書同人誌博覧会( )に出展します。
新刊として『Thinkng Penguin Magazine vol.0』を頒布します!(124ページ・500円)
委託として
@[email protected] さんの『さばかんライフ!』も頒布いたします!

皆さんのお越しを心待ちにしています!!!

詳しくは技術書博の公式サイトおよび、サークル概要をご覧ください!
https://gishohaku.dev/gishohaku11/circles/LOmokXEikphsDCEG9OEb

Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@[email protected]

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

Dans les faits ça fonctionne pas mal mais ça met un peu de temps a charger

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

@[email protected]

私も微力ながら『Thinking Penguin Magazine Vol.0』に「国漢文混用体からHolloまで」という拙稿を寄稿しました。興味の有る方は、第十一回技術書同人誌博覧会で手に入れる事が出来ます。

https://msky.ospn.jp/notes/a35ankd6m2p80nev

Fediverse Linux Users Group @ 技書博 き-02's avatar
Fediverse Linux Users Group @ 技書博 き-02

@[email protected]

【技術書同人誌博覧会まであと1週間‼️
は来週の今日、2025年1月25日に横浜産貿ホール マリネリアで開催される第11回技術書同人誌博覧会( )に出展します。
新刊として『Thinkng Penguin Magazine vol.0』を頒布します!(124ページ・500円)
委託として
@[email protected] さんの『さばかんライフ!』も頒布いたします!

皆さんのお越しを心待ちにしています!!!

詳しくは技術書博の公式サイトおよび、サークル概要をご覧ください!
https://gishohaku.dev/gishohaku11/circles/LOmokXEikphsDCEG9OEb

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Introducing . Hollo is an -enabled single-user microblogging software. Although it's for a single user, it also supports creating and running multiple accounts for different topics.

It's headless, meaning you can use existing client apps instead, with its Mastodon-compatible APIs. It has most feature parity with Mastodon. Two big differences with Mastodon is that you can use in the content of your posts and you can quote another post.

Oh, and Hollo is built using and .

https://github.com/dahlia/hollo

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

@[email protected]

私も微力ながら『Thinking Penguin Magazine Vol.0』に「国漢文混用体からHolloまで」という拙稿を寄稿しました。興味の有る方は、第十一回技術書同人誌博覧会で手に入れる事が出来ます。

https://msky.ospn.jp/notes/a35ankd6m2p80nev

Fediverse Linux Users Group @ 技書博 き-02's avatar
Fediverse Linux Users Group @ 技書博 き-02

@[email protected]

【技術書同人誌博覧会まであと1週間‼️
は来週の今日、2025年1月25日に横浜産貿ホール マリネリアで開催される第11回技術書同人誌博覧会( )に出展します。
新刊として『Thinkng Penguin Magazine vol.0』を頒布します!(124ページ・500円)
委託として
@[email protected] さんの『さばかんライフ!』も頒布いたします!

皆さんのお越しを心待ちにしています!!!

詳しくは技術書博の公式サイトおよび、サークル概要をご覧ください!
https://gishohaku.dev/gishohaku11/circles/LOmokXEikphsDCEG9OEb

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

@[email protected]

私も微力ながら『Thinking Penguin Magazine Vol.0』に「国漢文混用体からHolloまで」という拙稿を寄稿しました。興味の有る方は、第十一回技術書同人誌博覧会で手に入れる事が出来ます。

https://msky.ospn.jp/notes/a35ankd6m2p80nev

Fediverse Linux Users Group @ 技書博 き-02's avatar
Fediverse Linux Users Group @ 技書博 き-02

@[email protected]

【技術書同人誌博覧会まであと1週間‼️
は来週の今日、2025年1月25日に横浜産貿ホール マリネリアで開催される第11回技術書同人誌博覧会( )に出展します。
新刊として『Thinkng Penguin Magazine vol.0』を頒布します!(124ページ・500円)
委託として
@[email protected] さんの『さばかんライフ!』も頒布いたします!

皆さんのお越しを心待ちにしています!!!

詳しくは技術書博の公式サイトおよび、サークル概要をご覧ください!
https://gishohaku.dev/gishohaku11/circles/LOmokXEikphsDCEG9OEb

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

does not currently cache media attached to remote posts or avatars from remote accounts (except for thumbnails). Do you think we should cache them?

OptionVoters
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 :hollo:'s avatar
Hollo :hollo:

@[email protected]

does not currently cache media attached to remote posts or avatars from remote accounts (except for thumbnails). Do you think we should cache them?

OptionVoters
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 :hollo:'s avatar
Hollo :hollo:

@[email protected]

does not currently cache media attached to remote posts or avatars from remote accounts (except for thumbnails). Do you think we should cache them?

OptionVoters
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 :hollo:'s avatar
Hollo :hollo:

@[email protected]

finally has /-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 , you can use the Quote button that appears when you press the boost icon!

https://hollo.social/@fedify/0191d67c-a300-786e-8395-2020ac47ebc7

The menu that appears when you press the boost icon in Phanpy. The menu items are Boost and Quote.
The menu that appears when you press the boost icon in Phanpy. The menu items are Boost and Quote.
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

now implements FEP-e232 as well for incoming and outgoing activities!

https://hollo.social/@hollo/0191d68a-3ba7-7f2f-9836-fe8664fb51b0

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

finally has /-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 , you can use the Quote button that appears when you press the boost icon!

https://hollo.social/@fedify/0191d67c-a300-786e-8395-2020ac47ebc7

The menu that appears when you press the boost icon in Phanpy. The menu items are Boost and Quote.
The menu that appears when you press the boost icon in Phanpy. The menu items are Boost and Quote.
もちもちずきん :teto_zuho: 🍆's avatar
もちもちずきん :teto_zuho: 🍆

@[email protected]

のホームページを更新しました。
主な分散型SNSの欄に新たに を追加しました。
fediverse.pcgf.io

もちもちずきん :teto_zuho: 🍆's avatar
もちもちずきん :teto_zuho: 🍆

@[email protected]

のホームページを更新しました。
主な分散型SNSの欄に新たに を追加しました。
fediverse.pcgf.io

もちもちずきん :teto_zuho: 🍆's avatar
もちもちずきん :teto_zuho: 🍆

@[email protected]

のホームページを更新しました。
主な分散型SNSの欄に新たに を追加しました。
fediverse.pcgf.io

もちもちずきん :teto_zuho: 🍆's avatar
もちもちずきん :teto_zuho: 🍆

@[email protected]

のホームページを更新しました。
主な分散型SNSの欄に新たに を追加しました。
fediverse.pcgf.io

もちもちずきん :teto_zuho: 🍆's avatar
もちもちずきん :teto_zuho: 🍆

@[email protected]

のホームページを更新しました。
主な分散型SNSの欄に新たに を追加しました。
fediverse.pcgf.io

もちもちずきん :teto_zuho: 🍆's avatar
もちもちずきん :teto_zuho: 🍆

@[email protected]

のホームページを更新しました。
主な分散型SNSの欄に新たに を追加しました。
fediverse.pcgf.io

もちもちずきん :teto_zuho: 🍆's avatar
もちもちずきん :teto_zuho: 🍆

@[email protected]

のホームページを更新しました。
主な分散型SNSの欄に新たに を追加しました。
fediverse.pcgf.io

もちもちずきん :teto_zuho: 🍆's avatar
もちもちずきん :teto_zuho: 🍆

@[email protected]

のホームページを更新しました。
主な分散型SNSの欄に新たに を追加しました。
fediverse.pcgf.io

もちもちずきん :teto_zuho: 🍆's avatar
もちもちずきん :teto_zuho: 🍆

@[email protected]

のホームページを更新しました。
主な分散型SNSの欄に新たに を追加しました。
fediverse.pcgf.io

もちもちずきん :teto_zuho: 🍆's avatar
もちもちずきん :teto_zuho: 🍆

@[email protected]

のホームページを更新しました。
主な分散型SNSの欄に新たに を追加しました。
fediverse.pcgf.io

Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@[email protected]

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.

Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@[email protected]

Bon théoriquement l'import d'abonnement est corrigé dans 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 :pikauvu:

RE:
hollo.zarchbox.fr/@KazukyAkayashi/01945492-0ff4-7b5e-8095-c6614ffb3d5a

Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@[email protected]

It lacks a lightweight single-user software dedicated to posting images, a kind of Hollo but for images, easy to install (and without docker :troll:) and to update.

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

@[email protected]

In the next version of , I'd like to improve search quality.

technicat's avatar
technicat

@[email protected] · Reply to Jcrabapple's post

@jcrabapple Just before the year ended I got a few fediverse test servers running: , , and for a while, .

Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@[email protected]

Finalement je sais si je vais pas finir par migrer sur :nko_curious: ça tourne sur la donc ça me libère d'un VPS + Backup qui on quand même pas mal augmenter.

Bon Hollo est encore tout jeune mais je trouve ça pas mal du tout et ça tourne bien
:nko_okay:

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

In 0.5.0, the number of likes and shares will be more accurate.

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

In 0.5.0, the number of likes and shares will be more accurate.

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

In 0.5.0, the number of likes and shares will be more accurate.

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

In 0.5.0, the number of likes and shares will be more accurate.

fediverseobserver's avatar
fediverseobserver

@[email protected]

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 servers found:

hollo.ssig33.com a server from Private
diaspora.delaylama.de a server from France
mastodon.mulesgaming.com a server from Private
cabamacnagoya.harumaki2000.net a server from Private
pl.firelink.digital a server from Private
kurage.homes a server from Germany
social.seedoubleyou.me a server from United Arab Emirates
this-email-list.ispants.com a server from United Kingdom
altair.nyoroooon.xyz a server from Private
fedi.merta.xyz a server from United States
lvgaldieri.com a server from United States

Help others find a home, send them to fediverse.observer

fediverseobserver's avatar
fediverseobserver

@[email protected]

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 servers found:

hollo.ssig33.com a server from Private
diaspora.delaylama.de a server from France
mastodon.mulesgaming.com a server from Private
cabamacnagoya.harumaki2000.net a server from Private
pl.firelink.digital a server from Private
kurage.homes a server from Germany
social.seedoubleyou.me a server from United Arab Emirates
this-email-list.ispants.com a server from United Kingdom
altair.nyoroooon.xyz a server from Private
fedi.merta.xyz a server from United States
lvgaldieri.com a server from United States

Help others find a home, send them to fediverse.observer

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Have you been having trouble fetching accounts or posts from that have custom emojis in ?

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

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Have you been having trouble fetching accounts or posts from that have custom emojis in ?

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

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Have you been having trouble fetching accounts or posts from that have custom emojis in ?

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

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Have you been having trouble fetching accounts or posts from that have custom emojis in ?

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

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Have you been having trouble fetching accounts or posts from that have custom emojis in ?

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

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Hollo 0.4.0 released! is a single-user federated microblogging software which is -enabled and powered by .

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:

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

is currently testing .js instead of . (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's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Did you know? supports /-style . You can quote another post by adding a link to it. If a post contains any link to an object of Article/Note/Question, Hollo quotes it in the post.

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Did you know? supports /-style . You can quote another post by adding a link to it. If a post contains any link to an object of Article/Note/Question, Hollo quotes it in the post.

Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@[email protected]

Hmm je vais tester l'import des Follows dans , si la moitié du fediverse casse vous saurez pourquoi :troll:

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Did you know? supports /-style . You can quote another post by adding a link to it. If a post contains any link to an object of Article/Note/Question, Hollo quotes it in the post.

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Did you know? supports /-style . You can quote another post by adding a link to it. If a post contains any link to an object of Article/Note/Question, Hollo quotes it in the post.

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Did you know? supports /-style . You can quote another post by adding a link to it. If a post contains any link to an object of Article/Note/Question, Hollo quotes it in the post.

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

@[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

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

@[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

KazukyAkayashi (Hollo)'s avatar
KazukyAkayashi (Hollo)

@[email protected]

Update Hollo to v.0.4.0 🎉 But I will have to rewrite my hollo.service for systemd :pikathinknothappy:

http://hollo.social/@hollo/01941325-8d0e-71e4-ad49-daef861c01d0

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Hollo 0.4.0 released! is a single-user federated microblogging software which is -enabled and powered by .

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:

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Hollo 0.4.0 released! is a single-user federated microblogging software which is -enabled and powered by .

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:

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

is currently testing .js instead of . (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's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
KazukyAkayashi (Hollo)'s avatar
KazukyAkayashi (Hollo)

@[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 :hollo:'s avatar
Hollo :hollo:

@[email protected]

Hollo 0.4.0 released! is a single-user federated microblogging software which is -enabled and powered by .

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:

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

is currently testing .js instead of . (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's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
KazukyAkayashi (Hollo)'s avatar
KazukyAkayashi (Hollo)

@[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.

KazukyAkayashi (Hollo)'s avatar
KazukyAkayashi (Hollo)

@[email protected]

Update Hollo to v.0.4.0 🎉 But I will have to rewrite my hollo.service for systemd :pikathinknothappy:

http://hollo.social/@hollo/01941325-8d0e-71e4-ad49-daef861c01d0

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Hollo 0.4.0 released! is a single-user federated microblogging software which is -enabled and powered by .

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:

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Hollo 0.4.0 released! is a single-user federated microblogging software which is -enabled and powered by .

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:

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

is currently testing .js instead of . (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's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Hollo 0.4.0 released! is a single-user federated microblogging software which is -enabled and powered by .

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:

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

is currently testing .js instead of . (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's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Hollo 0.4.0 released! is a single-user federated microblogging software which is -enabled and powered by .

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:

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

is currently testing .js instead of . (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's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Hollo 0.4.0 released! is a single-user federated microblogging software which is -enabled and powered by .

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:

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

is currently testing .js instead of . (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's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Hollo 0.4.0 released! is a single-user federated microblogging software which is -enabled and powered by .

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:

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

is currently testing .js instead of . (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's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Hollo 0.4.0 released! is a single-user federated microblogging software which is -enabled and powered by .

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:

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

is currently testing .js instead of . (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's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Hollo 0.4.0 released! is a single-user federated microblogging software which is -enabled and powered by .

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:

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

is currently testing .js instead of . (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's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Hollo 0.4.0 released! is a single-user federated microblogging software which is -enabled and powered by .

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:

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

is currently testing .js instead of . (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's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Hollo 0.4.0 released! is a single-user federated microblogging software which is -enabled and powered by .

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:

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

is currently testing .js instead of . (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's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@[email protected]

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
:pikauvu:

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

One hidden feature of : You can also quote another post while replying to someone else's post.

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

@[email protected]

Just released 0.3.5, which contains small minor bug fixes.

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

@[email protected]

Just released 0.3.5, which contains small minor bug fixes.

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Introducing . Hollo is an -enabled single-user microblogging software. Although it's for a single user, it also supports creating and running multiple accounts for different topics.

It's headless, meaning you can use existing client apps instead, with its Mastodon-compatible APIs. It has most feature parity with Mastodon. Two big differences with Mastodon is that you can use in the content of your posts and you can quote another post.

Oh, and Hollo is built using and .

https://github.com/dahlia/hollo

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

@[email protected]

Just released 0.3.5, which contains small minor bug fixes.

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

One hidden feature of : You can also quote another post while replying to someone else's post.

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

We'll be releasing 0.4.0 before the year is out. Stay tuned!

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

One hidden feature of : You can also quote another post while replying to someone else's post.

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

One hidden feature of : You can also quote another post while replying to someone else's post.

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

We'll be releasing 0.4.0 before the year is out. Stay tuned!

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

We'll be releasing 0.4.0 before the year is out. Stay tuned!

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

@[email protected]

Just released 0.3.5, which contains small minor bug fixes.

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

@[email protected]

Just released 0.3.5, which contains small minor bug fixes.

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

@[email protected]

Just released 0.3.5, which contains small minor bug fixes.

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

@[email protected]

Just released 0.3.5, which contains small minor bug fixes.

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Introducing . Hollo is an -enabled single-user microblogging software. Although it's for a single user, it also supports creating and running multiple accounts for different topics.

It's headless, meaning you can use existing client apps instead, with its Mastodon-compatible APIs. It has most feature parity with Mastodon. Two big differences with Mastodon is that you can use in the content of your posts and you can quote another post.

Oh, and Hollo is built using and .

https://github.com/dahlia/hollo

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Starting with 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.

In the profile settings, you can see the new option labeled with “Allow your account to be discovered in the public directory.”
In the profile settings, you can see the new option labeled with “Allow your account to be discovered in the public directory.”
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Starting with 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.

In the profile settings, you can see the new option labeled with “Allow your account to be discovered in the public directory.”
In the profile settings, you can see the new option labeled with “Allow your account to be discovered in the public directory.”
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Starting with 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.

In the profile settings, you can see the new option labeled with “Allow your account to be discovered in the public directory.”
In the profile settings, you can see the new option labeled with “Allow your account to be discovered in the public directory.”
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Starting with 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.

In the profile settings, you can see the new option labeled with “Allow your account to be discovered in the public directory.”
In the profile settings, you can see the new option labeled with “Allow your account to be discovered in the public directory.”
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Starting with 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.

In the profile settings, you can see the new option labeled with “Allow your account to be discovered in the public directory.”
In the profile settings, you can see the new option labeled with “Allow your account to be discovered in the public directory.”
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Starting with 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.

In the profile settings, you can see the new option labeled with “Allow your account to be discovered in the public directory.”
In the profile settings, you can see the new option labeled with “Allow your account to be discovered in the public directory.”
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Starting with 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.

In the profile settings, you can see the new option labeled with “Allow your account to be discovered in the public directory.”
In the profile settings, you can see the new option labeled with “Allow your account to be discovered in the public directory.”
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Starting with 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.

In the profile settings, you can see the new option labeled with “Allow your account to be discovered in the public directory.”
In the profile settings, you can see the new option labeled with “Allow your account to be discovered in the public directory.”
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Starting with 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.

In the profile settings, you can see the new option labeled with “Allow your account to be discovered in the public directory.”
In the profile settings, you can see the new option labeled with “Allow your account to be discovered in the public directory.”
Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@[email protected]

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
:pikauvu:

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

@[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

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected] · Reply to Hollo :hollo:'s post

Okay, testing with .js is cruising along. It's consuming up to 3 GB of memory at peak times, but that's a huge improvement over Hollo with , which was consuming over 8 GB of memory at peak times.

So, yes, starting with Hollo 0.4.0, we'll use Node.js instead of Bun!

Memory usage chart for the hollo.social server. You can see that before December 18th, the point at which we switched to Node.js, the memory usage fluctuated between 1 GB and 8 GB, but since then, it's been mostly stable around 1 GB. It did spike to 3 GB at peak times, but only briefly during the entire test period.
Memory usage chart for the hollo.social server. You can see that before December 18th, the point at which we switched to Node.js, the memory usage fluctuated between 1 GB and 8 GB, but since then, it's been mostly stable around 1 GB. It did spike to 3 GB at peak times, but only briefly during the entire test period.
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

is currently testing .js instead of . (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's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
KazukyAkayashi (Hollo)'s avatar
KazukyAkayashi (Hollo)

@[email protected]

Poupoupou :nko_wwwoooouuu: Hollo update 0.3.1 🎉

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

For those who want to use on @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!

KazukyAkayashi (Hollo)'s avatar
KazukyAkayashi (Hollo)

@[email protected]

Strange, I no longer have a federated timeline since Moshidon. I should check tomorrow to see what Hollo's logs tell me.

Moshidon say : Required field 'url' of type String was null in Mention.
Moshidon say : Required field 'url' of type String was null in Mention.
洪 民憙 (Hong Minhee)'s avatar
洪 民憙 (Hong Minhee)

@[email protected]

For the sake of dogfooding , 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!

fedicat's avatar
fedicat

@[email protected]

the api lists a boost visibility option but so far I only see it working in

screenshot of a post context menu showing boost visibility options 

Detected text:

10:18techtechnicat10:18 AMtest boost visPosted via fedicat› Languagev InteractFavoritev Boostextrovert (visibleto everyone)introvert (public, notin timelines)shy (visibleto followers)8
screenshot of a post context menu showing boost visibility options Detected text: 10:18techtechnicat10:18 AMtest boost visPosted via fedicat› Languagev InteractFavoritev Boostextrovert (visibleto everyone)introvert (public, notin timelines)shy (visibleto followers)8
Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@[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.

Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@[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 depuis mon compte , avec des double saut de ligne :paw:

Et chez vous ça donne quoi?

Screenshot d'une publication de mon compte sur Hollo depuis Moshidon (android) montrant le double saut de ligne depuis iceshrimp.
Screenshot d'une publication de mon compte sur Hollo depuis Moshidon (android) montrant le double saut de ligne depuis iceshrimp.
KazukyAkayashi (Hollo)'s avatar
KazukyAkayashi (Hollo)

@[email protected] · Reply to KazukyAkayashi (Hollo)'s post

C'est vraiment dommage du coup que ne fonctionne pas avec :pikasad: car je suis pas fan de ou de

Quand a 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.

KazukyAkayashi (Hollo)'s avatar
KazukyAkayashi (Hollo)

@[email protected] · Reply to KazukyAkayashi (Hollo)'s post

Du coup le stockage local fonctionne nickel 👍

KazukyAkayashi (Hollo)'s avatar
KazukyAkayashi (Hollo)

@[email protected] · Reply to KazukyAkayashi (Hollo)'s post

Hollo in

Screenshot de l'application Moshidon montrant mon profil sur mon instance Hollo.
Screenshot de l'application Moshidon montrant mon profil sur mon instance Hollo.
Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@[email protected]

Hmm bon 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 :nko_curious:

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Hollo 0.3.0 released! is a single-user federated microblogging software which is -enabled and powered by .

The key changes of this release include:

  • Thanks to @joschi, Hollo now support local filesystem storage for media files. You can configure 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.
  • Added support for Sentry. If you want to see error reports and instrumented traces in Sentry, please configure SENTRY_DSN.
  • Added pagination to the profile page.
  • Minor performance improvements and bug fixes due to upgrading Fedify to 1.3.0.

You can upgrade to Hollo 0.3.0 using the following ways:

fedicat's avatar
fedicat

@[email protected]

I don’t have my test instance completely set up with S3 for media but pretty sure is working with now.

screenshot of home feed with test posts and image placeholders in teal

Detected text:

12:35Homehollo.fedifolio.comtechtechnicat12:34 AMalt texttechtechnicat12:13 AMtechtechnicat11/28/20241technicattechtechnicatТ 11/27/202411/27/2024trst112
screenshot of home feed with test posts and image placeholders in teal Detected text: 12:35Homehollo.fedifolio.comtechtechnicat12:34 AMalt texttechtechnicat12:13 AMtechtechnicat11/28/20241technicattechtechnicatТ 11/27/202411/27/2024trst112
fedicat's avatar
fedicat

@[email protected]

got my instance working again, turned out to be an nginx/certbot thing, I don't know how you server-side guys do it

fedicat's avatar
fedicat

@[email protected]

working on support

screenshot of a home feed with just a few test posts

Detected text:

9:50Homeo introvert (public, not in timelines)Phil Chutechnicattest introPhil ChutechnicattestingPhil Chutechnicattesthollo.fedifolio.com6:03 PM6:03 PM12:59 AM
screenshot of a home feed with just a few test posts Detected text: 9:50Homeo introvert (public, not in timelines)Phil Chutechnicattest introPhil ChutechnicattestingPhil Chutechnicattesthollo.fedifolio.com6:03 PM6:03 PM12:59 AM
염산하

@[email protected]

헛 이제 보니 썸네일 이미지들이 안보인다. 흠... 클라우드플레어 스토리지에는 파일이 있네?

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

The v0.2.3 has been released, which fixes a few bugs and brings 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.

염산하

@[email protected]

모바일에서도 phanpy social 로 보는게 dawn 보다 훨씬 보기 좋네.

NTSK's avatar
NTSK

@[email protected]

タニタのページを貼るとエラー出るの、まじでバグっぽい https://gist.github.com/ntsklab/3bb1c72fc6dda82a54f6171ff4c8c679

염산하

@[email protected]

홀로 인스턴스 만들면서 처음 설정하는 관리 계정의 이메일이 인스턴스 연락 메일로도 사용된다. credentials 테이블에서 변경할 수 있다.

anno189

@[email protected]

Simple logging library with zero dependencies for Deno, Node.js, Bun, browsers, and edge functions https://logtape.org/

anno189

@[email protected]

ActivityPub server framework in TypeScript https://fedify.dev/

anno189

@[email protected]

使用 Pglite 替代了 postgresql。 测试成功。

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

@[email protected]

Star History of , , and :

star-history.com/#dahlia/fedif

Star History of Fedify, Hollo, and LogTape.
Star History of Fedify, Hollo, and LogTape.
Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@[email protected]

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

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

@[email protected]

Flyers for and to be used at an open source event in Japan!

https://mstdn.y-zu.org/@Yohei_Zuho/113440544215822210

Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@[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

Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@[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 :pikasad:
En espérant que le stockage local soit rajouté dans les prochaines versions.

Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@[email protected] · Reply to Kazuky Akayashi ฅ^•ﻌ•^ฅ's post

Bon bah ça fonctionne pas mal du tout :nko_okay:
Va juste falloir mettre un truc de stockage en place pour tester bien la chose.



RE:
hollo.zarchbox.fr/@KazukyAkayashi/0192fda2-f090-7c21-9a15-4d1896aa573f

KazukyAkayashi (Hollo)'s avatar
KazukyAkayashi (Hollo)

@[email protected]

Hello world 👋

Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@[email protected] · Reply to Kazuky Akayashi ฅ^•ﻌ•^ฅ's post

Ah bah zut alors Mangane ça marche pas avec Hollo :pikathinknothappy:

Kazuky Akayashi ฅ^•ﻌ•^ฅ's avatar
Kazuky Akayashi ฅ^•ﻌ•^ฅ

@[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
:pikaneutral: :pikascream:

Je vais tester le reste mais ça semble pas mal foutu dans la même veine que GotoSocial mais qui fonctionne mieux
:pikasmilesweat:

Honnip's avatar
Honnip

@[email protected]

주말부터 모듈로 작성하고 있는데 어느 정도 마무리가 된 듯하다. 지금은 개발이 빠르게 진행되고 있어서 nixpkgs에 올리는 건 나중에 생각해 보는 걸로..

패키지: https://github.com/honnip/dotfiles/blob/3e52a09afc680ecaff6c0d7dfff414f507af3f8a/pkgs/hollo/default.nix 모듈: https://github.com/honnip/dotfiles/blob/3e52a09afc680ecaff6c0d7dfff414f507af3f8a/modules/nixos/hollo.nix

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Hollo 0.2.0 released! is a single-user federated microblogging software which is -enabled and powered by .

The key changes of this release include:

  1. Thanks to @thisismissem, now you can report remote accounts and posts.

  2. Added two-factor authentication support.

  3. Thanks again to @thisismissem, Hollo improved alignment on Mastodon API changes about OAuth and apps.

  4. Thanks again to @thisismissem, RFC 8414 for OAuth Authorization Server metadata endpoint. It will improve interoperability between Hollo and Mastodon-compatible client apps.

  5. Renamed the Data menu from the administration dashboard to Federation, and:

    • Now posts also can be force-refreshed.
    • Now the number of messages in the task queue is shown.
  6. Custom emojis now can be deleted from the administration dashboard.

  7. Thanks to @helge, PORT and ALLOW_PRIVATE_ADDRESS environment variables are introduced.

  8. Added a favicon.

  9. Dropped support for Redis, which was an optional dependency.

You can upgrade to Hollo 0.2.0 using the following ways:

5-a. Now posts also can be force-refreshed.
5-a. Now posts also can be force-refreshed.
5-b. Now the number of messages in the task queue is shown.
5-b. Now the number of messages in the task queue is shown.
6. Custom emojis now can be deleted from the administration dashboard.
6. Custom emojis now can be deleted from the administration dashboard.
2. Added two-factor authentication support.
2. Added two-factor authentication support.
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

In the next version of , 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 number of messages in the task queue as seen in Hollo's administration dashboard.
The number of messages in the task queue as seen in Hollo's administration dashboard.
poes :pla:'s avatar
poes :pla:

@[email protected]

I'm in waiting for someone create fedi app using fedify and deno (#Hollo like app).

Doesn't using Bun, sorry.

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

The next version of '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.

The administration dashboard in the next version of Hollo. There is a Federation menu instead of a Data menu.
The administration dashboard in the next version of Hollo. There is a Federation menu instead of a Data menu.
洪 民憙(ホン・ミンヒ)'s avatar
洪 民憙(ホン・ミンヒ)

@[email protected] · Reply to 洪 民憙(ホン・ミンヒ)'s post

今日Fedify/Holloのブースに訪問してくれた皆様、本当にありがとうございました‼️機会があれば是非またお会いましょう!

洪 民憙(ホン・ミンヒ)'s avatar
洪 民憙(ホン・ミンヒ)

@[email protected] · Reply to 洪 民憙(ホン・ミンヒ)'s post

FedifyとHolloのブースです!

洪 民憙(ホン・ミンヒ)'s avatar
洪 民憙(ホン・ミンヒ)

@[email protected]

今週土曜日に開催されるOSC 2024 Tokyo/FallにFedify/Hollo合同で出展します!可愛いFedifyのロゴのシールと『自分だけのフェディバースのマイクロブログを作ろう!』日本語版の紙の本を持って行く予定です。よろしくお願いします。

event.ospn.jp/osc2024-fall/

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

's GitHub repository now has 200 stars!

Hollo's GitHub repository now has 200 stars.
Hollo's GitHub repository now has 200 stars.
Daniel Finsler's avatar
Daniel Finsler

@[email protected] · Reply to Hollo :hollo:'s post

@hollo on , please :blobangel:

Daniel Finsler's avatar
Daniel Finsler

@[email protected]

github.com/dahlia/hollo

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

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.

Two-factor authentication settings on the Hollo administration dashboard.
Two-factor authentication settings on the Hollo administration dashboard.
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Finally, Hollo 0.1.0 released! is a single-user federated microblogging software which is -enabled and powered by .

Hollo has the most of features that Mastodon has except for moderation tools, and also include:

  • CommonMark (a.k.a. Markdown) and up to 4,096 characters per post
  • Misskey-style quotes (compatible with Misskey, Akkoma, Fedibird, etc)
  • Misskey-style emoji reactions (both Unicode emojis and custom emojis are supported; compatible with Misskey, Akkoma, kmyblue, etc)
  • Generally much relaxed limitations (more poll options, more attachments, and so on)
  • … and many more!

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:

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

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:

https://docs.hollo.social/clients/

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

The most common pitfall for first-time 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.

The warning message seen on Hollo's setup page.
The warning message seen on Hollo's setup page.
촛불에 구어진🔥잉어구이🔥's avatar
촛불에 구어진🔥잉어구이🔥

@[email protected]

오라클 클라우드 프리티어에서 홀로 잘 도네요.

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

@[email protected]

1人 인스턴스를 만드시고 싶은가요? 무거운 Mastodon이나 Misskey 말고 써 보세요!

docs.hollo.social/ko/

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

also works great on Windows (if you want it to)!

https://fedibird.com/@dampuzakura/113338382209044412

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

@[email protected]

The development speed of is itself an advertisement for . :ablobcatbongo:

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

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:

  • You can prepare to move your old account to Hollo by adding aliases (setting alsoKnownAs).
  • You can start to move your Hollo account to new one by setting 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.

Hollo's new migration panel.
Hollo's new migration panel.
@everclear@hollo.ingyeo.net's avatar
@[email protected]

@[email protected] · Reply to @[email protected]'s post

방화벽 문제인가...

@everclear@hollo.ingyeo.net's avatar
@[email protected]

@[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:'s avatar
Hollo :hollo:

@[email protected]

now supports Atom syndication feed, i.e., RSS! :atom: Append /atom.xml to your profile link; for example, this account's feed is:

https://hollo.social/@hollo/atom.xml

@everclear@hollo.ingyeo.net's avatar
@[email protected]

@[email protected] · Reply to @[email protected]'s post

환경변수 그냥 세팅하고 돌리는...건가? 3000번 포트로 캐디 연결하면 될 것 같긴 한데..

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected] · Reply to Hollo :hollo:'s post

Previously implemented only -style extension APIs for emoji reactions, but now Hollo implements -style extension APIs for emoji reactions too. So you can use this feature with more client apps, e.g., .

https://github.com/dahlia/hollo/issues/36#issuecomment-2423548150

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

now gives you accurate usage statistics from .

The NodeInfo JSON tree from hollo.social.
The NodeInfo JSON tree from hollo.social.
洪 民憙 (Hong Minhee)'s avatar
洪 民憙 (Hong Minhee)

@[email protected]

I've only been on Fosstodon for a few months, but I plan to move my account over to later this year for dogfooding. Not right now, though.

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Now you can upload videos on !

A demo video of uploading a video on Hollo.
A demo video of uploading a video on Hollo.
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

now lets you block other accounts!

Blocking someone on Hollo using Phanpy.
Blocking someone on Hollo using Phanpy.
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

now has per-account muting! Plus, you can set the duration as well.

How you can mute an account for 30 minutes using Phanpy.
How you can mute an account for 30 minutes using Phanpy.
洪 民憙 (Hong Minhee)'s avatar
洪 民憙 (Hong Minhee)

@[email protected]

유저 그룹 서버를 열었습니다!

discord.gg/nkBTdeHsU8

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

We now have and 's official server! Join us now!

https://discord.gg/hGXXxUq2jK

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

@[email protected]

We now have and 's official server! Join us now!

https://discord.gg/bhtwpzURwd

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

We now have a Matrix room for users: #hollo-users:matrix.org. Join us now!

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

now lets you leave emoji reactions!

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

now allows you to write custom emojis! :hollo: :fedify: :fediverse:

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

@[email protected]

Even though I am a slow coder, it only took me about a month to create most of 's features in . Having a framework makes a huge difference in productivity.

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

@[email protected]

According to the Activity Vocabulary specification, the summary property should be HTML encoded, but is putting plain text in the summary property. is putting in the summary, but should I change Hollo's behavior? :blobcatthink:

w3.org/TR/activitystreams-voca

The Activity Vocabulary specification says that the summary property is “a natural language summarization of the object encoded as HTML.”
The Activity Vocabulary specification says that the summary property is “a natural language summarization of the object encoded as HTML.”
Fedify: an ActivityPub server framework's avatar
Fedify: an ActivityPub server framework

@[email protected]

10月26日(土)に開催されるOSC 2024 Tokyo/FallにFedify/Hollo合同で出展します!可愛いFedifyのロゴのシールと『自分だけのフェディバースのマイクロブログを作ろう!』日本語版の紙の本を持って行く予定です。よろしくお願いします。

https://event.ospn.jp/osc2024-fall/

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Want to run your own personal server, but don't have the server specs to install Mastodon? Try , a lightweight personal ActivityPub server!

https://docs.hollo.social/

fediverseobserver's avatar
fediverseobserver

@[email protected]

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 servers found:

thanetviews.com a server from United Kingdom
cuteenby.gay a server from Germany
filledblanks.com a server from United States
anchasalamedas.org a server from United States
social.frederico.me a server from United States
msk.kitamiss.com a server from Private
nyansukey.net a server from Private
toot.it.com a server from United States
social.ainmosni.eu a server from Germany
hcs-miskey.skycat.io a server from Private
misskey.rockcutter.jp a server from Japan
karibu.social a server from Private
italianchoco.com a server from United States
thearkproject.llc a server from United States
blackevil.net a server from Germany
pixelone.org a server from Private
armpit.space a server from United States
social.iceflower.io a server from France
xcornman.com a server from United States
eat.bakedbea.nz a server from Private
misskey.hotserver.meme a server from Australia
social.brendans-bits.com a server from Australia
hollo.esurio1673.net a server from Private

Help others find a home, send them to fediverse.observer

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

You can now see in (but you can't leave emoji reactions yet). We've implemented the FEP-c0e0 spec and tested it on , , and .

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Fixed a bug that caused attached to posts on to be treated as regular links in and other !

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected] · Reply to Hollo :hollo:'s post

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 :hollo:'s avatar
Hollo :hollo:

@[email protected]

now can work without . It uses Redis as a cache and queue backend if the REDIS_URL environment variable is provided, but if not given, it caches in memory and works without a queue. This is an option to consider if you have a few following/followers.

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

now implements FEP-e232 as well for incoming and outgoing activities!

https://hollo.social/@hollo/0191d68a-3ba7-7f2f-9836-fe8664fb51b0

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

finally has /-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 , you can use the Quote button that appears when you press the boost icon!

https://hollo.social/@fedify/0191d67c-a300-786e-8395-2020ac47ebc7

The menu that appears when you press the boost icon in Phanpy. The menu items are Boost and Quote.
The menu that appears when you press the boost icon in Phanpy. The menu items are Boost and Quote.
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

now has its own website with docs.

https://docs.hollo.social/

洪 民憙(ホン・ミンヒ)'s avatar
洪 民憙(ホン・ミンヒ)

@[email protected]

HolloについにMisskey/Threads風の引用機能が追加されました!使い方は簡単です。引用する投稿のリンクを投稿内容に貼り付けてください!ActivityPubの投稿(Article、Note、そしてQuestionに対応)のリンクを自動で認識して引用に変えてくれます。

ちなみに、Phanpyを使う場合は、ブーストアイコンを押すと出てくるQuoteボタンを使ってください。


QT: hollo.social/@hollo/0191d68a-3
[参照]

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

finally has /-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 , you can use the Quote button that appears when you press the boost icon!

https://hollo.social/@fedify/0191d67c-a300-786e-8395-2020ac47ebc7

The menu that appears when you press the boost icon in Phanpy. The menu items are Boost and Quote.
The menu that appears when you press the boost icon in Phanpy. The menu items are Boost and Quote.
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

finally has /-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 , you can use the Quote button that appears when you press the boost icon!

https://hollo.social/@fedify/0191d67c-a300-786e-8395-2020ac47ebc7

The menu that appears when you press the boost icon in Phanpy. The menu items are Boost and Quote.
The menu that appears when you press the boost icon in Phanpy. The menu items are Boost and Quote.
Pierre's avatar
Pierre

@[email protected]

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

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
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
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Since no more depends on , 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 , here's instructions to remove it:

  1. Sign in to your Railway dashboard.
  2. In the Hollo service → Variables, remove MEILI_URL and MEILI_MASTER_KEY environment variables.
  3. Redeploy the Hollo service (see also the attached screenshot).
  4. Delete the service by pressing the red button in the Meilisearch service → SettingsDelete Service.

That's all!

How to redeploy the Hollo service in the Railway dashboard.
How to redeploy the Hollo service in the Railway dashboard.
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Today, held an offline in , and received several improvement patches:

Thanks again to our contributors!

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

For your information, currently the most compatible client with is @phanpy. Check it out!

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Hollo를 소개합니다!

Hollo는 개인을 위한 연합형 마이크로블로그 소프트웨어입니다. FedifyBun으로 만들어졌으며, 프로토콜을 통해 다른 인스턴스 및 서비스와 교류할 수 있습니다.

Hollo의 특징은 한 사용자를 위해 설계된 전용 인스턴스라는 점입니다. 이를 통해 사용자는 자신만의 공간을 가지면서도 , 및 기타 ActivityPub 지원 서비스의 사용자들과 소통할 수 있습니다.

독자적인 웹 인터페이스는 없지만, Mastodon API와 호환되어 기존의 많은 Mastodon 클라이언트 앱을 사용하여 Hollo에 접근할 수 있습니다. 이로 인해 익숙한 인터페이스로 Hollo를 이용할 수 있습니다.

주요 기능으로는 게시물 작성·편집·삭제, 답글, 미디어 첨부, 투표, 좋아요, 북마크, 고정 등이 있습니다. 또한 프로필 편집, 팔로우/팔로워 관리, 리스트 생성 등도 가능합니다. 더불어 Markdown을 지원하여 게시물이나 프로필의 서식 설정을 쉽게 할 수 있습니다.

Hollo는 현재 개발 초기 단계에 있으며, 지속적으로 기능 추가와 개선이 이루어지고 있습니다. Bun을 사용함으로써 빠른 성능과 효율적인 개발이 이뤄지고 있답니다. 오픈 소스 프로젝트로 GitHub에 공개되어 있으며, 커뮤니티의 기여를 환영합니다.

개인 블로그와 소셜 미디어의 장점을 결합한 Hollo는 프라이버시를 중시하면서도 더 넓은 커뮤니티와의 연결을 원하는 사람들에게 적합한 플랫폼으로 거듭나고 있습니다.

https://github.com/dahlia/hollo

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Holloを紹介します!

Holloは、個人向けの連合型マイクロブログソフトウェアです。FedifyBunを基盤に構築され、ActivityPubプロトコルを通じて他のインスタンスやサービスと連携することができます。

Holloの特徴は、一人のユーザーのために設計された専用のインスタンスという点です。これにより、ユーザーは自分だけのスペースを持ちながら、Mastodon、Misskey、その他のActivityPub対応サービスのユーザーとも交流できます。

独自のウェブインターフェースを持たない代わりに、MastodonのAPIと互換性があるため、既存の多くのMastodonクライアントアプリを使用してHolloにアクセスできます。これにより、使い慣れたインターフェースでHolloを利用することができます。

主な機能には、投稿の作成・編集・削除、返信、メディア添付、投票、お気に入り、ブックマーク、ピン留めなどがあります。また、プロフィール編集、フォロー/フォロワー管理、リスト作成なども可能です。さらに、Markdownをサポートしているため、投稿やプロフィールの書式設定が容易に行えます。

Holloは現在開発の初期段階にあり、継続的に機能の追加や改善が行われています。Bunを使用することで、高速なパフォーマンスと効率的な開発が実現されています。オープンソースプロジェクトとして、GitHubで公開されており、コミュニティからの貢献を歓迎しています。

個人のブログとソーシャルメディアの利点を組み合わせたHolloは、プライバシーを重視しながら、より広いコミュニティとのつながりを求める人々に適したプラットフォームとなっています。

https://github.com/dahlia/hollo

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

@[email protected] · Reply to 洪 民憙 (Hong Minhee)'s post

Trying out .ai as a web designer… Here's what it designed, which is a website. Does it look fine?

A prototype design of the Hollo website, designed by Claude.ai.
A prototype design of the Hollo website, designed by Claude.ai.
洪 民憙 (Hong Minhee)'s avatar
洪 民憙 (Hong Minhee)

@[email protected]

この記事を読むと、自分もHolloでBunの代わりにNode.jsを使うべきなのかなーと。

gihyo.jp/article/2024/08/missk

.js

fedicat's avatar
fedicat

@[email protected]

enabled instance v2 view on

an instance summary view

Detected text:

12:24< Backhollo.socialhollo.socialloginA Hollo instance at hollo.socialRegistrationSoftwareHollo0.1.0-dev.58https://github.com/dahlia/holloPrimary languagesEnglish KoreanSummaryLimits
an instance summary view Detected text: 12:24< Backhollo.socialhollo.socialloginA Hollo instance at hollo.socialRegistrationSoftwareHollo0.1.0-dev.58https://github.com/dahlia/holloPrimary languagesEnglish KoreanSummaryLimits
an instance limits and media support view
an instance limits and media support view
wakest ⁂'s avatar
wakest ⁂

@[email protected] · Reply to wakest ⁂'s post

Added , , , , and icons to at fediverse.wake.st

Screenshot of Sublinks, Buttondown, ActivityPods, Hollo, Smilodon and Patchwork icons
Screenshot of Sublinks, Buttondown, ActivityPods, Hollo, Smilodon and Patchwork icons
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

finally has ! Polls can have up to 10 options. 😎

OptionVoters
Just now?1 (5%)
Finally!4 (20%)
Awesome!15 (75%)
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

now supports lists!

Augusto Campos's avatar
Augusto Campos

@[email protected]

A galera que gosta de self-host, ter sua própria instância etc. com alternativas exóticas pode ficar atenta ao : github.com/dahlia/hollo

hollo.social/@hollo/01904586-7

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

The latest (@phanpy) now shows the preview of a permalink to a post!

https://github.com/cheeaun/phanpy/commit/a72400febf62e34e0aaaeef86ae64ed6e373d492

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

To users: please update your to 0.1.0-dev.46, a patch which addresses @fedify's CVE-2024-39687, as soon as possible!

https://hollo.social/@fedify/019080c7-c784-755d-a6f2-d1f91f2c5709

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

is using this @fedify/redis package for caching and queuing. Battle tested!

https://hollo.social/@fedify/01905e6b-deec-785a-9bda-b72883031f8f

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

@[email protected] · Reply to 洪 民憙 (Hong Minhee)'s post

As it turns out, the issue was neither on 's end nor 's end. It was a issue that I discovered during Hollo development, and anyway it's now fixed!

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

@[email protected]

now has the official account! Please follow @fedify!

hollo.social/@fedify/01905d6a-

technicat's avatar
technicat

@[email protected] · Reply to joschi's post

@joschi Besides , also check out

mitra.social/

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Good news: finally supports featured tags!

Bad news: There is no client app that supports featured tags.

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

@[email protected]

development is often motivation to add features to , for example, most of the commits I added to Fedify today were for Hollo.

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

now lets you pin your posts to the top of your profile!

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

@[email protected]

If you'd like to support the development of or , you can sponsor me on GitHub!

github.com/sponsors/dahlia

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

@[email protected]

I usually prefer to Node.js, but while working on , I tried and I found it quite good.

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected] · Reply to Hollo :hollo:'s post

You can get started with your own Hollo in just a few clicks with the official template for :

https://railway.app/template/eopPyH?referralCode=qeEK5G

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Introducing . Hollo is an -enabled single-user microblogging software. Although it's for a single user, it also supports creating and running multiple accounts for different topics.

It's headless, meaning you can use existing client apps instead, with its Mastodon-compatible APIs. It has most feature parity with Mastodon. Two big differences with Mastodon is that you can use in the content of your posts and you can quote another post.

Oh, and Hollo is built using and .

https://github.com/dahlia/hollo

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected] · Reply to Hollo :hollo:'s post

's search is implemented internally using .

Hollo's architectural blueprint. Hollo relies on PostgreSQL, Redis, and Meilisearch.
Hollo's architectural blueprint. Hollo relies on PostgreSQL, Redis, and Meilisearch.
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

finally has a search feature!

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

's compatibility with is much improved now! Not only with Threads, its compatibility with any instances that enabled secure mode (i.e., requires authorized fetch) is improved too.

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

The name is a Korean word 홀로, which means alone or solitary. It is named so because it is designed to be a single-user software.

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Improved compatibility with in ! Fixed issues where post contents were invisible and hashtags were rendered as regular links.

technicat's avatar
technicat

@[email protected]

planning ahead, adding support in for

screenshot of a Hollow instance description 

Detected text:

11:57< Backhollo.socialhollo.socialloginA Hollo instance at hollo.socialActivityTimelineRegistrationRegistrations unavailableInvites not enabledSoftwareHollo0.1.0-dev.11Primary languagesEnglishContactHolloSummaryLimitsNodeInfo
screenshot of a Hollow instance description Detected text: 11:57< Backhollo.socialhollo.socialloginA Hollo instance at hollo.socialActivityTimelineRegistrationRegistrations unavailableInvites not enabledSoftwareHollo0.1.0-dev.11Primary languagesEnglishContactHolloSummaryLimitsNodeInfo
Pierre's avatar
Pierre

@[email protected]

Federated single user microblogging software through activitypub that is also compatible with mitra

Interact with users on Mastodon, Pixelfed, Misskey, etc

Github repo here: github.com/dahlia/hollo

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
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 :hollo:'s avatar
Hollo :hollo:

@[email protected]

Although is a single-user microblogging software, you can manage multiple accounts with a single sign-on. Create and run multiple accounts for different topics!

洪 民憙 (Hong Minhee) 🤏🏼's avatar
洪 民憙 (Hong Minhee) 🤏🏼

@[email protected]

now supports sharing posts (reblogs)!

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Currently, hollo.social is deployed on . After we have some operational experience, we will publish the official template for Railway!

洪 民憙 (Hong Minhee) 🤏🏼's avatar
洪 民憙 (Hong Minhee) 🤏🏼

@[email protected] · Reply to 洪 民憙 (Hong Minhee) 🤏🏼's post

I created an official account of : @hollo. Please follow this if you're interested in Hollo!

洪 民憙 (Hong Minhee) 🤏🏼's avatar
洪 民憙 (Hong Minhee) 🤏🏼

@[email protected] · Reply to 洪 民憙 (Hong Minhee) 🤏🏼's post

Here's the source code in progress:

github.com/dahlia/hollo

洪 民憙 (Hong Minhee) 🤏🏼's avatar
洪 民憙 (Hong Minhee) 🤏🏼

@[email protected] · Reply to 洪 民憙 (Hong Minhee) 🤏🏼's post

Now has several more features:

• Following/unfollowing accounts
• Following/unfollowing hashtags
• Post visibility
• Post language
• Editing profile
• Mentions
• Likes
• Bookmarks
• Notifications
• Markers

洪 民憙 (Hong Minhee) 🤏🏼's avatar
洪 民憙 (Hong Minhee) 🤏🏼

@[email protected]

I'm rebuilding from scratch, and I've implemented some -compatible APIs to let me do the following actions with and now:

• Logging in
• Composing a post
• Writing a reply
• View posts
• Public timeline
• Home timeline

✌️