Hello all,

You may have seen @[email protected]’s latest post regarding his new UI - as I love testing these things out, I’ve spun up this up at next.lemmy.zip.

Its very new and in active development, and you will be able to join in the conversation at the lemmy-ui-next community.

The new UI is described as:

Lemmy-ui-next is a brand new alternative frontend, built from the ground up with modern and popular tooling - a framework known as NextJS. Lemmy-ui-next has (or aims to have) the following high-level features:

  • Open source (AGPL)
  • Drop-in replacement for lemmy-ui - same exact URL structure, so all existing links will continue working
  • Very plain & minimalistic UI, strongly inspired by other link aggregator sites (of course including the original lemmy-ui!)
  • Very basic and “typical” NextJS architecture, to encourage open source contributions
  • Fully functional even when JavaScript is disabled (but works better with JS enabled!)
  • Optimized data transfer between your browser and the server (filtering out only relevant data from the Lemmy API, caching, memoization)
  • Strong focus on privacy and security (all authentication with the Lemmy API is done through secure httpOnly cookies, user IP addresses are not leaked to external image hosts, etc)
  • @[email protected]English
    4•6 months ago

    Wow, you set this up very quickly 😃

    I think it’s offline right now, but when I checked it before, I immediately noticed that https://next.lemmy.zip is significantly slower than https://next.lemm.ee, and it would be interesting to find out the reasons. Can you share a few details about your deployment? I’m interested in:

    • RAM
    • CPU
    • Is it connecting directly to your Lemmy backend, or through a proxy/proxies?
    • What is the latency in ms between next.lemmy.zip and your Lemmy backend?