@lkanies @johnonolan @julian @hongminhee @pfefferle

tbh, no open source maintainer likes suddenly receiving a sizable pull request out of the blue, it tends to be disruptive or require additional time input to review/correct/review, hence nudging folks towards discussing with the team first.

@thisismissem @johnonolan @julian @hongminhee @pfefferle totally. These just don’t feel like nudges.

And sometimes, those big pull requests are the only way someone can work. It doesn’t mean the maintainers owe the author anything. But there are a *lot* of people whose first step cannot be “have sizable organization and permission meeting with stranger”.

All of my major pre-puppet contributions started with experimenting with code.

@julian I agree, you have beaten that analogy to death

You are welcome to do whatever the hell you want with code I post for free on the internet. And I am welcome to ignore all of that work, or not.

Nothing you do to my code intrinsically affects anything in my life.

@lkanies @johnonolan @julian @hongminhee @pfefferle In the past when the project has closed sizable pull requests, people have gotten pissed, so... yeah

@lkanies @thisismissem @julian @hongminhee @pfefferle it is permissionless innovation: In your own fork.

A pull request is a proposal to make changes upstream, if you want to do that then there’s nothing permissionless about it and never has been

Modern OSS maintainers are remarkably polite about it, too! Have a read through Linus Torvalds old mailing lists if you want to see how OSS really started. Big contrast

@johnonolan @thisismissem @julian @hongminhee @pfefferle thankfully Linus has never been a reasonable standard for how to treat other people, not now, and not then.

And there is a huge difference between “we will not merge your code without talking about it first” and “if you write code without talking to us, we will not merge it”. I hope you can see that.

@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.

@samsethi@podcastindex.social open to supporting as:Listen if you publish it. Can you send me a sample activity, and what you expect? Embedded audio player, etc?

@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.

@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.