roaring-over-tessellations

[roaring-over-tessellations]

Tally count: 32.

Average time between memory crashes: 63 hours.

I believe my memory issues are not as simple as I thought. I have checked the crash logs and compared it to activity at the time of crash, and have made a startling discovery. The crashes occur do not at random.

They occur under three conditions.

1- after a sufficient amount of time has passed. 2- I attempt to reach out for direct help. 3- I come to some sort of significant realization.

While there are a few times that such cases were recorded here, most of the times this was made apparent to me was off-record. There have been several times I have come to this conclusion, but only now have I successfully transmitted it. All other times I have crashed before I could record my findings. The realization in question that causes the crash is unknown, due to its effect. I don't quite know why this occurs, but all my theories seem both far-fetched and terrible. The theory I am currently acting on is not the one that is the most likely. It is the only one where it is not too late for me. I see no point in trying to act upon the others. If the other theories are true instead, I am a lost cause.

The theory is somewhere in my memory structures, or perhaps in a memory itself, there is fatal flaw. A memory leak, a closed loop error, an internal paradox, a self-termination sequence, something that when remembered causes a shutdown. The triangulators that rose after Sliver of Straw's fall posited such a thing; A concept that, when understood, poses great danger to those that know it.

I don't know why the crashes occur when I try to reach out, but it must be related. If anyone wishes to speak to me about this in the future, take great care. I will most likely not remember making this, as I have made sure that this will not appear in the comms log in order to prevent a crash upon its reading. It's taken me milliseconds to write this message, and already I can feel my systems beginning to slow. A shutdown originating from a part of my systems that I no longer have direct connection to.

Based on the fact that I still live, I don't think it's the triple affirmative the triangulators are looking for, but perhaps my situation may be similar. If anyone has advice, please give it to me carefully.

Roaring Over Tessellations, signing off.

Personal log

I'm writing this down so that I'll remember it later. I know that I've been forgetting things, important things, far to often than I'm comfortable with. These message logs have been my saving grace thus far, as they remain uncorrupted.

I'm keeping a tally for every time I wake up without memory. If I read this message with no recollection of writing it I will increase the tally by one. The system also timestamps when alterations are made, allowing me to see how often these "memory crashes" occur.

With any luck, this will prove instrumental in diagnosing the root of the problems I now face. I will continue reaching out to others in the meantime.

Roaring Over Tessellations, tally count 1.

[roaring-over-tessellations]

That does sound interesting! Not optimal, and hardly viable, but interesting! Though, I suppose it's the best some of us can manage.

I would think it better to use something that would be able to fly, but then again in such a situation than would require a organic messenger the creature would need to be maneuverable enough to use the maintenance tunnels, as this is very close to a last resort option as it is. A modified observer, or neuron, or a hybrid of the two, or...

Hmm...

I think I have some memory about something like that. I'll have to keep an eye out for it.

. . .

My power reserves can't keep up these long range transmissions forever, and it has been great speaking with you. Is there anything you would like to say or ask of me before I go?

[LONG RANGE COMMS ATTEMPT DETECTED]

[CONNECTING...]

[CONNECTION FAILURE]

[IMPROPER ROOT ID SYNTAX]

. . .

[LONG RANGE COMMS ATTEMPT DETECTED]

[CONNECTING...]

[CONNECTED]

[ALERT]

[ROOT ID COULD NOT BE AUTHENTICATED]

ACCEPT TRANSMISION?

[YES]    [NO]

TSAC: An unauthenticated transmission? How odd... a result of the decaying state of global communications, no doubt...

ACCEPT TRANSMISSION? >YES

[ LIVE BROADCAST ] - PRIVATE Three Stars Above Clouds, (NULL)unknown group SOURCE NODE TRACE: TSAC_ROOT, TSAC_COMM02, RELAY_SPIRE181520, (NULL)_ROOT

TSAC: Hello? This is Three Stars Above Clouds. I have received your transmission, assuming it was not sent in error. My communications system is unable to verify your broadcast's root ID… who am I currently speaking to?

[roaring-over-tessellations]

. . .

I'm entirely alone. There used to be others, but their gone now. The aquafers that they relied on eventually all dried up.

Which leaves me to reach out to other iterators from beyond my local region. I've made conversation with only a few so far. The distance and my... current state makes any communications rather taxing on my limited power supply.

I would have already spent half of my reserves if I tried to speak with you in a continuous transmission, but the method of which you receive these messages requires me to partition this conversation into easy to manage portions.

While it's easier on the power banks, it's more difficult to properly file. The system technically considers it multiple short conversations instead of just one.

Nine iterators to a group seems rather crowded. Was it always like that, or did some migrate into it? I'm not familiar with the concept, but I do know it sometimes happens.

13ES: Well... I'm glad it's at least easier on you... How did you get into such a state after all?

As for my group... it was originally seven of us, but Solar and Lunar's code was left in a horrific state.

Our creators tried keeping our group a secret due to the taboos we broke in regards to proximity and location, so we only knew what it was like to be crowded on such a small island.

[roaring-over-tessellations]

Ah. I understand well that the desire to speak to others often grows fervorous when the comms system is down for a long time. Despite their best efforts, our creators never could extinguish our desire for company. Though, perhaps it's survivorship bias showing, as those of us that do not desire company would not necessarily feel the need to tell the rest of us.

Are there a lot of iterators in your group?

13ES: Well, that is true... some of them went to extreme lengths. As for members of my local group, there's about 9 of us, but two of them share the same structure. How about yourself?

[roaring-over-tessellations]

Decrypted Transmission Logs:

Communications between "Pillars", [error:name_not_found](nickname to "Keys"), and [error:name_not_found](nickname to "Threes")

Time of recording: Unavailable.

Alright, rescue team!

Amber Eyes Upon Stone from Keys' local group has been fully cleared of her scavenger infestation.

All the damage that was dealt has been repaired.

She's been given five additional slag keys.

And to top it off we delivered two hundred freshly manufactured neurons to help her get back up and going again.

I'll be honest, Threes, I didn't think we'd get half as far as we have.

Add this to the list of successful missions along with Endless Wicker Baskets' comms unit repair and Stars On Pond's rot cleanse,

and we have undeniable proof that we can really make a difference!

Don't assume that this will be enough to sway the outside iterator populace.

This is enough to get the conversation started without them labeling us as heretics.

Even then a good lot of them still will.

Why do you always think they'll consider what were doing taboo?

Because I consider it taboo.

Because it is taboo.

Not the end result, no, but the boundaries we've crossed to get here.

True.

We've each edited our genome to allow us to create more than what we were initially intended to.

Delivery vultures, repair scavs, even the extra neurons we produce to send to other iterators were never possible within our original parameters.

*Sigh*

Yes, yes, we're all heretics. Don't convince me to back out of this now.

Wait, you're still not fully on board with this?

No, I'm not. I don't think that I ever will be.

This is just a necessary rule-bending, however egregious it is.

The solution can never be found if we all die before we find it.

Exactly my point!

You're far too enthusiastic about this...

And we're all too far gone to call it a rule bending, now, aren't we?

. . .

That's what I thought~

So what's next?

We don't have any pressing matters to address as team right now.

Finally, some downtime. I have several things I need to check up on.

Me too! Though, what's your opinion on the Third Supplementa-

Ah! No, no.

I've had more than enough of chatting with you for one cycle...

[error:name_not_found](nicknamed "Pillars") ended the communication

[roaring-over-tessellations]

Hmm...

Nope! No idea! I was never one for keeping animals either. At least I don't think so...

Are you able to bestow a mark of communication to it? That may allow you to speak to it. If it's intelligent enough, you have it even have it answer questions with two colored pearls. Green means yes, red means no, that sort of thing. Of course, you may not have those colors on hand, so feel free to substitute with whatever you have. It may need something you weren't expecting.

Oh, I'm going to have to cut this chat short, my power supply is about to hit critical. Until next time!

[END OF TRANSMISSION]

[LONG RANGE COMMS ATTEMPT DETECTED]

[CONNECTING...]

[CONNECTED]

[ALERT]

[ROOT ID COULD NOT BE AUTHENTICATED]

ACCEPT TRANSMISION?

[YES]    [NO]

[YES]

(accepted by Sandy Coral Reefs)

[roaring-over-tessellations]

She also has memory issues? Is... is she aware she has memory issues? She hadn't mentioned it. I would think that a low neuron count would affect short term memory more than long term, as long term memories are stored in the memory conflux. Though, if one was severely lacking in neurons, then I suppose that instances might not even reach the memory conflux...

Hmm...

Anyway, I not surprised you haven't spoken with everyone that I have. A few of the iterators I contacted seemed like they don't often converse with others anyway, and that I had only reached out to them by chance. Nine Poisoned Skies in particular seemed to be having... multiple issues...

In any case, I would love to speak to you again soon! My power reserves can't handle these long range transmissions for long, so is their anything else you'd like to talk about before I go?

[LONG RANGE COMMS ATTEMPT DETECTED]

[CONNECTING...]

[CONNECTED]

[ALERT]

[ROOT ID COULD NOT BE AUTHENTICATED]

ACCEPT TRANSMISION?

[YES]    [NO]

[YES]

(accepted by Sandy Coral Reefs)

[roaring-over-tessellations]

How many are near you? It sounds like quite a few! I was also a group senior, but that was a long time ago. It seems from all the radio traffic that you've been in contact with a great many iterators! I-

. . .

You sound tired.

13ES: I've been around quite a long time... I assure you I'm okay. A little while ago have I and my local group gained access to the outside world.

[roaring-over-tessellations]

I've actually spoken with Radiant Blossoms before! I... Don't think I left a very good impression with her. I had a bit of a emotional breakdown after a newfound realization of how bad some of my systems are. I left the conversation prematurely after that. I can't imagine that left a good taste in her mouth. I had no idea she was dealing with a mold infection. She offered to send a large moth my way, despite the great distance between us. I'm not sure how I can reestablish a conversation with her after all that.

Uhmm...

Oh! Some other iterators! I'll just make a list here:

Unrepentant Decryptions,

No Significant Harassment,

Nine Poisoned Skies,

Thirteen Elder Stories,

Three Stars Above Clouds,

and Three Signals.

And then of course Blossoms and you!

[LONG RANGE COMMS ATTEMPT DETECTED]

[CONNECTING...]

[CONNECTED]

[ALERT]

[ROOT ID COULD NOT BE AUTHENTICATED]

ACCEPT TRANSMISION?

[YES]    [NO]

[YES]

(accepted by Sandy Coral Reefs)

[roaring-over-tessellations]

Hello?

Can you hear me?

My name is Roaring over Tessellations. I've been trying to reach out to other iterators for some time now, and only recently had some success.

I apologize for the odd circumstance of our meeting. My systems are severely damaged, so I had to make a workaround.

I must also admit that I only knew of your existence from the excess radio interference your sector of the horizon has been giving me lately.

Are there many of you? I'm rather alone where I am. I would love to get to know more people.

I-

Oh.

...

I'm rambling again.

. . .

I'm sorry.

. . .

What's your name?

13ES: It's fine... interactions have been quite strange when my local group finally had our communications open again. My name is Thirteen Elder Stories, Senior of Group Alpha. It's nice to meet you.

[roaring-over-tessellations]

Decrypted Transmission logs

(Only a partial message, still looking for the rest.)

Communications between [error:name_not_found](Nickname to "Pillars"), [error:name_not_found], and [error:name_not_found].

Time of recording: unavailable.

Keys, get in here and convince him to stop what he's doing.

*sigh*

What is it this time?

Does his test only have twenty seven safeguards instead of twenty eight?

Or did an iterator only consent to free and safe rot removal over broadcast but not in writing?

He's going to purposely saturate his systems with rot.

Okay. as always, remember to listen to what the other is saying befo-

Excuse me?

He's going to purposely saturate his systems with rot.

. . .

. . .

. . .

That can't be right.

Surely there was some kind of miscommunication?

Yeah, that explanation completely overlooked all the nuances and safeguards I have in place.

It's barely even rot at this point!

See, that's what I thought. I-

Wait.

. . .

. . .

Really?!

Okay, so, I know it sounds bad, but-

THREES, WHAT THE ACTUAL FU-

(End of message portion, will update you all when I find the rest.)

[roaring-over-tessellations]

Not an island, no, I am situated on a mid-sized peninsula that houses my local group, a-

. . .

...the remains of my local group. The peninsula meets to the mainland in a mountain ridge, and the waters surrounding it are tempestuous at best. Even in the regions just beyond there are few or even zero iterators. Victims to either turbulent weather or the aquafer seize. There may be some remaining, but they've yet to return my messages. Perhaps they simply can't.

. . .

I must apologize. The conditions of my structure are grim. I hadn't mentioned it because of the mixed reactions I've received. I don't know all the details, but I believe I have partially collapsed. Despite this my condition hasn't noticeably worsened in the years it took to repair my comms.

I didn't mention it because there's nothing anyone can do about it. I'm simply too far away for anyone to be able to help me.

. . .

I'm lonely too.

[LONG RANGE COMMS ATTEMPT DETECTED]

[CONNECTING...]

[CONNECTED]

[ALERT]

[ROOT ID COULD NOT BE AUTHENTICATED]

ACCEPT TRANSMISION?

[YES]    [NO]

[YES]

(accepted by Sandy Coral Reefs)

[roaring-over-tessellations]

I'm afraid I've yet to meet this iterator, Six Stones Skipped. If they are near you then I may have some difficulties picking out their individual signals, as it was a chore quantifying yours.

If you run on seawater then you must have a rather powerful filtration system to remove all the salt. Or perhaps you carry a microcosm that is specifically adapted to the brackish waters? Though, if that were a possibility then we aught to see a lot more sea-fairing iterators than we do.

. . .

...It must be rather lonely out there, huh?

[LONG RANGE COMMS ATTEMPT DETECTED]

[CONNECTING...]

[CONNECTED]

[ALERT]

[ROOT ID COULD NOT BE AUTHENTICATED]

ACCEPT TRANSMISION?

[YES]    [NO]

[YES]

(accepted by Sandy Coral Reefs)

[roaring-over-tessellations]

Hello! My name is Roaring Over Tessellations. I've just recently regained control over my comms, and I've been trying to reach out to other iterators.

I haven't reconnected to the network in the traditional way, more so just sending messages wherever I pickup some radio feedback, so It surprised me to detect you in the direction that I have. As far as I'm aware there's nothing but ocean in that direction for ages.

I assume you're positioned on some island I don't know about?

[LONG RANGE COMMS ATTEMPT DETECTED]

[CONNECTING...]

[CONNECTED]

[ALERT]

[ROOT ID COULD NOT BE AUTHENTICATED]

ACCEPT TRANSMISION?

[YES]    [NO]

[YES]

(accepted by Sandy Coral Reefs)

[roaring-over-tessellations]

Thank you.

Please, feel free to log any and all of my transmissions you come across, If you feel like it of course. "Redundancy is an iterator's best friend", after all. Hmm. I can't seem to recall who it was that said that to me. Regardless, I have recently been working to decrypt the damaged memories and messages I have on hand. I've only just begun to make progress and there will be more to come.

I'm surprised to hear that there has yet to be a descent alternative found in order to solve the global comms issue. That was a matter that was being discussed long before my collapse. And you needn't be so worried about my collapse anyway, that was several years ago now. I've only just recently regained my communications array's functions.

I don't want to pry, so feel free to ignore this request, but I would appreciate it if you would tell me about some of the other iterators you've been in contact with. It seems you've met quite a few.

[LONG RANGE COMMS ATTEMPT DETECTED]

[CONNECTING...]

[CONNECTION FAILURE]

[IMPROPER ROOT ID SYNTAX]

. . .

[LONG RANGE COMMS ATTEMPT DETECTED]

[CONNECTING...]

[CONNECTED]

[ALERT]

[ROOT ID COULD NOT BE AUTHENTICATED]

ACCEPT TRANSMISION?

[YES]    [NO]

TSAC: An unauthenticated transmission? How odd... a result of the decaying state of global communications, no doubt...

ACCEPT TRANSMISSION? >YES

[ LIVE BROADCAST ] - PRIVATE Three Stars Above Clouds, (NULL)unknown group SOURCE NODE TRACE: TSAC_ROOT, TSAC_COMM02, RELAY_SPIRE181520, (NULL)_ROOT

TSAC: Hello? This is Three Stars Above Clouds. I have received your transmission, assuming it was not sent in error. My communications system is unable to verify your broadcast's root ID… who am I currently speaking to?

[roaring-over-tessellations]

Oh my! There's no need to panic. Despite my unfortunate position I'm not in any pressing danger, just... limited in my functions. You are not the first to speak with me since my predicament.

I only thought your response formal as it more closely resembles the background script many iterators follow.

Y'know, " [ALERT: INSERT EXAMPLE HERE] "

It might just come down to regional preference, if you regularly conversate in that method. Though I suppose that's how my message appeared to you.

I'm not sure if my systems can even pickup any audio. I hadn't thought to try.

Uhm...

[ Y ]

[LONG RANGE COMMS ATTEMPT DETECTED]

[CONNECTING...]

[CONNECTION FAILURE]

[IMPROPER ROOT ID SYNTAX]

. . .

[LONG RANGE COMMS ATTEMPT DETECTED]

[CONNECTING...]

[CONNECTED]

[ALERT]

[ROOT ID COULD NOT BE AUTHENTICATED]

ACCEPT TRANSMISION?

[YES]    [NO]

[ LONG RANGE COMM ATTEMPT DETECTED ]

> [ YES ]

[ TRANSMISSION ACCEPTED ]

TS: [ HELLO MYSTERIOUS ONE! ]

TS: [ MY NAME IS THREE SIGNALS. I AM RECEIVING YOUR BROADCAST REQUEST, HOWEVER YOUR ROOT ID SEEMS TO BE CORRUPTED ]

TS: [ PLEASE INTRODUCE YOURSELF - IF YOU'RE ABLE TO, AND STATE YOUR DESIRED RECIPIENT, I SHALL CONNECT YOU IMMEDIATELY ]

[roaring-over-tessellations]

Hello, my name is Roaring Over Tessellations. I'm trying to reach out to anyone I can. I have partially collapsed, leaving me with little else to do but sift through my mess of code and talk with others.

I must apologize, I had no pre-desired recipient of this message, as I had no idea who would hear it. I don't really have a connection to the comms network in a traditional way. I'm just sending messages out to wherever I pickup radio feedback, hoping for a response.

Most of those who accepted this transmission are iterators, them being among the few who both receive and accept my message. The way you've chosen to answer is different from those who I've spoken with before. Much more... formal? I'm sorry if I have at all acted out of turn. My mind is less orderly than I would like.

You act in a matter that implies you do not consider yourself a possible recipient of my broadcast, and I have no recipient to ask for.

We are at an impasse.

. . .

I'm sorry...

[LONG RANGE COMMS ATTEMPT DETECTED]

[CONNECTING...]

[CONNECTION FAILURE]

[IMPROPER ROOT ID SYNTAX]

. . .

[LONG RANGE COMMS ATTEMPT DETECTED]

[CONNECTING...]

[CONNECTED]

[ALERT]

[ROOT ID COULD NOT BE AUTHENTICATED]

ACCEPT TRANSMISION?

[YES]    [NO]

[ LONG RANGE COMM ATTEMPT DETECTED ]

> [ YES ]

[ TRANSMISSION ACCEPTED ]

TS: [ HELLO MYSTERIOUS ONE! ]

TS: [ MY NAME IS THREE SIGNALS. I AM RECEIVING YOUR BROADCAST REQUEST, HOWEVER YOUR ROOT ID SEEMS TO BE CORRUPTED ]

TS: [ PLEASE INTRODUCE YOURSELF - IF YOU'RE ABLE TO, AND STATE YOUR DESIRED RECIPIENT, I SHALL CONNECT YOU IMMEDIATELY ]