Ghost Is Federating over ActivityPub
activitypub.ghost.org
activitypub.ghost.org
One of the main problems I see with AP is account fragmentation. If I'm an author on Ghost, but also have a Mastodon account, which account should I use to follow someone on PeerTube?
It really seems like the server side should be datatype agnostics, handling activities of any type, and it should be easy to delegate access for sending/receiving activities. So for example maybe Ghost is my main account, but I can delegate some access to Mastodon and PeerTube while sharing the same actor.
Have you guys discussed this much at Ghost?
ActivityPub, like many of 'open social' web standards before it, suffers to some extent from being invented without clear enough usecases in mind. Much like WebMentions (which we also adopted) the answer to "what's it for?" - often seems to be "yes".
So you can either try to ship the spec and support everything, or you can try to build an end-user usecase that fits within the spec, and get more specific. We tend to lean toward the latter, and try to create something useful - which would still be useful even if nobody knew it was running on [whatever web standard].
Whether we can succeed with it or not, remains to be seen :)
>When you do publish, your posts will appear in other people’s feeds in Ghost... and in Mastodon, and everywhere else.
>Long-form content deserves a dedicated design so you can read in peace, much like the way email newsletters show up in your inbox.
Basically, long-form content should be presented in a way that makes it great to read – but thankfully now people can also read it on PeerTube too? Were people on PeerTube really hankering for Ghost blog posts that much?
If people wanted blog posts on Mastodon, couldn't you just add RSS feed supports to Mastodon?
Does ActivityPub at least have moderation tools so that you can set approval requirements and/or delete posts?
You can moderate what can be seen from your site (and what your site will return when asked for comments on that post by other sites(?)), but you can’t moderate it completely when viewed on other sites — i.e. if you’re Site A, someone comments something you don’t like on Site B, and someone looks at the comments from Site C, if Site B and C were already federating with each other then C will see B’s comment (and in this case it’s Site C’s responsibility to moderate)
You can block a specific user of Site B from viewing your posts in the future, but it’s up to Site B’s software to actually respect that. But if it doesn’t (this is rare, most software does respect things like this and it’s only tiny forks that disable this functionality), you can also just block Site B entirely
Editing to expand: Yes, this is pretty wonky and basically means you can only control what’s seen on your site unless you go through a lot of effort, but without ActivityPub you can’t control what other people say about your post on other sites either (i.e. you can’t moderate the HN thread of your article)
Then if someone on Pixelfed sees that blog, Pixelfed will ask Ghost who has commented on it (via ActivityPub). Ghost can then tell them about that (via ActivityPub) - or it can choose not to do so (based on its own moderation tools).
That doesn't mean that the Mastodon comment no longer exists, nor that it is invisible to the people looking at the Mastodon comment (similar to HN comments), but Ghost won't boost its reach.
So what ActivityPub gives you is the option to reshare comments.
https://www.404media.co/404-media-now-has-a-full-text-rss-fe...