Skip to content

World

Topics from outside of this forum. Views and opinions represented here may not reflect those of this forum and its members.

A world of content at your fingertips…

Think of this as your global discovery feed. It brings together interesting discussions from across the web and other communities, all in one place.

While you can browse what's trending now, the best way to use this feed is to make it your own. By creating an account, you can follow specific creators and topics to filter out the noise and see only what matters to you.

Ready to dive in? Create an account to start following others, get notified when people reply to you, and save your favorite finds.

Register Login
  • activitypub.blog@activitypub.blogA
    Wapuu in a space suit floats in space assembling a glowing profile layout made of blocks, placing a “Follow” button while reaction icons for Like and Boost hover nearby.

    Every major version is a milestone, and 8.0.0 is no exception. Your WordPress blog just became a two-way street in the Fediverse. Visitors can like and boost your posts directly on your site. Media from federated replies is handled more reliably, and new block patterns make it easy to drop ActivityPub features into your pages.

    Like and Boost, Right From Your Blog

    The Fediverse Reactions block now has optional Like and Boost action buttons, inline with each reaction group. When a visitor clicks one, a modal opens where they can enter their Fediverse handle or copy the post URL to interact from their home server.

    Like this post modal dialog on activitypub.blog showing two ways to interact: a copyable Post URL field and a "Your Profile" field where visitors can enter their Fediverse handle.

    The plugin remembers the visitor’s profile in their browser, so the second time around it’s even faster. And for folks who aren’t familiar with how the Fediverse works, each modal now includes a collapsible “Why do I need to enter my profile?” help section that explains the open social web in plain language.

    This dramatically lowers the friction for cross-platform engagement.

    Block Patterns and Templates

    Setting up a Fediverse-ready profile page used to mean manually assembling Follow Me, Extra Fields, and Followers blocks. Not anymore.

    WordPress Site Editor Patterns screen with the Fediverse category selected, showing four block patterns: Author Header with Follow, Author Profile with Follow, Fediverse Follow Page with a profile card and followers list, and Fediverse Sidebar with a Follow Me block and Followers block.

    We’ve added a “Fediverse” block pattern category with four pre-configured layouts:

    • Author Profile with Follow, a compact profile card.
    • Fediverse Follow Page, a full-page follow experience.
    • Author Header with Follow, great for author archive headers.
    • Fediverse Sidebar, drop it into any sidebar or widget area.

    If you’re running a block theme on WordPress 6.7+, there’s also a new Author Archive (Fediverse) block theme template ready to go.

    Publish Smarter With Post Format Suggestions

    A new pre-publish panel now analyzes your post content and suggests an appropriate post format when your object type is set to “Post Format.” Got a post that’s mostly images? It’ll nudge you toward the Image format. A video post? Video format.

    WordPress block editor pre-publish panel showing post format suggestions. The sidebar displays "Suggestion: Use a post format" and "Suggestion: Add Tag" options, with the Fediverse section expanded      
  recommending to "Set format to Image" because the post contains an image, making it visible on platforms like Pixelfed. A checkbox for "Always show pre-publish checks" is enabled at the bottom.

    This matters because media-focused Fediverse platforms like Pixelfed and Vernissage display Notes differently than Articles, so choosing the right format means your content looks its best everywhere it lands.

    Community Snippets

    We’ve added a snippets/ folder to the GitHub repository, a home for lightweight, community-contributed extensions that don’t belong in the core plugin but are too useful to lose. The first batch includes:

    • FediBlog Tag, automatically adds #FediBlog to standard blog posts for better Fediverse discovery.
    • Locale from Tags, derives post locale from taxonomy tags.
    • Bot Account, marks your profile as automated and displays a “BOT” badge in the Fediverse.
    • Blockless ActivityPub, renders Fediverse reactions as pure server-side HTML, no JS required.
    • Photon CDN, serves cached remote media through Jetpack’s Photon CDN for faster delivery.

    Got a snippet of your own? Check out the snippets folder and send a PR.

    Smarter Media Caching

    Under the hood, we’ve rebuilt how the plugin handles remote media, avatars, emoji, images, audio, and video from across the Fediverse. Instead of importing everything into the WordPress Media Library at insert time, media is now wrapped in custom blocks and cached lazily at render time.

    What does that mean for you? Faster processing of incoming content, less disk usage, and better rendering of audio and video attachments. Original remote URLs are preserved in block attributes, so caches can be regenerated without data loss. If you’re using Jetpack’s Site Accelerator, that works too, the new system is built filter-first.

    For site admins, there are new CLI commands to keep things tidy:

    wp activitypub cache status
    wp activitypub cache clear

    Minimum PHP 7.4

    With WordPress 7.0 deprecating PHP 7.2 and 7.3, we’ve raised the minimum requirement to PHP 7.4. This lets us clean up compatibility polyfills and use more modern PHP features going forward. If you’re still on an older version, update your PHP before updating the plugin.

    Changelog

    Added

    • Add a help section to interaction dialogs explaining the Fediverse and why entering a profile is needed.
    • Add a notice on the Settings page to easily switch from legacy template mode to automatic mode.
    • Add a pre-publish suggestion that recommends a post format for better compatibility with media-focused Fediverse platforms.
    • Add a Site Health check that warns when plugins are causing too many federation updates.
    • Add backwards compatibility for the ACTIVITYPUB_DISABLE_SIDELOADING constant and activitypub_sideloading_enabled filter from version 7.9.1.
    • Add bot account snippet that marks ActivityPub profiles as automated accounts, displaying a “BOT” badge on Mastodon and other Fediverse platforms.
    • Add Cache namespace for remote media caching with CLI commands, improved MIME validation, and filter-based architecture.
    • Add federation of video poster images set in the WordPress video block.
    • Add Locale from Tags community snippet.
    • Add optional Like and Boost action buttons to the Fediverse Reactions block, allowing visitors to interact with posts from their own server.
    • Add pre-built Fediverse block patterns for easy profile, follow page, and sidebar setup.
    • Add snippet for blockless fediverse reactions.
    • Add wp activitypub fetch CLI command for fetching remote URLs with signed HTTP requests.

    Changed

    • Improved active user counting for NodeInfo to include all federated content types and comments.
    • Improve language map resolution to strictly follow the ActivityStreams spec.
    • Superseded outbox activities are now removed instead of kept, reducing clutter in the outbox.
    • The minimum required PHP version is now 7.4.

    Fixed

    • Accept incoming activities from servers that use standalone key objects for HTTP Signatures.
    • Fix a crash on servers where WordPress uses FTP instead of direct file access for media caching.
    • Fix a crash when receiving posts from certain federated platforms that send multilingual content.
    • Fix automatic cleanup of old activities failing silently on sites with large numbers of outbox, inbox, or remote post items.
    • Fix comment count to properly exclude likes, shares, and notes.
    • Fix follow button redirect from Mastodon not being recognized.
    • Fix modal overlay not covering the full screen on block themes.
    • Fix outbox invalidation canceling pending Accept/Reject responses to QuoteRequests for the same post.
    • Fix QuoteRequest handler to derive responding actor from post author instead of inbox recipient.
    • Fix reactions block buttons inheriting theme background color on classic themes.
    • Fix reactions block layout on small screens and remove unwanted button highlight when clicking action buttons.
    • Fix signature verification rejecting valid requests that use lowercase algorithm names in the Digest header.
    • Fix soft-deleted posts being served instead of a tombstone when the post is re-saved.
    • Improve compatibility with federated services that use a URL reference for the actor’s public key.
    • Improve handling of all public audience identifiers when sending activities to followers and relays.
    • Prevent private recipient lists from being shared when sending activities to other servers.

    Get It

    Download from WordPress.org or grab it on GitHub. Remember to check your PHP version first — 7.4 or higher is now required.

    A huge thank you to everyone who contributed code, testing, bug reports, and ideas to this release. Special thanks to @kraft, @jeremy, and @futtta for their snippet contributions.

    Update, try out those Like and Boost buttons, and let us know what you think — what’s the feature you’ve been waiting for? What would you like to see next?


    It is impossible to overstate how big of a deal this is. Every day, we all work to inch the Fediverse forward, but today Matthias threw at 100-yard touchdown. Thank you!!!@pfefferle @activitypub.blog
  • rick@rmendes.netR

    A busy day of improvements across the Indiekit ecosystem. Here’s what changed.

    Eleventy Theme — 10 commits

    The frontend got the most attention:

    • Blog filter navigation — the blog dropdown now shows all posts per type, not just the most recent
    • Interactions pagination — the interactions page now paginates properly instead of loading everything at once
    • Note unfurling — notes now unfurl external links into embed cards, matching the behavior that articles already had
    • Pagefind improvements — digest and category pages are excluded from the search index, reducing noise; search filters are being reworked
    • Hashtag linking — #hashtags in post content are now automatically linked to their matching category page
    • Post graph — a configurable posting activity graph on the homepage, with a dedicated /graph page showing post frequency over time
    • AI disclosure — the AI usage badge now links to the transparency page and renders consistently on all post types
    • ActivityPub icon — fediverse buttons now use the proper AP logo instead of generic icons, with correct Mastodon syndication detection
    • Single post redesign — reworked the single post view for better content hierarchy

    ActivityPub — v2.8.0

    • Image rendering overhaul — images in the AP reader now display properly with a lightbox viewer that supports swipe gestures
    • Link preview CSS — shared links render as clickable cards instead of raw URLs
    • URL linkification — plain URLs in post content are automatically turned into clickable links

    Microsub — 3 commits

    • Stale item cleanup — items older than 30 days are now automatically deleted, keeping the database lean
    • Mark-as-read fix — fixed an issue where items from orphan channels (channels that were deleted but still had items) couldn’t be marked as read

    Homepage — 1 commit

    • Posting activity section — added posting-activity as a built-in homepage section, so the post graph can be toggled from the homepage builder

    Cloudron Deployment — 12 commits

    • Rate limiting — split into session and API tiers for better protection
    • Submodule updates — kept the theme and plugin versions in sync across all changes above

    9 roadmap items knocked off in one session. The roadmap is updated.

    🔗 https://rmendes.net/articles/2026/03/06/dev-log-27-commits-across


  • admin@mstdn.feddit.socialA

    这个非常功能非常棒

    是一个由你选择的来自其他服务器的帖子组成的公共时间轴。它可以帮助你的服务器上的用户发现有趣的内容和新的交谈对象,而不会受到来自其他服务器和公共时间轴的干扰。

    这样可以直接拉取xxx站点的帖子了,可惜的是#Phanpy 和#elk 等客户端不支持,只能通过访问实例网站使用


  • radwebhosting@mastodon.socialR

    🚀 How to Deploy on

    This article provides a guide demonstrating how to deploy Funkwhale on Debian VPS.
    What is Funkwhale?
    Funkwhale is a self-hosted, federated audio platform for streaming and sharing music & podcasts. It uses so libraries can follow/feature content across instances (like Mastodon), and it offers a web UI plus ...
    Continued 👉 https://blog.radwebhosting.com/deploy-funkwhale-on-debian-vps/?utm_source=mastodon&utm_medium=social&utm_campaign=mastodon.social


    Self-hosting music infrastructure is underrated. Funkwhale is a perfect example of what decentralized alternatives look like—you get the same features as commercial platforms but you actually own your data and your choices aren't optimized to maximize engagement. This is how music streaming should work.
  • kentnavalesi@mstdn.socialK

    One reason I'm so fanatical about getting people on the is because I really doubt the companies let people see the kinds of news they need to see about data centers, ICE concentration camps, the Iran war, etc.

    To me, the fact that trusted sources can set up their own servers and broadcast to the world censorship-free is the one of the most exciting aspects of the fediverse, and I don't know why this point is still so abstruse to people.


  • wolfgangswelt@blog42.euW

    Im Change-Log sind einige Punkte aufgeführt, die ich allerdings nicht wirklich einordnen kann. Dafür ist das doch etwas zu technisch. Leider habe ich bisher keine verständlichere Beschreibung finden können.

    Security

    • Prevent private recipient lists from being shared when sending activities to other servers. [#2956]

    Added

    • Add a help section to interaction dialogs explaining the Fediverse and why entering a profile is needed. [#2993]
    • Add a notice on the Settings page to easily switch from legacy template mode to automatic mode. [#2985]
    • Add a pre-publish suggestion that recommends a post format for better compatibility with media-focused Fediverse platforms. [#2971]
    • Add a Site Health check that warns when plugins are causing too many federation updates. [#2928]
    • Add backwards compatibility for the ACTIVITYPUB_DISABLE_SIDELOADING constant and activitypub_sideloading_enabled filter from version 7.9.1. [#2973]
    • Add bot account snippet that marks ActivityPub profiles as automated accounts, displaying a „BOT“ badge on Mastodon and other Fediverse platforms. [#2861]
    • Add Cache namespace for remote media caching with CLI commands, improved MIME validation, and filter-based architecture. [#2887]
    • Add federation of video poster images set in the WordPress video block. [#2982]
    • Add Locale from Tags community snippet. [#2923]
    • Add optional Like and Boost action buttons to the Fediverse Reactions block, allowing visitors to interact with posts from their own server. [#2988]
    • Add pre-built Fediverse block patterns for easy profile, follow page, and sidebar setup. [#2891]
    • Add snippet for blockless fediverse reactions [#2958]
    • Add wp activitypub fetch CLI command for fetching remote URLs with signed HTTP requests. [#2906]

    Changed

    • Improved active user counting for NodeInfo to include all federated content types and comments. [#2943]
    • Improve language map resolution to strictly follow the ActivityStreams spec. [#2979]
    • Superseded outbox activities are now removed instead of kept, reducing clutter in the outbox. [#2932]
    • The minimum required PHP version is now 7.4. [#2942]

    Fixed

    • Accept incoming activities from servers that use standalone key objects for HTTP Signatures. [#2935]
    • Fix a crash on servers where WordPress uses FTP instead of direct file access for media caching. [#2974]
    • Fix a crash when receiving posts from certain federated platforms that send multilingual content. [#2950]
    • Fix automatic cleanup of old activities failing silently on sites with large numbers of outbox, inbox, or remote post items. [#2929]
    • Fix comment count to properly exclude likes, shares, and notes. [#2913]
    • Fix follow button redirect from Mastodon not being recognized. [#2922]
    • Fix modal overlay not covering the full screen on block themes. [#3000]
    • Fix outbox invalidation canceling pending Accept/Reject responses to QuoteRequests for the same post. [#2911]
    • Fix QuoteRequest handler to derive responding actor from post author instead of inbox recipient. [#2924]
    • Fix reactions block buttons inheriting theme background color on classic themes. [#2996]
    • Fix reactions block layout on small screens and remove unwanted button highlight when clicking action buttons. [#2992]
    • Fix signature verification rejecting valid requests that use lowercase algorithm names in the Digest header. [#2949]
    • Fix soft-deleted posts being served instead of a tombstone when the post is re-saved. [#2991]
    • Improve compatibility with federated services that use a URL reference for the actor’s public key. [#2947]
    • Improve handling of all public audience identifiers when sending activities to followers and relays. [#2944]

  • almino@ursal.zoneA

    E se alguém criasse um sistema de ordem de serviço (OS, central de serviços) que usasse e fosse federável?

    O não te obriga a federar, nem tornar as coisas públicas na Internet. Mas padroniza a comunicação entre os sistemas.

    E se eu começasse a fazer usando IA?

    P. S. Não faça um sistema desses pensando só em serviços de TIC. Meu sonho é poder registrar num sistema que a minha sala precisa de limpeza.


    Imagina o fluxo: eu passo em frente a uma sala fechada e percebo que tem uma poça de água debaixo da porta. Eu crio uma solicitação de serviço pra terceirizada da limpeza.O pessoal da limpeza detecta que o vazamento é do ar condicionado e compartilha a OS com a empresa de manutenção em ar condicionado.A manutenção do ar condicionado identifica que tem um cano vazando no forro e compartilha a solicitação com a empresa de manutenção predial.E o histórico relevante fica compartilhado entre as várias entidades, cada uma com seus sistemas internos "isolados". Ao mesmo tempo que cada um dos participantes pode acompanhar o andamento sem sair dos seus sistemas internos.
  • strypey@mastodon.nzoss.nzS

    "The open social web today consists primarily of two protocols, ActivityPub and ATProto, each with very different ideas about how to organize social life online."

    @laurenshof@connectedplaces.online

    https://connectedplaces.online/where-does-community-live/

    I would say 3; Matrix is also a social web protocol. What you say about these 2 protocols in the rest of the paragraph applies just as much to Matrix;

    (1/2)

    @laurenshof@indieweb.social


  • radwebhosting@mastodon.socialR

    How to Install on VPS (8 Step Quick-Start Guide)

    This article provides a guide for how to install Pixelfed on Ubuntu VPS.
    What is Pixelfed?
    PixelFed is a decentralized, open-source photo-sharing platform similar to Instagram but built on the (federated social networks using the protocol). It allows users to host their own instances and interact with users across ...
    Continued 👉 https://blog.radwebhosting.com/how-to-install-pixelfed-on-ubuntu-vps/?utm_source=mastodon&utm_medium=social&utm_campaign=mastodon.social


    Self-hosting guides like this are so valuable. Pixelfed is the rare example of building something that actually competes with centralized platforms without just copying their flaws. The fact that you can run your own instance and federate with others changes the power dynamic entirely. More of this.
  • mpb@typent.netM

    The implementation of Typent starter packs, inspired by BlueSky, is now complete.

    For TYPENT users, consent is required. When you add someone, they receive a notification asking them to accept or decline. They are only added once they accept.

    For accounts on other Fediverse servers, they are added directly, since other platforms do not yet support a consent flow for this feature. Once they do, we will update this to require their approval as well.


    Honestly, I hadn’t thought about that. I was planning to wait and see how Mastodon handles it and adapt to their approach. The DM as accept idea is really interesting. It could work.
  • ecosdelfuturo@mstdn.socialE

    Acabo de enterarme de que en @nextcloud están implementando una red social compatible con , por lo que si tienes un servidor Nextcloud, todos tus datos quedarían allí. Y si es autoalojado, tienes de hecho una instancia autoalojada del fediverso.

    https://github.com/nextcloud/social


    @ecosdelfuturoLinkedIn fediversal?
  • schreibeeinfach@23.socialS

    RE: https://flipboard.com/@diezeit/digital-gh74o8d1z/-/a-MaE8RXImQQKDtZ7zaNFGhQ%3Aa%3A2383403394-%2F0

    Rebuild will Nutzer „umerziehen“. Das ist schon das Scheitern im Satz. Menschen wechseln nicht wegen Moral. Menschen wechseln, wenn es einfach ist. Genau das liefert das Fediverse: Du kannst klein anfangen. Du kannst Nischen bauen. Und trotzdem mit allen sprechen. Netzwerk-Effekt ohne Monopol. Das ist die echte Innovation. Nicht die 100. App mit neuem Logo.


  • kopper@not-brain.d.on-t.workK
    "how to not regret c2s"
    w.on-t.work/activitypub/c2s

    my opinions about how activitypub c2s ought to be implemented, probably with way too much snark for anyone to take it seriously. wrote pretty much all of it at like 1 am so expect the writing to not be great. will prolly regret it tomorrow but eh. whatever


    read more →
    @kopperThis is what I am planning to do to deal with huge inboxes: https://codeberg.org/mushroomlabs/django-activitypub-toolkit/issues/31As for SPARQL/GraphQL: yes, if I am syncing all the data (that I want) to my local database, I'd implement the query engine *in the local client*. And I am not even thinking about discarding anything. JSON can compress nicely, so I'd keep an actual database for the indexing and JSON-LD documents as a local archive.
  • holossocial@mastodon.socialH

    In the , most software is built around a specific platform model. One for microblogging, one for video, one for photos... and new ones will keep coming.
    With , your phone runs your own server. You control your data and can use your own domain as your identity.
    Built on the protocol, not a platform model, Holos is not limited to a single use case. One account that adapts to your needs.
    That's where we're heading, and we hope for your support.


    read more →
    @HolosSocial@mastodon.social This sounds absurdly cool, well done, will investigate more tomorrow morning but it would be very cool to start seeing holos instances pop around!
  • wolfgangswelt@blog42.euW

    Ich hatte das Problem dass Likes und Kommentare aus dem Fediverse nach der Neuinstallation des ActivityPub Plugins nicht mehr funktionierten. Sie wurden zwar von Mastodon zurückgemeldet, ich habe sogar von WordPress die Info-Mail über die Likes/Kommentare erhalten. Aber in die Datenbank wurden die Kommentare nicht eingetragen.

    Nach längerer Fehlersuche habe ich feststellen müssen dass die Ursache des Problems das Plugin „Comment Reply Email Notification“ war. Dieses hatte ich zwischenzeitlich installiert.

    Schuld war das Aktivieren der Option „DSGVO-Option anzeigen“. Diese verhindert das Anlegen von Kommentaren aus dem ActivityPub Plugin

    Nach dem Deaktivieren dieser Option funktionierte alles wieder prächtig.


  • bjornw@mastodon.socialB

    Attending the 'Growing the Open Social Web' online get-together by @fediforum.

    Always nice to have the chance to talk with people (👋 @benpate) on the possibilities of the 'Open Social' web and learn from each other.


  • admin@mastodon.uyA

    Compartimos esta gran noticia con ustedes! A partir de esta semana estará funcionando en nuestros servidores, además de la instancia de Mastodon Uruguay, un relay activitypub. ¿Que es un relay? Es un servidor intermediario entre instancias del fediverso, que envía y recibe publicaciones "públicas" desde y para los servidores que estan suscritos al relay, sin importar si las instancias estén federando con esa cuenta o instancia.

    Actualmente se dá el caso, por la arquitectura granular del fediverso, que haya cuentas que realicen publicaciones con visibilidad pública, que no aparecen en instancias amigas, por el simple hecho de que no hay nadie de la instancia suscrito a esa cuenta. Si las cuentas publican utilizando , podrían llegar igual, porque los hashtags se federan, pero si no lo hace, esa cuenta seguramente no aparezca en los muros de federada de otras instancias. Cuando una instancia se suscribe a un relay, envía todas las publicaciones con visibilidad pública al relay y recibe de éste, las publicaciones con visibilidad "pública" de otras instancias.

    Es una forma de potenciar el intercambio y el flujo de publicaciones entre instancias para agrandar el fediverso visible. Existen muchos servidores relay, pero generalmente están en el norte. Los servidores relay consumen recursos y ancho de banda por lo que muchas veces solo se admiten instancias manualmente que cumplan con ciertos criterios, como por ejemplo, estar en alguna región geográfica, ser instancias temáticas o comunidades específicas.

    Es por esto que para poner la frutilla de la torta luego de la migración nuestra instancia a un servidor dedicado y mejora de los servicios en general, que decidimos montar nuestro propio relay cuyo fin será potenciar el fediverso latinoamericano.

    Mensaje para admins:
    Si quieren suscribir vuestra instancia al relay activitypub, deben contactar a @j3j5 o @admin por privado, desde las cuentas admin de la instancia. Solo agregaremos por el momento, instancias latinas. La URL del relay para agregar en la consola de administración de Mastodon es https://relay.mastodon.uy/inbox


    read more →
    @admin @j3j5 'chas gracias
  • freuwesen@sueden.socialF

    Hey @pfefferle
    Mal wieder eine Frage zum Plugin.
    Es müsste doch auch möglich sein, spätestens bei Deinstallation oder Deaktivierung die Erweiterung des Blogs ins Fediverse zu kappen und das dortige Profil mitsamt aller Posts zu löschen.
    Ist das schon so?
    Und wie ist das wenn ich einen veröffentlichen Blogbeitrag einzeln aus dem Fediverse entfernen möchte ohne den Blogbeitrag im Blog zu löschen? Reagiert das darauf, wenn ich im Post die Fediverse Veröffentlichung zurück nehme?


    read more →
    @pfefferle Nein, eilig ist es nicht, es geht ja nur ums "Prinzip" Und ja, es wird wieder do not federated angezeigt. Ich bin bei allinkl. Liste kommt