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

How does Misskey handle scrobbles? Do they come in the same shape as Pleroma scrobbles or are they entirely different?

Really this just reminds me of why I think that there shouldn’t have been such a reliance on these activities/objects in the DB in the first place. It always struck me as them contorting Postgres from a relational database into a document store. Ideally, all this stuff should have been properly processed on arrival, and the activities stored for analytical/forensic purposes, if not outright discarded.

But all that’s water under the bridge now. Considering this, I think just having transmogrifier differentiate between Pleroma scrobbles and Funkwhale audio blobs, plus whatever else we see down the way, is the better option. It might, however, merit adding an entry in the ActivityPub entry specifying that it’s a Pleroma scrobble to make it particularly easy to differentiate. Something like merging this into it:

The reality of ActivityPub is that it’s pretty open-ended, and so the idea that there’s a “proper” use of these types is fairly dubious to begin with. But we’ll see how things hash out.

I don’t think I’ve ever heard of Funkwhale. Anyway, to me, this raises two questions:

• Will changing the type from Audioto something else make it so that we can’t look at existing Listen actions without modifying the code, and
• What do you think it ought to be changed to, and why?

Fair enough. One thing I’m a massive sperg about is constantly rebasing my fork onto develop or whatever. I do this across projects just to keep on top of this sort of thing, so I can have all the new features/bug fixes/etc worth keeping while still having all of my own bullshit.

Are these issues in the commit I submitted or is it due to some cherry-pick weirdness? I’m not seeing any. I’m asking because if there are any I’d like to fix it.

How is it broken?

Here’s the goalpost for technical basis to reject this PR. It must meet ALL of the requirements:

• It must introduce a bug that wasn’t already there
• It can’t be from data errors created by another endpoint
• The same complaint can’t be issued against any other endpoints already in the codebase, example: if the complaint is that you can inundate the scrobbles endpoint, then the same complaint can be made about the statuses endpoint, making this an invalid basis for rejection
• It must reproducible

I’m not setting this goalpost because I think it will be met, I’m setting it because I want to give those who aren’t technical a baseline for evaluation here. If ANY of these requirements aren’t met, we can conclude that it’s not about any technical issue. It’s about who made the PR.

They didn’t even mention “security risks,” assuming there even are any. There are no “security risks” to delivering a little bit of JSON from a scrobbles table that only has text in it, and there definitely aren’t any new “security risks” considering this exact content can be retrieved from another endpoint.

I don’t understand what you mean

If you want to look at the actual commit so you can make your own variation, it’s this:

https://git.pleroma.social/NEETzsche/pleroma-fe/-/commit/2c9930bd5b5c1279e0890aeba673ad6b5ce2af18

You could probably cherry-pick it, really. It’s not a very complicated commit.

I think putting it in the post body is good, especially since it only shows the most recent one. That being said, I think the CSS could be improved.

You gotta convince @Moon to update the PleromaFE frontend. It’s in the main repo.

Example, which got federated from my instance.

Me and some people on my instance for a long time. I just today patched AkkomaFE/BE on BMC. I might re-submit my SoapboxFE PR to display it there. I’m convinced scrobbling really will catch on if allowed to.

I said I would fix it if there’s an actual issue, but it seems mostly schema sperging. That is, there are no actual bugs, they just don’t like the shape of the JSON blobs being passed around with AP.

Multiple ways to do that, but I wrote a script that pulls from Last.fm and pushes to Pleroma:

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

Man, fuck Illinois

RT:: https://shitposter.club/objects/3017c535-94ea-4c3c-9fb1-a12210ad7768

The “radfem community” is falling apart because it can’t decide if it’s more anti-rape (anti-Muslim) than it is anti-white (anti-Israel, even though jews aren’t really White).

So, this is the person “reviewing” my code. It’s not going to be accepted, not because of the content of it, but because of who I am. Any basis for rejection will be entirely pretextual at best.