Came across [this thoughtful post](https://socialbc.ca/@rainer/114536463416519694) on the fediverse about the need for ActivityPub-based platforms for public institutions. This resonates deeply for South Korea too. 🇰🇷 Our public services shouldn't depend on centralized platforms like Naver, Kakao, or Instagram for critical communications. Projects like @npub1tlfg...wz08 and @npub1sqlc...0z0c could enable our government agencies to build ActivityPub-native services with minimal effort—imagine following <ruby lang="ko">災難安全文字<rp>(</rp><rt>재난안전문자</rt><rp>)</rp></ruby> (emergency alerts) or local traffic updates directly in your fediverse timeline! Not just convenient, but a matter of information sovereignty. What government communications would you want to follow in the fediverse? View quoted note →
Just received word that @npub1tlfg...wz08 wasn't selected for @NLnet'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