chikaidestroyer | ∞ 62: Quietly conducting business [voice]

Current Mood: worried

Entry tags:

∞ 62: Quietly conducting business [voice]

[Locked to Vyse, Yuri Lowell, Sigmund, Raine, Yuan]

Vyse. Mr. Lowell. Sir Sigmund. May I ask how your group rosters are looking at this time? It's been awhile since I've inquired about this.

And we should consider meeting in person. As soon as is practical to gather everyone.

/locked

I believe the experiment is over now. And not a moment too soon; the practical jokes were going stale.

And there are still New Feathers arriving... Hm.

Flat | Top-Level Comments Only

It's becoming far too common a trend for New Feathers to be left to their own devices, too. The longer they remain unattached to a cause, the more likely it is they will fall into the same pit of inactivity that some residents are in. I encourage each of you to advise your groups to reach out to New Feathers. We have an especially high amount of them now, considering the influx in the last month or so.

I can ask Sonic about the list. He made it back in April, I think, so it's going to need to be updated again. But at least it'll be better than nothing. Aside from that, I've made a note of which members of the Blue Rogues have healing abilities.

Anyway, if we want more involvement from New Feathers, we'll have to talk them off the journals and explain what's really going on. That's either in person or using those laptop things from the tunnels.

If they'll let us, we can tell them about it while taking them back to the village. That's something I told my guildmates to do a while ago, but I guess it didn't really stick for too long. Otherwise, we can keep doing it through the laptops.

Unless someone else has a better idea.

Edited 2009-08-13 21:51 (UTC)

Is there a type of code that we can use? Something that means little or nothing to the Malnosso, but that we can use to get around their surveillance? It would take a great deal of work to implement, but it could work towards letting the New Feathers know more about what is going on here.

Or another group similar to Canard could be established, with villagers specifically geared towards integrating New Feathers and explaining things that can and can't be talked about over the networks.

Codes would be something we could work towards implementing, as long as we were all on the same page with them. They could help with arranging meeting locations.

I was hoping that Canard would take the initiative, given the slight interest in it once more, but nothing seems to have come of it as of yet. We have a lot of work to do, in terms of getting our acts together with general organization.

In any case, the cycle has gone on for so long this time around that there is a lot of catching up to do.

Codes require constant vigilance. We could establish a new code each meeting, for security's sake. Ideas on codes and their meanings?

The issue with relying on another group to explain the situation is that they should not be held responsible for something everyone in the village should be aware of. If you have the opportunity to meet a New Feather in person, you should explain what you can. Canard does not even benefit from having a standard way of informing New Feathers of what is going on.

Hold your meetings at your discretion, if you must. But recognize the benefits -- especially considering the nature of this place. If you cannot account for a 'member' beyond their initial recruitment, should they be on your roster when a dangerous experiment or something else comes up? Case in point, the situation we are currently facing.

I hardly see the need for such a code. We've already established this is the safest location and Albert can easily round us all up if there's ever an urgent need for another meeting.

As for Canard, as far as I can tell it's out of the equation. That group lacks everything from members to proper leadership. If we want an entire organization to inform New Feathers of the situation, it should either be added to the list of responsibilities of our already existing factions, or we gather a new group of people alltogether.

The code thing sounds like a pain, but it could be useful for saving time. When it comes to Canard, getting in contact with whoever was in charge might be enough of a push to get them back into action. If that doesn't work, then what Yuan said works just as well.

Yuan, please do not dismiss the idea of the codes. It is our security that comes to mind, and we are not foolish enough to believe that an amount of filtering to the same group of people will be overlooked.

As for possible ones we could use... hm. That will take some though. Something of relevance to us all, and that we are not likely to forget over the passage of time. Or if need be, we could write them down. Perhaps a reference to a certain weather condition, or animal...

... as for Canard, I suppose they never really were "in action" to begin with, but it's something that does need be seen to. Although if it comes to it, I suppose I'll simply have to organize something myself. I probably should have, considering the guide. Luceti's number has grown quite a bit... there are a lot of people that some of us just don't know. While we can't be expected to know everyone and what they have to offer, we could be doing a better job of it.

Exactly. The code is a diversionary tactic, because they will notice our meetings in time. The Malnosso will catch on if we talk about it point blank, or if we cut away on the journals after talking about something similar. It could have plenty of purposes depending on how developed it becomes, but all of them start with the intent for secrecy. Once it's been developed, it will have been worth the effort.

I've heard little of Canard in recent months, and our numbers are growing larger. You have better connections than any one of us, Raine, but we are all here because of our responsibility and dedication to this village. If it is to be reformed, I think we need someone who is willing to devote themselves fully to the task. I know you would, Raine, but you're already busy enough. We should attempt to contact what's left of Canard, see if it is worth salvaging, then perhaps see if there are other residents who are willing to take up the task. There are plenty of able people here - it's a matter of utilizing them more effectively.

Start with something simple and harmless, and then see how efficiently it works. For example, "I want something to drink tonight" could mean we should meet tonight. Carry a bottle of liquor from the bar to complete the illusion.

I agree with your sentiments, Yuri, Sigmund, though I don't have a good opinion of Canard because of its past examples of instability. If it can be organized into something, good; if not, we will look at other options.

Our priority should be uniting whoever wishes to be involved. Those left in the dark will undoubtedly question the apparent stagnation in Luceti, which has been an issue in the past. If they wish to head out to the desert ruins, they should be told what to expect. If they wish to know about the tunnels, they should be told what we have been able to do thus far.

Sounds like an easy enough code. It gets the point across and isn't too suspicious for outsiders. As long as we agree on a new one at the end of each meeting, there shouldn't be a problem.

Edited 2009-08-15 22:41 (UTC)

Perhaps we should even treat that example as the code for our next meeting. "A drink tonight", "A drink tomorrow", with a suggestion toward the time of day. We will likely have enough time to brainstorm for the code for the next meeting as well, and take it from there.

I suppose there have been a few individuals expressing concern and interest in organization that could be of help. Perhaps something can at least be arranged with them, as far as establishing things go; it won't be difficult to arrange meeting with them, really. We've been here a long time. While fresh eyes see what we've all seen before, they may also have some new suggestions that we could incorporate. I have a few ideas as well, but I'll do my best to not get too involved.

As for our current situation, we aren't even certain what we're dealing with or if we'll be dealing with anything. But this is not the time for slacking off. We have some goals in mind; we simply need to find the best route to implement them.

Edited 2009-08-16 03:01 (UTC)

I'd say to be careful around anyone who looks out of place, but that's just about everyone here. We don't really have much of anything to go off of when it comes to identifying these guys either. I guess we'll have to wait for ANI to say something again and keep an eye out for any aggressive people no one's seen before in the meantime.

Edited 2009-08-16 04:55 (UTC)

Indeed. In the mean time, Yuri and Vyse, continue having your groups on alert. I'm sure everyone will hear if ANI contacts us again, but report anything strange as soon as you see it.

If no one has any objections to the current code, we will use it to call for our next meeting. I trust that all of you will be attentive.

Are there any other items that need to be discussed?

[Yuan gives a shake of his head.]

As far as I can tell, we've covered all the topics that are relevant right now. We have plenty to work with for a while and in regards to the current situation, there's no other option but to wait and see what happens. I suggest calling another meeting when all of this has blown over, so we can review matters then.

I have no objections. All the pressing concerns have been spoken of. When we have more to work with, then we can meet once more.

Then lets all hope that we make progress before the next meeting.

Yeah. Hopefully, we will.

Flat | Top-Level Comments Only

∞ 62: Quietly conducting business [voice]

[action // the meeting]

[action // the meeting]

[action // the meeting]

[action // the meeting]

[action // the meeting]

[action // the meeting]

[action // the meeting]

[action // the meeting]

[action // the meeting]

[action // the meeting]

[action // the meeting]

[action // the meeting]

[action // the meeting]

[action // the meeting]

[action // the meeting]

[action // the meeting]

[action // the meeting]

[action // the meeting]

[action // the meeting]