It will now again be possible to speak directly to the Grid Owner, Starflower Bracken, through public chat from anywhere on the grid. If you want a more virtual world experience, please go to one of the enquiry centres, the Beach Bar on Annwfn, either the Quay House or the Harbourmaster's Office on Celyddon, or the main bar of the Merry Maids Inn on Gododdin and, as if by magic, her avatar (or rather, an NPC representation of it) will appear and she will speak to you through it. Please be patient if you do not get an instant response but be assured that Starflower (or Star, if you prefer) will be doing her best to be available. Sometimes she may be busy, working or using a phone to type! You don't need to be in one of these specific locations to get in touch.

Please say "Starflower" or "Star" in public chat to increase the likelihood of being immediately noticed on the in-world chat.

For a technical and administrative explanation, please read further:

Today the IRC backend has been restored so that ONLY admninistrators can see public chat, although it isn't normally recorded unless a suspected breach of TOS is being investigated (which has never happened on Ocean Grid to date). It may be possible to add an XMPP bridge, although this isn't a major priority and will only be done if in-world chat remains entirely secure.

These chat servers were never used except by administrators when they were last in use, so even if they are made publicly accessible again, channels connected to the in-world public chat channel will not be re-opened to the outside. People in-world would not know who was listening and could be spoken to anywhere by anybody on the channel, which would make potential for unpleasant misuse of the chat channel. Use by administrators or welcome staff is entirely different and can help to provide a more personal experience to visitors who could not otherwise easily make contact in person.

The available RAM on the server running five simulator-regions (one region per simulator) has been increased from 8GB to 32GB (DDR3) and performance has been radically improved as a result. Even for OpenSim, which is quite heavy on memory, this is a lot.

Ocean Grid is still operating on an old Intel® Core™ i5-2400 CPU @ 3.10GHz x 4 processor with 1TB hard drive space. However, it is more than capable of running a Linux server.

The grid has been down since 2020 as a result of a server hardware fault that has now been rectified. Hooray, we are back.

The service is no longer available, as happened to its predecessor HYPEvents. We hope that this will be resolved somehow.

Resolved by a server reset following an enquiry.

It is now possible and recommended to log into Ocean Grid securely using TLS (often wrongly known by the name of its now defunct predecessor SSL). The OpenSim software does not directly allow this, although simulators can communicate with the ROBUST server and the viewer by secure ports (for example the 1280x1280 test region Rheged on Ocean Grid). However, it is possibly to achieve secure logins using a reverse proxy like Nginx, which is what was used here. The port that has been used is 9002. The information on the web site has been updated accordingly. The insecure port 8002 is still available for the reasons explained below. Both work fine. Please use the secure port if you can.

A blog post detailing how this was done can now be found will appear on Starflower Bracken's blog in the fullness of time. We have used Let's Encrypt certificates and these are accepted by the viewer. If you get an SSL connect error, please read the next paragraph because it DOES work and it's not a problem with the grid:

Issue: there is a viewer bug [FIRE-24068, SV-2392] in all older viewers that prevents the Grid selector from allowing https:// prefixes, which is annoying. This means, for the present if you use such viewers, that you may need to manually edit grids.user.xml or grids.xml depending on which viewer you use. Consequently this isn't yet very accessible except to users of older viewers with unless they have considerable technical competence. For now, This means that the old insecure HTTP port 8002 will remain in use as well but this is now under review.

[Edited: 2020-05-03, 2021-09-26]