Shakedown Social

7 posts5 participants3 posts today

@reiver ⊼ (Charles) :batman:2/I think there is a need for a "dumb" document format. HTML is no longer that.Markdown probably isn't it.No one really uses enriched-text (IETF RFC 1896).(I prefer wiki like formats, for various reasons, but —)I don't think there is an obvious choice for a "dumb" document format, right now.<a href="https://mastodon.social/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActivityPub</a> <a href="https://mastodon.social/tags/ActivityStreams" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActivityStreams</a> <a href="https://mastodon.social/tags/DeSo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DeSo</a> <a href="https://mastodon.social/tags/FediDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FediDev</a> <a href="https://mastodon.social/tags/FediDevs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FediDevs</a> <a href="https://mastodon.social/tags/Fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fediverse</a>

@reiver ⊼ (Charles) :batman:1/I think HTML being the default content type for ActivityPub / ActivityStreams is unfortunate in some ways.HTML was originally a "dumb" document format. But, it is now a "smart" application format — with privacy & security concerns.<a href="https://mastodon.social/@reiver/108237663610634862" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://mastodon.social/@reiver/108237663610634862</a>You should NOT just take whatever HTML is in the 'content', and put it in the web-browser to view it.You have to sanitize it. Or, render (unsafe) HTML to (safe) HTML.<a href="https://mastodon.social/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActivityPub</a> <a href="https://mastodon.social/tags/ActivityStreams" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActivityStreams</a> <a href="https://mastodon.social/tags/DeSo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DeSo</a> <a href="https://mastodon.social/tags/FediDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FediDev</a> <a href="https://mastodon.social/tags/FediDevs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FediDevs</a> <a href="https://mastodon.social/tags/Fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fediverse</a>

@reiver ⊼ (Charles) :batman:Previews in ActivityPub / ActivityStreams is what should bind the disparate software and user-experiences on the Fediverse.Not the ActivityStreams 'Note'....Previews using 'icon', 'image', 'name', 'summary', etc.<a href="https://mastodon.social/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActivityPub</a> <a href="https://mastodon.social/tags/ActivityStreams" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActivityStreams</a> <a href="https://mastodon.social/tags/DeSo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DeSo</a> <a href="https://mastodon.social/tags/FediDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FediDev</a> <a href="https://mastodon.social/tags/FediDevs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FediDevs</a> <a href="https://mastodon.social/tags/Fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fediverse</a> <a href="https://mastodon.social/tags/MastodonInTheRoom" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MastodonInTheRoom</a> <a href="https://mastodon.social/tags/SocialWeb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SocialWeb</a>

洪民憙 (Hong Minhee)I just discovered why some of my followers from larger <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/Mastodon" target="_blank">#Mastodon</a> instances (like mastodon.social) would mysteriously unfollow me after a while!<a href="https://github.com/mastodon/mastodon/pull/34272" rel="nofollow noopener noreferrer" target="_blank">A pull request was just merged in Mastodon that fixes a critical bug in their follower synchronization mechanism.</a>Turns out Mastodon implements the <a href="https://w3id.org/fep/8fcf" rel="nofollow noopener noreferrer" target="_blank">FEP-8fcf</a> specification (Followers collection synchronization across servers), but it expected all followers to be in a single page collection. When followers were split across multiple pages, it would only see the first page and incorrectly remove all followers from subsequent pages!This explains so much about the strange behavior I've been seeing with <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/Hollo" target="_blank">#Hollo</a> and other <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/Fedify" target="_blank">#Fedify</a>-based servers over the past few months. Some people would follow me from large instances, then mysteriously unfollow later without any action on their part.Thankfully this fix has been marked for backporting, so it should appear in an upcoming patch release rather than waiting for the next major version. Great news for all of us building on <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/ActivityPub" target="_blank">#ActivityPub</a>!This is why I love open source—we can identify, understand, and fix these kinds of interoperability issues together. 😊<a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/fediverse" target="_blank">#fediverse</a> <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/fedidev" target="_blank">#fedidev</a>

Jeff SikesOooh <a href="https://fed.brid.gy/r/https://snarfed.org/about" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@snarfed.org</a> will be speaking about "All the protocols, compared" in 45 minutes at 4:45 PM CT. <a href="https://atprotocol.dev/atmosphereconf-2025-talks/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://atprotocol.dev/atmosphereconf-2025-talks/</a><a href="https://mastodon.social/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActivityPub</a> <a href="https://mastodon.social/tags/BlueSky" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BlueSky</a> <a href="https://mastodon.social/tags/FediDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FediDev</a> <a href="https://mastodon.social/tags/OpenSocial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSocial</a>

wakest ⁂Theres a new interview with <a href="https://hackers.pub/@hongminhee" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@hongminhee</a> (of <a href="https://hollo.social/@fedify" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@fedify</a>, <a href="https://hollo.social/@hollo" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@hollo</a>, and now <a href="https://social.wake.st/tags/Ghost" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ghost</a> fame). It's in with Korean subtitles but quite readable with YouTube's autogenerated English subs.<a href="https://www.youtube.com/watch?v=sqxR8zscSDo" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.youtube.com/watch?v=sqxR8zscSDo</a><a href="https://hollo.social/@hongminhee/0195a85a-6a29-71fa-a60f-3e79c1295b05" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://hollo.social/@hongminhee/0195a85a-6a29-71fa-a60f-3e79c1295b05</a> <a href="https://social.wake.st/tags/fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fediverse</a> <a href="https://social.wake.st/tags/fedidev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fedidev</a>

Fedify: an ActivityPub server frameworkComing soon in <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/Fedify" target="_blank">#Fedify</a> 1.5.0: Smart fan-out for efficient activity delivery!After getting feedback about our queue design, we're excited to introduce a significant improvement for accounts with large follower counts.As we discussed in <a href="https://hollo.social/@fedify/0195802b-35d0-7a9b-a8f8-92e3035415d8" rel="nofollow noopener noreferrer" target="_blank">our previous post</a>, Fedify currently creates separate queue messages for each recipient. While this approach offers excellent reliability and individual retry capabilities, it causes performance issues when sending activities to thousands of followers.Our solution? A new two-stage “fan-out” approach:<ol> <li>When you call <code>Context.sendActivity()</code>, we'll now enqueue just one consolidated message containing your activity payload and recipient list</li><li>A background worker then processes this message and re-enqueues individual delivery tasks</li> </ol>The benefits are substantial:<ul> <li><code>Context.sendActivity()</code> returns almost instantly, even for massive follower counts</li><li>Memory usage is dramatically reduced by avoiding payload duplication</li><li>UI responsiveness improves since web requests complete quickly</li><li>The same reliability for individual deliveries is maintained</li> </ul>For developers with specific needs, we're adding a <a href="https://unstable.fedify.dev/manual/send#when-to-use-each-option" rel="nofollow noopener noreferrer" target="_blank"><code>fanout</code> option</a> with three settings:<ul> <li><code>"auto"</code> (default): Uses fanout for large recipient lists, direct delivery for small ones</li><li><code>"skip"</code>: Bypasses fanout when you need different payload per recipient</li><li><code>"force"</code>: Always uses fanout even with few recipients</li> </ul><pre><code>// Example with custom fanout setting await ctx.sendActivity( { identifier: "alice" }, recipients, activity, { fanout: "skip" } // Directly enqueues individual messages ); </code></pre>This change represents months of performance testing and should make Fedify work beautifully even for extremely popular accounts!For more details, check out our <a href="https://unstable.fedify.dev/manual/send#optimizing-activity-delivery-for-large-audiences" rel="nofollow noopener noreferrer" target="_blank">docs</a>.What other <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/performance" target="_blank">#performance</a> optimizations would you like to see in future Fedify releases?<a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/ActivityPub" target="_blank">#ActivityPub</a> <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/fedidev" target="_blank">#fedidev</a>

Fedify: an ActivityPub server frameworkWe've been working on adding custom background task support to <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/Fedify" target="_blank">#Fedify</a> as planned for version 1.5.0. After diving deeper into implementation, we've realized this is a more substantial undertaking than initially anticipated.The feature would require significant API changes that would be too disruptive for a minor version update. Therefore, we've decided to postpone this feature to Fedify 2.0.0.This allows us to:<ul> <li>Design a more robust and flexible worker architecture</li><li>Ensure better integration with existing task queue systems</li><li>Properly document the new APIs without rushing</li> </ul>We believe this decision will result in a more stable and well-designed feature that better serves your needs. However, some smaller improvements from our work that don't require API changes will still be included in Fedify 1.5.0 or subsequent minor updates.We appreciate your understanding and continued support.If you have specific use cases or requirements for background task support, please share them in our <a href="https://github.com/fedify-dev/fedify/issues/206" rel="nofollow noopener noreferrer" target="_blank">GitHub issue</a>. Your input will help shape this feature for 2.0.0.<a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/ActivityPub" target="_blank">#ActivityPub</a> <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/fedidev" target="_blank">#fedidev</a>

Fedify: an ActivityPub server frameworkPatch releases for <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/Fedify" target="_blank">#Fedify</a> versions <a href="https://github.com/fedify-dev/fedify/releases/tag/1.0.21" rel="nofollow noopener noreferrer" target="_blank">1.0.21</a>, <a href="https://github.com/fedify-dev/fedify/releases/tag/1.1.18" rel="nofollow noopener noreferrer" target="_blank">1.1.18</a>, <a href="https://github.com/fedify-dev/fedify/releases/tag/1.2.18" rel="nofollow noopener noreferrer" target="_blank">1.2.18</a>, <a href="https://github.com/fedify-dev/fedify/releases/tag/1.3.14" rel="nofollow noopener noreferrer" target="_blank">1.3.14</a>, and <a href="https://github.com/fedify-dev/fedify/releases/tag/1.4.7" rel="nofollow noopener noreferrer" target="_blank">1.4.7</a> are now available. These updates address two important bugs across all supported release lines:<ol> <li>Fixed a WebFinger handler bug that prevented matching <code>acct:</code> URIs with port numbers in the host. Thanks to <a translate="no" class="h-card u-url mention" href="https://fosstodon.org/@revathskumar" rel="nofollow noopener noreferrer" target="_blank">@revathskumar</a> for reporting and debugging the bug!</li><li>Resolved server errors that occurred when invalid URLs were passed to the <code>base-url</code> parameter of followers collections.</li> </ol>We recommend all users upgrade to these latest patch versions for improved stability and federation compatibility.<a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/ActivityPub" target="_blank">#ActivityPub</a> <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/fedidev" target="_blank">#fedidev</a>

Jeff SikesA collection of silly Mastodon apps (the best kind). It includes a Fax-To-Mastodon app. :omgdotlol: <a href="https://halcy.de/blog/2025/03/18/silly-mastodon-apps/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://halcy.de/blog/2025/03/18/silly-mastodon-apps/</a><a href="https://mastodon.social/tags/MastoDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MastoDev</a> <a href="https://mastodon.social/tags/FediDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FediDev</a> <a href="https://mastodon.social/tags/Fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fediverse</a> <a href="https://mastodon.social/tags/mastodonapps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mastodonapps</a>

wakest ⁂Just noticed this "Open in the application? " banner on <a href="https://framatube.org/accounts/framasoft" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@framasoft</a>'s "What is the fediverse" <a href="https://framapiaf.org/@peertube" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@peertube</a> video and I have the app installed thru <a href="https://floss.social/@fdroidorg" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@fdroidorg</a> but it takes me to the Google Play download page for it instead of opening it in the app. Makes for a really bad fediverse experience, we need to figure out these sorts of flows and make sure they reliably work. <a href="https://social.wake.st/tags/fedidev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fedidev</a> <a href="https://social.wake.st/tags/peertube" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#peertube</a> <a href="https://social.wake.st/tags/fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fediverse</a>

@reiver ⊼ (Charles) :batman:What about the Fediverse or Mastodon, etc, frustrates you or confuses you?<a href="https://mastodon.social/tags/DeSo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DeSo</a> <a href="https://mastodon.social/tags/FediDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FediDev</a> <a href="https://mastodon.social/tags/FediDevs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FediDevs</a> <a href="https://mastodon.social/tags/Fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fediverse</a> <a href="https://mastodon.social/tags/FediverseUX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FediverseUX</a> <a href="https://mastodon.social/tags/FediUX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FediUX</a> <a href="https://mastodon.social/tags/Mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mastodon</a>

洪民憙 (Hong Minhee)Most <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/ActivityPub" target="_blank">#ActivityPub</a> implementations include <code>Mention</code> objects in the <code>tag</code> attribute when someone mentions another actor within the <code>content</code> of a <code>Note</code> or <code>Article</code>. Should actor objects like <code>Person</code> or <code>Group</code> also include <code>Mention</code> objects in their <code>tag</code> attribute when mentioning other actors within their bio (<code>summary</code>)? Are there any implementations that already work this way? (I've checked Mastodon and it seems they don't include these mentions.) What are your thoughts on this?<a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/fediverse" target="_blank">#fediverse</a> <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/fedidev" target="_blank">#fedidev</a>

infinite love ⴳfor any <a href="https://mastodon.social/tags/fedidev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fedidev</a> trying to build a distributed database: are your activities ACID-compliant? do you expect or require other people’s incoming activities to represent ACID-compliant transactions?

infinite love ⴳsomewhat rhetorical question for <a href="https://mastodon.social/tags/fedidev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fedidev</a> space: are you trying to build a web of documents or a distributed database? the difference matters more than you may think.

Fedify: an ActivityPub server frameworkGot an interesting question today about <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/Fedify" target="_blank">#Fedify</a>'s outgoing <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/queue" target="_blank">#queue</a> design!Some users noticed we create separate queue messages for each recipient inbox rather than queuing a single message and handling the splitting later. There's a good reason for this approach.In the <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/fediverse" target="_blank">#fediverse</a>, server response times vary dramatically—some respond quickly, others slowly, and some might be temporarily down. If we processed deliveries in a single task, the entire batch would be held up by the slowest server in the group.By creating individual queue items for each recipient:<ul> <li>Fast servers get messages delivered promptly</li><li>Slow servers don't delay delivery to others</li><li>Failed deliveries can be retried independently</li><li>Your UI remains responsive while deliveries happen in the background</li> </ul>It's a classic trade-off: we generate more queue messages, but gain better resilience and user experience in return.This is particularly important in federated networks where server behavior is unpredictable and outside our control. We'd rather optimize for making sure your posts reach their destinations as quickly as possible!What other aspects of Fedify's design would you like to hear about? Let us know!<a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/ActivityPub" target="_blank">#ActivityPub</a> <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/fedidev" target="_blank">#fedidev</a>

洪民憙 (Hong Minhee)Just published a post about Hackers' Pub's unique username change policy! Unlike most <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/fediverse" target="_blank">#fediverse</a> platforms, they allow a one-time username change while preserving your connections and content history. It's all possible thanks to some clever <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/ActivityPub" target="_blank">#ActivityPub</a> implementation using UUID-based actor URIs instead of username-based ones. If you're interested in trying it out, the platform is currently in invitation-only beta—check the post for details on how to request access!<a href="https://hackers.pub/@hongminhee/2025/hackers-pub-introduces-flexible-username-changes" rel="nofollow noopener noreferrer" target="_blank">https://hackers.pub/@hongminhee/2025/hackers-pub-introduces-flexible-username-changes</a><a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/HackersPub" target="_blank">#HackersPub</a> <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/fedidev" target="_blank">#fedidev</a>

洪民憙 (Hong Minhee)Hackers' Pub Introduces Flexible Username Changes: Breaking the Fediverse Norm <a href="https://hackers.pub/@hongminhee/2025/hackers-pub-introduces-flexible-username-changes" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://hackers.pub/@hongminhee/2025/hackers-pub-introduces-flexible-username-changes</a>

Julian FietkauI'm finally unveiling the <a href="https://fietkau.social/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActivityPub</a> project that has been consuming my weekends: Encyclia, an <a href="https://fietkau.social/tags/ORCID" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ORCID</a> bridge that will make ORCID records followable and interactable on the fediverse. 🙂It's early-stage and the ORCID following function is not publicly available yet. We're seeking community feedback on functionality and safety aspects. Read more at <a href="https://encyclia.pub" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://encyclia.pub</a> or follow <a href="https://fietkau.social/@encyclia" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@encyclia</a> for news!<a href="https://fietkau.social/tags/fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fediverse</a> <a href="https://fietkau.social/tags/fedidev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fedidev</a> <a href="https://fietkau.social/tags/scicomm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#scicomm</a> <a href="https://fietkau.social/tags/wisskomm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#wisskomm</a> <a href="https://fietkau.social/tags/academicchatter" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#academicchatter</a>

fashionable cyber witch project vyrwe now have some GoToSocial docs about importing your archived posts in general: <a href="https://docs.gotosocial.org/en/latest/user_guide/importing_posts/" rel="nofollow noopener noreferrer" target="_blank">https://docs.gotosocial.org/en/latest/user_guide/importing_posts/</a>most of the specifics are in the <code>slurp</code> docs, but if you write your own importer and think it might be of general interest to GTS users, please let us know.<a href="https://princess.industries/tags/gotosocial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GoToSocial</a> <a href="https://princess.industries/tags/gts" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GTS</a> <a href="https://princess.industries/tags/fedidev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FediDev</a>

Recent searches

Search options

Administered by:

Server stats:

#fedidev