The case for Yuna's pretty simple, though I have to be a bit vague on my information dispersal for self-protection, which I no longer think is as important with the free night, but we'll get to that in a bit.

I can say with near absolute certainty that she did not kill DK, and that creates two formulas, one for each scenario, 2 scummers and 3 scummers.

If we have 2 scummers, then one of them did the kill and the other did not. There are ten of us, though really 9 since we all know our own alignment and whether we did it.

If two scummers, the odds any individual players is a ninja is 2/9, and the odds a given person did the deed are 1/9. 50% of the odds of them being scum, if Yuna's a scummer, but didn't kill DK, she would only be 1/9, whereas anyone else is 2/9. For 3 scummers, it shifts to 3/9 and 2/9 for her, either way, she is less likely to be a scummer, she could still be one, it is simply less probable than random, that is sufficient at this time for me to strike her off my list of lynch candidates as a poor choice, but not to view her as def-town. Now, from the perspective of an y townie but me, this actually shifts, accepting me at my word on this and taking me for town, and knowing one's self to be town, changes other's odds for ninja-dom to 2/8 or 3/8, and her values to 1 in 8 or 2/8 respectively, there's other components I'll discuss should we mass claim that I feel work in her favor as well, but as said, she still deserves suspicion but should be assumed to be less likely to be scum than the average person. All this, again, is based off knowing she didn't kill DK, and knowing (presumably) that a scummer did, it proves nothing, merely tips the odds.

Now, in my opinion, though I don't expect to get the necessary support for this, our best move at this time is a structured massclaim. Were everyone to agree - or enough to force compliance - I would suggest we have everyone code their role into a message, then we claim openly and show where we coded. The coding aspect is tricky, and I have some suggestions and advice on how people can do this so as to limit the chance of it being cracked while showing it wasn't back-coded (decryption made up backwards to fit the newly desired role) while there may be some leaking from this, for practical purposes it would amount to the same effect as a mass simultaneous claim, and we'd have two shots to find our culprits off that before we'd be at risk of NK, with good odds of interference or protective roles stopping those attacks, since they'd only have 7 people to pick from and should have good odds of decreasing that through educated guesses from the mass claim and what follows.

I don't think people will accept this proposal, but let me point out before we discuss or reject it, that we often claim in mass on Day 3, rarely later than day 4, and for our purposes, the threat from massclaim today is identical to a day 3 mass claim. If we plan to massclaim on day 3, doing so today is of equal threat. More, it is quite probable that the ninjas haven't spent much time discussing fake RCs yet, day 2 rarely involves revealing so little need and you have to adapt as you see the roles come out. I think this can work, and if nothing else, it is a more appealing option than what we all know we will otherwise do, kill off low posters or BA voters or those who meet both criteria - those factors will likely still come into play, but it will leave room for much more meaningful discussion.

It goes without saying nobody should RC yet, we want everyone to reveal in such a fashion that they do not know anyone else's claim when they list theirs, then then need only state their role and show where they proclaimed it when everyone is done, even if some people slip up, we'll be no worse off then if they simply claimed normally, but a total success would equal a simultaneous claim and a partial - even assuming the ninjas take the time to try to decode, would be better than a normal claim. I will now claim, in such as way no one can doubt the claim I make is influenced by later claims, as an example

IPUFODTUDKQRWTRIONEFOR

Contained in that is my coded role message and sufficient data that on explanation it will be clear I was specifically claiming this particular thing, good luck anyone trying to crack that, it definitely isn't a piece of cake.