@samsethi @julian this seems like a weird expectation to me. As:Listen is an activity. It's a thing that the (sending) actor did, or is doing. It would make sense to put an audio clip in an audio object, but not directly in a listen activity.

Anyway, since I'm not building a podcast app, I would be inclined to interpret a listen activity as a kind of presence update. Like an AIM away message. If you want something like a share or recommendation, I would expect that to be an announce activity

@jenniferplusplus@hachyderm.io @samsethi@podcastindex.social yeah, as:Listen(object) or some such.

I'd have to refactor a bit since my code pretty much expects either Announce or Create, but it's for the better anyway.

@lkanies @thisismissem @julian @hongminhee @pfefferle and I think this reasoning has been explained to you in some detail by several people. Hopefully you can see that

@johnonolan @thisismissem @julian @hongminhee @pfefferle definitely a situation where neither of us is convincing the other ‍️. But I’m just some guy with opinions on the internet (and experience in other OSS projects). My opinions deserve no weight here, so I will slink away

@jenniferplusplus @samsethi @julian Pleroma uses Listen activities to display "currently listening" status: https://docs-develop.pleroma.social/backend/development/API/pleroma_api/#get-apiv1pleromaaccountsidscrobbles
I think this activity can also be used for counting podcast listeners.

@silverpill@mitra.social Very cool, thank you!

Hopefully @samsethi@podcastindex.social will reconsider and perhaps federate out as:Listen in addition

@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

@julian // There is no target="_top", only target="_blank". Well, you can use _top, but it is just a normal name and any new link opened will replace a page previously opened, which will likely be not what a user wanted.

Just coming across this now, hello everyone -- I wanted to say that Hometown has implemented what @julian proposes in the OP for its entire existence, since about 2019. It's worked quite well!

More content types

A supported fork of Mastodon that provides local posting and a wider range of content types. - More content types · hometown-fork/hometown Wiki

GitHub (github.com)

@dariusk @darius@friend.camp Thanks for sharing this, I think it's fantastic that this is already adopted in a Mastodon fork.

May I ask whether there have been attempts in the past to get these changes back upstream to Mastodon?

cc @renchap@oisaur.com

@julian This was ~4 years ago but I asked someone on the team (I forget who) if it would be a welcome PR and I was told that it probably wouldn't be, so I didn't make the PR.

Of course that was a long time ago! Also of note, this was completely and totally a hack and I don't think my actual implementation is what I would want to put upstream at this point. What's more interesting is that it hasn't been the cause of any UI concerns; basically what you postulate above, that the "hide long content behind a cut" functionality pretty much solves the problem, is true.

@dariusk I may be overly optimistic, but I'd like to move forward thinking that perhaps that was then and this is now.

Let's chat tomorrow (?) about the merits of your implementation and see whether we can make some waves!