fediverse

<p>cross-posted from: <a href="https://lemmy.bestiver.se/post/363594" rel="nofollow">lemmy.bestiver.se/post/363594</a></p><p><p><a href="https://lobste.rs/s/m65t5p/site_for_making_bots_for_fediverse" rel="nofollow">Comments</a></p></p> <small class="notice" x-post-type-data="None"> Takahe has limited support for this type: <a href="https://lemmy.dbzer0.com/post/43531151">See Original Page</a> </small>

<p>We’re back with a fresh release, and this one makes following and sharing smoother than ever—plus gives you more control over how your posts can be quoted.</p><p>A New Way to Follow (For Now)</p><p>Starting today, users on WordPress.com sites and self-hosted sites connected through Jetpack can see the posts of accounts they follow directly in their WordPress.com Reader timeline. The Following UI has been around for a little while, yet hidden, and with this release it will be enabled by default for these sites.</p><p>When you follow an account, ActivityPub checks for a discoverable RSS feed. If one exists, it’s automatically added to your Reader timeline so new posts appear alongside everything else you already follow. Unfollowing works the same way—the feed disappears when you remove the account. And if you’d like to view the feed for an account you’ve followed, just hover over it in the list table and click View Feed.</p><p>Think of this as a bridge: a simple way to read the posts of accounts you follow today, while we continue building a full, first-class ActivityPub reading experience for tomorrow.</p><p>There are a couple of details to keep in mind. Removing a subscription directly in the Reader won’t update your site’s Following list, and interactions are limited to what RSS allows, which means sharing and reposting rather than the full range of ActivityPub features.</p><p>Running a self-hosted site without Jetpack? You can still <a href="https://activitypub.blog/2025/07/09/7-0-0-i-will-follow-you/" rel="nofollow">enable the Following UI manually</a>—it just won’t connect with the Reader.</p><p>Quote Post Controls</p><p>We’ve also added support for Mastodon’s quote post feature—and given you an easy way to control how others can quote your content.</p><p>When writing in the Block Editor, you’ll now see a sidebar setting that lets you decide whether everyone can quote your post, only your followers can, or if quoting is reserved for you alone. Once published, Mastodon and other compatible platforms will honor your choice automatically. No extra setup needed—just write, choose, and publish with confidence.</p><p>Full Changelog</p><p>Added</p><p>Added a setting to control who can quote your posts.<br>Added support for QuoteRequest activities (FEP-044f), enabling proper handling, validation, and policy-based acceptance or rejection of quote requests.<br>Add upgrade routine to enable ActivityPub feeds in WordPress.com Reader<br>Add Yoast SEO integration for author archives site health check.<br>Improved interaction policies with clearer defaults and better Mastodon compatibility.<br>New site health check warns if active Captcha plugins may block ActivityPub comments.<br>Sync following meta to enable RSS feed subscriptions for ActivityPub actors in WordPress.com Reader<br>You can now follow people and see their updates right in the WordPress.com Reader when using Jetpack or WordPress.com.</p><p>Changed</p><p>Added support for fetching actors by account identifiers and improved reliability of actor retrieval.<br>Clarify error messages in account modal to specify full profile URL format.<br>Improved checks to better identify public Activities.<br>Improved compatibility by making the ‘implements’ field always use multiple entries.<br>Improved recipient handling for clarity and improved visibility handling of activities.<br>Remote reply blocks now sync account info across all blocks on the same page<br>Standardized notification handling with new hooks for better extensibility and consistency.<br>Updated sync allowlist to add support for Jetpack notifications of likes and reposts.</p><p>Fixed</p><p>Fixed an issue where post metadata in the block editor was missing or failed to update.<br>Fix Flag activity object list processing to preserve URL arrays<br>Fix PHP warning in bulk edit scenario when post_author is missing from $_REQUEST<br>Posts now only fall back to the blog user when blog mode is enabled and no valid author exists, ensuring content negotiation only runs if an Actor is available.</p><p>Downloads</p><p>WordPress.org: <a href="https://downloads.wordpress.org/plugin/activitypub.7.5.0.zip" rel="nofollow">activitypub.7.5.0.zip</a><br>GitHub: <a href="https://github.com/Automattic/wordpress-activitypub/releases/tag/7.5.0" rel="nofollow">tag/7.5.0</a></p><p>Thank you!</p><p>Thanks to everyone who contributed code, tested, offered feedback, or lent support along the way. Update to 7.5.0 today and follow, share, and quote to your heart’s content!</p> <small class="notice" x-post-type-data="type=&#x27;Article&#x27; attributed_to=None"> Takahe has limited support for this type: <a href="https://activitypub.blog/2025/10/01/7-5-0-follow-the-feed-quote-the-lead/">See Original Article</a> </small>

<p>My crawler updates are doing a better job than I expected finding some of the smaller servers, expect some crazy numbers for a few more days as we dig in deeper to the <a href="/tags/fediverse/" rel="tag">#fediverse</a> and see who is out there!</p><p><a href="https://gitlab.com/diasporg/poduptime/-/commit/99e7945affb1ccba679af66a344187c19ed79bb0" rel="nofollow">gitlab.com/diasporg/poduptime/…</a></p> <small class="notice" x-post-type-data="type=&#x27;Article&#x27; attributed_to=None"> Takahe has limited support for this type: <a href="https://fediverse.one/display/fdc30534-1468-e41e-98a3-2aa890119049">See Original Article</a> </small>