#hollo ......如果用过 #botkit ,那差不多就相当于用过hollo了 (
虽然也是和 #gotosocial 一样的“单”用户实例;
但是gotosocial,只是推荐单用户;
而hollo,应该是一个管理员,可以创建多个账户,比如这个@[email protected] ,还可以创建 @[email protected]
创建多账户上这一点要比botkit更好?botkit是一域名一机器人的,就像 @mybot@drawbot
Gotosocial还是要比Hollo完善许多,Gotosocial在功能上不比mastodon差多少,hollo就算了
总的来说吧,单用户不推荐自托管 #fedify-dev/hollo,如果想搭建机器人,可以用fedify-dev/botkit

介绍 #Hollo。Hollo 是一款支持 #ActivityPub 的单用户微型博客软件。虽然它只针对单一用户,但它也支持为不同主题创建和运行多个账户。
它是无头的,意味着你可以使用现有的 #Mastodon 客户端应用,配合其兼容 Mastodon 的 API。它与猛犸象在特征上几乎相当。Mastodon 的两个大区别是你可以在帖子内容中使用 #Markdown,并且可以引用其他帖子。
哦,Hollo 是用 #Bun 和 #Fedify 构建的。
https://github.com/dahlia/hollo
#fedidev

这里也确实提到了“虽然它只针对单一用户,但它也支持为不同主题创建和运行多个账户”
hollo最近发了一个投票:

Hollo 一直都是无头的——没有内置前端,只有一个兼容 Mastodon 的 API。你自己选客户。这正是重点。
但我们一直在想:如果 Hollo 发布自己的网页前端会怎样?Mastodon 兼容的 API 会保留,所以你当前的客户端设置不会改变。这只是多了一个选择。
你会用吗?

你要我怎么夸你呢?占用1.4GB内存......还是“创建 #fediverse 账户变得非常简单低成本吗?”

Links:
https://hollo.social/@hollo
https://github.com/fedify-dev/botkit
https://github.com/fedify-dev/hollo
https://fedihollo.org/@admin

抱歉hollo的开发者们

RE: https://fedihollo.org/@admin/019d3008-b3ec-7869-9a15-71eb70de9ffd

@COSCUP にて「FediDevKR & FediLUG (Japan)」でブースを出展についても採択されました! ​
東アジアのFediverseの発信地・交流の場として準備を進めています!!
日本のFediLUGからはノベルティ配布などの企画を考えています!詳細情報をお楽しみに!!
https://blog.coscup.org/2026/03/coscup-x-ubucon-asia-2026-first-wave-of.html
#Fediverse #SocialWeb #COSCUP #ActivityPub #fedidev
COSCUP x UbuCon Asia 2026 首波社群攤位名單公布 First wave of accepted community booth

無論您是開放原始碼的開發者、推廣者、使用者,都歡迎您來參加 COSCUP「開源人年會」

2026年8月8–9日台湾・台北にて開催される @COSCUP にて、 #FediDevKR#FediLUG が主催する「Fediverse & Social Web」トラックが採択されました!#フェディバース、#ActivityPub 、オープンなソーシャルウェブをテーマに、丸一日・計6時間のトラックを予定しています。

発表者向けのCFP(申し込み)はまだ始まっていませんが、公開され次第お知らせします!

#Fediverse #SocialWeb #COSCUP #ActivityPub #fedidev

@COSCUP 2026(台北、8月8–9日)にて、Fediverse & Social Webトラックが採択されました!#フェディバース#ActivityPub、オープンなソーシャルウェブをテーマに、丸一日・計6時間のトラックを予定しています。

発表者向けのCFPはまだ始まっていませんが、公開され次第お知らせします。お楽しみに!

#Fediverse #SocialWeb #COSCUP #ActivityPub #fedidev

@COSCUP 2026(臺北(타이베이), 8月(월) 8–9日(일))에서 저희 Fediverse & Social Web 트랙이 承認(승인)되었습니다! #聯合宇宙(연합우주), #ActivityPub, 오픈 소셜 웹을 主題(주제)로 하루 終日(종일), 總(총) 6時間(시간)을 進行(진행)할 豫定(예정)입니다.

發表者(발표자) 募集(모집) CFP는 아직 열리지 않았지만, 始作(시작)되는 대로 바로 公知(공지)하겠습니다. 期待(기대)해 주세요!

#페디버스 #연합우주 #SocialWeb #COSCUP #fedidev

Our Fediverse & Social Web track has been accepted for @COSCUP 2026 (Taipei, Aug 8–9)! We'll have a full day—six hours—to fill with talks on the #fediverse, #ActivityPub, and the open social web.

The CFP for speakers isn't open yet, but we'll announce it here when it is. Stay tuned!

#SocialWeb #COSCUP #fedidev

@sindum Thanks for taking the initiative to create a focused and simple solution for groups in the fediverse. Looks good, too!
Once you have a prototype you're happy with, what's the plan forward? Will you still use AI for development? Will you keep the current codebase, or start from scratch?

#fedibook #fedidev

Cursor just launched Composer 2, a purpose-built coding model that outperforms Claude Opus 4.6 on CursorBench and dramatically undercuts rivals on price, with input starting at $0.50 per million tokens. I unpack the benchmarks, pricing table, and market context (OpenAI, Anthropic, Google, GitHub Copilot) in my latest TechGlimmer deep dive: https://techglimmer.io/what-is-cursor-composer-2/
#Cursor #AI #FediDev #DeveloperTools #OpenSource #Coding #Anthropic #OpenAI
Cursor's Composer 2 Is the Cheapest Frontier Coding Model Yet

Cursor's Composer 2 beats Claude Opus 4.6 on benchmarks and costs just $0.50 per 1M tokens. Here's what developers need to know before switching.

techglimmer.io

So, an interesting issue came up in the #Fedify repo that I've been thinking about: #629.

You know how every #fediverse server uses schema:PropertyValue in actor attachment for profile metadata fields (like “Website”, “GitHub”, etc.)? Turns out, strict #AS2 validators like browser.pub reject it, because the AS2 spec says attachment should only contain Object or Link—and PropertyValue is a schema.org type, not an Activity Streams 2.0 type.

The thing is, we can't just drop the type like we did with Endpoints (#576), because Mastodon and others rely on seeing "type": "PropertyValue" to render profile fields. But at the same time, it's technically not spec-compliant.

I'm leaning towards writing a #FEP to formalize this existing practice rather than trying to invent a new type (like toot:PropertyValue extending Object), which would be a nightmare to migrate across the whole fediverse.

What do you all think? Has anyone else run into this? Would love to hear thoughts from implementers and spec folks.

#fedidev #ActivityPub #ActivityStreams #ActivityStreams2 #AS2 #PropertyValue

PropertyValue attachments serialize with invalid type for AS2 Object/Link validation · Issue #629 · fedify-dev/fedify

Description When Fedify serializes actor attachment properties containing PropertyValue items (used by Mastodon for profile metadata fields), the resulting JSON-LD uses schema:PropertyValue as the ...

GitHub

7/

Continuing to look for an alternative to "attachment" (for properly supporting an Actor specifying a list of CALL Service actors associated with it) —

Maybe a call specific custom top-level attribute would be useful.

Maybe something like:

"call": [
{
"rel":"callpub",
"href":"https://videocalls.example/users/joeblow"
}
]

Or even:

"call": [
"href":"https://videocalls.example/users/joeblow"
]

.

#ActivityPub #ActivityStreams #AudioCall #Call #FediDev #Fediverse #VideoCall