Fandom Snowflake Challenge (03)

[static_whisper]

Challenge #3: In your own space, Scream Into the Void. Get it all out.

Sometimes I just rely on the Blanket Permission Highlighter because I feel like I'm playing a high stakes puzzle by looking at profiles.

I give blanket permission for fanworks, just ask me first :)

I can only assume that this means the person will always give permission to anyone who asks, but like, that's still 'ask first'.

Don't repost, copy, or host podfics on any site outside of ao3

I mean, okay, sure. It just sounds like a nope to any podfics then because ao3 doesn't host them. Even if someone wants a shared link to a Google Drive upload, so it's not on a site itself, the mp3 files have to go somewhere before they can be posted onto ao3. Host does not equal post. (Some phrasing also lumps podfic in with copying and reposting fanfic in a way that seems a bit disingenuous, but this venting isn't about that.)

I give blanket permission for podfics, just let me know first

Is the Related Work Notification email not enough? (Bonus puzzling out if the profile has zero way of contacting them in the profile itself. I am not going to crawl through dozens or hundreds of fanworks to maybe find links to other sites in the end notes.) Should I give a heads up before I record, or do I need to comment after I've posted in case the email notifications are turned off? If I don't have to ask, what does 'let me know' actually mean here?

Comments

[tjs_whatnot]

You've given me a lot to think about. I think we all get caught up in our own little perspective and forget to see it from the other side. I also think we were so eager to grant the permission that we just copy/pasted the one that was going around without giving it much thought. But, I think what you're saying is that it's the "first" that invalidates the blanket statement?

*goes and checks my blanket statement*

Phew. I think it's okay?

[static_whisper]

Well, there are transformative work policies that are 'blanket permission with caveats' or some people view 'blanket' to mean 'here's my position so you don't have to ask' and that might still include reaching out in some capacity before podficcing. So, it's not really that "first" invalidates the blanket statement, in a manner of speaking. To me, that type of blanket statement just doesn't always and/or automatically come across the same as "you don't have to ask for permission to podfic my work".

Personally, I interpret your transformative work policy/statement as "no need to ask to podfic first". It sounds like you'd appreciate knowing about a podfic after it's posted (but don't require any one method like commenting), so I assume that getting a Related Work Notification email from AO3 will suffice.