reverienet | text | un: hudie

Three things.

1 -

I have a network-based service for task coordination up and running as of now. It's a BBS-style system hosted on a spare communicator. Project leaders can upload files, maintain contact lists, issue automated alerts to individuals or groups within the project, etc. Project members' permissions are set by the leader, but they can access the main board and receive alerts from the group by default, and have options to use the contact lists to send messages through the service, download and upload certain files, check in to report what they've done, etc.

Send "DOCS" to @bulletin for the manual. If you want to host one, send "NEW" and it'll take you through an automatic setup process. Right now it's set so each account can run one board, to keep traffic low, but if you need more I can manually set them up.

Credit to Haru Okumura for user experience feedback. It was designed for the garden, but should be customizable for any project.

2 -

There's a calendar running on the garden board, but I didn't want to implement calendar functions across the service yet...because we don't know what year or month or weekday it is. The comms don't have dates, but there's a decently reliable timekeeping system based on computer ticks. Should the station reactivation be Day 1 and calendars just count up from that? Seven-day weeks? This is all a UI question, not a system one. I need some input.

3 -

I found a manual for the VR hardware. The sets are still NOT confirmed safe for use. There's a lot to look through before that, probably more than checking over the sets themselves would cover.

But if there's anything from this you're interested in, I can look into it. Checking this against other device standards, salvaging useful parts, etc.

If there's any chance of modifying these so they're sure to fail to safe, and getting into the controlling computer, I'd like to make a zero-G training simulation. That's a lot of ifs, though. And it's a way lower priority than opening more doors and gaining control of the station control systems, so this won't cut into work for that.

[[ooc: if you have any questions about how this thing works, hmu, my technical knowledge is wobbly but i can at least say oh yeah it can/can't do that. It's a network-based system - like, you send a text to @bulletin with your project login info, it sends you a text back with the current project board in full ASCII glory and the keywords for viewing specific info, getting files, etc. Messages sent via the service come from @bulletin with the sender's name and the project name front and center. Alerts can be set up to be automatic but come in as texts. It's a BBS service by way of email groups by way of a massive stack of scripts running on one poor little communicator.

Also the security on it is diamond fucking hard.

If you want to lmk when someone sets up a board, so that I have an OOC tally of IC knowledge, that'd be swell.]]

Threaded | Flat

Been thinkin' about the calendar thing.

What if we just take the date that everyone woke up as 1/1/0 and go from there? At least we'll have some sorta frame of reference to talk about time here.

[Yeah, he's been keeping track of the number of days they've been here, but even then, he can't even tell if it's accurate.]

Also, dude... this is a ton of work. You've been gettin' some time in to do other stuff too, right?

I was following you initially, but you've lost me. Can I ask you to help guide me through this in person?

everything i've seen around the station is making me think this place is from Earth. If we follow an Earth-based calendar, it might make more sense?

While evidence suggests this station may have originated from Earth, that is not Earth that it is currently orbiting.

A calendar based on sun cycles would not be helpful. One that charts the revolutions of the station would.

So, you were the one arranging the scheduling for Okumaru-san. I appreciate your efforts.

As for dating systems while considering the new information presented: we have no frame of reference as to "when" 2654 occurred. Consequently, a dating system following the typical Gregorian calendar with a start year of "0" while treating the first arrivals' collective awakening as the start should be fine. Further complicating the systems already in place creates unnecessary trouble, given we'd then have to adjust our communicator's internal time systems to suit it. As we're already running on military time, I believe it would be easiest to continue running on it.

Of course, there's the potential for multi-functionality. A board that offers typical calendar dates for Earth societies and a numerical equivalent (such as Day 1) might be an adequate compromise.

[ Might as well work with what they got on their communicators already. Trying to sync everyone to a new time (willingly) sounds like a nightmare. ]

Can you simplify what you said a little more? I don't get any of it.

[A2 YOU'RE A FUCKING COMPUTER....]

So does that mean we'll have an up to date list of the different projects people are working on? That's really useful.

@skull

text: un: brightness_kholin

text; un: burton

un:1

@r.asuka

un: A2

un: apollo2