# ActivityPub Plugin

**URL:** https://meta.discourse.org/t/activitypub-plugin/266794
**Category:** Plugin
**Tags:** experimental, activitypub
**Created:** [May 31, 2023, 5:21pm UTC](https://meta.discourse.org/t/activitypub-plugin/266794 "2023-05-31T17:21:52Z")
**Posts on this page:** 20
**Page:** 9

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [April 1, 2024, 12:08pm UTC](https://meta.discourse.org/t/activitypub-plugin/266794/165 "2024-04-01T12:08:03Z")

</div>

Ok, can you link me to an example of a post with note tags where the note tags were ignored? And also the note on Mastodon or similar.

If you could indicate where in the post the note tags were applied when the post was first created (as I won’t have access to the edit view / history).

If you could also share what the maximum note character count is currently set at in the ActivityPub site settings.

Thanks!

---

<div class="post-metadata">

### Author: ![gde](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gde/32/481170_2.png) [@gde](https://meta.discourse.org/u/gde)
#### Post date: [April 1, 2024, 12:58pm UTC](https://meta.discourse.org/t/activitypub-plugin/266794/166 "2024-04-01T12:58:29Z")

</div>

I made a couple more tests and what I didn’t expect was that new lines or line breaks must not be used between the `[note][/note]` tags in order for them to be taken into account

It works better once I removed them, but The overall message doesn’t look as good though… I suppose there’s no way to include them ?

---

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [April 1, 2024, 1:27pm UTC](https://meta.discourse.org/t/activitypub-plugin/266794/167 "2024-04-01T13:27:54Z")

</div>

Thanks for the update. Could you share:

1. An example of what is currently working for you.
2. An example of what you expect to be working.
3. Ideally a link to a live version of 1.

That’ll help me test and verify the specific issue you’re referring to. Examples are always helpful to ensure we’re on the same page.

---

<div class="post-metadata">

### Author: ![Mte90](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mte90/32/120441_2.png) [@Mte90](https://meta.discourse.org/u/Mte90)
#### Post date: [April 4, 2024, 8:31am UTC](https://meta.discourse.org/t/activitypub-plugin/266794/168 "2024-04-04T08:31:47Z")

</div>

You can see that [TicketZon: concerti e mostre nel fediverso - Progetti - forum.linux.it](https://forum.linux.it/t/ticketzon-concerti-e-mostre-nel-fediverso/1378) is reported as shared but it isn’t.  
The account exists on mastodon and in the log I have finally something for you:

`[Discourse Activity Pub] https://forum.linux.it/ap/actor/fc1e23a5fc2214ab70c6c0aa1061a4f0 failed to schedule https://forum.linux.it/ap/activity/229b771ac7e5943928795da1122d847d for delivery: no recipients`

```plaintext
/var/www/discourse/plugins/discourse-activity-pub/lib/discourse_activity_pub/delivery_handler.rb:93:in `log_failure'

/var/www/discourse/plugins/discourse-activity-pub/lib/discourse_activity_pub/delivery_handler.rb:35:in `can_deliver?'

/var/www/discourse/plugins/discourse-activity-pub/lib/discourse_activity_pub/delivery_handler.rb:13:in `perform'

/var/www/discourse/plugins/discourse-activity-pub/lib/discourse_activity_pub/delivery_handler.rb:27:in `perform'

/var/www/discourse/plugins/discourse-activity-pub/app/models/concerns/discourse_activity_pub/ap/model_callbacks.rb:140:in `activity_pub_deliver_activity'

/var/www/discourse/plugins/discourse-activity-pub/app/models/concerns/discourse_activity_pub/ap/model_callbacks.rb:38:in `perform_activity_pub_activity'

/var/www/discourse/plugins/discourse-activity-pub/plugin.rb:680:in `block (2 levels) in activate!'

/var/www/discourse/lib/plugin/instance.rb:545:in `block in on'

/var/www/discourse/lib/discourse_event.rb:12:in `block in trigger'

/usr/local/lib/ruby/3.2.0/set.rb:511:in `each_key'
/usr/local/lib/ruby/3.2.0/set.rb:511:in `each'
/var/www/discourse/lib/discourse_event.rb:12:in `trigger'

/var/www/discourse/lib/post_destroyer.rb:115:in `recover'

/var/www/discourse/app/controllers/topics_controller.rb:689:in `recover'

actionpack-7.0.8.1/lib/action_controller/metal/basic_implicit_render.rb:6:in `send_action'

actionpack-7.0.8.1/lib/abstract_controller/base.rb:215:in `process_action'

actionpack-7.0.8.1/lib/action_controller/metal/rendering.rb:165:in `process_action'

actionpack-7.0.8.1/lib/abstract_controller/callbacks.rb:234:in `block in process_action'

activesupport-7.0.8.1/lib/active_support/callbacks.rb:118:in `block in run_callbacks'

/var/www/discourse/app/controllers/application_controller.rb:423:in `block in with_resolved_locale'

i18n-1.14.4/lib/i18n.rb:322:in `with_locale'

/var/www/discourse/app/controllers/application_controller.rb:423:in `with_resolved_locale'

activesupport-7.0.8.1/lib/active_support/callbacks.rb:127:in `block in run_callbacks'

activesupport-7.0.8.1/lib/active_support/callbacks.rb:138:in `run_callbacks'

actionpack-7.0.8.1/lib/abstract_controller/callbacks.rb:233:in `process_action'

actionpack-7.0.8.1/lib/action_controller/metal/rescue.rb:23:in `process_action'

actionpack-7.0.8.1/lib/action_controller/metal/instrumentation.rb:67:in `block in process_action'

activesupport-7.0.8.1/lib/active_support/notifications.rb:206:in `block in instrument'

activesupport-7.0.8.1/lib/active_support/notifications/instrumenter.rb:24:in `instrument'

activesupport-7.0.8.1/lib/active_support/notifications.rb:206:in `instrument'

actionpack-7.0.8.1/lib/action_controller/metal/instrumentation.rb:66:in `process_action'

actionpack-7.0.8.1/lib/action_controller/metal/params_wrapper.rb:259:in `process_action'

activerecord-7.0.8.1/lib/active_record/railties/controller_runtime.rb:27:in `process_action'

actionpack-7.0.8.1/lib/abstract_controller/base.rb:151:in `process'

actionview-7.0.8.1/lib/action_view/rendering.rb:39:in `process'

rack-mini-profiler-3.3.1/lib/mini_profiler/profiling_methods.rb:89:in `block in profile_method'

actionpack-7.0.8.1/lib/action_controller/metal.rb:188:in `dispatch'

actionpack-7.0.8.1/lib/action_controller/metal.rb:251:in `dispatch'

actionpack-7.0.8.1/lib/action_dispatch/routing/route_set.rb:49:in `dispatch'

actionpack-7.0.8.1/lib/action_dispatch/routing/route_set.rb:32:in `serve'

actionpack-7.0.8.1/lib/action_dispatch/journey/router.rb:50:in `block in serve'

actionpack-7.0.8.1/lib/action_dispatch/journey/router.rb:32:in `each'

actionpack-7.0.8.1/lib/action_dispatch/journey/router.rb:32:in `serve'

actionpack-7.0.8.1/lib/action_dispatch/routing/route_set.rb:852:in `call'

/var/www/discourse/lib/middleware/omniauth_bypass_middleware.rb:64:in `call'

rack-2.2.8.1/lib/rack/tempfile_reaper.rb:15:in `call'

rack-2.2.8.1/lib/rack/conditional_get.rb:40:in `call'

rack-2.2.8.1/lib/rack/head.rb:12:in `call'

actionpack-7.0.8.1/lib/action_dispatch/http/permissions_policy.rb:38:in `call'

/var/www/discourse/lib/content_security_policy/middleware.rb:12:in `call'

/var/www/discourse/lib/middleware/anonymous_cache.rb:393:in `call'

/var/www/discourse/lib/middleware/csp_script_nonce_injector.rb:12:in `call'

/var/www/discourse/config/initializers/008-rack-cors.rb:14:in `call'

rack-2.2.8.1/lib/rack/session/abstract/id.rb:266:in `context'

rack-2.2.8.1/lib/rack/session/abstract/id.rb:260:in `call'

actionpack-7.0.8.1/lib/action_dispatch/middleware/cookies.rb:704:in `call'

actionpack-7.0.8.1/lib/action_dispatch/middleware/callbacks.rb:27:in `block in call'

activesupport-7.0.8.1/lib/active_support/callbacks.rb:99:in `run_callbacks'

actionpack-7.0.8.1/lib/action_dispatch/middleware/callbacks.rb:26:in `call'

actionpack-7.0.8.1/lib/action_dispatch/middleware/debug_exceptions.rb:28:in `call'

actionpack-7.0.8.1/lib/action_dispatch/middleware/show_exceptions.rb:29:in `call'

logster-2.19.1/lib/logster/middleware/reporter.rb:40:in `call'

railties-7.0.8.1/lib/rails/rack/logger.rb:40:in `call_app'

railties-7.0.8.1/lib/rails/rack/logger.rb:27:in `call'

/var/www/discourse/config/initializers/100-quiet_logger.rb:20:in `call'

/var/www/discourse/config/initializers/100-silence_logger.rb:29:in `call'

actionpack-7.0.8.1/lib/action_dispatch/middleware/remote_ip.rb:93:in `call'

actionpack-7.0.8.1/lib/action_dispatch/middleware/request_id.rb:26:in `call'

/var/www/discourse/lib/middleware/enforce_hostname.rb:24:in `call'

rack-2.2.8.1/lib/rack/method_override.rb:24:in `call'

actionpack-7.0.8.1/lib/action_dispatch/middleware/executor.rb:14:in `call'

rack-2.2.8.1/lib/rack/sendfile.rb:110:in `call'

actionpack-7.0.8.1/lib/action_dispatch/middleware/host_authorization.rb:131:in `call'

rack-mini-profiler-3.3.1/lib/mini_profiler.rb:191:in `call'

message_bus-4.3.8/lib/message_bus/rack/middleware.rb:60:in `call'

/var/www/discourse/lib/middleware/request_tracker.rb:236:in `call'

railties-7.0.8.1/lib/rails/engine.rb:530:in `call'

railties-7.0.8.1/lib/rails/railtie.rb:226:in `public_send'

railties-7.0.8.1/lib/rails/railtie.rb:226:in `method_missing'

rack-2.2.8.1/lib/rack/urlmap.rb:74:in `block in call'

rack-2.2.8.1/lib/rack/urlmap.rb:58:in `each'

rack-2.2.8.1/lib/rack/urlmap.rb:58:in `call'

unicorn-6.1.0/lib/unicorn/http_server.rb:634:in `process_client'
unicorn-6.1.0/lib/unicorn/http_server.rb:739:in `worker_loop'
unicorn-6.1.0/lib/unicorn/http_server.rb:547:in `spawn_missing_workers'
unicorn-6.1.0/lib/unicorn/http_server.rb:143:in `start'
unicorn-6.1.0/bin/unicorn:128:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/3.2.0/bin/unicorn:25:in `load'
/var/www/discourse/vendor/bundle/ruby/3.2.0/bin/unicorn:25:in `<main>'

```

---

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [April 4, 2024, 9:02am UTC](https://meta.discourse.org/t/activitypub-plugin/266794/169 "2024-04-04T09:02:52Z")

</div>

> [@gde](#):
>
> I didn’t expect was that new lines or line breaks must not be used between the `[note][/note]` tags in order for them to be taken into account

I’ve added block support to `[note][/note]` tags in this PR (it needs to be reviewed and merged)

[https://github.com/discourse/discourse-activity-pub/pull/81](https://github.com/discourse/discourse-activity-pub/pull/81)

This will be standard Discourse markdown block support following the approach described here

> [@Discourse CommonMark migration plans confetti\_ball balloon](https://meta.discourse.org/t/discourse-commonmark-migration-plans-confetti-ball-balloon/64234/6):
>
> I may pull this out to another topic, but I feel that I need to hammer_and_wrench hamster some stuff. Inline multiline quote[quote]that spans lines and blocks [/quote]Is a terrible format should not be supported Instead joy_catman_in_tuxedo:t4 Inline multiline quote [quote] that spans lines and blocks [/quote] Is a terrible format should not be supported At least the new format can not be as unreadable.

So this

```plaintext
[note]
First line

Second line
[/note]

Third line

```

Will produce a Note content of

```plaintext
"First line\nSecond line"

```

Whereas this

```plaintext
[note]First line

Second line[/note]

Third line

```

Will produce a Note content of

```plaintext
First line\nSecond line\nThird line

```

(i.e. the `[note][/note]` tags are ignored and removed)

> [@Mte90](#):
>
> The account exists on mastodon and in the log I have finally something for you:
> 
> `[Discourse Activity Pub] https://forum.linux.it/ap/actor/fc1e23a5fc2214ab70c6c0aa1061a4f0 failed to schedule https://forum.linux.it/ap/activity/229b771ac7e5943928795da1122d847d for delivery: no recipients`

This means there is no-one following the Category actor, so it’s got no-one to deliver to.

---

<div class="post-metadata">

### Author: ![Mte90](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mte90/32/120441_2.png) [@Mte90](https://meta.discourse.org/u/Mte90)
#### Post date: [April 4, 2024, 9:23am UTC](https://meta.discourse.org/t/activitypub-plugin/266794/170 "2024-04-04T09:23:33Z")

</div>

> [@angus](#):
>
> This means there is no-one following the Category actor, so it’s got no-one to deliver to.

Uhm so for the same reason there should be the green marker in the post that says that was published or not?  
Now I am following all the various categories on mastodon and I will do a test.

---

<div class="post-metadata">

### Author: ![Mte90](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mte90/32/120441_2.png) [@Mte90](https://meta.discourse.org/u/Mte90)
#### Post date: [April 4, 2024, 9:32am UTC](https://meta.discourse.org/t/activitypub-plugin/266794/171 "2024-04-04T09:32:10Z")

</div>

**I can confirm that works it is required that the account is followed.**

---

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [April 4, 2024, 9:55am UTC](https://meta.discourse.org/t/activitypub-plugin/266794/172 "2024-04-04T09:55:21Z")

</div>

Perhaps what you’re expecting is that without any followers the posts of the Category Actor would still show as toots on a representation of the Actor on Mastodon? That would require Mastodon to implement a version of outbox importing, i.e.

[https://github.com/mastodon/mastodon/issues/34](https://github.com/mastodon/mastodon/issues/34)

Note that this plugin will be supporting outbox importing soon (the functionality is already built and will be exposed to admins in upcoming updates). In other words, you will be able to backfill the content from a remote actor.

---

<div class="post-metadata">

### Author: ![roke\_julian\_lockhart](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/roke_julian_lockhart/32/540179_2.png) [@roke\_julian\_lockhart](https://meta.discourse.org/u/roke_julian_lockhart)
#### Post date: [April 9, 2024, 2:22pm UTC](https://meta.discourse.org/t/activitypub-plugin/266794/173 "2024-04-09T14:22:06Z")

</div>

It works for me now, using [Making sure you're not a bot!](https://koji.fedoraproject.org/koji/buildinfo?buildID=2426311).

---

<div class="post-metadata">

### Author: ![ernestdefoe](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ernestdefoe/32/118137_2.png) [@ernestdefoe](https://meta.discourse.org/u/ernestdefoe)
#### Post date: [April 11, 2024, 2:25am UTC](https://meta.discourse.org/t/activitypub-plugin/266794/174 "2024-04-11T02:25:03Z")

</div>

I’s getting the whole note not listed error as well. What am I doing wrong? Did I need to put an @ symbol in the section shown below?

 ![Screenshot 2024-04-10 212413](https://global.discourse-cdn.com/meta/original/4X/e/1/c/e1c420b70457f3ff0882526b8239b8d81267f31c.png)

I’m not sure what I am doing wrong here.

---

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [April 11, 2024, 5:55am UTC](https://meta.discourse.org/t/activitypub-plugin/266794/175 "2024-04-11T05:55:07Z")

</div>

> [@ernestdefoe](#):
>
> I’s getting the whole note not listed error as wel

Sorry, I don’t quite follow. Could you explain a bit more?

---

<div class="post-metadata">

### Author: ![ernestdefoe](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ernestdefoe/32/118137_2.png) [@ernestdefoe](https://meta.discourse.org/u/ernestdefoe)
#### Post date: [April 11, 2024, 11:02am UTC](https://meta.discourse.org/t/activitypub-plugin/266794/176 "2024-04-11T11:02:08Z")

</div>

Nothing is being published to ActivityPub.

---

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [April 11, 2024, 12:00pm UTC](https://meta.discourse.org/t/activitypub-plugin/266794/177 "2024-04-11T12:00:26Z")

</div>

> [@ernestdefoe](#):
>
> Nothing is being published to ActivityPub

Could you explain a bit more about what you expect to happen? For example

1. I make a post on my forum.
2. I expect to see…

---

<div class="post-metadata">

### Author: ![ernestdefoe](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ernestdefoe/32/118137_2.png) [@ernestdefoe](https://meta.discourse.org/u/ernestdefoe)
#### Post date: [April 11, 2024, 12:11pm UTC](https://meta.discourse.org/t/activitypub-plugin/266794/178 "2024-04-11T12:11:12Z")

</div>

Well I figured that when I make a post in the categories I have this enabled in to be published on ActivityPub and they aren’t. They aren’t being published at all.

---

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [April 11, 2024, 12:21pm UTC](https://meta.discourse.org/t/activitypub-plugin/266794/179 "2024-04-11T12:21:22Z")

</div>

What do you mean by “ActivityPub”? Where are you expecting to see? I’m sorry for the questions. I want to get to the bottom of the issue from a usability perspective, so I’m trying to get you to explain it in your own words 🙂

You may have the same issue which others have reported, which is that there are no followers of your category. The post isn’t going to appear anywhere if no-one is following it because there’s no-where to send it to. Or in other words

> [@ActivityPub Plugin](https://meta.discourse.org/t/activitypub-plugin/266794/171):
>
> I can confirm that works it is required that the account is followed.

ActivityPub publishing relies on follow relationships to work. Your category actor will still show up on Mastodon (or other services) without any followers, but keep in mind that what Mastodon shows you there is up to Mastodon.

If you could walk me through your expectations a bit more it would really help! Maybe if you could give an example of another ActivityPub service where you feel this is working? Thanks.

---

<div class="post-metadata">

### Author: ![ernestdefoe](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ernestdefoe/32/118137_2.png) [@ernestdefoe](https://meta.discourse.org/u/ernestdefoe)
#### Post date: [April 11, 2024, 12:24pm UTC](https://meta.discourse.org/t/activitypub-plugin/266794/180 "2024-04-11T12:24:24Z")

</div>

The little eye symbol has a line through it and when I click on it it says this not been published.

 ![IMG_1371](https://global.discourse-cdn.com/meta/original/4X/1/0/0/100beb331229716cdb6a6cf340a94ac7d03a9c91.jpeg)

---

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [April 11, 2024, 12:26pm UTC](https://meta.discourse.org/t/activitypub-plugin/266794/181 "2024-04-11T12:26:47Z")

</div>

Most likely because there is no-one following your category. If you turn on the site setting `activity_pub_verbose_logging` and look in your logs you will probably see a message that looks like this

> [@Mte90](#):
>
> [Discourse Activity Pub] [News - forum.linux.it](https://forum.linux.it/ap/actor/fc1e23a5fc2214ab70c6c0aa1061a4f0) failed to schedule [https://forum.linux.it/ap/activity/229b771ac7e5943928795da1122d847d](https://forum.linux.it/ap/activity/229b771ac7e5943928795da1122d847d) for delivery: no recipients

I’m definitely going to put a “reason” in that modal as this has come up a few times now! Follow your category on Mastodon, and then create a new topic.

\*\*edit or perhaps I will just change it to “published” in that scenario, as it does in fact add the activity to the outbox. It just doesn’t send it anywhere (as it has nowhere to send it to). So it technically is “published” (i.e. it’s in the outbox).

---

<div class="post-metadata">

### Author: ![eisammy](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eisammy/32/528804_2.png) [@eisammy](https://meta.discourse.org/u/eisammy)
#### Post date: [April 12, 2024, 3:27pm UTC](https://meta.discourse.org/t/activitypub-plugin/266794/182 "2024-04-12T15:27:09Z")

</div>

It’s a good moment to implement this protocol or I should wait a few? I wish open my community to fediverse and archive whole contents for everyone and forever but I had read about Mastodon and Lemmy and I suppose that not the while new laws are rolling around.

---

<div class="post-metadata">

### Author: ![mcdanlj](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mcdanlj/32/131829_2.png) [@mcdanlj](https://meta.discourse.org/u/mcdanlj)
#### Post date: [April 12, 2024, 6:09pm UTC](https://meta.discourse.org/t/activitypub-plugin/266794/183 "2024-04-12T18:09:45Z")

</div>

> [@eisammy](#):
>
> I suppose that not the while new laws are rolling around.

I think that discussion of the legal circumstances in any particular jurisdiction are probably outside the scope of this topic. 🙂

---

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [April 15, 2024, 1:12pm UTC](https://meta.discourse.org/t/activitypub-plugin/266794/184 "2024-04-15T13:12:32Z")

</div>

A few updates to share here! All ActivityPub configuration will soon move to a unified administration panel:

[https://github.com/discourse/discourse-activity-pub/pull/78](https://github.com/discourse/discourse-activity-pub/pull/78)

Following tags will soon become possible:

[https://github.com/discourse/discourse-activity-pub/pull/84](https://github.com/discourse/discourse-activity-pub/pull/84)

Along with NodeBB, Flarum, Lemmy and a number of other ActivityPub platforms we’ve created a W3C working group to better align Forum and Link sharing software in the Fediverse. We’re already coordinating that work via ActivityPub. For example our next meeting is being organised in a single topic across both Discourse and NodeBB

> **[Our next meeting](https://socialhub.activitypub.rocks/t/our-next-meeting/4079)**
>
> Last Meeting Recording Passcode: z+1\*4pUB Minutes To refresh your memory, you can read the minutes of last week’s meeting here. Follow up The Social Web Community Group approved our application to turn this into a Task Force. Async work...

[Previous page](https://meta.discourse.org/t/activitypub-plugin/266794.md?page=8)

[Next page](https://meta.discourse.org/t/activitypub-plugin/266794.md?page=10)
