GNU social now supports that initiative with the Web Monetization plugin.

With this, we also introduce an ActivityPub (FEP-8c3f) GS extension gs:webmonetizationWallet. This enables actors to support other actors with Web Monetization in the fediverse.

It looks like this:

Own profile

In the profile of other actors

We also take screenshots of all pages and compare them with the previous, allowing us to spot (possibly) unintended changes in the UI.

The way we do this is by using a docker image derived from node, with pa11y-ci installed, which doesn't have an entrypoint. This then allows us to spin up a webserver, PHP and Redis containers, mimiking a staging environment. pa11y-ci uses a JSON config file to tell it what to do, and handles visiting all pages with the given resolution, logging in and registering any accesibility violations found.

Note that most of these errors are actually the same.

The saved screenshots are then used to detect changes, with ImageMagik's compare, to generate a report on visual changes.

We were already striving for making GNU social accesible, which is clear from the really low number of violations found, but there's always room for improvement :)

This structure has the following implication:

Collection -> OrderedCollection
|-> Notes (known as Feed)
|-> Actors (known as Circle)
|-> Other Object (known as Collection of ...)
  |-> Attachments: AttachmentCollection
  |-> Tags: TagCollection

And it allow us to centralise the scope system in the core, ensuring that no actor will have access to notes or other objects that shouldn't be able to see.

Finally, with this, a plugin such as Note Type Feed Filter can be useful in every note collection (feed).

It also allows plugins such as ActivityPub to translate every collection automatically.

We also introduced the Circle component, which has a UI similar to the Attachments Collections, and enables circle mentions with @#circle_name.

Notes Filter and Sorting Options

Actors Filter and Sorting Options

The Search Component

Results

Note Options

Actor Options

ActivityPub Examples

We haven't implemented federation of Groups yet, but group tags and discussion on how unbounded groups can be federated via ActivityPub has already started.

Concerning federation of traditional groups, we will port our logic from v2 and translate following the same rules as AndStatus because they work, as yvolk beautifully stated :)

Finally, also note that the group actors now have "self-tags", as the other actors, which was a milestone.

With this feature, an actor has more ways to express itself to the community as a whole. This activity is federated using Mastodon's featured collection extension.

Source

latex

Markdown

An album is a specialisation of an attachment collection, which is itself a specialisation of a collection.

Albums were implemented with the Attachment Collections plugin.

Here's how it looks

Adding an attachment (this is in the right sidebar of attachment pages)

List of collections

Viewing a collection of attachments

This milestone could be just this, what's different from any other ActivityPub plugin? How is it better than v2's?

It's better in how it's organised and extensible, check the EVENTS.md for examples.

Video of GNU social v3 exchanging notes with GNU social v2.