Email or username:

Password:

Forgot your password?
Top-level
Qazm

@fulanigirl @atomicpoet @kraft @fediversenews There are essentially two (main) interactions that make sense to me for blogs:

- broadcasting post announcements
- collecting (and managing) comments

Blogs are unlikely to broadcast the entire article contents to the Fediverse (also for compatibility reasons), but automatically pushing a nicely formatted post announcement to followers' feeds is very feasible.

They can then also receive replies to that post and display them as blog comments, which I think would be a really nice feature. (I saw a custom example of this a while back.)
Since the received comments are a local copy, they can still be moderated as normal by the blog owner too, at least in theory.

Which of these WordPress will implement I don't know, of course, and they could also add something I haven't thought of.

11 comments
fulanigirl

@Qazm @atomicpoet @kraft @fediversenews OK Thanks. we just came off Twitter where we normally posted our announcements. Just opened a Mastodon acct to do that, but having comments might be interesting. We keep those heavily moderated because our topics are race related. I will keep my eye on further announcements.

Qazm

@fulanigirl @atomicpoet @kraft @fediversenews I'm looking forward to seeing it too, since it's an interesting user experience problem.

I'm not sure it's possible to turn off replies to announcement posts entirely, but a Fediverse server could well decide not to relay them unless given the okay manually. (This means they'd at first be visible only to the commenter, their followers, and others on the same instances as either. Edit: and optionally on the rendered blog page I assume, since that part can be easily revoked and doesn't "spill" them elsewhere.)

I don't think it would be technically possible to widely hide them again once relayed, due to how authorisation works. I haven't checked too closely, though.
Ideally it should be possible to report comments to their origin instance's admins, since afaik *they* do have the power to wipe a post across the network relatively well. Mastodon has that feature, but I've seen some other implantations gaining it only week or so after launch.

@fulanigirl @atomicpoet @kraft @fediversenews I'm looking forward to seeing it too, since it's an interesting user experience problem.

I'm not sure it's possible to turn off replies to announcement posts entirely, but a Fediverse server could well decide not to relay them unless given the okay manually. (This means they'd at first be visible only to the commenter, their followers, and others on the same instances as either. Edit: and optionally on the rendered blog page I assume, since that part...

fulanigirl

@Qazm @atomicpoet @kraft @fediversenews yeah, it's an interesting issue. And I suppose that might create more work for the server administrators. For people whose WP sites are for marginalized folks that might be problematic.

Qazm

@fulanigirl @atomicpoet @kraft @fediversenews There's discussing about adding reply control to ActivityPub here, in case you're curious about why that's (more) difficult (than on a centralised platform): github.com/w3c/activitypub/iss

The long and short of it is that various implementations handle authorisation a bit differently from each other, so a solution must be found that's acceptable with multiple methods.

fulanigirl

@Qazm @atomicpoet @kraft @fediversenews took a look at the link and the first thing I thought was: coders are really lawyers! We have have long extensive discussions about "should", 'must." and "can."But I think the thread does raise the relevant concerns. The monetization re ads is a good point also. We don't have ads but I can see that registering someone as a hit on the site itself would be important. I appreciate the folks who take the time to work these things out.

Qazm

@fulanigirl @atomicpoet @kraft @fediversenews We have rfc-editor.org/rfc/rfc2119 fortunately, which standardized at least the language in this regard in a simple way.

A LOT of especially the low-level protocols effectively run on these "request for comments" documents, while the w3.org manages mainly recommendations for higher-level protocols like web pages, web accessibility (in terms of disability accommodation features) and ActivityPub.

(There's also the IEEE, which, among many other things, publishes often very polished and nice standards documents for certain data exchange formats like JPEG, but they're quite expensive to access.)

Not all of these are nice to work with. Certain grown systems like IRC and email can be difficult to implement in a way that works in practice with large existing implementations, for example, even if the original core protocol is very simple. Many RFCs describe fairly complex compounds that reference other de-facto standards, too.

@fulanigirl @atomicpoet @kraft @fediversenews We have rfc-editor.org/rfc/rfc2119 fortunately, which standardized at least the language in this regard in a simple way.

A LOT of especially the low-level protocols effectively run on these "request for comments" documents, while the w3.org manages mainly recommendations for higher-level protocols like web pages, web accessibility (in terms of disability accommodation features) and ActivityPub.

Chris Trottier

@Qazm @fulanigirl @kraft @fediversenews Comment control already exists on Hubzilla and Streams. I’ve used it, and it works well.

Qazm

@atomicpoet @fulanigirl @kraft @fediversenews Do you have a link with more info on hand? If I try to look this up for Hubzilla, that appears to be a Zot (which I can't find the spec of currently) rather than an ActivityPub feature.

Mike Macgirvin
The comment control feature is protocol agnostic. In streams, there is an app called 'Comment Control'. Install it and you have full control of comments on every post. In Hubzilla, this is controlled in the permission dialogs, and I believe you can set comment controls for a channel, but not per-post as you can do with streams. We tend to share a lot of ideas between these two repositories so the newer control will probably show up on Hubzilla eventually.

Federation isn't really involved in comment control. If I don't want to see your comment, it is my divine right to refuse it or delete it. The only place federation is involved is to not provide a comment box if we know in advance that the comment is only going into the rubbish bin and save you typing a long reply into space.  

The zot/6 spec is under 'spec' in the Hubzilla repo and there are some implementation details of the ActivityPub implementation of comment controls in FEDERATION.md in the streams repository. We've since extended these to be at least partially compatible with FEP-5624 -- if you don't like the way we implemented it in 2012. Since nobody has shown any real interest in nomadic identity or working together on better permission controls on the fediverse (preferring to extinguish us instead), I haven't yet provided a spec for Nomad (which is basically Zot/11). The streams repository does include the only known reference implementation of Nomad.
The comment control feature is protocol agnostic. In streams, there is an app called 'Comment Control'. Install it and you have full control of comments on every post. In Hubzilla, this is controlled in the permission dialogs, and I believe you can set comment controls for a channel, but not per-post as you can do with streams. We tend to share a lot of ideas between these two repositories so the newer control will probably show up on Hubzilla eventually.
Chris Trottier

@mike @fediversenews Who is trying to extinguish nomadic identity? I’ve been a big fan of your work. And when I mention the concept to others, I only get positive responses.

ilja
@Qazm @fulanigirl @atomicpoet @kraft @fediversenews

> Blogs are unlikely to broadcast the entire article contents to the Fediverse

They already do. Fedi is not just for microblogging. See e.g. also WriteFreely and Plume.
Go Up