@BeAware @hallenbeck @evan @swf here is an example of the TrueFans activities we are publishing to AP.
https://truefans.social/samsethi
https://truefans.social/podcasts/podnews-weekly-review
@BeAware @hallenbeck @evan @swf here is an example of the TrueFans activities we are publishing to AP.
https://truefans.social/samsethi
https://truefans.social/podcasts/podnews-weekly-review
@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.
@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.
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
@julian @silverpill we will we have two more changes ot make to our AP client tomorrow. We just enabled any AP user/client to follow any podcast and get their new episode, play, comment etc actvitiy. But next week we will publish with the listen verb for clips and see what happens ... thank you
Step 1 TrueFans now allows you to follow any podcast via ActivityPub in TrueFans.social in order to get 'announcements' of new episodes, who recently became a fan, any boosts/comments or they have a new blog post, tickets or merch - we will finish the UI today.
So now you can follow a user and/or podcast.
Step 2: We will add publishers and musicians next. So you could follow Wondery or Ainsley Costello.
Step 3: Is enabling the ActivityPub inbox so you reply or message users/podcasts
@julian thanks, Yes an embed player so users can hear a clip in situ. I am not sure we want users to hear the full podcast episode in the AP client.
@thisismissem @pfefferle @julian @hongminhee @johnonolan We wanted to originally publish the activity out of Truefans using the Summary verb but it marked everything as sensitive. After some digging and help from the AP community it was a known bug so we switched to using Notes. We also tried the Listen verb but that didn't work in Mastodon or clones so we abandoned that idea. TreuFans will now build our own full AP client and support the verbs and display them correctly in our app.
3/3 - @deadsuperhero @fedify @evan @fedidb @fediforum Sean I wouldn't get down. In the Podcasting 2.0 community we have similar challenges and problems. The big players like Apple and Spotify are not supporting the new RSS tags/standards. The collective open nature of developing new RSS tags means it moves slower than proprietary platforms like Spotify or YouTube.
Sean I don't have an answer to your questions but I do see momentum in both ActivityPub and Podcasting 2.0
2/3 - @deadsuperhero @fedify @evan I still think ActivityPub has a strong future. Sometimes it takes a decade before a technology finds its mojo. In recent months I have observed Flipboard, Threads, numerous new AP clients and my own app TrueFans all adopt ActivityPub. @fedidb has shown a significant growth on AP user numbers and @fediforum was great.
Also Apple, Linkedin, YouTube, Twitter and others are scraping our data to train their AI's. The Fediverse may be the only safe haven.
1/3 @deadsuperhero As someone new to developing ActivityPub apps the poor documentation was a big turn off. @fedify have done a great job in making it easier to build new apps and their documentation is much better. The new book by @evan is also a great read for new AP developers.
However given that the Activity Vocab was defined way back in 2017 by the W3C and Mastodon the biggest AP client still doesn't support all the verbs is a disappointment. e.g summary, listen etc.
@BeAware I think 18.1 is coming to the developer build shortly. All of it is pointless as all the so-called Apple Intelligence only works on iPhone 15 Pro Max and above and I have not updated my iPhone for a few years. #NoNeedToUpgrade - I will wait until next year when iOS18 actually has the AI features before I upgrade.
@BeAware you can switch back in the iPhone UI under settings.
@thisismissem @jenniferplusplus @julian again 100% agree, otherwise we can end up overloading people who follow us. Filters by verbs in clients is critical. We are testing this now in TrueFans.social so if you want to follow what I publish from TrueFans you can limit what you receive. So in my TrueFans.fm settings I choose what activity verbs I want to publish to my public Activitystream - https://truefans.social/samsethi - but we want to offer you the option to apply a filter so you can choose.
@jenniferplusplus @julian I think we all want to use the right vocab verbs. I want to use listen, announce, article, buy, follow etc. This will allow me to add a filter to our TrueFans.social activitystream pages e.g http://truefans.social/samsethi - there are multiple ways we can hack this to work but I would prefer to not use Note for everything. We tried to use Summary but Mastodon marked every post with verb Summary as sensitive. So we couldn't use that either.
@thisismissem @evan 100% agree but how?
@evan sadly its chicken and egg. If we publish with the listen verb and no apps read/render it then. our users will ask why their activity was not published. So we are forced to use the lowest common denominator aka note so it is read now by AP clients. Very happy to experiment as I know we are a new use case.
@evan @julian @pfefferle @manton @renchap @andypiper @Gargron I 100% agree with Julian. We are new to AP development but very excited. I was surprised by the lack of AP vocab support in Mastodon given the AP vocab has not been updated since May 2017.
Being a podcast & music app we had hoped to use the LISTEN verb. Sadly we can't as there is no support? Equally we offer blogging and event ticketing in our platform, so using ANNOUNCE, ARTICLE and BUY verbs will hopefully work???
@thisismissem thanks. I have read everything on W3C, Fedify and Evans book and must have missed the do not use a name. We need to think this through but I am wondering how I can fix my current issue. I have deleted my public/pvt keys and removed all cookies to try and get it to reset. The good news all AP clients see my truefans.social acct again and I can follow.