skyem123

Well someone else can make a standard using CBOR. I won't steal their thunder, though I recommend to whoever does it, use a structure similar to this. ^^;

I chose MessagePack because I didn't think about or see the other thing.
Maybe another thing would be "better", but there's a point where you just have to pick something, and theoretically you could use a similar method on other ways to encode / store tables. For example, this could be done with the OpenOS table serialise function for extra inefficiency, however this specific standard uses MessagePack.

It's very hard to convert Markdown into what this forum uses, so the specification and example implementation is in a gist:
https://gist.github.com/skyem123/f5aa955699da26a5b8b9a6390552232a

I may change the wording or fix bugs, but the actual specification will not / should not change.

That's good to know, I'd say one port is better, especially if the users want to change it / remap it.

Why does GERT need 172 ports? That seems a bit too many. Theoretically you can stuff it all into one port, and have your own system for "sub" ports? I dunno, but it would probably be better/nicer if it only needed one port?

I see... it would make automatic configuration systems harder in general though.

For issues such as using up the server's processing power and security, don't worry about that. OC has a lot of strict limits that prevent that.

Making OC execute on clients would not really work and could actually cause more harm as now clients have to send a lot of data to the server, and the server would have to execute OC itself for each client's response to verify the client isn't cheating somehow.
The key thing that is useful for OC is robots and drones that do things with out any player intervention... they HAVE to be able to run without clients doing things for them.

I understand you want security and stuff, but compared to the general risk of running a Minecraft server, OC is not a big deal!

The two potential issues with storing files on your server are

1. You having to deal with potentially sensitive information being stored
2. Storage space on your server being used up.

(1) can be solved by warning people that storing stuff on a computer is like saying it publicly in chat or writing it on a an in game sign
(2) is not any real worry because OC has size limitations AND it'll be easier to just generate new terrain to use up disk by running a long way than it is to write files.

For the record, it should not be a guide on how to use it, and while your white-paper does explain the protocol, has unnecessary advertising for it at the start. Don't advertise, just describe how it works and why things are the way they are.

I'm reading this, and while it does seem like a good idea, using the port number as some sort of VLAN seems to conflict with other services and you using port 1.
Also, I am a bit worried about using port 1, as while it's a good number, someone earlier could have used it?

No... not a video. A text document describing technical details, like an RFC on the IETF.

First off, this formatting is terrible.
While I'm being nitpicky, this is standard thing rather than an advertising thing, so maybe don't describe why you think it's awesome, instead, focus on explanations of the protocol with neat graphics.

Anyway, it is good that  you have explained how your protocol works in a step by step way.

I have the same issue using Google Chrome on Windows 10, middle click opens the new tab, and it also goes to the link like I wasn't middle clicking.

Well, I have made miniOS (the FS system needs to be fixed, but you don't need that part) that is small, you could use it a base and modify it to suit your needs. You would need to write the code for the LUA interpriter.

This sounds like an idea for the "OS" of computers like the ZX Spectrum.

The autocompletion thing may not work as the CPU in opencomputers is slowed down to make it not overload multiplayer servers / your computer, If you implemented it efficiently, maybe?

I need more motivation to finish this...

The current major bug is the fs.resolve() function. If / when I fix that, I can make another "milestone" release.

If anyone wants to help, https://github.com/OpenPrograms/skye-Programs/blob/WIP/miniOS/minios.lua#L750 is the fs.resolve function.

It seems to resolve "." as "/".

2. wat.

You can't really mod Minecraft PE...

Are you sure in the server rack GUI you selected the right side for the disk?

Nickname: Skye
Age: 14
Minecraft Name: skyem123
IRC nick: skyem123

Output: true

t = { "World", "Hello", "and", "Computer", "Hello"}
o = ""
for k,v in ipairs(t) do
o = v .. " " .. o
end
print(o)

Well, you could have a look at my OS, miniOS.

It is less complex than openOS, so that might help you!

miniOS

MiniOS is an OS that is similar to early versions of MS-DOS. It crashes often, but it has one key advantage over openOS. It leaves around 100k of RAM free on 192k systems (Where did you think I got the name from?).

As of now the API is simple, all the libs are in the global namespace and require just returns what is in the global namespace.

THIS IS ALPHA QUALITY! BUGS WILL EXIST! BAD CODING!

Commands:

cmds - views all of the internal commands

<DRIVE LETTER>: - switches to the drive

Screenshot:

Download:

GitHub

version 0.5.9.4.zip (Old Version use GitHub!)

Todo list, if you want to help me:

GitHub TODO.txt

GitHub Issues

Todo, Continued:

Use address instead of drive letter for locating command.lua?

Unix FS loadable driver?