@julian Ghost already represents posts as `as:Article` objects. Interestingly, they put `as:Note` into the `as:preview` property of `as:Article` objects, which I don't think Mastodon utilizes.

ActivityPub/src/handlers.ts at 46ef68e2c79ec9e8e3fb8d9e5ebbd0729c6bae72 · TryGhost/ActivityPub

A full-featured ActivityPub server for networked publishing with Ghost - ActivityPub/src/handlers.ts at 46ef68e2c79ec9e8e3fb8d9e5ebbd0729c6bae72 · TryGhost/ActivityPub

GitHub (github.com)

@renchap @pfefferle @mike @michael

@julian Good to know, thank you!

The JSON-LD processor ended up being #Fedify's bottleneck, so I'm in the process of fixing Fedify to generate JSON-LD without the proper JSON-LD processor.

#JSONLD #fedidev #ActivityPub

@julian The link to FEP-400e actually goes to FEP-7888. Anyway, great job!

For educational purpose, I've created a federated microblog example using #Fedify, with a total of about 30 commits, which you can follow step by step.

Now, I'm starting to write a hands-on Fedify tutorial based on this example code. I'll make it public when I'm done!

GitHub - dahlia/microblog: A simple federated microblog example using Fedify for educational purpose

A simple federated microblog example using Fedify for educational purpose - dahlia/microblog

GitHub (github.com)

#fedidev #ActivityPub

@julian Yes, Fedify implements it. Here's the implementation:

fedify/src/sig/proof.ts at 0.14.4 · dahlia/fedify

ActivityPub server framework in TypeScript. Contribute to dahlia/fedify development by creating an account on GitHub.

GitHub (github.com)

I received a request from @ghost today to add #LDSignatures to @fedify for compatibility with #Mastodon, as Mastodon does not plan to implement Object Integrity Proofs (FEP-8b32) for the near future.

However, Mastodon's implementation of LD Signatures does not even use valid JSON-LD properties (despite the name), so I'm not sure how to make it compatible with Mastodon since #Fedify does JSON-LD processing.

#ActivityPub #fedidev

As the creator of Fedify, I'd like to see either ActivityPub implementations all deal with JSON-LD properly, or the ActivityPub spec gives up on JSON-LD.

The `fedify inbox` command, which is shipped with @fedify/cli, is a tool that creates an ephemeral #ActivityPub server so that you can debug and test the activities you send.

Here's a demo of it.

fedify: CLI toolchain | Fedify

The fedify command is a CLI toolchain for Fedify and debugging ActivityPub-enabled federated server apps. This section explains the key features of the fedify command.

(fedify.dev)

#fedidev

@pablo Not all ActivityPub implementations process JSON-LD properly. Rather, the situation is the other way around: the most of ActivityPub implementations treat Activity Streams objects as plain JSON objects.