Izaya

Minitel
Minitel is a simple, efficient networking protocol implementing layers 3, 4 and 5 of the OSI model. It supports automatic configuration and routing over large and small networks.
Currently supported platforms include OpenOS, KittenOS NEO (via this package), and embedded devices.
Features include:
Flood routing with route caching Reliable packet delivery Packet segmentation Ordered delivery Bidirectional, ordered, reliable streams Installation instructions and API documentation can be found in the Github repo, though they can be summarised as "oppm install minitel".
Demos:
Minitel and the net API Mail over Minitel FRequest in action

Bumping because it's basically been re-written; we're on 2.0 now, and it has some big improvements:
Better re-connect logic Multiple connections pcap capture support for the vTunnel bridge with a wireshark plugin for dissecting Minitel packets Additionally, this post will contain a list of known public relays:
lain.church, port 4096 luna.nosafe.space, port 4096 (thanks @Adorable-Catgirl )

vTunnel can be used to add bridging over the internet to any existing OpenOS software that uses linked cards.
Despite originally being written for Minitel, vTunnel implements a fully-functional linked card emulator and a server that will run under most unix-likes (OpenBSD is currently somewhat flaky, Linux is recommended).
You can peruse the page on Github, for documentation and protocol information.
Install it with oppm:
oppm install vtunnel Additionally, you can read the documentation in-game with
man vtunnel  

Hey! I'm asie, and while I'm not an official certified OpenComputers developer, I contribute to the project from time to time. However, for a long time, I've had some types of patches in the pipeline that couldn't quite reach the upstream - fixes and changes like:
a screen renderer rewrite, with major performance boosts; updates to JNLua and LuaJ, fixing bugs and significantly improving performance; Lua 5.4.0 support. For the purpose of testing these changes as a way to see if they are ready for mass adoption, I've created a fork of OpenComputers called OC-Staging. It is available right here to download. The more people give their feedback (even if it's as simple as "I've ran it on my server, no problems found!"), the sooner we can bring those changes and improvements to upstream - and also, free resources to working on more exciting changes!
To give feedback, please post in the feedback thread or report bugs on the issue tracker. You can also find me on the #oc IRC on EsperNet.

Ever needed real-world time in OpenComputers? I did today, so I did something about it.
realtime
realtime is a set of libraries and protocols designed to let you synchronise your computers with the real world, and includes:
The realtime library, for taking and keeping time. The realtime-sync daemon, for synchronising your realtime library with the real world The realtime-relay daemon, for synchronising your realtime across the local network. All of these can be downloaded via oppm, or from the Minitel GitHub repository.
Additionally, all of these come with manual pages describing their functionality and usage, all of which can be found here.

Features:
FlatScreen Panel 
frameless screen which can be configured to be "rotated/tilted" on the x/y axis and can render transparent (they work as normal Screens, Touchinput will be improved in the final release)
CardDock 
external housing for OpenComputer Cards which can be bound to any machine in the Network
Cases
additional Tier3 computer cases from ZefTheFox
 
Download on curseForge for Minecraft 1.12.2
https://minecraft.curseforge.com/projects/ocdevices
 

Wow, isn't it annoying to write EEPROMs? Don't you hate how messy they are?
Well, I have the utility for you! LuaComp!
LuaComp
A general purpose Lua preprocessor and minifier.

Building
To build, either execute luapreproc or luacomp on src/init.lua

luapreproc
Execute luapreproc init.lua ../luacomp.lua

luacomp
Execute luacomp init.lua -xO ../luacomp.lua
NOTE: Do not use a minifier, it breaks argparse!

How-To

Merging Lua source files
-- myfile.lua local my_lib = {} function my_lib.hello_world() print("Hello, world!") end -- main.lua --#include "my_file.lua" my_lib.hello_world()
Getting enviroment variables
print("This was compiled in the shell "..$(SHELL))
Macros
@[[function my_macro(a, b)]] print("Hello, @[{a}]. Your lucky number is @[{b}].") @[[end]] @[[my_macro("world", 7)]] @[[my_macro("user", 42)]] @[[my_macro("Earth", 0)]] @[[my_macro("Satna", 666)]] @[[my_macro(os.getenv("USER"), os.getenv("UID")]]

OC-ports
OC-ports provides a database and library for using said database to cross-reference between protocol names and network port numbers. The database also contains the entity that registered the port(s) and, if applicable, a link to more information.
API
The portinfo API provides one function:
portinfo.search(*query*, [*database*]) table: result The search() function takes your query - either a string or a port number - and searches the database, defaulting to the OC ports database, for your query, returning the first result as a table in the format:
name port registered by more information This is more than enough to use for simple port lookups and generating tables.
Reserving ports
To reserve a port in the database, please submit an issue on the GitHub repository.
Download
portinfo can be installed via oppm from the Minitel repository, using the command
oppm install portinfo Additionally, to install manually, place portinfo.lua into /usr/lib/, and both oc.db and minitel.db into /usr/lib/ports/.

Ever needed real-world time in OpenComputers? I did today, so I did something about it.
realtime
realtime is a set of libraries and protocols designed to let you synchronise your computers with the real world, and includes:
The realtime library, for taking and keeping time. The realtime-sync daemon, for synchronising your realtime library with the real world The realtime-relay daemon, for synchronising your realtime across the local network. All of these can be downloaded via oppm, or from the Minitel GitHub repository.
Additionally, all of these come with manual pages describing their functionality and usage, all of which can be found here.

Ever needed real-world time in OpenComputers? I did today, so I did something about it.
realtime
realtime is a set of libraries and protocols designed to let you synchronise your computers with the real world, and includes:
The realtime library, for taking and keeping time. The realtime-sync daemon, for synchronising your realtime library with the real world The realtime-relay daemon, for synchronising your realtime across the local network. All of these can be downloaded via oppm, or from the Minitel GitHub repository.
Additionally, all of these come with manual pages describing their functionality and usage, all of which can be found here.

OpenSolidState
for Minecraft 1.12.2
____________________________________________________
Source Code and builds can be found on Github.
Note: Requires Forgelin.
 
General Purpose (E)EPROMs?
Have you ever wanted fast storage? How about wanting to boot PsychOS 2 on a uC? Well, now you can! There are two main variants: The card and the drive.
 
The Card!

 
The Drive!

 
Tiers:
Tier 1 - Manually erased EPROM, erased with the assembler. 64KiB Tier 2 - Electronically erased! Still 64KiB Tier 3 - Bigger EEPROM! 128KiB!  
But how do I craft them?
Just use JEI, trust me.
 
What else is included?
A utility floppy and ROMFS boot EEPROM are included with the mod!
 
Feel free to ask more questions!
 
i need to make docs

Minitel is a simple, efficient networking protocol implementing layers 3, 4 and 5 of the OSI model. It supports automatic configuration and routing over large and small networks.
This topic contains links to all known Minitel protocols.
Core protocols (OSI layers 3 through 5):
protocol-3.md - describes the format of Minitel packets and basic behavior of each node. protocol-4.md - describes how ordered sequences of packets should be handled. protocol-5.md - describes how Minitel's bidirectional streams work Application layer protocols:
FRequest - a simple file retrieval protocol MMail - simple mail delivery protocol If you wish to have a protocol added to this list, post it here.

Have you ever wanted to encrypt something but couldn't afford a T2 data card? Well, look no further than icekey-lua and Igloo!
Low Level: IceKey
IceKey is the low level library. It's no RSA, but it should work for most purposes in OC. If you want to learn more about ICE, click here. Useful if you want to do more with the block cipher, rather than just encrypting files or whatnot. It can be found here.
High Level: Igloo
Igloo is the high level library, great for encrypting/decrypting files. Automatically uses a CBC and padding. It can be found here.
 
PRs welcome!

Minitel
Minitel is a simple, efficient networking protocol implementing layers 3, 4 and 5 of the OSI model. It supports automatic configuration and routing over large and small networks.
Currently supported platforms include OpenOS, KittenOS NEO (via this package), and embedded devices.
Features include:
Flood routing with route caching Reliable packet delivery Packet segmentation Ordered delivery Bidirectional, ordered, reliable streams Installation instructions and API documentation can be found in the Github repo, though they can be summarised as "oppm install minitel".
Demos:
Minitel and the net API Mail over Minitel FRequest in action

uncpio is a rather simple binary CPIO extractor (File begins with 0x71C7 or 0xC771, made with cpio -oHbin). To acquire uncpio, run
pastebin get YbrVjRwa /bin/uncpio.lua To use, make the directory you'll be extracting your CPIO archive to, cd into it, then run
uncpio path/to/your/file.cpio And it will extract to the current directory. Currently only works in OpenOS, as far as I know.

Please calm down.
There are some component methods that block the computer for a tick when called, yes. Such methods usually interact with the world. For example, a transposer allows to transfer items between invetories by calling the transferItem method, which takes a tick to execute (so you get up to 20 stacks/second).
On the other hand, there are a lot of direct methods, which can be called several times per tick. For example, the GPU's methods are direct. And the processor (as well as RAM) determines how many direct calls are allowed per tick. I think T2 T3 setup allows you to call gpu.get one thousand times every tick. Or 256 gpu.sets. Or 128 gpu.fills.
I also believe you don't realize how bad ComputerCraft is for servers. A really simple and stupidly-written program can eat up all the memory the server has. That's why OC limits the memory available for an in-game computer. And running CPU-intensive tasks on a CC's computer makes the whole server run slow, whereas OC requires scripts to pause to allow other in-game computer to run. OpenComputers imposes the limits not because the mod developers want users to suffer (although I do sometimes think of that when I try to do some stupidly complex things with it), but to make it server-friendly.
What's important is that OC allows you to configure these limits for your needs. Have you opened its configuration file? It is more than a 1.5k lines long, and has more than 300 settings you can change, each with a comment that explains the effect of the setting. There's callBudgets to increase the direct call number limit. Or decrease it. There's also the ramSizes setting for memory, and hddSizes for the HDD sizes.
But even with all of these limits, OC can run a lot of programs, including graphical shells, 3D games, reactor control systems. It allows you to send HTTP requests to the real websites, and open raw TCP sockets to interact with network services. It can display 320x200 images. It can even play videos — inside the game, and on the default OC settings!

The sound card is added by Computronics, a wonderful addon for OpenComputers. There are a few who actually know what it does. Even less people are able to use it. No one dares to understand how it works, or so I hope.
Anyway, it appeared a few years (?) ago, and is still mostly undocumented. There is a page in the in-game manual, which fails to explain how great the card is. Of course it does! It has a heap of different methods, which you can use to cast many crazy magics to make the sound card sound, and it's impossible to teach someone to do magic by reading a single page.
OK, I'm serious now. Last year I managed to understand how to use it, and even wrote a few posts about that. In Russian. Half a year later, I translated them to English. And now I thought of posting a topic here so that you could read them, too.
Here's the link.
The first two parts are all about basic things, like getting simple sounds, ADSR, and modulation. The third part features a little bit more complex things, like complex numbers and Fourier transforms. I tried to keep it simple, so I could get something wrong. If so, please leave a comment there pointing out the mistake. Grammar fixes are also highly appeciated.

vTunnel can be used to add bridging over the internet to any existing OpenOS software that uses linked cards.
Despite originally being written for Minitel, vTunnel implements a fully-functional linked card emulator and a server that will run under most unix-likes (OpenBSD is currently somewhat flaky, Linux is recommended).
You can peruse the page on Github, for documentation and protocol information.
Install it with oppm:
oppm install vtunnel Additionally, you can read the documentation in-game with
man vtunnel  

The following document is still a DRAFT and a subject to change, though protocol and assigned numbers should not change.
 
1. Purpose
ON2 - OCNet L2 protocol - is a very simple standard is aimed at advanced network stacks. It provides protocol tagging and optional vlan separation for devices that support it.
 2. Protocol
ON2 utilizes the fact that OpenComputers network message can have multiple parameters. When a message(data frame) is sent using ON2 layer, the implementation sets first data parameter to protocol number and passes the data via second data argument. Port number(if supported by device) can be used as VLAN tag allowing network separation. Default port number(vlan) is 1
Here is an example modem call for sending data frame with protocol 0x46 (IP frame):
component.invoke(modem, "send", dest, vlan, 0x46, ip_data) 3. Implementation recommendations
Each network stack implementation should default to listening and sending on port 1. If packet of with unknown protocol number is received is should be silently dropped. Implementations should pass local/remote address and interface information(modem ID, vlan or interface object) to higher layers.
4. Protocol numbers:
Protocols are identified by numbers assigned in table below.
|-------------------------------------------------------------| | PROTOCOL NUMBER | PROTOCOL NAME | DEFINING STANDARD | |-----------------X--------------------X----------------------| | 0x0C | OC HOST DISCOVERY | OETF #9 | |-----------------X--------------------X----------------------| | 0x46 | IPv4 or IPv6 Frame | RFC791 and RFC2460 | |-----------------X--------------------X----------------------| | 0xCF | OHCP CONFIG PROTO | OETF #10 | |-----------------X--------------------X----------------------| | 0x1000 | MultICE | ??? | |-----------------X--------------------X----------------------| | Above 0xFFFF | User defined | N/A | |-------------------------------------------------------------|  
You can apply for assigning protocol number by a post in this thread.