洪 民憙 (Hong Minhee)

Cool to see Fedify, Mitra and the FEP processes get some time on stage at the Open Social track at #DwebCamp from Sefano and Zach

After months of behind-the-scenes preparation, we’re excited to finally share the complete conference schedule with everyone. Check out the sessions and start planning your very own COSCUP journey!

https://s.coscup.org/sessions

@evan Yeah, I already follow @pfefferle! He's doing some interesting C2S work on the WordPress ActivityPub plugin. I should reach out and compare notes.

@dahukanna Ah, I see the confusion. I meant “put” in a conceptual sense: whether the Mastodon API has a concept that corresponds to a given feature. Not about storage or persistence at all.

@fedicat Yeah, the quote post collision was a clear example. Whether it's deliberate or just indifference, the Mastodon team doesn't seem to treat the API as a shared surface that evolves across implementations. Hard to build on top of that.

@fedicat That's fair. I know other platforms extend the Mastodon API, but I've been reluctant to do the same. It doesn't feel like a surface that's meant to be extended, and I'd rather not pile more non-standard behavior on top of an API that's already a moving target.

@dahukanna I'm not sure I'm following the storage question. Could you say more about what you mean by runtime data here?

On the second point: the Mastodon API and ActivityPub are completely different in design. They're separate specifications: the Mastodon API is a REST API, ActivityPub is an entirely different protocol. The two look nothing alike, so I'm not sure what “Mastodon instance API that implements ActivityPub” refers to.

@django That would be great. A themeable C2S PWA that Hollo could reuse as its own frontend is exactly the kind of thing I've been hoping for. Looking forward to it.

@mariusor Looks interesting, a CLI C2S client could be really handy for testing. I'll check it out, thanks!

@evan Yeah, exactly. I'm thinking Hollo's own frontend could use the ActivityPub API internally.

The more I work on Hollo, the more its Mastodon-compatible API feels like a straitjacket. I chose it for a practical reason: people could use existing clients, and I wouldn't have to build a frontend too. I still think that was the right call at the time.

The problem is that clients can only expose what Mastodon's API represents. I keep coming up with ideas, then asking whether the API has anywhere to put them. If it doesn't, I have no way to get the feature in front of users.

ActivityPub API (so-called “C2S”) might be the eventual answer, but it doesn't help much today. I don't know of any clients Hollo users could realistically use with it, and adoption is still limited.

So I keep coming back to the idea that Hollo will need a frontend of its own. I'd keep the Mastodon API for existing apps. I'm not especially eager to take on a whole frontend, but I don't see another way to try ideas that don't fit Mastodon's model.

Hello World

Coucou! This is just a first post announcing Nuages to the world.

Nuages is an ActivityPub app, connecting to your favourite servers that support the Client to Server API.

Follow us to get our latest updates, we’ll be officially launching the app in the coming weeks 😉

#ActivityPub #c2s #ActivityPubAPI #Fediverse

Announcing it here publicly for the first time!

I've been building a general purpose activitypub pwa.

Follow @nuages for official updates!

#activityPubAPI #ActivityPub

I recently moved my personal blog from a PHP setup to Astro on Netlify because I wanted to add ActivityPub support with Fedify.

Somehow, it took me until then to realize that I had never actually tried running Fedify on Netlify.

Netlify Database is PostgreSQL, so the persistence side should already fit @fedify/postgres. The less obvious part is background delivery: Netlify Functions cannot keep a queue consumer alive, while Async Workloads uses a push-based model similar to WorkersMessageQueue in @fedify/cfworkers.

So I’m going to try making @fedify/netlify, with my own blog as its first real test case. I wrote down the initial design in issue #930.

🎉 COSCUP x UbuCon Asia 2026 Welcome Party is ON!

Our favorite pre-con warmup is back ✨ No presentation pressure, just a super chill gathering.

First-timer or old friend, come hang out, catch up, and share what cool projects you’ve been hacking on lately! 💬

📅 Fri, Aug 7 | 18:15–21:30
📍 Cosmos Bistro (Hua Shan Din)
🎟️ Pass: https://s.coscup.org/welcomeparty

💡 Free to drop in, no pre-registration required! Grab a pass to support the community and make it an amazing night ✨

@smallcircles Fair, and I'll be honest, I haven't read the linked post yet, it's a long one and I want to give it a proper read rather than skim it.

I'd like to be more involved in the standardization side of this too. Language is a real hurdle for me there, participating in that kind of discussion in a second language is harder than it looks, so bear with me if I'm slower to engage than I'd like. That said, writing this case up as a FEP seems worth trying, and I might take a shot at it.

#Mastodon's #ActivityPub inbox treats object types in tiers. Note and Question are supported directly. A second tier, Article, Page, Image, Audio, Video, and Event, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as Note regardless of what the object actually is.

mastodon/mastodon#24079 asks for content to show up whenever it's present and the mediaType is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

Updates on my website

• Added art works and status updates on OSS projects.

ZennにBotKitを使ってフェディバースのRSSボットを作成するチュートリアルが公開されました。DenoとNode.jsの両方に対応しており、動的にRSSフィードを追加するところまで実装しています。ActivityPubの開発を全く知らない方でも簡単に進められるように書きましたので、ぜひ一度ご覧ください！

A tutorial on building a fediverse RSS bot is now up on the BotKit website. It supports both Deno and Node.js, and even covers how to dynamically add RSS feeds. It's designed to be easy to follow even if you have zero experience with ActivityPub development, so be sure to check it out!

Having some nice ActivityPub design/implementation conversations with @hongminhee in the @fedify Matrix chat at #fedify:matrix.org

And if it sometimes boils down to an exchange of 😮‍💨 and 😞, then maybe that's what we need that day, and 💪 can be for tomorrow.

As an example, I've already put together a curated list for Django developers(https://social.silicon.moe/collections/116839954192203195), as well as a broader one for general developers (https://social.silicon.moe/collections/116837709178617613) (including the Lobsters account)

I'd love to see a coordinated campaign across some of the more active instances — recommending well-known and influential accounts to follow. I'm especially trying to curate lists for Fosstodon and Hachyderm, but doing this alone is tough. Would anyone be interested in collaborating?

Mastodon 4.6 has just been released, introducing a new "Collections" feature. Like Bluesky's Starter Packs, this lets us curate and recommend accounts to newcomers on the fediverse, so they don't land on an empty, lifeless timeline when they first join.

Sometimes, while designing some hypothetical fediverse software, I run into this feeling

setting aside ActivityPub spec compatibility itself, there are these frustrating moments where I hit preconditions like 'this won't work because of which FEPs (e.g. Activity Intents) other fediverse software happens to support' and it just kills the momentum.

@bitbraindev They say they have their reasons.

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

Requested a #CVE ID through a #GitHub Security Advisory on June 27 and still nothing, almost two weeks now. GitHub's docs say it usually takes up to three days.

Anyone else seeing longer waits from the GitHub CNA lately, or is this just me? Curious whether it's a general slowdown or something specific to my request.

#FOSS #InfoSec #GHSA

@Profpatsch Oh, the quote seems still pending. I'm quoting it: https://tldr.nettime.org/@tante/116880003584050912.

BotKit: Standalone ActivityPub bots in TypeScript by @hongminhee https://lobste.rs/s/tbs5t3 #javascript #web
https://botkit.fedify.dev/