RE: ActivityPub Plugin for WordPress: let's assume I would work on a feature that would allow you to follow a complete blog, what would be the best identifier for that account? @feed@example.org? @blog@example.com?
What are your ideas?
@pfefferle
Not having a catch-all user is one of the reasons I haven't installed the #ActivityPub plugin on our radio station #WordPress blog.
We use the Category feature to identify different shows, so when a new post is made it would be great if it was simultaneously published as @Feed, @Author, and @Category
And to be able to choose the @Feed name in the plugin configuration.
Thanx for a great plugin! I've installed it on other "less demading" sites 😁
@pfefferle@evan
Configurable identifier? Maybe it's not in the cards,but I'd like to control what subset(s) of my posts would go out on ActivityPub, and maybe the identifier then uses category as the identifier? Does that break the follow paradigm, or make it more powerful?
When I first pondered this on discovering mastodon I envisaged just declaring certain accounts that I could name arbitrarily and then have each follow specific accounts, but that then fails to boost each follow post. The intention was to allow for multiple subset feeds, like news sites offering categories.
But perhaps this could be done at the server? The plugin would auto-boost public toots from a specified accts or a category?
@pfefferle Tbh, anything would be great because this is a really important feature that I’ve been wanting for a while now!
But likely user definable would be best as I doubt one uniform name will work across all types of WordPress “blogs” (many of which are not exactly blogs anyway, but may be event listings, press releases, or whatever, esp as WP is used so often as a general CMS).
@pfefferle another problem is if WP is installed under a subdirectory like domain.com/blog (and leaving the root domain to be handled by some other CMS).
@pfefferle the identifier has to be source defined not reader defined. There maybe different feeds on different pages or different parts of the site or even different sites on the same domain.
As the general naming of feeds is /feed it's probably reasonable to concatenate the URL such as page-section-feed.mydomain.com.
But the simplest case is to use the title of the feed, with perhaps -feed appended to it.
@pfefferle I would prefer either @blogtitle or @example.com@example.com. Otherwise, as the domain part often won't be shown, you would only see something like @all or @feed which might be a little bit confusing.
@pfefferle@luca Uhh, nice trick! And categories are boosts of the respective categories? That would all be interesting and make sure there are not many “copies” of the same post. (Bending the ontology here a little bit.)
@pfefferle lots of good points mentioned by others already. I'm thinking it should be @blog@example.com by default, and of course make it configurable.
Reasoning: people know the blog by its title, and Fediverse clients may shorten the name to just the first part without domain name. @feed, @blog or @all are going to be too generic for that
@pfefferle Gut feeling without knowing the internal workings of Wordpress: @feed for everything, @feed+category for specific categories, and @commonts+postid for comments to specific post. Ideally both ways.
Add comment