Now anyone can follow any podcast to see what activity is happening.
-
Now anyone can follow any podcast to see what activity is happening. i.e if there is a new episode published (announce), if a new comment has been made (boost) and by whom or someone becomes a new fan (subscribe) or even who just played the podcast. (listen).
Equally once you claim your podcast in TrueFans, all of this published activity is up to the podcast creator to choose what verbs they make public. /cc @dave @davejackson @theDanielJLewis @evan
-
Sam Sethi :pc2red: βreplied to Sam Sethi :pc2red: β last edited by
@dave @davejackson @theDanielJLewis @evan
The next step tomorrow is to build the truefans.social/{podcastname} landing pages.
We also had to build actors/users/artists aka people on one server and podcasts/publishers aka services on another server.
We use @fedify which is great but they don't allow dual node dispatchers so we have to run one server for actors/users and one server for podcasts.
So at the moment we have @podnews-weekly-review - we will hide this mess.
-
Emelia πΈπ»replied to Sam Sethi :pc2red: β last edited by [email protected]
-
Sam Sethi :pc2red: βreplied to Emelia πΈπ» last edited by
@thisismissem at the moment we have TrueFans.social/username we also want to have TrueFans.social/podcasts.
So my address is @[email protected] but my podcast right now is @podnews-weekly-review
For some reason we have to run two servers to publish activities for actors and services. We canβt do it with one activity dispatcher.
-
Emelia πΈπ»replied to Sam Sethi :pc2red: β last edited by
@samsethi @fedify that doesn't sound right?
federation.setActorDispatcher("/users/{handle}", β¦)
Doesn't have to be `/users/`for the actor, it could be `/actors/:uuid` where the UUID is the ID column in either the Users table or the Podcasts table.
In fact, using the username in the actor address is an anti-pattern, you were bitten by this with your own actor when you changed username.
Preferred Username can be different to the βhandleβ & I'd actually argue the Fedify docs should use {actor}