Tixel Known Issues & Limitations

Tixel does not display the earliest pixel changes from its initial release.

In earlier versions, Tixel used a forward-logging system, where each pixel update stored the new color applied at that moment in time.

Following a later redesign, Tixel adopted a backward-logging system, where each change records the previous color of a pixel and reconstructs history by applying changes in reverse against the current canvas state.

This architectural change significantly improved storage efficiency and reconstruction flexibility, but introduced incompatibility with the original logging format.

As a result:

• Legacy logs cannot be directly interpreted by the current systems.
• Migrating legacy logs would require complex transformation logic.

Due to these constraints, the current logging system starts from a new baseline, and earlier pixel history is not included.

Tixel is hosted on a free, limited platform, which imposes constraints on connection duration and resource usage.

To ensure stability and avoid excessive resource consumption, Tixel terminates inactive and idle connections.

This measure is necessary to maintain service availability while operating within platform constraints.

However, users may still experience occasional unexpected disconnects.

These may be caused by:

• Platform-level limitations or throttling
• Network instability
• Backend restarts

Sometimes clients may display outdated canvas states.

This issue is typically caused by delayed updates or missed events.

In most cases, this can be resolved by performing a refresh.

Tixel relies heavily on modern web technologies.

Some older browsers may not fully support certain CSS or JavaScript features, which may result in visual or functional inconsistencies.

For the best experience, a modern and up-to-date browser is recommended.