Just received word that @npub1tlfg...wz08 wasn't selected for @npub1n8y6...l96n's Open Call this round. While disappointing, I understand the competition was fierce with many worthy projects seeking limited funding. The journey continues though—#Fedify development will move forward at its own pace. Thanks to everyone who's shown interest and support for this project so far. Building tools for the #fediverse remains important work, and I'm committed to seeing it through. If you know of other funding opportunities that might be a good fit for open source #ActivityPub tools, I'm all ears.

I've been reflecting lately on projects like @npub1tlfg...wz08, @npub1mz3d...tpw7, and @botkit@hollo.social. Sometimes I wonder if I'm solving problems that very few people actually need solved. How many developers truly want to build their own #ActivityPub server from scratch? It feels a bit like inventing shoes that let people walk on their hands all day. Would there be a viable market? How many would actually buy them? That's the sense I get with these projects. They do have users who find them tremendously valuable, but the total user base is inherently limited. The tools serve an important function for a small audience of specialized developers. There are moments when my motivation wavers. When the user community consists of just a handful of enthusiastic supporters, it's sometimes difficult to maintain momentum and justify the ongoing investment of time and energy. And yet, there's something meaningful about creating specialized tools that solve complex problems well, even if they're only used by a few. Perhaps that's enough. #fedidev

Hello @npub1u84d...s78a, I wanted to share some feedback on the documentation provided in the [*Highlighting Journalism on Mastodon*](

Mastodon Blog

Highlighting journalism on Mastodon

Today we

) blog post. Specifically, in [*The technical*](

Mastodon Blog

Highlighting journalism on Mastodon

Today we

) section, the example code for the `fediverse:creator` meta tag is given as: ``` <meta name="fediverse:creator" content="@npub1vl7j...f6g0" /> ``` Based on my testing (and that of others), Mastodon doesn't seem to recognize the creator link correctly when the leading `@` is present in the `content` attribute. It only works when the `@` is removed, like this: ``` <meta name="fediverse:creator" content="Gargron@mastodon.social" /> ``` Following the blog's example directly led to some wasted time figuring out why it wasn't working. It would be great if either the example in the blog post could be corrected to reflect the current requirement, or if Mastodon's parser could be made more flexible to accept the handle with or without the leading `@`. Appreciate all you do for #Mastodon! #fedidev #fediverse

I talked about #ActivityPub and #Fedify on @npub10rc3...elu9's wonderful podcast, [Software Sessions]. I'm embarrassed by my poor English, but if you're interested, please listen!

Software Sessions

Hong Minhee on ActivityPub

Use cases and implementation

[Software Sessions]:

Software Sessions

Software Sessions

Practical Conversations about Software Development

Not a Cult

Jeremy (@guu@notacult.social)

I spoke with @hongminhee@hollo.social about ActivityPub, the Fediverse, and his experience implementing the specification! https://www.softwareses...

View quoted note →

Hello, I'm an open source software engineer in my late 30s living in #Seoul, #Korea, and an avid advocate of #FLOSS and the #fediverse. I'm the creator of @npub1tlfg...wz08, an #ActivityPub server framework in #TypeScript, @npub1mz3d...tpw7, an ActivityPub-enabled microblogging software for single users, and @npub1sqlc...0z0c, a simple ActivityPub bot framework. I'm also very interested in East Asian languages (so-called #CJK) and #Unicode. Feel free to talk to me in #English, #Korean (#한국어), or #Japanese (#日本語), or even in Literary Chinese (#文言文, #漢文)! #introduction

I hope @phanpy@hachyderm.io allows me to choose alternative translation services like DeepL.

@npub1z2ke...7409 Currently, #BotKit supports the following 7 types of event handlers (see attached image): - `onFollow` - `onUnfollow` - `onAcceptFollow` - `onRejectFollow` - `onMention` - `onReply` - `onMessage` What else can you think of as event handlers?

If you'd like to support the development of @npub1tlfg...wz08 or @npub1mz3d...tpw7 or @npub1sqlc...0z0c, you can sponsor me on GitHub!

GitHub

Sponsor @dahlia on GitHub Sponsors

I usually write open source software libraries and small CLI programs, which means their consumers are mostly software engineers. My interests are:...

#ActivityPub #fedidev #Fedify #Hollo #BotKit #sponsor