Chris Down

It doesn't, sadly. My use case is irrelevant though -- my main argument is that the RFC very clearly wants people to use SPF records, not TXT records.

I know that djbdns and nsd (two other extremely popular servers) implement it, it's definitely not just bind. Even if they didn't, I don't see how that's a good argument...

github.com uses them, off the top of my head. I will send a patch if I can understand the code well enough and have the time, I guess. Unfortunately this...

In the meantime my broken software actually allowed using TXT records :-D Having SPF records in here while non-draft RFCs promote them is a good idea, though, in my opinion.

Specifically, because you do not properly sanitise all your variables, only $data, and the rest still have arbitrary input.

I like the idea, my only concern is (for example) how does audioscrobbler deal with that? AFAIK it only supports a single artist.

Hey! I actually added comment support to audiotags in preparation for this a few months ago, but there has been no release since: https://github.com/TianyiShi2001/audiotags/commit/b6b3df18c941f4f4ed575b5a09273135edb12a33 So the first step would be...

Looks like a release is close: https://github.com/TianyiShi2001/audiotags/pull/40

Moving into [community] requires an Arch TU, it's their decision if they want to merge it. I can take a look at the other commits to see if any are...

Just looking at this again, are there some commits or fixes in particular which you were thinking about merging from https://github.com/taylorskalyo/sshrc? Happy to cherry pick some and massage them in,...