Moving contexts (aka topics/threads) between audiences (aka categories/communities) should be something that can be communicated outward. NodeBB is experimenting with using the Move activity to communicate this to other instances. When a context is moved from one audience to another, the object and all of its descendants go with it. This is communicated with a Move activity with the resolvable context as object, and with origin and target referring to the outgoing and incoming audience, respectively. An example Move: { @context: <... snipped>, id: "https://activitypub.space/topic/123#activity/move/1761362910015", type: "Move", actor: "https://activitypub.space/uid/1", to: ["https://www.w3.org/ns/activitystreams#Public"], cc: [ "https://activitypub.space/category/1/followers", "https://activitypub.space/category/2/followers", ], object: "https://activitypub.space/topic/1", origin: "https://activitypub.space/category/1", target: "https://activitypub.space/category/2", } The object https://activitypub.space/topic/1 doesn’t necessarily mean anything to most implementors, so unless the object domain is yours, you are expected to resolve it to find the root object (and associated context if necessary.) Would adding a new property like contextRoot pointing to the root-level object be useful for implementors? If target is null, theoretically this could signify the removal of a context from its audience. null values are apparently a no-no in AP so Remove activity is recommended instead. rimu@piefed.social and nutomic@lemmy.ml melroy@kbin.melroy.org I wanted to ping you all as I am interested in your feedback as I move toward drafting this FEP.

Hey @bonfire @mayel and crew, if you ever feel like putting a spec down to attach academic citations to #ActivityPub objects for your Open Science Network, ping me.I have ideas for building something out of https://schema.org/ScholarlyArticle, https://schema.org/citation and dashes of https://w3c.github.io/scholarly-html/ for @encyclia. Could enable e.g. “this post discusses this article”, “find posts related to this publication”, or long-form articles with declarative references.Maybe @jonny has thoughts too?@general

The in-person events at FediCon in Vancouver lit a fire in the Canadian ActivityPub community. One of the louder calls were for a place in the fediverse for ActivityPub discussions; a place for groups to form and for long-running discussions to be had. I was more than happy to get involved. I also wanted such a place, and I’ve discussed it on and off for the past year. ActivityPub development discussions are fragmented across multiple disconnected channels, and none of them fully capture the entirety (or a majority, or even a sizeable minority) of the AP developer community. ActivityPub.Space is my answer to that call. One constant about ActivityPub is that all ActivityPub developers are on the fediverse, and so it only makes sense that discussions about AP development should also take place on the fediverse. At the same time, the “fediverse” isn’t one singular entity. jaz@mastodon.iftas.org famously quipped “There is One Fediverse. There are a Million Fediverses.” While I can’t make guarantees about this site connecting with a million fediverses, I can say that it does connect with the microblogiverse, the blogiverse (WordPress blogs!), and the Threadiverse (Lemmy/Piefed/MBin/NodeBB/Discourse). So how does it work? The site is divided up into several categories: General Discussion is for any non-technical discussions about ActivityPub Technical Discussion is for technical deep-dives Meta contains discussions about this site itself Random is for everything else (there’s always a “Random” category on a forum, isn’t there…?) We also pull in content direct from Fediverse news outlets such as “Week in Fediverse”, “Connected Places”, and “Relay, by We Distribute”. On the threadiverse side, we directly link to several other fediverse-focused communities on Lemmy and Piefed. We utilise a number of relays to both distribute local content out and receive content from the wider microblogiverse. When content comes in via microblogs, they’re not usually categorized, so we check for relevant hashtags and automatically categorize them into one of the local categories. The wonderful thing about this site is that it fully federates, which means you can follow all of these categories from your app of choice. You don’t even have to register a local account if you don’t want to, but you definitely can (and should!) if you want the best experience browsing the categorized topics. The categories today are rather broad, but over time I hope to split them up into smaller topics based on user demand. Give the site a try today!

In May 2024, we launched IFTAS Connect as a community platform to support volunteer moderators, administrators, and safety advocates across the decentralised web. Our vision was to provide a central space for collaboration, resource sharing, and mutual support, especially for those working in independent and often under-resourced environments.Despite several hundred moderators signing up and expressing early interest, sustained engagement across the Connect portal and its associated Matrix Space (a collection of chat rooms) has remained limited. As we evaluate our role in this evolving ecosystem, we believe it is time to step back from hosting a dedicated community platform and refocus our resources where they are most impactful.As a non-profit organisation, IFTAS relies on community support to operate. Our financial and staffing capacity is not unlimited, and hosting platforms such as Connect comes with direct costs, both technical and human. In the current environment, where funding has diminished, we must prioritise sustainability and impact.After 18 months of operating Connect, it is clear that this particular space has not provided the kind of active collaboration we had hoped for. We believe that this may be a reflection of the need for smaller, more targeted, and organically driven networks of support. This is not a failure of the community, but rather an opportunity to rethink how collaboration can best be facilitated across diverse, decentralised projects.We remain deeply grateful to those who participated, contributed resources, and helped build a shared understanding of moderation and safety in federated systems. The need for community remains, even if the model needs to evolve.We extend our sincere thanks to everyone who joined IFTAS Connect, contributed their time, knowledge, and questions, shared resources, supported others, or otherwise helped build the space. Your efforts helped shape the Community Library and informed our broader work in ways that continue to matter. We are especially thankful to the moderators and safety contributors who helped keep the space respectful, accessible, and safe throughout its operation.What’s NextIFTAS Connect and the Matrix Space will remain available for existing accounts until 30 October 2025. After that date, both will be permanently shut down. New accounts can no longer be created.1. Preserving the Community LibraryThe Connect Community Library will be preserved in static form on the IFTAS web site. Unless otherwise marked, all content is published under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 licence, feel free to preserve copies of anything you deem valuable. The full archive will also be made available to any project, server, or individual who wishes to mirror or reuse the material.2. Ongoing News and UpdatesThe aggregated news feed from Connect will transition to a Channel.org feed. This will offer continued updates on trust and safety, regulation, and federated technology developments in a lower-overhead format. When this is ready, we’ll announce it on our main Fediverse account.3. Stay ConnectedIFTAS will not be hosting a new community forum ourselves. However, we will point to third-party community spaces that align with our values. In particular, we encourage moderators to review the discussion forum hosted at @moderation@activitypub.space. This community is available to any moderator on the Fediverse, and participation does not require a separate account. Simply mention @moderation@activitypub.space from your existing account to post or engage in the conversation.4. Private Signal GroupsFor those seeking a more private communication channel, we will be operating a Signal group chat for verified community moderators. Participation will be by request, and membership will require demonstrated moderator responsibilities on a Fediverse server that hosts community accounts. This space will serve as a light-touch backchannel for peer support, coordination, and urgent queries. We will also offer a Signal group for the SW-ISAC, geared toward both admins and moderators to share information about network abuse, spam, illegal content and other threats. Send a direct mention to @iftas@mastodon.iftas.org for access to these groups. 5. Data Privacy and Account DeletionNo member data or content from IFTAS Connect or the Matrix Space will be shared, transferred, or retained after closure. All account information and related backups will be permanently destroyed following the shutdown.Our Continued CommitmentIFTAS was created to support decentralised online communities in building safer, fairer, and more resilient digital spaces. That mission remains unchanged.We will continue advocating for shared resources, moderation tooling, and transparent practices. Our annual survey and other activities will continue.We will maintain our role in threat intelligence sharing, with a focus on coordinated abuse, network harms, and platform-level safety.We will continue working in support of marginalised communities, prioritising human rights, privacy, and safety online and offline.Jaz will continue to attend relevant conferences, maintaining relationships with internet safety regulators and ensuring the perspectives of decentralised communities are represented in wider policy and safety conversations.Looking AheadThe closure of IFTAS Connect is not the end of community collaboration. It is a recalibration. We remain committed to supporting moderators and trust and safety teams with open resources, shared intelligence, and public-interest advocacy. We invite those who share these values to stay connected through our web site, our Mastodon account, the news channel, and future initiatives that reflect the needs of decentralised communities.

LineageOS 23 got released, which inspired me to install it on my Pixel 5. So quick, so seamless. My favourite feature is the PIN scrambling on the lock screen. What’s yours? [image: 1760326461339-1000013987-resized.jpg]