Tesseract

81 readers

2 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]

Lemmy 1.0 (dubvee.org)

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

4 comments fedilink hide all child comments

So, when I do get back into my regular development cycle, I'm going to be working on 1.0 support. Yay 🙄

Breaking Changes: https://join-lemmy.org/news/2025-02-03_-_Breaking_Changes_in_Lemmy_1.0

Just going to get my gripes out of the way first: The Lemmy devs have no fucking clue how to version an API. They added an API v4 with some legitimately welcome changes. That's great. But the whole reason you version your API is to not break previous API versions. Random shit is breaking in v3 on 1.0.0-alpha because they changed the v3 behavior instead of implementing all the breaking changes in the new API v4.

I tested Tess 1.4.31 against voyager (that's as far as I ever want to touch .ml ugh), and there's a lot of stuff that needs to be fixed. Maintaining limited compatibility with older API versions (specifically the remote community browser) is also going to be a thing because of the moronic breaking changes that shouldn't be breaking if the devs had any goddamned sense.

Have I mentioned how much I hate the Lemmy devs?

The Answer is 'a lot'

The answer is "a lot"

I'm not sure how far out 1.0 is, but don't expect Tess to be ready on launch day. That said, 1.0 support is going to be developed in a new version (1.5 series) that bumps the minimum API to 1.0 because, again, the Lemmy devs have no fucking clue how to do versioned APIs and only concern themselves with Lemmy UI and everyone else be damned.

I'm so tired, y'all.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 2 days ago* (last edited 2 days ago)

Running Testlog

Tests are performed against voyager [dot] lemmy [dot] ml and are limited to regular user and community mod actions only. Testing is also limited to the functionality exposed by that instance's config (e.g. no signup app, captcha, email verify, etc).

Works

Basic signup (no application, captcha, or email verification)
Logging in
Creating a community
Subscribing / unsubscribing to a community
Infinite scroll in main post feed
Browsing a community (e.g. /c/test)
Creating a post with text only
Commenting on a post
Viewing votes on a post/comment as a moderator
Upvoting a post/comment

Doesn't Work

Detecting whether to enable downvotes; defaults to downvotes disabled. Seems to be related to the more granular voting restrictions, and Tess looks at the old downvotes disabled key in the site response.
Browsing communities (The moron devs changed the sort types and broke compatibility)
Editing a community's settings
Viewing user profiles (moron devs broke v3 API)
Modlog? Can't tell b/c voyager is running on a potato and the request times out.

Can't Test Currently

Any admin functionality
Image uploads (avatars, community icons/banners, etc)
Downvoting a post/comment (Tess limitation due to change in getSite response and missing "downvotes enabled" key.

Untested

Signup with Captcha enabled
Signup with application
Signup with email verification
Email verification
Login with TOTP
Image uploads
Anything else not explicitly listed as broken/working