Embed Notice

And now, for my fee: if I actually go through the trouble of writing up this thousand word document telling people what title, album, artist, and length mean and put in a PR that makes it reference that document in the way this AS spec likes, the PleromaBE maintainers will take it and undeprecate scrobbles. It will happen pretty unceremoniously and without a protracted code review process. It will not be subjected to nitpicky, spurious rejection. “It works” will be the final argument on the topic. The only valid reasons to reject it will be something an external actor can break with it, in a way that impacts end users; you’ll need to make it blow up or find a security hole that lets them see/do things they shouldn’t or something like that. This standard will trump everybody’s style guides and linters.

I’m pretty staunch on this being a non-issue. As it’s currently implemented, there are no known bugs that an end user will ever have to deal with, and doing this rigmarole to conform to this spec adds no new features. This means it’s unimportant, from an objective standpoint. Because I’m not getting paid, I value my time, and I’m not motivated by backend nitpicking, the only end this serves to me is a social one: assuaging concerns I disagree with in the first place. Will going through this trouble actually accomplish that, @hj ?