Protecting our residents from potential sources of harm is a prime directive of the ZetaWorlds administration. In most cases this takes the form of targeted removals from our systems, with some extreme cases requiring more drastic measures. We always try to keep disruptions to a minimum and be as targeted as we can with access restrictions. Unfortunately as we have received an increasing number of reports over the past few weeks we had to resort to broader restrictions against offenders. This took the form of updating our automated systems to be more aggressive towards offending sources and resorting to temporary or permanent restrictions earlier.

We continue to monitor the situation and are evaluation both additional measures and ways to be more selective, but you may have already encountered some of the more drastic measures we have put into place. The major one of which was increasing the hitrate of our automated system to flag malicious traffic to our infrastructure and restrict access from those sources. This is something we will continually tweak to adjust to the situation we face, but it is likely to at least stay more in line with what it is currently set to. Meaning plainly that there is an increased likelihood of entire grids being restricted access to ZetaWorlds if their traffic is out of the ordinary or particularly malicious in nature.

Additionally we have elected to look into the abuse originating from various of the dynamic dns services some grids use now. With the most egregious offenders abusing such systems to hide themselves behind ever new IP addresses making it near impossible to create permanent restrictions. The solution to outright remove access from grids that use such services is not in our interest so we have elected to only remove access of specific providers of such services that lack a proper setup and workflow for reporting and dealing with abuse. This is a step we did not want to take, but seeing as the reports have increased at an alarming rate and these services not policing their systems even after repeated information has been fielded by us, there really is not much more we can do. Our aim is, and has always been, for the metaverse to be open and promote diversity, but much like not being tolerant of intolerance, we cannot maintain being open to grids with the intend to be a detriment to us and our residents....

It has come to our attention that some users have elected to use disposable email accounts of straight up entered a non-existent email as their account email. Not only is this against our rules, it also complicates any matters regarding the account. Resetting passwords, receiving offline-IM or any other email will not work. Additionally when the email associated with an account does not exist we are unable to verify the validity of ownership claims made for that account.

As of now when registering for an account with ZetaWorlds an email will sent with a link to verify the newly created accounts email address. Until this verification is completed the account will remain unable to join ZetaWorlds.

Changing an email address associated with an account will now also require verification from that new email as well to ensure account safety.

Remember, a valid email address on your account is required and using a non-existing email will result in the account being locked....

UPDATE:
We have received word that and I quote: "We’re dockerizing it so we can get it back up and more easily move the service or restore it if we have problems with a provider in the future. We’ll get it back up as soon as we can."

Naturally still not a very acceptable answer to the ongoing issues, but we will continue to monitor and put pressure on to get the service restored.


The Gloebits currency service, which is handled by a third party, has experienced an outage and is down.
It is a complicated situation but as far as we know, nobody has lost any money, and the service will be restored eventually.
We apologise for the inconvenience and we'll pass on any news we get from them. ...

A new update for the selfhost preconf binary is available. Fixes this time are minimal, we have reverted a bad commits from core OpenSim that was causing some issues with regions. There was also an issue with estates that should be resolved now. If you find any bugs feel free to let staff know. As usual with each new release the oldest release will be deprecated and no longer allow connection to the grid. ...