Tesseract

126 readers

3 users here now

Tesseract: An Advanced Lemmy Client

The goal of Tesseract is to address as many things in Lemmy that annoy me as I can. I also trawl various "is there any way to [blank] in Lemmy?" posts to get feature ideas. Both of those lists are pretty extensive, so Tesseract has accumulated quite a few features.

Github: https://github.com/asimons04/Tesseract/

Hosted / Demo Instance: https://tesseract.dubvee.org/

Note that the hosted instance defaults to Lemmy World, but it is unlocked to be able to connect to any Lemmy server.

Announcements, support, and guidance for the Tesseract UI.

All instance rules apply here. Beyond that, just be civil and constructive.

founded 2 years ago

MODERATORS

[email protected]

Hosted Instance Currently Unavailable (nyc.status.ramnode.com)

submitted 2 months ago* (last edited 2 months ago) by [email protected] to c/[email protected]

2 comments fedilink hide all child comments

The VPS hosting provider is having issues in their NY datacenter, and the VM for the hosted Tesseract instance is currently unavailable (as well as another VM I have in the same DC).

Currently do not have an ETA.

top 2 comments

sorted by: hot top controversial new old

[–] [email protected] 1 points 2 months ago (1 children)

Goddamn 16 hours downtime. The fuck happened to them? >_<

[–] [email protected] 2 points 2 months ago

DC migration gone wrong, apparently. I think my VMs were fine until they got to a later portion of the recovery and basically everything went down.

We are currently experiencing a disruption in our NYC/EWR cloud region due to a failure in the storage backend following our ongoing datacenter migration (NYC to EWR). A portion of our CEPH storage cluster was physically relocated ahead of schedule, while another portion remains at the old location. One critical node is also currently offline, resulting in a degraded cluster state.

As a result, the CephFS (used to access base images and volumes) is in a hung state and blocking all instance operations. This means that starting, stopping, or rebooting instances is currently not possible, although running instances remain online.

Additionally, instances with attached volumes are also unable to boot.