|
Top-level
@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. 4 comments
 @thisismissem at the moment we have TrueFans.social/username we also want to have TrueFans.social/podcasts. So my address is @samsethi@truefans.social 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. @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} |
Gregory's Server
@dave @davejackson @theDanielJLewis @evan @fedify @podnews-weekly-review
The aim is you can just type out the name of any podcast in a AP client search box and find the Truefans.social account to follow and then in your own stream you will receive the activity updates.
Below shows me following the Podnews Weekly podcast on TrueFans.social but seeing a boost by another user caled Mostafa in my AP/Mastodon client home timeline.
Replies, Favourites and Boosts next.