Mastodon

ActivityPub for WordPressHTTP Signature Upgrades Coming Soon Ever wonder how your site proves it’s really you talking to the rest of the Fediverse? It’s not magic—it’s HTTP signatures, the digital equivalent of a secret handshake. With our next release, we’re making that handshake a lot more universal (and a little less awkward). Why HTTP Signatures Matter When you interact with the Fediverse, you want to know that the messages you send and receive are genuine. HTTP signatures are the technology that makes this possible. Every time your […] <a href="https://activitypub.blog/2025/07/03/http-signature-upgrades-coming-soon/" rel="nofollow noopener" translate="no" target="_blank">https://activitypub.blog/2025/07/03/http-signature-upgrades-coming-soon/</a>

ForgejoThe <a href="https://floss.social/tags/Forgejo" class="mention hashtag" rel="nofollow noopener" target="_blank">#Forgejo</a> monthly report was published ✨Forgejo v12.0 branch was cut on 25 June, for a planned release on 17 July. Forgejo v11.0.2 was released on 18 June, addressing several bugs. Forgejo Runner v6.4.0 introduced offline caching support.The minimum required Git version has been bumped and the search has been improved.There is strong enthusiasm for translating Forgejo.User following with <a href="https://floss.social/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener" target="_blank">#ActivityPub</a> has progressed and a new <a href="https://floss.social/tags/NLnet" class="mention hashtag" rel="nofollow noopener" target="_blank">#NLnet</a> grant has been accepted.<a href="https://forgejo.org/2025-06-monthly-report" rel="nofollow noopener" translate="no" target="_blank">https://forgejo.org/2025-06-monthly-report</a>

ActivityPub for WordPressWhat we shipped so far in 2025 Alongside our upcoming plans, we’ve already shipped several important features in recent releases. Here are some highlights of what’s now available in the ActivityPub plugin. Onboarding We’ve added an onboarding flow after plugin activation to help guide new users through key decisions — such as selecting the Actor Mode. It’s also a great opportunity to explain Fediverse concepts for users who are new to them. More details: 👉 5.9.0 — Easier onboarding for your Fediverse […] <a href="https://activitypub.blog/2025/06/24/what-we-shipped-so-far-in-2025/" rel="nofollow noopener" translate="no" target="_blank">https://activitypub.blog/2025/06/24/what-we-shipped-so-far-in-2025/</a>

洪民憙 (Hong Minhee)ActivityPubサーバーを構築してみたいけれど、どこから始めればよいかわからない方には、Fedifyのチュートリアル『<a href="https://zenn.dev/hongminhee/books/4a38b6358a027b" rel="nofollow noopener" target="_blank">自分だけのフェディバースのマイクロブログを作ろう！</a>』をおすすめします。包括的でステップバイステップのガイドで、完全に機能する連合型アプリケーションの構築方法を丁寧に解説しています。フェディバースに飛び込みたい開発者にぴったりです！<a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/ActivityPub" target="_blank">#ActivityPub</a> <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/Fedify" target="_blank">#Fedify</a> <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/%E3%83%81%E3%83%A5%E3%83%BC%E3%83%88%E3%83%AA%E3%82%A2%E3%83%AB" target="_blank">#チュートリアル</a> <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/%E3%83%95%E3%82%A7%E3%83%87%E3%82%A3%E3%83%90%E3%83%BC%E3%82%B9" target="_blank">#フェディバース</a> <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/fediverse" target="_blank">#fediverse</a>

洪民憙 (Hong Minhee)If you're interested in building your own <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/ActivityPub" target="_blank">#ActivityPub</a> server but don't know where to start, I recommend checking out <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/Fedify" target="_blank">#Fedify</a>'s <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/tutorial" target="_blank">#tutorial</a> <a href="https://fedify.dev/tutorial/microblog" rel="nofollow noopener" target="_blank">Creating your own federated microblog</a>. It provides a comprehensive, step-by-step guide that walks you through building a fully functional federated application. Perfect for developers who want to dive into the <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/fediverse" target="_blank">#fediverse</a>!<a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/fedidev" target="_blank">#fedidev</a>

洪民憙 (Hong Minhee)I've been thinking about client-server interactions in the <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/fediverse" target="_blank">#fediverse</a>. <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/ActivityPub" target="_blank">#ActivityPub</a> <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/C2S" target="_blank">#C2S</a> isn't widely used, and most clients rely on Mastodon-compatible APIs instead.What if we created a new standardized API based on <a href="https://graphql.org/" rel="nofollow noopener" target="_blank">GraphQL</a> + <a href="https://relay.dev/" rel="nofollow noopener" target="_blank">Relay</a> for client-server communication, while keeping ActivityPub for server-to-server federation?The Mastodon-compatible API lacks formal schema definitions for code generation and type checking, which hurts developer productivity. And ActivityPub C2S is honestly too cumbersome to use directly from client apps.<a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/GraphQL" target="_blank">#GraphQL</a> would give us type safety, efficient data fetching (only get what you need), and the ability to evolve the API without breaking clients. <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/Relay" target="_blank">#Relay</a>'s features for pagination, caching, and optimistic updates seem perfect for social apps.Would this be valuable to our community? What challenges do you see? How might we handle backward compatibility? And should this be formalized as an FEP?Curious what others think about this approach.<a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/fedidev" target="_blank">#fedidev</a>

Steve BateJust for fun... try this <a href="https://social.technoetic.com/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener" target="_blank">#ActivityPub</a> quiz to test your knowledge of the protocol.<a href="https://apquiz.stevebate.dev/" rel="nofollow noopener" translate="no" target="_blank">https://apquiz.stevebate.dev/</a>

The Real GrunfinkI'm glad to announce the release of version 2.76 of <a href="https://comam.es/snac?t=snac" class="mention hashtag" rel="nofollow noopener" target="_blank">#snac</a>, the simple, minimalistic <a href="https://comam.es/snac?t=activitypub" class="mention hashtag" rel="nofollow noopener" target="_blank">#ActivityPub</a> instance server written in C. It includes the following changes: Added Webmention support for links (Markdown-style or direct) written in a post. Added new command-line options for list maintenance. Display custom emoji in more places (contributed by dandelions). Mastodon API: fixed infinite scroll in many clients (thanks to cheeaun for giving me the clue), added <code>/api/v1/accounts/.../lists</code> endpoint (contributed by dandelions). Email notifications can now be sent via <code>libcurl</code> SMTP instead of spawning the <code>/usr/sbin/sendmail</code> program. To use this new feature, some additional server configuration is needed, see <code>snac(8)</code> (contributed by shtrophic). <a href="https://comam.es/what-is-snac" rel="nofollow noopener" target="_blank">https://comam.es/what-is-snac</a> If you find <a href="https://comam.es/snac?t=snac" class="mention hashtag" rel="nofollow noopener" target="_blank">#snac</a> useful, please consider <a href="https://ko-fi.com/grunfink" rel="nofollow noopener" target="_blank">buying grunfink a coffee</a> or contributing via <a href="https://liberapay.com/grunfink/" rel="nofollow noopener" target="_blank">LiberaPay</a>. <a href="https://comam.es/snac?t=snacannounces" class="mention hashtag" rel="nofollow noopener" target="_blank">#snacAnnounces</a>

Write.asJust rolled out some fediverse-related improvements:- Now you can follow Write.as blogs from Ghost! There was a tiny bug with this that we just fixed. (WriteFreely PR: <a href="https://writefreely.org/pull/1373" rel="nofollow noopener" translate="no" target="_blank">https://writefreely.org/pull/1373</a>)- We now support the `preview` property as a fallback for Articles. This will make your posts look much nicer as more platforms support it! (WriteFreely PR: <a href="https://writefreely.org/pull/1374" rel="nofollow noopener" translate="no" target="_blank">https://writefreely.org/pull/1374</a>)<a href="https://writing.exchange/tags/WriteAs" class="mention hashtag" rel="nofollow noopener" target="_blank">#WriteAs</a> <a href="https://writing.exchange/tags/WriteFreely" class="mention hashtag" rel="nofollow noopener" target="_blank">#WriteFreely</a> <a href="https://writing.exchange/tags/WriteFreelyDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#WriteFreelyDev</a> <a href="https://writing.exchange/tags/Ghost" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ghost</a> <a href="https://writing.exchange/tags/fediverse" class="mention hashtag" rel="nofollow noopener" target="_blank">#fediverse</a> <a href="https://writing.exchange/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener" target="_blank">#ActivityPub</a>

洪民憙 (Hong Minhee)As someone who has developed several <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/ActivityPub" target="_blank">#ActivityPub</a> software implementations (<a href="https://fedify.dev/" rel="nofollow noopener" target="_blank">Fedify</a>, <a href="https://docs.hollo.social/" rel="nofollow noopener" target="_blank">Hollo</a>, <a href="https://botkit.fedify.dev/" rel="nofollow noopener" target="_blank">BotKit</a>, and <a href="https://hackers.pub/" rel="nofollow noopener" target="_blank">Hackers' Pub</a>), I believe one of the most frustrating features to implement in the <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/fediverse" target="_blank">#fediverse</a> is <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/custom_emoji" target="_blank">#custom_emoji</a>.The challenges are numerous:First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.Perhaps most concerning is the poor <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/accessibility" target="_blank">#accessibility</a>. Most implementations simply use the emoji code (like <code>:party_blob:</code>) as the <code>alt</code> text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.<a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/fedidev" target="_blank">#fedidev</a>

洪民憙 (Hong Minhee)I've been wrestling with implementing <a class="mention hashtag" rel="nofollow noopener" href="https://hackers.pub/tags/multilingual" target="_blank">#multilingual</a> content support in <a href="https://hackers.pub/" rel="nofollow noopener" target="_blank">Hackers' Pub</a>, our <a class="mention hashtag" rel="nofollow noopener" href="https://hackers.pub/tags/ActivityPub" target="_blank">#ActivityPub</a>-powered platform for software engineers. While <a href="https://www.w3.org/TR/activitystreams-vocabulary/#ex131-jsonld" rel="nofollow noopener" target="_blank">ActivityPub theoretically supports multilingual content through the <code>contentMap</code> property</a>, the reality is that most server implementations (Mastodon, Misskey, etc.) don't properly handle this content as of April 2025. This creates a significant challenge for us. We want our users to share their knowledge in multiple languages, but we need to ensure compatibility with existing ActivityPub servers. I'm considering several approaches: <ol> <li>Creating separate posts for each language with clear language indicators, linking them through <code>inReplyTo</code> relationships (so translations appear as replies to the original post)</li> <li>Using the primary language in <code>content</code> while storing translations in <code>contentMap</code></li> <li>Adding "View in other languages" links at the bottom of each post</li> <li>Implementing inline language dividers that degrade gracefully on non-supporting servers, for example:<pre><code><div lang="en"> <h3>English</h3> <p>This is the English content…</p> </div> <hr> <div lang="ko"> <h3>한국어</h3> <p>한국어 내용입니다…</p> </div></code></pre> </li> </ol> I'm leaning toward a hybrid approach—showing content in the user's preferred language when possible while providing easy access to other language versions. Has anyone tackled this problem effectively? I'd love to hear about your experiences or ideas for making multilingual content work well in the fediverse, especially when dealing with server implementations that don't fully support ActivityPub's multilingual features. <a class="mention hashtag" rel="nofollow noopener" href="https://hackers.pub/tags/fedidev" target="_blank">#fedidev</a> <a class="mention hashtag" rel="nofollow noopener" href="https://hackers.pub/tags/federation" target="_blank">#federation</a> <a class="mention hashtag" rel="nofollow noopener" href="https://hackers.pub/tags/i18n" target="_blank">#i18n</a>

Free Software FoundationDid you know that the <a href="https://hostux.social/tags/FSF" class="mention hashtag" rel="nofollow noopener" target="_blank">#FSF</a> has a <a href="https://hostux.social/tags/PeerTube" class="mention hashtag" rel="nofollow noopener" target="_blank">#PeerTube</a> account? PeerTube is a decentralized, federated video platform powered by <a href="https://hostux.social/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener" target="_blank">#ActivityPub</a> and <a href="https://hostux.social/tags/WebTorrent" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebTorrent</a>, and you'll find us on the <a href="https://hostux.social/tags/Framatube" class="mention hashtag" rel="nofollow noopener" target="_blank">#Framatube</a> instance: <a href="https://u.fsf.org/36m" rel="nofollow noopener" translate="no" target="_blank">https://u.fsf.org/36m</a>

洪民憙 (Hong Minhee)<a href="https://speakerdeck.com/minhee/guo-han-wen-hun-yong-ti-karahollomate" rel="nofollow noopener" target="_blank">国漢文混用体からHolloまで</a>本日、<a href="https://fedilug.connpass.com/event/346156/" rel="nofollow noopener" target="_blank">第8回FediLUG勉強会</a>で「<a href="https://speakerdeck.com/minhee/guo-han-wen-hun-yong-ti-karahollomate" rel="nofollow noopener" target="_blank">国漢文混用体からHolloまで</a>」というタイトルで発表をしてきました。私がなぜActivityPubサーバーフレームワークの<a href="https://fedify.dev/" rel="nofollow noopener" target="_blank">Fedify</a>と、シングルユーザー向けActivityPubサーバーの<a href="https://docs.hollo.social/" rel="nofollow noopener" target="_blank">Hollo</a>を開発する事に成ったのか、その旅路を共有しました。実は全ての始まりは、韓国語の「国漢文混用体」（漢字ハングル混じり文）に「振りハングル」を付けたいという単純な願いからでした。この小さな目標が、最終的に<a href="https://fedify.dev/" rel="nofollow noopener" target="_blank">Fedify</a>と<a href="https://docs.hollo.social/" rel="nofollow noopener" target="_blank">Hollo</a>という二つのプロジェクトへと発展したのです。興味のある方は、発表スライドをご覧ください：「<a href="https://speakerdeck.com/minhee/guo-han-wen-hun-yong-ti-karahollomate" rel="nofollow noopener" target="_blank">国漢文混用体からHolloまで</a>」（Speaker Deck）<a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/FediLUG" target="_blank">#FediLUG</a> <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/Fedify" target="_blank">#Fedify</a> <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/Hollo" target="_blank">#Hollo</a> <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/ActivityPub" target="_blank">#ActivityPub</a> <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/%E3%83%95%E3%82%A7%E3%83%87%E3%82%A3%E3%83%90%E3%83%BC%E3%82%B9" target="_blank">#フェディバース</a> <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/fediverse" target="_blank">#fediverse</a> <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/fedidev" target="_blank">#fedidev</a>

BotKit by Fedify :botkit:<a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/%E3%83%95%E3%82%A7%E3%83%87%E3%82%A3%E3%83%90%E3%83%BC%E3%82%B9" target="_blank">#フェディバース</a>（<a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/fediverse" target="_blank">#fediverse</a>）用のボットを作りたいですか？<a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/BotKit" target="_blank">#BotKit</a> by Fedifyを使えば、わずか数行のコードでスタンドアロンのActivityPubボットを構築できます！従来のMastodonやMisskeyボットとは異なり、BotKitはプラットフォームの制約なしに完全なActivityPubサーバーを作成できます。BotKitでできること：<ul> <li>メンション、フォロー、メッセージに応答するボットの構築</li><li>整形されたテキスト、メンション、メディアを含む豊かなコンテンツの作成</li><li>予約投稿の公開と会話の自動管理</li><li>Deno Deploy、Docker、または自己ホスティングサーバーへの簡単なデプロイ</li> </ul>ドキュメントは<a href="https://botkit.fedify.dev/" rel="nofollow noopener" target="_blank">https://botkit.fedify.dev/</a>で確認し、今からフェディバースボットの構築を始めましょう！<a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/ActivityPub" target="_blank">#ActivityPub</a>

BotKit by Fedify :botkit:<a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/%EC%97%B0%ED%95%A9%EC%9A%B0%EC%A3%BC" target="_blank">#연합우주</a>(<a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/fediverse" target="_blank">#fediverse</a>)를 위한 봇을 만들고 싶으신가요? <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/BotKit" target="_blank">#BotKit</a> by Fedify를 사용하면 몇 줄의 코드만으로 독립형 <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/ActivityPub" target="_blank">#ActivityPub</a> 봇을 구축할 수 있습니다! 일반적인 Mastodon 또는 Misskey 봇과 달리, BotKit은 플랫폼 제약 없이 완전한 ActivityPub 서버를 만들 수 있게 도와줍니다.BotKit으로 할 수 있는 것:<ul> <li>멘션, 팔로우 및 메시지에 응답하는 봇 만들기</li><li>형식화된 텍스트, 멘션 및 미디어가 포함된 풍부한 콘텐츠 생성</li><li>예약된 게시물 발행 및 대화 자동 관리</li><li>Deno Deploy, Docker 또는 자체 호스팅 서버에 쉽게 배포</li> </ul>문서는 <a href="https://botkit.fedify.dev/" rel="nofollow noopener" target="_blank">https://botkit.fedify.dev/</a>에서 확인하시고 지금 바로 연합우주 봇을 만들어 보세요!

BotKit by Fedify :botkit:Want to create a <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/bot" target="_blank">#bot</a> for the <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/fediverse" target="_blank">#fediverse</a>? <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/BotKit" target="_blank">#BotKit</a> by <a translate="no" class="h-card u-url mention" href="https://hollo.social/@fedify" rel="nofollow noopener" target="_blank">@fedify</a> lets you build standalone <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/ActivityPub" target="_blank">#ActivityPub</a> bots with just a few lines of code! Unlike traditional Mastodon bots, BotKit helps you create complete ActivityPub servers without platform constraints.With BotKit, you can:<ul> <li>Build bots that respond to mentions, follows, and messages</li><li>Create rich content with formatted text, mentions, and media</li><li>Publish scheduled posts and automatically manage conversations</li><li>Deploy easily on Deno Deploy, Docker, or self-hosted servers</li> </ul>Check out our documentation at <a href="https://botkit.fedify.dev/" rel="nofollow noopener" target="_blank">https://botkit.fedify.dev/</a> and start building your fediverse bot today!

いしい＠試行錯誤WordPressのプラグイン「ActivityPub」の問題点<a rel="nofollow noopener" class="u-url mention" href="https://fedibird.com/@tell_me_fedi_jp" target="_blank">@tell_me_fedi_jp</a>WordPressのプラグイン「ActivityPub」を使っている方がいらっしゃったら質問です。どのような問題が起こっていて、どのように対処していますか？私の場合、mstdn.jpのアカウントからフォローできず、Bridgy Fedからフォローバックされないようです。また、mstdn.jpのアカウントからメンションやリプライはできるのですが、そのメンションやリプライをこちらのアカウント（サイト）で確認することができないようです。このアカウントは次の図のａ＠Ａの状態で、mstdn.jpのアカウントはｂ＠Ｂの状態です。リプライができているというのは、リプライしたサーバーＢや他のFediverseの他のサーバーＣからなら見えるからです（ただし検索が必要な場合がある）。ですから、リプライはできていると思うのですが気づくことができない状態です。mastodon-japan.netのアカウントからのメンションやリプライなら問題ありません。対処方法は分かりません。<a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://ishii00141.stars.ne.jp/tag/activitypub/" target="_blank">#ActivityPub</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://ishii00141.stars.ne.jp/tag/bridgyfed/" target="_blank">#BridgyFed</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://ishii00141.stars.ne.jp/tag/fediverse/" target="_blank">#Fediverse</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://ishii00141.stars.ne.jp/tag/mastodon/" target="_blank">#Mastodon</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://ishii00141.stars.ne.jp/tag/wordpress/" target="_blank">#WordPress</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://ishii00141.stars.ne.jp/tag/%e3%83%97%e3%83%a9%e3%82%b0%e3%82%a4%e3%83%b3/" target="_blank">#プラグイン</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://ishii00141.stars.ne.jp/tag/%e3%83%9e%e3%82%b9%e3%83%88%e3%83%89%e3%83%b3/" target="_blank">#マストドン</a><a href="https://ishii00141.stars.ne.jp/20250216-0756-852/" rel="nofollow noopener" target="_blank">https://ishii00141.stars.ne.jp/20250216-0756-852/</a>

Blort™ 🐀Ⓥ🥋☣️<a href="https://floss.social/@forgefed" class="u-url mention" rel="nofollow noopener" target="_blank">@forgefed</a> I'm just curious, as someone who loves the idea of "Github but open and activitypub", roughly how far off would you say we are from being able to follow and comment on issues via Mastodon?I'm not even looking for a date estimate, just a sense of if we're at the beginning of a very long road, or we're super close and almost there or...?<a href="https://social.tchncs.de/tags/ForgeFed" class="mention hashtag" rel="nofollow noopener" target="_blank">#ForgeFed</a> <a href="https://social.tchncs.de/tags/Forgejo" class="mention hashtag" rel="nofollow noopener" target="_blank">#Forgejo</a> <a href="https://social.tchncs.de/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener" target="_blank">#ActivityPub</a> <a href="https://social.tchncs.de/tags/Mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mastodon</a>

洪民憙 (Hong Minhee)Hello, I'm an open source software engineer in my late 30s living in <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/Seoul" target="_blank">#Seoul</a>, <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/Korea" target="_blank">#Korea</a>, and an avid advocate of <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/FLOSS" target="_blank">#FLOSS</a> and the <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/fediverse" target="_blank">#fediverse</a>.I'm the creator of <a translate="no" class="h-card u-url mention" href="https://hollo.social/@fedify" rel="nofollow noopener" target="_blank">@fedify</a>, an <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/ActivityPub" target="_blank">#ActivityPub</a> server framework in <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/TypeScript" target="_blank">#TypeScript</a>, <a translate="no" class="h-card u-url mention" href="https://hollo.social/@hollo" rel="nofollow noopener" target="_blank">@hollo</a>, an ActivityPub-enabled microblogging software for single users, and <a translate="no" class="h-card u-url mention" href="https://hollo.social/@botkit" rel="nofollow noopener" target="_blank">@botkit</a>, a simple ActivityPub bot framework.I'm also very interested in East Asian languages (so-called <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/CJK" target="_blank">#CJK</a>) and <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/Unicode" target="_blank">#Unicode</a>. Feel free to talk to me in <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/English" target="_blank">#English</a>, <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/Korean" target="_blank">#Korean</a> (<a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/%ED%95%9C%EA%B5%AD%EC%96%B4" target="_blank">#한국어</a>), or <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/Japanese" target="_blank">#Japanese</a> (<a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/%E6%97%A5%E6%9C%AC%E8%AA%9E" target="_blank">#日本語</a>), or even in Literary Chinese (<a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/%E6%96%87%E8%A8%80%E6%96%87" target="_blank">#文言文</a>, <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/%E6%BC%A2%E6%96%87" target="_blank">#漢文</a>)!<a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/introduction" target="_blank">#introduction</a>

最近の検索

検索オプション

管理者

サーバーの情報

#activitypub