'
>
> sidekiq-6.5.9/lib/sidekiq/processor.rb:131:in `block (4 levels) in dispatch'
>
> sidekiq-6.5.9/lib/sidekiq/processor.rb:263:in `stats'
>
> sidekiq-6.5.9/lib/sidekiq/processor.rb:126:in `block (3 levels) in dispatch'
>
> sidekiq-6.5.9/lib/sidekiq/job_logger.rb:13:in `call'
>
> sidekiq-6.5.9/lib/sidekiq/processor.rb:125:in `block (2 levels) in dispatch'
>
> sidekiq-6.5.9/lib/sidekiq/job_retry.rb:80:in `global'
>
> sidekiq-6.5.9/lib/sidekiq/processor.rb:124:in `block in dispatch'
>
> sidekiq-6.5.9/lib/sidekiq/job_logger.rb:39:in `prepare'
>
> sidekiq-6.5.9/lib/sidekiq/processor.rb:123:in `dispatch'
>
> sidekiq-6.5.9/lib/sidekiq/processor.rb:168:in `process'
>
> sidekiq-6.5.9/lib/sidekiq/processor.rb:78:in `process_one'
>
> sidekiq-6.5.9/lib/sidekiq/processor.rb:68:in `run'
>
> sidekiq-6.5.9/lib/sidekiq/component.rb:8:in `watchdog'
>
> sidekiq-6.5.9/lib/sidekiq/component.rb:17:in `block in safe_thread'
>
> ```
The Note does not seem to appear in my feed š¢
(feel free to move this message to a more appropriate place)
---
### Author:  [@pmusaraj](https://meta.discourse.org/u/pmusaraj)
#### Post date: [June 1, 2023, 3:55pm UTC](https://meta.discourse.org/t/activitypub-plugin/266794/4 "2023-06-01T15:55:04Z")
> [@mcdanlj](#):
>
> It would be nice to provide a profile picture for each designated actor. In Mastodon, I just see the gray elephant picture for each category actor, and Iād love to add a little personality here.
In the long run, I agree, this should be specific per actor and configurable. But atm, the site logo _should_ be picked up. It does for me for `@feature@meta.discourse.org`:
---
### Author:  [@mcdanlj](https://meta.discourse.org/u/mcdanlj)
#### Post date: [June 1, 2023, 4:29pm UTC](https://meta.discourse.org/t/activitypub-plugin/266794/5 "2023-06-01T16:29:23Z")
> [@pmusaraj](#):
>
> But atm, the site logo _should_ be picked up. It does for me for `@feature@meta.discourse.org`:
Ok, probably this was related to one of the errors I saw, then. Site logo makes lots of sense to me.
Thinking about thisā¦ If there would be a possibility to use the category color in there it would be awesome but I donāt know whether there would be a place for that.
---
### Author:  [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [June 1, 2023, 5:33pm UTC](https://meta.discourse.org/t/activitypub-plugin/266794/6 "2023-06-01T17:33:01Z")
I retried andā¦
Partly working: the note was shortened a bit too much (71 characters) from the original:
> Weāve been waiting for it: now thanks to Angus McLeod and the #pavilion team, as well as CDCK, Inc. the company behind #Discourse, the #SocialHub is now federated! You can follow @fediverse@socialhub.activitypub.rocks for general announcements, and @feps@socialhub.activitypub.rocks for Fediverse Enhancement Proposals.
> š¤
---
### Author:  [@sunjam](https://meta.discourse.org/u/sunjam)
#### Post date: [June 1, 2023, 7:11pm UTC](https://meta.discourse.org/t/activitypub-plugin/266794/7 "2023-06-01T19:11:56Z")
General recommendation:
Think on it for a few days _ **before** _ you enable Activitypub integration.
Remember that these accounts will be listed forever within the fediverse of social networks and can create confusion if you realize the account/category name should be changed after the fact. ā¤
---
### Author:  [@mcdanlj](https://meta.discourse.org/u/mcdanlj)
#### Post date: [June 1, 2023, 7:23pm UTC](https://meta.discourse.org/t/activitypub-plugin/266794/8 "2023-06-01T19:23:47Z")
I believe that in the _long_ run, it would be possible to additionally implement account movement to rename the actor for a category. Itās just more work that has to be valuable to someone willing to do the work, so I doubt itās a short term thing. āŗ At least, I hope it comes later than other more valuable work! š
That doesnāt invalidate your point at all.
---
### Author:  [@angus](https://meta.discourse.org/u/angus)
#### Post date: [June 2, 2023, 9:07am UTC](https://meta.discourse.org/t/activitypub-plugin/266794/10 "2023-06-02T09:07:32Z")
Thanks for the feedback guys š
@hellekin This will address the exceptions you were reporting. @mcdanlj It will also address the second exception you reported (same issue).
[https://github.com/discourse/discourse-activity-pub/pull/6](https://github.com/discourse/discourse-activity-pub/pull/6)
@mcdanlj The first issue you reported is a little stranger how frequently are you seeing it? Could you possibly share more details?
> [@mcdanlj](#):
>
> So if you would consider an āalso federate sub-categoriesā option, that might inform my plans
Thanks for the feedback on that, will definitely consider it in phase 2 of the work š
> [@mcdanlj](#):
>
> I think that it might be interesting to also add a site-wide setting for an ActivityPub actor that federates all public posts on a site
I think thatās probably not going to happen in phase 2, but noted š
> [@mcdanlj](#):
>
> For others here, what it _really_ means is that if you federate, editing is currently disabled on all posts as soon as they are federated (except for posts with a literal `[note]...[/note]` section); this message shows up only when you try to _save_ your edit
Editing is only disabled on the content of the post that makes up the Note. If you donāt use the Note tags, thatās the first 500 characters, or whatever you set `activity pub note excerpt maxlength` to. One of the things Iām definitely considering for phase 2 is to _require_ `[note][/note]` tags for a Note as I can see confusion arising out of this.
> [@mcdanlj](#):
>
> I canāt turn this on without the ability to disable this control (or the control being removed because edits are federated). By way of a general example applicable beyond such trusting sites, any category with wiki-mode posts will be broken by setting up federation for that category.
You can address this by using `[note][/note]` tags to separate the Note from the other content.
> [@mcdanlj](#):
>
> I tried to delete a federated post that I had made a wiki, and got this:
Noted! We havenāt explicitly tested this with wiki posts. I havenāt been able to reproduce your issue with deleting wiki posts so far. Can you reliably reproduce it? Iāve added some specs in this PR which are all passing for that scenario, but keen to get to the bottom of that one.
[https://github.com/discourse/discourse-activity-pub/pull/7](https://github.com/discourse/discourse-activity-pub/pull/7)
> [@hellekin](#):
>
> Partly working: the note was shortened a bit too much (71 characters) from the original:
The excerpt parsing is currently handled by the same system used by the topic excerpt parsing in Discourse (for the purposes of the topic list) which is probably why it cut out a fair chunk of that (topic list excerpts would have as well). I think we might need to use a separate parser as I can forsee this creating a few issues. Sit tight on this one; itāll definitely be addressed in phase 2.
> [@sunjam](#):
>
> Remember that these accounts will be listed forever within the fediverse of social networks and can create confusion if you realize the account/category name should be changed after the fact.
Keep in mind that you can change the display name as much as you like and that the limitation on changing the username is not unique to this plugin. So while what you say is true, this is true for a fair chunk of the fediverse.
> **[Changeable usernames?](https://socialhub.activitypub.rocks/t/changeable-usernames/830)**
>
> Itās me and my weird edge cases again š In the spec, thereās nothing that inherently prevents one from changing their username, yet the very idea of it seems to be very much opposed by most of the community ā or, at least, the Mastodon team. So...
Moreover, I havenāt included the username in the Actorās id, partly to allow for the possibility of adding the ability to change the username in the future.
> [@mcdanlj](#):
>
> it would be possible to additionally implement account movement to rename the actor for a category
The pluginās ActivityPub data is abstracted from Discourseās data. Thereās no inherent limitation in changing the Discourse model (i.e. what category) an actor is associated with. You could even possibly associate the actor with a different _type_ of Discourse model in the future, i.e. associate an Actor you created for a category with a user instead (the relationship between Actors and Discourse models is polymorphic). Not saying these will be explicitly added as features, but more to say that there arenāt hard limitations in this respect.
In general, yes itās worth considering what categories you want as actors, but overall this implementation has a relatively high degree of flexibility so your degree of concern should be relative to that context. Iāve explained a little more about the nature of the data flow in the plugin, which further elucidates this point, here
> **[Adding federation support to Discourse](https://socialhub.activitypub.rocks/t/adding-federation-support-to-discourse/2966/6?u=angus)**
>
> Thanks! The best way to think about the implementation is that it can support FEP-1b12 (aka the Lemmy implementation). The first version aims at an integration with Mastodon, so it doesnāt look like FEP-1b12. But that will be quite doable in...
Thanks again everyone! Itās great to have engaged users.
---
### Author:  [@mcdanlj](https://meta.discourse.org/u/mcdanlj)
#### Post date: [June 2, 2023, 11:55am UTC](https://meta.discourse.org/t/activitypub-plugin/266794/11 "2023-06-02T11:55:30Z")
> [@angus](#):
>
> @mcdanlj The first issue you reported is a little stranger how frequently are you seeing it? Could you possibly share more details?
I think it was associated with deleting posts, since I deleted three test posts and there were three instances of the error.
> [@angus](#):
>
> One of the things Iām definitely considering for phase 2 is to _require_ `[note][/note]` tags for a Note as I can see confusion arising out of this.
That would make it absolutely unusable for my site. Iām not trying to use Discourse as a harder way to write posts to the fediverse than just writing them in Mastodon. Trying to force my entire community to start using `[note]...[/note]` bbcode annotations, including the frequent new site users seeking help, would be a non-starter.
> [@angus](#):
>
> You can address this by using `[note][/note]` tags to separate the Note from the other content.
No, I definitely canāt. Itās not _about_ me. Itās about my site users, who are Discourse users, not discourse/discourse-activity-pub.git users.
Itās just an edit.
Federating edits is normal. To the best of my understanding, most of the widely-used ActivityPub implementations out there have allowed edits for a long time. Mastodon was the odd hold-out among popular implementations until last year when they finally caved and allowed edits.
I recognize that edits werenāt part of the MVP release, but until it either federates edits or gives me the option to turn off making the note uneditable, I canāt turn this on for my site. I donāt know whether my use case is weird or normal, of course.
My own goal for using the ActivityPub plugin is to make it easier to follow and share content as it is being created by my community forum members using Discourse. Itās not to use Discourse as a weird uneditable post-only replacement for Mastodon. āŗ
My understanding is that you do intend to eventually support federating edits, since the error message says ānot currently supportedā ā is that right? In that case, this is all just a temporary limitation and our difference in use case are not important. But it does make me wonder about investing effort into protecting edits vs. supporting federating edits.
> [@angus](#):
>
> We havenāt explicitly tested this with wiki posts. I havenāt been able to reproduce your issue with deleting wiki posts so far. Can you reliably reproduce it?
I had forgotten to remove the `retort` plugin from my sandbox site when I removed it from my production site. Removing `retort` fixed both the weird error log and the weird error message. My mistake!
> [@angus](#):
>
> (the relationship between Actors and Discourse models is polymorphic).
Does this mean that as the plugin stands today, we could use the same actor for multiple categories? Or that the data model is very flexible and the implementation details are easy to change?
> [@angus](#):
>
> The excerpt parsing is currently handled by the same system used by the topic excerpt parsing in Discourse (for the purposes of the topic list) which is probably why it cut out a fair chunk of that (topic list excerpts would have as well). I think we might need to use a separate parser as I can forsee this creating a few issues. Sit tight on this one; itāll definitely be addressed in phase 2.
FWIW in my use case, my preference would be to post the whole thing without any limitations. I know thatās not how others might configure it, but I think in the end I would set the max size to the same as the max size for a post on my Discourse, which isā¦ large! āŗ
---
### Author:  [@angus](https://meta.discourse.org/u/angus)
#### Post date: [June 2, 2023, 12:26pm UTC](https://meta.discourse.org/t/activitypub-plugin/266794/12 "2023-06-02T12:26:26Z")
> [@mcdanlj](#):
>
> I think it was associated with deleting posts, since I deleted three test posts and there were three instances of the error.
Gotcha, Iāll investigate further soon.
> [@mcdanlj](#):
>
> No, I definitely canāt. Itās not _about_ me. Itās about my site users, who are Discourse users, not discourse/discourse-activity-pub.git users.
Understood. My comment was more that editing non-note content is indeed possible after publication currently. Youāre right that this first version is not going to be without its UX issues for general use by any user. It does support other uses quite well though, e.g. federating announcements.
> [@mcdanlj](#):
>
> My understanding is that you do intend to eventually support federating edits, since the error message says ānot currently supportedā ā is that right? In that case, this is all just a temporary limitation and our difference in use case are not important. But it does make me wonder about investing effort into protecting edits vs. supporting federating edits.
Yes, weāll be adding support for editing Note content post-publication in phase 2. Note that editing is currently supported prior to the note being published. When you build something like this you have to reduce the number of moving parts as much as possible.
> [@mcdanlj](#):
>
> Does this mean that as the plugin stands today, we could use the same actor for multiple categories?
No, not yet. Could you explain what you mean here a bit more? Are you thinking of having a site-wide actor or are you more thinking about the sub-category issue?
> [@mcdanlj](#):
>
> Or that the data model is very flexible and the implementation details are easy to change?
Yes, although I wouldnāt necessarily use the term āeasyā š
> [@mcdanlj](#):
>
> FWIW in my use case, my preference would be to post the whole thing without any limitations. I know thatās not how others might configure it, but I think in the end I would set the max size to the same as the max size for a post on my Discourse, which isā¦ large!
Iām curious where youāre anticipating federating the unrestricted content? Genuine question; I want to understand where youāre coming from a bit more here.
---
### Author:  [@mcdanlj](https://meta.discourse.org/u/mcdanlj)
#### Post date: [June 2, 2023, 1:50pm UTC](https://meta.discourse.org/t/activitypub-plugin/266794/13 "2023-06-02T13:50:03Z")
> [@angus](#):
>
> Gotcha, Iāll investigate further soon.
I forgot to edit that out after discovering that my leaving `retort` in place accidentally was the source of the error. š³
Oops.
> [@angus](#):
>
> Yes, weāll be adding support for editing Note content post-publication in phase 2.
Good enough! š
Iāll not worry about this any more, and in phase 2 Iāll help test that.
> [@angus](#):
>
> Are you thinking of having a site-wide actor or are you more thinking about the sub-category issue?
I vaguely wondered about both, but it was a low-value question. Was just curious how far I could carry my experimentation with my staging site, and didnāt want to try things that were known to be impossible already. š
> [@angus](#):
>
> Iām curious where youāre anticipating federating the unrestricted content? Genuine question; I want to understand where youāre coming from a bit more here.
Iāll try!
Context: Mastodon limits the length of post it will allow users to _author_ but not the length of post it will _display._ I run a Mastodon-glitch server configured with a 2000-character limit; Iāve seen several people post about configuring a 31337-character limit (because _of course_). I see long posts in my feed from folks using pleroma, akkoma, etc.
We have some really cool content showing up on Maker Forums (my discourse) from time to time (in my opinion, anyway!), and Iād like to promote it on the Fediverse generally to make it accessible to a wider audience. I know that Mastodon has been opinionated that 500 characters is the magic length for microblogging ā but ActivityPub isnāt limited to microblogging. Itās federation, including but not limited to microblogging. When I follow an ActivityPub actor in my Mastodon account, itās not limited to short posts. I can read, comment on, and boost longer posts.
So the āwhere youāre anticipating federatingā is a confusing question to me.
- I would boost the content from my Mastodon-glitch server. Boosts do not apply the character limit that applies to authoring posts even on stock Mastodon.
- I would expect community members to follow from any ActivityPub server (recognizing this will be more Mastodon than others at least right now), and they wonāt all have the same opinionated view of how long an ActivityPub note should be.
Ultimately, as the server administrator, Iām not in control of where this content is federated to. This is the decision of every _follower._ Itās not obvious to me why excepting vs federating the entire discourse post as an activitypub note would be the default even for followers on Mastodon, but more so throughout the Fediverse.
Iām not sure that answers your question. But Iām not sure I understand it well, either. š Happy to dive deeper on this if youād like.
---
### Author:  [@angus](https://meta.discourse.org/u/angus)
#### Post date: [June 2, 2023, 3:11pm UTC](https://meta.discourse.org/t/activitypub-plugin/266794/14 "2023-06-02T15:11:16Z")
> [@mcdanlj](#):
>
> I forgot to edit that out after discovering that my leaving `retort` in place accidentally was the source of the error. š³
No worries! Glad weāve covered the exceptions for now then. Let us know if you see any more. @hellekin Likewise, let us know if you see any other issues or strange behaviour.
> [@mcdanlj](#):
>
> Iāll not worry about this any more, and in phase 2 Iāll help test that.
Great! Thank you.
> [@mcdanlj](#):
>
> Iām not sure that answers your question
It does! Thank you, itās useful context for our planning of phase 2.
---
### Author:  [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [June 2, 2023, 3:17pm UTC](https://meta.discourse.org/t/activitypub-plugin/266794/15 "2023-06-02T15:17:30Z")
Iām about to upgrade to the latest version. One thing that would be useful is to choose the audience: whether the post will be public or followers-only. Now itās the latter, so we cannot boost it, and must follow the account prior to receiving notices. I appreciate that because it remains experimental, but it should definitely be an option to post publicly so we can advertise the feature more widely to the Fedizens š
---
### Author:  [@angus](https://meta.discourse.org/u/angus)
#### Post date: [June 2, 2023, 3:20pm UTC](https://meta.discourse.org/t/activitypub-plugin/266794/16 "2023-06-02T15:20:41Z")
> [@hellekin](#):
>
> One thing that would be useful is to choose the audience: whether the post will be public or followers-only
Yes, thatās something weāll be considering in phase 2 š
---
### Author:  [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [June 2, 2023, 3:32pm UTC](https://meta.discourse.org/t/activitypub-plugin/266794/17 "2023-06-02T15:32:07Z")
Do you have a public roadmap for the development phases?
---
### Author:  [@angus](https://meta.discourse.org/u/angus)
#### Post date: [June 2, 2023, 3:34pm UTC](https://meta.discourse.org/t/activitypub-plugin/266794/18 "2023-06-02T15:34:49Z")
Thereās no public roadmap, but I will let you know when we figure out the specifics. Any reasonable suggestions for what should be in it are welcome! Specific use case examples like @mcdanljās are always helpful too.
---
### Author:  [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [June 2, 2023, 6:58pm UTC](https://meta.discourse.org/t/activitypub-plugin/266794/19 "2023-06-02T18:58:13Z")
I made some proposals on the SocialHub that were already made here some time agoā¦
> **[Adding federation support to Discourse](https://socialhub.activitypub.rocks/t/adding-federation-support-to-discourse/2966/9?u=how)**
>
> My top features would be: Enable public postings ā so that the Fediverse can boost announcements Enable full posting of Notes within \[note\]\[/note\] up to 500 chars Maybe add a character counter in the composer (but we can count ourselves) ...
---
### Author:  [@mcdanlj](https://meta.discourse.org/u/mcdanlj)
#### Post date: [June 2, 2023, 7:36pm UTC](https://meta.discourse.org/t/activitypub-plugin/266794/20 "2023-06-02T19:36:06Z")
> [@hellekin](#):
>
> One thing that would be useful is to choose the audience: whether the post will be public or followers-only. Now itās the latter, so we cannot boost it
I hadnāt gotten to the point of noticing this yet in my testing from a staging server, but Iād like to acknowledge that boosting is central to my own use case as well.
---
### Author:  [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [June 4, 2023, 11:53am UTC](https://meta.discourse.org/t/activitypub-plugin/266794/21 "2023-06-04T11:53:34Z")
## Handling 410 Gone
My logs have a lot of (changed URL):
```plaintext
[Discourse Activity Pub] GET request to https://activitypub.example/users/missing-account failed: Expected([200, 201, 202, 301, 302, 307, 308]) <=> Actual(410 Gone)
```
I believe this is related to: Object retrieval SHOULD respond with 410 Gone status code if `Tombstone` is in response body, otherwise responds with 404 Not Found (`server:object-retrieval:deleted-object:410-status`): the account has moved to another instance.
* * *
Also getting a few:
```plaintext
[Discourse Activity Pub] update_stored_from_json failed to save actor. AR errors: Ap has already been taken. Actor JSON: {"@context":["https://www.w3.org/ns/activitystreams","https://w3id.org/security/v1",{"manuallyApprovesFollowers":"as:manuallyApprovesFollowers","toot":"http://joinmastodon.org/ns#","featured":{"@id":"toot:featured","@type":"@id"},"featuredTags":{"@id":"toot:featuredTags","@type":"@id"},"alsoKnownAs":{"@id":"as:alsoKnownAs","@type":"@id"},"movedTo":{"@id":"as:movedTo","@type":"@id"},"schema":"http://schema.org#","PropertyValue":"schema:PropertyValue","value":"schema:value","discoverable":"toot:discoverable","Device":"toot:Device","Ed25519Signature":"toot:Ed25519Signature","Ed25519Key":"toot:Ed25519Key","Curve25519Key":"toot:Curve25519Key","EncryptedMessage":"toot:EncryptedMessage","publicKeyBase64":"toot:publicKeyBase64","deviceId":"toot:deviceId","claim":{"@type":"@id","@id":"toot:claim"},"fingerprintKey":{"@type":"@id","@id":"toot:fingerprintKey"},"identityKey":{"@type":"@id","@id":"toot:identityKey"},"devices":{"@type":"@id","@id":"toot:devices"},"messageFranking":"toot:messageFranking","messageType":"toot:messageType","cipherText":"toot:cipherText","suspended":"toot:suspended"}],"id":"https://mas.to/users/rikvipcode","type":"Person","following":"https://mas.to/users/rikvipcode/following","followers":"https://mas.to/users/rikvipcode/followers","inbox":"https://mas.to/users/rikvipcode/inbox","outbox":"https://mas.to/users/rikvipcode/outbox","featured":"https://mas.to/users/rikvipcode/collections/featured","featuredTags":"https://mas.to/users/rikvipcode/collections/tags","preferredUsername":"rikvipcode","name":"","summary":"","url":"https://mas.to/@rikvipcode","manuallyApprovesFollowers":false,"discoverable":false,"published":"2023-05-04T00:00:00Z","devices":"https://mas.to/users/rikvipcode/collections/devices","suspended":true,"publicKey":{"id":"https://mas.to/users/rikvipcode#main-key","owner":"https://mas.to/users/rikvipcode","publicKeyPem":"--...
```
* * *
And
```plaintext
[Discourse Activity Pub] GET request to https://mastodon.social/users/ejovoni46709 failed: Expected([200, 201, 202, 301, 302, 307, 308]) <=> Actual(410 Gone)
[Discourse Activity Pub] Failed to process https://mastodon.social/users/ejovoni46709: Could not resolve actor
[Discourse Activity Pub] Failed to process https://mastodon.social/users/ejovoni46709#delete: Could not create actor
[Discourse Activity Pub] Failed to process https://mastodon.social/users/epybisezax9438#delete: Could not find object
```
[Next page](https://meta.discourse.org/t/activitypub-plugin/266794.md?page=2)