@julian @thisismissem which is to say, the following are equivalent within the same scope...@\context: [{toot: http://joinmastodon.org/ns#,Emoji: toot:Emoji},{toot: http://joinmastodon.org/ns#,IdentityProof: toot:IdentityProof}]@\context: [{toot: http://joinmastodon.org/ns#,Emoji: toot:Emoji,IdentityProof: toot:IdentityProof}]
@dariusk I may be overly optimistic, but I'd like to move forward thinking that perhaps that was then and this is now.
Let's chat tomorrow (?) about the merits of your implementation and see whether we can make some waves!
@julian @Terence Eden At this point, one might want to distinguish between how something works according to the ActivityPub standard and how Mastodon has implemented it, if at all.#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ActivityPub #Mastodon
@[email protected] Thanks for the reply, I'm glad these discussions are taking place.
I independently settled on the approach advocated in that link you shared — given any Note ID, I traverse up the chain until I find the root, and that becomes the original topic post.
If there were some sort of standard for defining a topic ID, I would use that, although I think at present there are no consistent applications.
FEP-400e explicitly mentions forum topics, but I am not entirely certain whether this is something I'd want to follow as topic themselves don't have an "owner".
If anyone can use this, here you go. NodeBB, Redis & Python Script are all running on the same server. Please use the built in ACL to access the Redis database.
user mastodon +hgetall +zrange ~* on >PASSWORD
https://gitlab.com/Bullet64/nodebb_post_to_mastodon
blog! “How updates work in ActivityPub / Mastodon”I didn't realise this, so I'm documenting it to stop other people making the same silly mistake that I did. Messages in ActivityPub have two distinct ID strings. Here's a (truncated) view of what hap...
