Not really a lot new in this release, mostly just some bugfixes and polish.The only new "feature" is that it now indicates to the user if the instance is operating in "private" mode. Other than that, it's just some fine-tuning. Apologies for the delay in getting such a small release pushed out, but life has been hectic (to say the least) for the last few weeks and time hasn't been something I've had a surplus of lately.

Bugfixes

• Don't add comment text to conversation line button tooltip if comment is hidden.
• Check if comment_view.comment.content is undefined before setting the text to it. Only shows up in console log as an error, so it's non-breaking but still annoying
• Remove gap in post heading button bar where the "Moderation" button would be if the user is not a mod
• Fixed "Hide Deleted Posts" filter. It's a holdover from the 0.18.x days and recently, you can only see your own deleted posts. The filter was hitting the safety check to not hide your own content before t

I don't know exactly what cadence you'd call this, but all the point releases that are divisible by 10 are basically "cleanup releases".

I usually try not to introduce anything new in these and rather focus on debugging, refactoring, and streamlining all the changes for the previous 9 releases.

So, don't expect anything groundbreaking from the next version.

That said, I am asking for feedback on things; what can be improved (without adding anything new), what's buggy, etc.

So far in 1.4.40, I've done the following. In addition to these, are there any particular areas that could be improved?

Bugfixes:

• Don't add comment text to conversation line button tooltip if comment is hidden.
• Check if comment_view.comment.content is undefined before setting the comment text value to it. Only shows up in console log as an error, so it's non-breaking, but it's still annoying
• Fixed the gap where the moderation button would be in the post action toolbar if user is not a mod.
• Fix

I guess it also depends on how many days you've configured an account to be considered "new".

Reason being, with lemm.ee shutting down at the end of this month, a lot of accounts are moving to other instances, so you'll probably be inadvertently filtering far more people than you intend.

When things are stable, it's a nice filter option to hide the whack-a-mole trolls who keep popping up, but when a major instance closes shop and/or there's some kind of mass-migration in progress, it can be detrimental.

Highlights in 1.4.39

• Enhanced the content filtering options
• Revamped the comment section display
• Tweaked some mod tool behavior
• Spruced up the modlog
• Quite a few bugfixes

Changelog

:::spoiler Bugfixes

• Fix bug where expanding/collapsing the post image would trigger unwanted reactivity causing the comment section to refresh.
• Comments now respond to the "lockPost" event in order to disable/enable the reply button appropriately.
• If an inbox item is expanded, switching accounts or refreshing the list as a new item arrives would keep the text from the previous comment while updating the heading info correctly. Caused the wrong comment/reply to be displayed.
• Same as above but for moderation reports
• Don't invalidate/refresh Reports page when resolving a report (not needed).
• When removing a post/comment, if you enabled the option to send a reply message and left it blank, it would throw a toast message informing you as such but not reset the "loading" variable

Getting closer!

Differences since Beta 1: The updated filtering capabilities have been merged in. I hadn't originally planned to spruce up the filtering in this release, but it was born out of necessity. That said, I'm quite happy with the refinements that have been made.

As before, I need the extra eyes on this to suss out any last minute bugs. Hopefully no more features creep into this release. This one was an exception as I just...needed it.

If you find any bugs, please let me know: Reply/post here, Github issue, report it in the Matrix rooms, wrap a note around a brick, you know the drill.

::: spoiler Change Notes for Filtering System

Filtering Revamp

The filtering subsystem has been refactored and enhanced. Prior to this release, anything that was filtered was simply discarded before being rendered.

Now, filtered objects will show a placeholder that indicates which filter was triggered (or which keywords triggered the filter). Clicking the "eye" button on

This release isn't quite ready yet mostly because I'm still tweaking small things here and there. Functionally, all of the major changes are stable (plus or minus any undiscovered bugs). The hosted instance (https://tesseract.dubvee.org/) has been updated to this beta to get some more eyes on things. If you hit any bugs, please let me know in whatever manner is easiest for you (reply here, Matrix rooms, Github, note wrapped around a brick, etc)

Highlights

• Comment section has gotten an overhaul
• Spruced up the modlog
• Bugfixes and small UI tweaks

Change Log for 1.4.39

:::spoiler Bugfixes

Reactivity

• Fix bug where expanding/collapsing the post image would trigger unwanted reactivity causing the comment section to refresh.
• Comments now respond to the "lockPost" event in order to disable/enable the reply button appropriately.
• If an inbox item is expanded, switching accounts or refreshing the list as a new item arrives would keep the text from the previous comme

I was asking for tips about working with markdown tables, and this was recommended

https://thisdavej.com/copy-table-in-excel-and-paste-as-a-markdown-table/

It says it does it all in javascript, so is that possibly something you can add to Tesseract? I don't know what technical challenges that would involve -- just seeing if it's possible and/or if it's something you might think about adding.

Lately I have had the need to clear browser cookies. What I noticed is that not only will I be logged out of my account (logical) but the settings I had set in Tesseract are also reset to their default state. Logging into the server where I have my account does not give me my settings back unfortunately.

Is there a way to save all my settings? And if there is no option to do so, can we have that in Tesseract?
Ideally it would be on my own storage location. I host Tesseract on my docker server and if the settings can be saved there automatically then that would be great.

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.

Edit: I backported a small, but annoying, bugfix for long community names and am re-publishing the release. If you go to update, or already have updated, give it about 20 minutes from the time of this edit before pulling the new image.

This release brings bugfixes, a user-requested feature, enhancements to reactivity when performing mod actions, various UI polish, additions to status indicators, and a special little something-something for mods and admins to make their lives MUCH easier.

Bugfixes

• Now that most instances are on 0.19.4 and above which natively support alt text, remove the post title as a fallback alt text.
• Check if the first 150 characters of a post body contains an image since the lazy loading was sometimes preventing the "does the post body scroll" check from returning true. This caused the "expand" button to not appear unless you toggled the post to compact/card and back.
• Un-distinguishing a comment did not reactivly change the background back from

1.4.37

Apologies for the rapid release cycle this week. I'm taking advantage of the rare overlap in free time and motivation and trying to knock out all the low-hanging fruit as far as bugs and annoyances go plus incorporate feedback from the prior releases. The smaller, faster releases also help prevent me from getting too deep into feature creep.

Minor update with bugfixes, UI polish and, at least for now, the removal of a few rarely-used post views (they're rarely used and incompatible with the rewrite to the post body component).

Bugfixes

• Revert throw error in /post/instance/postid loader as it was preventing the prettier error in +page.svelte from showing
• Private message report modal wasn't closing properly.
• Issue 35: Preview length setting counts markup and trims before applying it resulting in short previews and broken links.
• Annoyance: When an <hr> element was used toward the top of the post bod

Summary: Unless anyone speaks up, I'm leaning toward removing those two views.

I'm rewriting the component for the post body preview in the feed to address my own gripes as well as Issue 35 in Github.

TL;DR is that the "Ultra-Compact" and "Reader" views rely on the "Post Body Preview Length" setting and the old method of doing the previews which was just a dumb "show X characters of the post body" based on the un-rendered body markdown.

The new method uses the rendered output and controls the height of the body text for a similar effect. It's also MUCH more responsive and able to take the screen width into account. In short, it's much more flexible, looks much better, and is probably what I should have done the first time.

"Reader" and "Ultra-Compact" rely on a setting that I'm going to be removing. So, rather than re-implement those and complicate what is, finally, a clean/simple refactor, can I just get rid of them?

If

Currently, the post buttons are always a double row. In dev, I've set them to be a single row on desktop and reflow to 2 rows when the screen width goes below the xl breakpoint for smaller viewports and mobile (see main post image).

I like it, and I think it makes better use of the available space + more compact on desktop, but before I change the post buttons again, thought I'd ask for feedback. This is probably not something I'm going to make an option for (there's too many options already lol).

Current Layout: Post action buttons/indicators are always two rows.

Bugfixes

• When zooming an image, it was using the thumbnail image rather than the actual image (when present). Apparently my local instance's thumbnails are close enough to the original quality that I just never noticed.
• Fixed truncation in site card for long instance names and domains.

New Features and Changes

Compatibility Layer: Supports Local /post/{post_id}/{comment_id} Route Format

Note: This only works for your home instance. It does not work for remotely fetched posts. Additionally, this is not a "supported" way to share Tesseract links; it's just there for convenience if you want to turn a local Lemmy UI link into a valid Tesseract link.

If you're in Lemmy UI and want to view a post in Tesseract, you can just change the domain and the post and/or comment params should translate transparently.

e.g. Where 123456 is the post ID and 98765 is the comment id:

Change https://lemmy.world/post/12345/98765 to https://t.lemmy.world/post/12345/98765

This is a bugfix / fine tune release building upon 1.4.34. No new features, just optimizing a few things based on feedback.

Bugfixes / Changes

• Post Titles: Decrease opacity from 90% to 80% when fading read post titles since 90% wasn't really perceptible
• Removed Comments -> Mod View: Got rid of "Removed Comment" spoiler on removed comments for mods and now show the text in-place like it used to be in 0.19.3. Still requires the automatic modlog lookup feature to be enabled and finding an entry for the comment in the modlog. The logic is the same, just the presentation a bit more streamlined to match what admins see (and what mods used to see).
• Markdown Editor: Fixed an errant comma causing the keyboard shortcut for inserting a hyperlink to not wrap the selected text correctly like the toolbar button does.
• Media Integrations -> Spotify: Additional Spotify CDN detection for their thumbnails (when did it become "good" practice to stop using file extensions?!

Bugfixes

• [a84bc5db] Add community-banned indicator to vote view if banned_from_community is present in the API response.
• [1e5bfeae] Disable actions if banned from community (all actions the API forbids if user is community banned):
  • Post/comment vote buttons
  • Edit post/comment
  • Delete/Restore post/comment
  • Report post/comment
  • Moderation buttons (if a mod is banned but not removed from mod team, they'll still see mod action buttons but be unable to perform any)
  • Create post, subscribe, and "community settings" buttons in /c/community and community modal
• [0216bc2a] Don't cache getCommunity lookup results. While nice in theory, it prevents being aware you've been banned or any changes to the community during the cache validity window with no way to automatically invalidate beyond a fixed TTL.
• [d4df7d05] Don't badge-ify post and comment links. That worked well until people would link entire paragraphs. :sigh: So they're regular links now, but they s

I'm testing a feature in my current dev branch and would like some feedback.

When loading a removed comment in the comment section, it automatically fetches the removal reason from the modlog and appends it below 'Removed by Mod" on the comment. The "Removed by Mod" text is also linked to the modlog entry for the item.

Not shown here, but if you're a mod, it will also append, in a spoiler block, the original comment that was removed. Somewhere between 0.19.3 and 0.19.9, the Lemmy devs decided mods should no longer be able to see removed comments in their own communities, which I think is a huge regression (though thankfully admins can still see them).

Thoughts? Is this asking for drama, or would it be generally beneficial? Right now, in the dev branch, it just does it, but I can make it a user option.

This is a mainly bugfix release.

Important: If you are using Tesseract on 0.19.10, this fixes a feature regression that disabled all 0.19.4+ features.

Bugfixes

• Piefed links are identical to Lemmy but not API compatible; fixed bug when loading a Piefed link in a modal. Now has button similar to /post to load the outside pos/comment link in a new tab/window.
• PeerTube seems to have a new video ID format. Added that to the detection regexes so those will embed.
• Fix typo in "Check for Notifications" label
• Fixed / accounted-for Spotify thumbanils (they don't have extensions and weren't being detected as images)
• Home-instance custom emojis exempted from inline media disable setting
• Fixed broken semver comparisons on 0.19.10+ (any features requiring greater than API 0.19.3 were being disabled).
• Removed mobile OS "share" integration as it was more trouble than it was worth. Now all 'share' and 'copy link' buttons just write the item to the clipboard.
• Add slight r

Note: I know it's probably a little early depending on your time zone, but I scheduled this to send at midnight UTC (8pm my time) because I wanted to release version 4.1 on 4/1 as I'm an absolute sucker for gimmicks (which will become very apparent as you read the release notes).

About

I've been working on this in a new repo for months, and I'm extremely excited about this release. In fact, this is such a major release and paradigm shift that I'm jumping 3 major and one minor versions (this was originally slated to be v2.0).

It's still AGPL, and I hope to make the source code public soon, but until I've done some cleanup, the repo is still private and is only released as pre-built Docker images. Unfortunately, only amd64 is supported at the moment since I'm having trouble with Github Actions and can't do arm64 builds locally. Hope to have that resolved by the next release. 🤞

What's New?

Absolutely everything!

I'm tired of being John Henry / "old man who yells at c

Late January, I had to step away from the project for a while to deal with some family stuff. That's resolved, but try as I might, I just cannot force myself to get back into development mode on this.

I've got other projects I want to work on, both hobby and home improvement. I need to focus on the latter, and really want to focus on the former. Like anyone else, my time is finite.

The Hard Truth

Tesseract was written for Lemmy, and I'm tired of porting it to Lemmy over and over again because the Lemmy devs keep breaking the API. Yes, yes, pre-1.0 technically means they can shred the API and break everything from release to release. But when a project is widely used, in perpetual beta, and has lots of other developers developing against it, it's disrespectful to them to constantly introduce so many breaking changes when it can be avoided. And it CAN be avoided; they just don't bother.

So where does that leave the project?

Well, potentially completely broken on