sitemap.xml is completely fine unless theres a < urlset > element in it. other name xml files are also fine as long as < urlset > doesnt appear. imma do some more testing

looks like its a regex scan for <urlset

<strong>it just occured to me to try this</strong>

alright back to the urlset thing. the file saves successfully if there is no proper xml heading. if it does, then it doesnt matter what the file type is (i tested txt and html), having <urlset makes neocities throw the errror "[filename] is not an allowed file type for free sites, supporter required"

the checks are quite simple, at least as far as ive tested (putting a blank line before the xml header bypasses the error), but since xml is an insanely strict specification, any attempt to bypass it also results in parsing errors so.

its not a big deal but idk why this is implemented. whats the point of paywalling THIS in particular?

argh thats enough i need to do WORK not get distracted again!! (difficulty: impossible)

maybe they accidentally implemented it as a leftover of other testing they could have been making?? i really am making a blind assumption because i can barely even comprehend with my diminute brain what's the issue here ^^; but i'll leave it as a plausible explannation to why is that a thing

fr???? that's insane ... i hope it's leftovers, because there's even like .xml for adding CSS to RSS feeds (which is why i have an xml file myself). i can't test if it truly is a nuke now that i have supporter but ... that's so Weird

@spotties i dont think its an accident bc the criteria for a file to get rejected specifically targets urlset tags for sitemaps. its too specific to be unintentional. and it does not affect other xml files, only sitemaps, so @zhongvie youre good

Oh dang in that case i must have sounded like an airhead ( ´△｀)

I can add one *with* a supporter account, so I assume it *is* intentionally paywalled, but it's weird because I see nothing relevant when searching for sitemap.xml or urlset on the neocities github

@bunglepaws tis prolly a backend thing