Lizzian

I've been working on a new server called "Freedom And Creativity" (Name subject to change). This is a creative building server set in a standard minecraft world. It features mods such as LittleTiles and OpenComputers, so whether you're a builder or a programmer you can find something to enjoy. This modpack is rather light-weight and should run on a wide range of machines. The server currently has 2.5GB of ram allocated to it, so please forgive any minor lag, in my testing it has maintained a solid 10-15 TPS while generating terrain. The player cap is currently 20, but may be raised or lowered as performance is measured.
We feature a ranking system, currently consisting of 3 main ranks. As you progress through them you will gain the ability to claim more chunks using FTBUtilities.
IP: 71.60.135.124
Modpack
Twitch Profile - https://drive.google.com/open?id=1Aa1_jlnVbTlsUVTiCXSL_LUL1TZaybVw
Raw mods folder - https://drive.google.com/open?id=1jStLpatxC32Q9cwYU4XuFyJEWg_HFQ8e
The modpack may be subject to change, to update mods to their latest versions. The mods, particularly littletiles, are still in development and are subject to frequent updates.
The mod compilations were last updated 3/8/20 at 5:37 EST

no primary 'modem' available.  It's looking for a component that provides "modem" Likely a network card, or a linked card.

OpenScreens
for Minecraft Forge 1.12 to 1.12.2
                                                                                                    

 
OpenScreens adds more display options for OpenComputers.
Curse Link: https://minecraft.curseforge.com/projects/openscreens
 
Holo Screens
Holo screens are floating displays with adjustable size and color.
 

Hologram projector model and texture by ZefTheFox
Right clicking a holo screen with a dye will change the background color. Right clicking the sides with an empty hand while crouching adjusts the size of the display.
 
Flatscreens
Flatscreens are simple displays that are... flat! There's two types, one on the front of the block and one on the back to allow more freedom.

 
I have questions/need support! Where can I get help?
You can always ask in my Discord server. If your issue is related to OpenComputers, you can read the OpenComputers Wiki. Report bugs here.
 
My website: https://itsmeow.dev/
Discord Server: https://discord.gg/zrjXjP5
 
Curse Link: https://minecraft.curseforge.com/projects/openscreens

Zorya BIOS
Zorya BIOS is an extendable and configurable BIOS and bootloader, capable of booting any OS with the right extensions. It's similar to GRUB.
(sorry in advance for bios.lua)
All you need to install the BIOS is to flash bios.lua to a blank EEPROM, insert a blank floppy, then reboot. Note: This has only been tested on Tier 3 hardware and Lua 5.3. requires an Internet card.
Github repo
PRs are welcome!
 
Future plans:
Ability to load from non-managed disks (like disks formatted with msdosfs, etc) Make it easier to extend Clean up code! Ability to edit options from bootloader Automatically load an OS after n seconds

The pastebin link you're trying to use has expired/been deleted/removed.
 
Not sure what one you were trying before but this might be good to look at
 

https://minecraft.curseforge.com/projects/openpython
https://github.com/EcmaXp/OpenPython
OpenPython makes micropython available on OpenComputers.
micropython is Python for embedded devices and is different from CPython.
Currently, micropython is partially compatible with Python version 3.4 as of October 2018.
Features include:
- Fully persistable.
- Runs in a sandboxed environment and does not require a separate native DLL.
- Supports virtual file system.
- It can call other components and supports Lua architecture's UserData.
Limitations include:
- The firmware is 256 KB and the memory limit has the same limit as the Lua architecture, but the stack is allocated in a separate memory.
- Most modules are difficult to use because the battery is partially included.
- The operating system is not yet fully implemented, so the Python interpreter now runs.
- Ctrl + C is not supported, so if you accidentally run infinite repeated code, the only way to stop it is to turn the computer off and then on.
To use the Python architecture, you need the following items:
- EEPROM (OpenPython): I'm sorry, but you have to bring items from the Creative tab.
- Floppy Disk (OpenPython OS): This item can be obtained by creating a floppy disk and Scrench, or you can check it on the Creative tab.
- OpenPython CPU: You can choose OpenPython architecture by holding Shift + Right Click on the Lua architecture CPU.
It is still unstable, but we plan to make further improvements in the future.
I need help from people who are familiar with OpenComputers and Python.
Thank you for playing.

For now I will quote Negi, I'll write something proper here later

Hi everyone.     A while back I promised more releases, so here you go: Big Reactors Grid Control is a multi reactor/turbine controller for Big Reactors and Extreme Reactors. Mission goal: Be the best big reactors controller there is. Nothing more, nothing less.
First things first - here's the website: https://tenyx.de/brgc/
NOTE: Due to a bug with OpenOS 1.7.4, BRGC will not work with that version. Please update to 1.7.5.
Main features Active and passive reactor support Support for multiple reactors and turbines at the same time (n:m) Control active and passive reactors with the same controller Automatic configuration of everything (EVERYTHING!) Setup instructions
wget the installer from here: http://xypm.tenyx.de/standalone/brgc_installer.lua Run it Done Big Reactors Grid Control comes with three rc.d files:
/etc/rc.d/brgc_reactor.lua /etc/rc.d/brgc_turbine.lua /etc/rc.d/brgc_grid.lua If you want the controller to run at boot time, you can just use OpenOS' rc.d schema.
  There's a GUI as well as a command line utility for advanced users.
To start the gui, simply run "brgc_gui" and watch the magic happen.
The gui scales the screen resolution to match the screens ratio and should scale with basically all screen setups.
I recommend 3x2 or 4x3 screens.
 
As of now the command line utility allows you to do (almost) everything you can do with the GUI and also allows you to change the controllers configuration at runtime (if you so desire).
Check out "brgcctrl help" for further information.
 
How to set up the grid
In a basic setup you just interconnect everything:
All active reactors can output steam to all turbines. All passive reactors and turbines output energy to the same grid.
You CAN have passive reactors and turbines output energy to different energy grids.
While this poses absolutely NO problem for passive reactors, you will have to set some turbines to "independent"-mode (more on that below).
If you want your reactors and turbines to properly cooperate, you'll also need to connect at least one energy storage block to your energy grid.
Currently supported storage "blocks" are:
EnderIO Capacitors (requires the mod "Computronics") Draconic Evolution Energy Storage multiblocks. RFTools Energy Cells Thermal Expansion Energy Cells Mekanism Induction Matrices You can connect them using OpenComputers Adapters.
 
Discovering new components As mentioned before the controller tries to autoconfigure everything:
 
Passive Reactors When a new passive reactor is connected to the controller, the controller will first try to measure its maximum energy output. The reactor will have its output increased step by step and the average (interpolated) maximum will be used for that value (CALIBRATING).
After calibration has been completed, the controller calculates the most efficient energy output of the reactor.
 
Active Reactors
When a new active reactor is connected to the controller, the controller will first try to measure its maximum steam output (CALIBRATING). For this to work correctly the reactor must be able to output at least SOME steam (read: you need a consumer) and you will need to provide sufficient ammounts of water. The controller will detect reactors with a potential steam output greater than 50 B/t and limit its energy accordingly.
 
Turbines
When a new turbine is connected to the controller, the controller will first try to measure its maximum energy output (CALIBRATING). For this to work, make sure your turbine is built correctly. This means your turbine can be run at maximum supported steam (25mb/t per blade) without exceeding 1950 RPM. Should your turbine exceed 1950 RPM at any stage, the controller will shut down the turbine and flag it as failed.
Note: Your turbine is NOT required to be able to process 2000 mB/t. Smaller turbines work perfectly fine.
 
Screenshots
After this wall of text, here're some screenshots (pre 4.2).
 
Setup:  
Main view:
 
Passive reactor details:
 
Active reactor details:

 
Turbine details:
 
Let's go in order:
When you start up the GUI you will be presented with the main view.
Here a combined overview of passive reactors, active reactors and turbines will be presented.
You can click (or touch) on any of these items to open up a detailed view of the component.
Here you can enable/disable the component or change its behaviour.
 
What behaviour? This is where it gets interesting.
 
Passive Reactors You will notice that passive reactors have two modes and an "auto" mode.
 
PWM This is the behaviour everyone knows: The reactor gets turned on when its internal energy storage drops below 10% and gets turned off when the energy storage exceeds 90% of it's maximum capacity.
In PWM mode the reactor will generate energy at its most efficient rod level.
Overall this mode allows the reactor to generate energy as efficiently as possible as long as your actual energy consumption is below or equal to its optimal energy output.
But sometimes you need just a bit more energy and you don't want to upgrade your reactor or build a new one. "Classic" controllers will fail to produce sufficient ammounts of energy here.
 
This leads me to the second behaviour: Load
In "Load"-mode the reactor will always aim to produce energy at the same rate as it's consumed. Maybe some people already suspect what that mode is all about: It's a PD-like regulator.
While "Load"-mode is not as efficient as PWM-mode in situations where the energy consumption is below the optimal energy output, it will guarantee you're never running into energy shortages - provided you're not exceeding the reactors maximal capacity.  
Auto "Auto"-mode aims to eliminate the disadvantages of both modes by combining them:
If the energy consumption can be satisfied with PWM-mode, PWM will be used. If the energy consumption is above optimal levels, "Load"-mode will be used instead.
As a result, "auto"-mode generates energy as efficient as possible while always saturating your energy demands.
 
Active Reactors As of now, active reactors only operate in "load" mode. Steam is consumed and produced way too fast and the reactors internal steam storage does not allow for anything else.
 
Turbines
Turbines controlled similar to reactors in "load" mode: The controller will always try to balance the turbines internal energy storage out to 50% by using a PD-like regulator.
Turbines can be operated in "ganged"-mode or in "independent"-mode, with "ganged"-mode being the default.
The only difference between these two modes is that turbines in "ganged"-mode can be shut down by the controller, while "independent" turbines will always be active, even if they overproduce energy at the lowest RPM allowed.
This is handy if one (or more) of your turbines produces energy for a seperate (dedicated) energy grid but has to be controlled by the same controller. If such a turbine is not in "independent"-mode it may be shut down which will lead to energy failure in that grid.
 
That's it for now. If you have any questions, want to report bugs, etc., feel free to drop a message here.
Also: Do you want an indepth tutorial on how to use the command line utility? Need a description on what the GUI is actually showing?  
Have fun XyFreak  

The Open Engineering Task Force is a bit like its real world counterpart, the IETF, if I recall correctly. This place is basically to discuss protocols and standards defined for communication between computers in OpenComputers, I'm guessing.
 
If I recall (I think it was) Lizzy's words, we can submit new RFCs here, comment and expand already existing ones, things like that.

Hello all, I'm here to announce the release of OpenSecurity!
Build Status: 
Downloads: https://minecraft.curseforge.com/projects/OpenSecurity
Change Log: http://ci.pc-logix.com/job/OpenSecurity/changes
Source: https://github.com/PC-Logix/OpenSecurity
OpenSecurity adds Items and Blocks that are useful for the security of your worlds or bases.
 
Documentation has been moved to GitHub: https://github.com/PC-Logix/OpenSecurity/wiki