Tesseract

143 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.

Codeberg: https://codeberg.org/tesseract-ui/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

ptz@dubvee.org

admiralpatrick@lemmy.world

1.4.42.alpha.6 Pushed to Hosted Instance (dubvee.org)

submitted 3 weeks ago* (last edited 3 weeks ago) by ptz@dubvee.org to c/tesseract@dubvee.org

3 comments fedilink hide all child comments

Post Image: Depicts the new search scoping using the inline keywords to set the search options without having to use the search form manually.

I'm slowly wrapping up the feature list (very slowly) but alpha 6 is up and live now.

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

Still no ETA on official release as I've got lots more to wrap up and many irons in the fire, but it's stable for what's working.

Alpha 6 Changelog

Since alpha 5, I've made the following changes:

Change Github icon to Codeberg
Add missing field in admin area to set the site's content warning
Make the content warning a one-time acknowledge and show it before rendering any of the main UI
Add a "show source" / toggle markdown button on posts/comments to be able to view the raw markdown without having to go into debug tools.
Add some April Fool's Day fun stuff even though I likely won't have this officially released by then. At least people using the hosted instance will get a laugh.

Search Scoping

Added the ability to scope the search to "Local", "All", or "Subscribed".

Added keywords to set those inline and expand the other search keyword filters.

@all: Searches all (unscoped) and is the default if omitted. I'm not sure why I added this since it's not very useful.
@me: If the query contains @me it will scope the search to only items you've posted/commented
@local: If the query contains @local it will scope the search to only local items (works for users/communities as well as posts/comments)
@subscribed: If the query contains @subscribed it will scope the search to only items to which you are subscribed to the communities (including the communities themselves).

These can also be combined with the existing search term keywords!

Search prefixes to set the search type. You can now prefix the search query to set the search scope from the search box:

user: {query}: Searches only for users with the given query string

users: {query: Alias for user:

community: {query}: Searches only for communities with the given query string

communities: {query]: Alias for community:

post: {query}: Searches only for posts with the given query string

posts: {query}: Alias for post:

comment: {query}: Searches only for comments with the given query string

comments: {query}: Alias for comment:

url: {query}: Searches only for posts which have the provided URL as the post link

Examples:

@me @local comment: Captain Picard will only search for comments you've made to local communities containing the text "Captain Picard"
@local comment: Captain Picard will search for any comment containing "Captain Picard" only on local communities
@local users: Picard will search for any local users that have "Picard" in their username or display name
@subscribed posts: Picard will search only communities to which you are subscribed and return only posts containing "Picard"
posts: picard @subscribed @local @me will search for any posts containing "Picard" and scope it to only posts you've made to local communities to which you are subscribed.
@local communities: Star Trek will search for any local communities that contain "Star Trek" in their names.
communities: Star Trek @subscribed will search for any subscribed communities that contain "Star Trek" in their names.
communities: Star Trek @subscribed @local will search for any local subscribed communities that contain "Star Trek" in their names.
@local url: https://example.com/foo/bar.html will search only local posts with the given URL.

You can set all of these in the search form, but it's very convenient to be able to type them into the search at the top and set them all inline.

top 3 comments

sorted by: hot top controversial new old

[–] IcedRaktajino@startrek.website 0 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

Looks nice! I've been running a copy locally for a while and switch between it and Voyager. Looking forward to whenever you release this since it seems a lot more polished than the version I'm running. You also replied a while back that you were going to add an option to hide hashtags? Is that in this version? And is there any way to run this version locally?

Also

You can now prefix the search query to set the search scope from the search box ... user: {query}

Wouldn't it make more sense to keep those all the same? "@user query" or "@local @user Picard" or "local: user: Picard" or is there a technical reason they're different? Not nitpicking just curious.

[–] ptz@dubvee.org 0 points 3 weeks ago

Thanks!

Is [hiding hashtags] in this version?

Yes.

And is there any way to run this version locally?

Unfortunately no. There are still uncommitted changes in my local repo that are required for a build of this branch. When I put together the beta, those will all be committed and everything merged into the 1.4.42 branch that will be reproducible. That's the main reason this is still in alpha stage.

Wouldn't it make more sense to keep those all the same? "@user query" or "@local @user Picard" or "local: user: Picard"

Yeah, probably lol. I already had the user: {query} etc syntax from much earlier in this version and added the scope modifiers the other day. Those didn't take parameters so it didn't make sense to use the old syntax with them. I was also thinking I had already used the user: etc syntax in the wild, but I haven't so I guess I should probably change them to all match - unless it breaks something which I don't think it should.

[–] reddwarf@feddit.nl 0 points 2 weeks ago

Just wanted to say how I appreciate all your effort on developing Tesseract. I'm still using 1.4.41 and looking forward to using 1.4.42 when it is available!

Curious: are you still using github or did you move to codeberg?