Notices by NEETzsche (neetzsche@iddqd.social), page 19

Whenever I need to sleep on an actual schedule I just can’t.

The trick is to click merge

RT:: https://gleasonator.com/objects/fbb8a5f1-7fae-4052-98d1-3d560be285c4

What prompted this?

Did Rockstar really go from actually edgy to ‘edgy’ lately?

Most secure WAN configuration

Basically, the way it works, is you hit /api/v1/pleroma/scrobble whenever you listen to a song, but the process can be automated. In the past, people would use Last.fm for this. You can hook Spotify, Pandora, WinAmp, and whatever else up to it.

I wrote a script that bridges Last.fm (which is supported by basically every music listening program and streaming service) into the Pleroma API:

https://github.com/TheStranjer/fediFM/

Yeah that’s exactly how it works.

She’s just one of those women spouting MGTOW/MRA talking points from like 15 years ago as though they’re new now.

I’m pretty sure Pearl Davis is one of those “based” “trad”wives on YouTube who appeals to male interests for views, not a liberal.

Nah it’s global.

Anybody have any clues why 4chan is down?

Or just give them cocaine.

There’s a brand of weeb these days that runs with it because they kind of know how ridiculous it all is, they just don’t care and will laugh in your face if you try to shame them for it. The clown world weebs, ya know. I can respect that.

In the 2000s you could troll weebs by calling them “japanese cartoons.” It still probably works.

@r000t out of curiosity, why do you use mastodong?

Long

@mint @hj

I’m reading this spec here:

https://www.w3.org/TR/activitystreams-vocabulary/#dfn-listen

It seems like using the Listen action to an Audio object is actually correct going by the spec. Or at least, as correct as we’re going to get. That is, I’m not seeing any way in this document that’s closer to the exact thing we really want. And that’s of course assuming that an Audio document truly needs to include a direct link to a literal audio file or else it’s “invalid.” I happen to think this interpretation is a bit much. After all, how would we use ActivityPub to reference songs that you can’t freely download legally, like, ya know, most of them? Sorry sweaty, you just can’t scrobble Taylor Swift because to do so would require you to insert a direct FLAC link to her song, which would violate copyright law in your jurisdiction.

I think that’s not correct. I don’t think that an Audio document requires you to link directly to an audio file. I think that you can state that you Listened to something without uploading or linking to that thing. You can just reference it. I think the way Pleroma’s BE is mostly ideal as-is. I think its deprecation is wrong-headed.

That being said, if I had carte blanche to change the way PleromaBE ingested scrobbles, I would change one thing: accepting a url. While I don’t think it should be mandatory, I do think it should be optional. Why? Well, there’s an appeal to be made to end-user utility. That is, you can store that URL and deliver it to the user. That URL format should be as open-ended as ActivityPub itself is, which is to say very. The URL could be a link to the Last.fm page that you ultimately got the scrobble from initially. It could be an audio file somewhere. It could be a YouTube link. It should be freeform and more or less up to the user. If the user submits trash, chalk it up to user error.

But the utility of seeing a song someone scrobbled and being able to click a link that takes you to either an audio file of the song itself, or some website where you can stream it or buy it or whatever, sounds fantastic. I want that feature. I would love to implement that feature.

Arguments for leaving the PleromaBE scrobble spec alone, but adding an optional url field, in more succinct form:

• Being able to link to the song itself in one form or another makes the experience for users better
• The implementation as-is works outright, and is in line with ActivityPub’s specification, except for perhaps the most anal interpretations of it that run into serious practical problems
• Adding a URL field brings us closer to that extremely anal interpretation
• Keeping the URL field optional allows people to break “the rules” since they don’t seem to really matter in the first place in this context

Yeah I just cloned Misskey and didn’t see the word anywhere in the codebase so I was scratching my head wondering if they had a Japanese word for the same idea.

Anyway, in light of the facts that I don’t see Pleroma absorbing Funkwhale Audio actions soon, ActivityPub is too open-ended for there to be a definitive “proper” use in the first place, Pleroma scrobbling has been around for a long time, and changing the way Pleroma ingests scrobbles would create a need for a migration to retroact all the previous scrobbles… I don’t think it’s worth it to do the change. Just leave it be.

Just my view on the subject.