i keep saying idgaf and i won’t post more about the episode but that’s a lie
can’t stop thinking about the topic of symbols this episode. ashton asks everyone to add some aspect of fcg to their clothing so they can all be reminded of them when they look at each other. they spend the evening making these symbols, acknowledging that what they carry on their person MATTERS. and then just as quickly, orym walks in with otohan’s blade on his back. and laudna is reminded of her death and the destruction otohan inflicted on them and will be every time she sees it. and then she’s told “it’s just a thing! it doesn’t mean anything! it’s just a sword!”
“It’s a symbol.”
110 notes
·
View notes
“Feyre is an unreliable narrator and constantly twists things to make herself seem more favorable or right in situations”
Insane thing to say when she constantly has self-deprecating thoughts and has no issue acknowledging when she’s wrong in a situation. She acknowledges that she was wrong for pushing Nesta to tell her story to the High Lords, she acknowledges that she should have been more mindful when it came to Elain’s trauma and the blame shouldn’t all be on Nesta, and she acknowledges that she was a bit of an asshole to Lucien on solstice.
She even takes fault for things that were completely out of her control so again…how is she twisting the narrative to make herself seem always right when she doesn’t even believe she’s always right?
33 notes
·
View notes
this line makes me wonder how long hori has had their backstory in mind, because in even in 193 afo states that yoichi was the only family he had left.
so I wonder if hori had their backstory in mind from the beginning or if he only had a vague idea of what their childhood looked like at this point.
I wouldn't be surprised if he did have their orphaned as babies backstory in mind here because the backstory explains so much of afo's behavior and the comic book they read was first mentioned here so he had to have some idea of how they stumbled across the comic that changed their lives at the very least ...
25 notes
·
View notes
qsmp francophone cubitos and their dynamic drive me wild, they all know they’re mutually lying and obscuring the truth to one another, they all know they’re keeping each other at arm’s distance, they all know they’re not as open as they once were when it was just them and the aftermath of a plane crash, but the love is still there. the worry and the concern. they pry information out of one another in supposedly subtle ways that really just convey how much they still care about each other. what’s your stance on the federation. how’s your code arm doing. even if in the end you don’t turn to me, please call out to someone. maybe looking out for yourself is looking out for others as well. i don’t know you anymore but i will protect the unknown anyway
107 notes
·
View notes
On Constructive Criticism.
Hey friends. You ever want to leave a critique on a fic, and the author says they like constructive criticism/"concrit," but then you leave your critique and you try to make it complimentary but the author still seems less than thrilled with you? You may have missed the point of "constructive!" Don't feel bad, you aren't alone. Took me until I started writing and receiving feedback to really figure it out.
The key to remember is, "constructive" doesn't mean "nice." It doesn't mean phrasing gently, or doing a compliment sandwich (although those are fine things to do as well). "Constructive" feedback is feedback that would make the story as the author has already written it stronger.
"The execution of this character's decision to do XYZ felt a little bit out of nowhere, to me. Was that your intent? It didn't seem like it was meant to be a big twist, either. Maybe some extra foreshadowing would make it stronger, or some shock on the part of the other characters." THAT'S constructive criticism.
This is NOT constructive criticism: "This character doing XYZ thing really doesn't make for as strong a story as it could. I think he should have done NQD thing, instead. That would have been better."
The first example offers some ideas on how to help a character's decision land better when the reader couldn't tell what the author's intent was. It's possible the reader didn't like the decision and that's why they noticed - maybe some foreshadowing would have helped them accept it better, or some indication that it was meant to be shocking would have validated the reader's surprise & displeasure. But, crucially, the reader did not suggest anything that would require a massive rewrite. Some tweaking, sure, maybe the addition of a few paragraphs. But not a change to the character's decision as a whole, the way the second example suggested. The second example does describe something the reader thinks would make for a stronger story...but it is not something that would make THIS story stronger. It is describing a different story than the one the author has already written so far, so it's just plain ol' criticism. Constructive criticism makes the existing story stronger.
That's the difference. You aren't workshopping. You are commenting on something that is already being written, that is already planned to the point where someone is already posting it. There is a BIG DIFFERENCE between workshopping a story and simply giving concrit! Unless the author has specifically asked for workshop-style help, offering things to do differently from what was already written is worse than useless. Don't.
Rule of thumb: if what you're saying can be boiled down to "I think this cake would be better if it was pie," say something else. The cake is not pie. It's not GOING to be pie. I didn't ask what you think I should bake, I put cake on the table and asked what you thought of this cake. Tell me what would make THIS cake better. Not the pie you were thinking of, and not a different cake you might have liked better. THIS CAKE.
52 notes
·
View notes