I didn't write anything summer to not add more things to an already full plate, but due to episode 174, I will live hire a few things I would love to see in the AP bridge (crazy or appropriate I live you to decide).
[ ] Ask for the latest X episodes. Similar to what latest . It could also fix what discussed on PI.social about the whole catalog.
[ ] Mention in the Fediverse message that the bridge generate the accounts that are in the person tags of the episode.
If the AP account that send the command, has a podcast personhost in the channel level allow these commands:
This would be like re-implementing the PI dashboard ( only PI admins) to what things made sense to be able to control directly the podcaster, probably with limits (one change per day or something similar). Another way could be a reclamation procedure in the dashboard for podcaster, but not sure if that is planed or preferable.
[ ] reset . Right now this PI entry has a lot of episodes duplicates due, I can ask in Github or Mastodon the PI folks to fix it (as I'm been doing) and continue their burden, or ask the podcaster that is in Mastodon, to send that command and fix himself his feed.
[ ] follow the account of the person tag of X episode or channel. Ideally this could be do automatically, but triggering with and account could be an anti-SPAM measure. This could improve discoverability and credits on the Fediverse.
[ ] pubnotify/podping. Not sure about this due to be able to do it by API, but this is a brainstorm
I use AP account instead of Mastodon to point that there are a lot of other services that could use this.
I didn't write anything summer to not add more things to an already full plate, but due to episode 174, I will live hire a few things I would love to see in the AP bridge (crazy or appropriate I live you to decide).
[ ] Ask for the latest X episodes. Similar to what
latest. It could also fix what discussed on PI.social about the whole catalog.[ ] Mention in the Fediverse message that the bridge generate the accounts that are in the
persontags of the episode.[ ] Add an image description in the messages, like this at least.
If the AP account that send the command, has a podcast
personhost in the channel level allow these commands: This would be like re-implementing the PI dashboard ( only PI admins) to what things made sense to be able to control directly the podcaster, probably with limits (one change per day or something similar). Another way could be a reclamation procedure in the dashboard for podcaster, but not sure if that is planed or preferable.[ ] reset . Right now this PI entry has a lot of episodes duplicates due, I can ask in Github or Mastodon the PI folks to fix it (as I'm been doing) and continue their burden, or ask the podcaster that is in Mastodon, to send that command and fix himself his feed.
[ ] follow the account of the person tag of X episode or channel. Ideally this could be do automatically, but triggering with and account could be an anti-SPAM measure. This could improve discoverability and credits on the Fediverse.
[ ] pubnotify/podping. Not sure about this due to be able to do it by API, but this is a brainstorm
I use AP account instead of Mastodon to point that there are a lot of other services that could use this.