Untitled attachment

Having Listen activity with just URLs pointing to outside of network or nonsensical data is tethering on being spam (same as Likes on nonexistent statuses), it also can conflict with other software that might want to use Listen for counting listens on actual Audio documents.

It’s literally in the spec that this is how it should work. It’s not spam anymore than anything else is. These are actual Audio documents. The idea that the Audio document must link to a literal audio file has already been hashed out and the conclusion is that it doesn’t. I’m not discussing this further.

url field according to https://www.w3.org/TR/activitystreams-vocabulary/#dfn-url is meant for url pointing representation of object, so for a Listen activity it would mean url should point towards the representation of listen activity itself, not what has been listened to.

See attachment #1. The url points to the song’s audio file or, in most cases when the rubber hits the road, page. Maybe you could argue that it should be structured as a {"type": "Link", "href": "https://example.com/whatever/"} object, but that’s as far as this line of thought goes.

if you want to link towards what is actually being listened to you should use “target” field instead, with description of Link object https://www.w3.org/TR/activitystreams-vocabulary/#dfn-link and add rel=[‘external’, ‘nofollow’] for arbitrary data to suggest servers not query it.

If you want to link towards what is actually being listened to you put it in the url field. This isn’t just silly, it’s incorrect. You’re actively being wrong here. Are you going out of your way to be wrong here? Because at this point I think you are.

Can you funking stop patronizing and trying to teach people how to do things?

Can you fucking stop wasting my time with bullshit? This is what you’re doing here. This whole post was bullshit that is either outright wrong or entirely not actionable.

Public

Notices where this attachment appears