I hope this isn't a question that's already been asked to death, in app search for "mbin" isn't all that helpful.

I'm still in the stages of looking for a permanent home here in the fediverse. So far mbin has really caught my eye because it's basically Lemmy+ for all intents and purposes (at least for mine). I'm not all that happy with what looks like the only Android app though.

So I was wondering if there were any plans to add mbin functionality to any existing Lemmy apps? Even if I used a Lemmy app solely for the 'Threads' or Lemmy section of mbin, then used the web page or only mbin app for everything else, I would be fine with that.

I tried to see if I could sign in with the app that I'm currently using (Eternity), with the kbin.earth instance and no luck. So obviously the API is just that much different.

Are any devs here thinking of expanding their apps in future? Or is there one I've missed? I've seen more than one app with the description "For Lemmy and the Fediverse", but what exactly is meant by "and the Fediverse" is unclear.

I've seen a lot of wishes in various comments and feature requests for Lemmy to support image galleries (e.g. similar to Reddit posts with multiple images you can swipe through).

My first thought was to just detect multiple images in the post body and render those (plus the thumbnail) as a gallery instead of just the thumbnail image. That's absolutely doable, but perhaps there's a better way?

My second thought, which is what I now prefer, was to make a custom markdown container for an image gallery (the same way the spoiler tag is implemented).

e.g.

:::gallery Gallery Title
![Image 1 Alt Text](https://example.com/image1.jpg "Caption for Image 1")
![Image 2 Alt Text](https://example.com/image2.jpg "Caption for Image 2")
![Image 3 Alt Text](https://example.com/image3.jpg "Caption for Image 3")
:::

It would then render that as an image gallery that can be swiped through.

Pros

• Easy to implement in most markdown libraries that support custom containers (markdown-it, marked-js, etc)
• Easy syntax for users
• Allows explicitly creating a gallery instead of relying on implicit behavior (e.g. detecting / rendering multiple post body images as a gallery)

Cons

• The custom markdown container would need to be implemented by clients (preferably more than just one or two)
• It wouldn't work in Lemmy-UI (hey, they should have to adopt one of our features for a change)
• The "title" component of the markdown image syntax would be interpreted by some clients as the code for a custom emoji, so that may need to be omitted if we want this to fail mostly-gracefully in less capable apps (cough Lemmy UI cough).

Thoughts? Other suggestions?

cross-posted from: https://lemmy.world/post/24420184

Hello, it's been a while!

I did most of this release like 6 months ago but never got around to finishing it up until yesterday.

There's a bunch of small theme changes, biggest being a slightly different header bar, and in general a lighter light theme and darker dark theme.

There's now a search field in the sidebar which lets you quickly search through your subscriptions, with a link to a full community search. You can search for a community by name, or for example @lemmy.world to see all from a certain instance.

By default now when using the "Card" layout the vote buttons are on the left now and all the buttons on this layout are a bit larger. If you prefer the vote buttons on the right like it was you can change it back in the settings.

On all the feeds there's now a refresh button on the bottom right so you don't need to refresh the whole tab.

There's a new "Feed Layout" option that makes it so clicking post links will bring you to that post page directly instead of opening it in the overlay or a second column.

That's about it for now! I hope to add some more missing features soon!

ie. that paginates the feed? I realise that Lemmy clients modeled their design after the for-profit apps, but the incentives that lead to infinite scroll are now gone.

Edit: while I'm at it, I wanted to say that I think it'd be a cool feature if apps supported sharing your blocklists.

hello! im developing lemmy client (on html5). i tried to do login function but... when i try to fetch /v3/user backend with auth-token it give me error:

{
  "error": "no_id_given"
}

but why? what im doing wrong? if you want here is my source file on github ( function: getLoggined() )

Cross-posted from "1.4.28 Released" by @[email protected] in [email protected]

---

1.4.28

Note: I only crosspost release info here when there are new features worth mentioning, so I copied over some of the notes from the previous release that I didn't post. Also, the image is just the only clearly visible new feature (formatting help/cheatsheet). I added that just so it would roll-up the two announcement posts into cross-posts.

This release brings a few bugfixes and several quality of life improvements. Also, mods are now able to see the votes on submissions to their communities (if their instance is on 0.19.4 or above).

Bugfixes

• [Bug/Annoyance] When highlighting text in the markdown editor and using the toolbar buttons (e.g. highlight a word and click "bold"), the text area would annoyingly scroll to the bottom. No longer does it do that.
• [Bug] Default moderation template had a missing piece (community) and didn't really make sense.
• [Bug] Don't poll notifications from Notification system timer handler if no active profile. The poll function didn't actually run, but no reason to call it if no profile
• [Bug] Usernames in direct message headers were improperly truncating
• [Regression] The 'Filter Annoying CC Licenses on Comments' option wasn't working since the markdown pre-processor re-write.
• [Bug] Ensure post titles are not linkified. This includes both regular URLs in the title (typically flotsam from Mastodon) and unwanted mailto:[email protected] email links when the titles contain [[email protected]](/c/[email protected]) or @[email protected].
• [Bug] Dynamically import separate CSS themes for HighlightJS depending on app theme. Makes code blocks easier to read since the default styling assumed light theme.
  • Known Quirk: Unfortunately, this is not reactive to changing the app theme without refreshing the page.

Minor Changes

• [Settings] Moved inbox/notification related settings to new section in /settings page.
• [Notifications] Notification poll interval is now configurable
• [Infrastructure] Removed unused settings key for notificaiton rate
• [Infrastructure] Can now specify section URL param on /settings page to open the specific panel (useful for linking to a settings section; yet to be implemented elsewhere)
• [Direct Messages] Updated the message header to be more email-like
• Can now set an option to expand all inbox, reports, and/or registration applications by default.

Vote Viewer Now Available to Mods

If connected to an instance running API 0.19.4 or higher, the vote viewer is now available to mods for items in their communities. I had always planned for it to be, but I wasn't aware that had been implemented in the API already. Apparently it's been available to mods at the API-level since 0.19.4 (thanks @[email protected] for pointing that out).

For those unaware, the vote viewer is accessible from the Moderation Modal -> View Votes... button.

Link Menu / Alternate Source Selector

The link menu / alternate source selector for YouTube-like videos now lists all user-defined Piped/Invidious instances instead of a single, static link to the currently-selected instance.

Added "RemovePaywalls.com" as an option in the archive link selector

Community Profile Modals

Post Drafts Less Likely to be Accidentally Lost

When creating a post in the community profile modal, the "Return to Home" back arrow will now prompt you for confirmation if there is anything in the post form. Helps prevent accidental loss of post draft via mis-click.

Upload Cleanup

When clicking the "return to home" button from the "Create Post" panel, the resetForm function from the post form will be called which will take care of cleaning up any uploaded media that would otherwise be abandoned.

Markdown Editor

Added new buttons to the toolbar

• Insert User Link
• Insert Community Link
• Table
• Code Block
• Formatting Help

The "Insert User/Community Link" buttons will let you search for a user and/or community and insert links to them in the body at the current cursor position. The inserted links are in the @[email protected] / [[email protected]](/c/[email protected]) format. Inline auto-complete is in the works but needs to bake a little longer.

The "Table" button will create a markdown table template.

The Code Block button is a menu which will let you select the lanaguage (or plaintext/other).

The Formatting Help button will load a modal with a markdown cheatsheet.

Toolbar Now Reflows

The markdown editor toolbar (with the formatting, emoji, image, etc) buttons will now reflow on mobile/small width screens rather than scroll horizontally.

Various Tweaks to Markdown Editor

1. Heading button is now a menu; can select headings 1 through 4
2. Fixed bug where highlighting text and using the toolbar buttons would always scroll it to the bottom
3. Numbered and bullet lists now give you three entries
4. On spoiler, code block, and lists, the cursor now goes to inside the block or in position for the first list item (respectively)
5. Highlighting text and clicking the "Link" button will now automatically put the text into the link label. For example, if you highlight the text "Home" and clicked link:

• Old behavior: Home -> [Label](url)Home
• New behavior: Home -> [Home](url)

---

Get Tesseract

Docker

• ghcr.io/asimons04/tesseract:1.4.28
• ghcr.io/asimons04/tesseract:v1.4.28
• ghcr.io/asimons04/tesseract:latest

Links

• Github: https://github.com/asimons04/tesseract
• Hosted Instance https://tesseract.dubvee.org

hello! i creating lemmy client which looks like it's from the old internet!

Cross-posted from "1.4.26 Released [Troll Buster 5000]" by @[email protected] in [email protected]

---

1.4.26

This release brings bugfixes, ability to upload videos, and new moderation capabilities.

Bugfixes

• Add /reports route that redirects to /moderation so the email links from the API work correctly if you're using Tesseract in place of Lemmy-UI as your default frontend.
• Add moderation button to crosspost items
• Long links in the modlog were not wrapping when reflowing to mobile
• Pause markdown videos/audio when leaving viewport instead of destroying (same as how post videos are now handled).

Bugfixes from 1.4.25

Didn't do a post for 1.4.25, but there were only some minor bugfixes in that release.

• When viewing a user's submissions in the profile modal from a /c/community page, the post meta is hiding the community and treating inCommunity as true.
• Removed code to switch between community icon and user avatars in CommentMeta component since that's actually useless since you can't browse just comments in a community.
• Comment card colors were not reactively updating when user was banned with content removal from site/community
• When removing/hiding a community, the local cache of the community details was not updated to reflect that; had to open the app in a new tab to get a new session in order to fetch it again. The cache now updates on block/unblock/hide/unhide.

New Features

Support for Video Uploads

Less a "new feature" and more a bugfix to canonize a feature I didn't realize already existed and mostly worked lol.

The file upload handler sets the supported MIME types, but it has no way to enforce them (it's more a suggestion to the browser). A user reported that they forced a video upload, and it worked, but the process was buggy. This was a surprise since I'd never actually tested or even thought about supporting video uploads.

So I patched up the upload handler to support video/mp4 and video/webm formats. The previewer will only show the first frame as if it were a static image, but it will no longer glitch out. It will also automatically disable and hide the "Pre-convert to webp" options if a video is detected.

I'm not sure how useful this will be since most instances limit upload file sizes or disallow videos, but if you're on a supported instance, hey, you can do videos now.

Edit/Clarification: You've always been able to link to a video. This addition allows you to upload a video to your instance's pict-rs as you would an image.

New Moderation Capabilities (aka Troll Buster 5000)

Added support for community moderators and admins to issue bulk community bans/unbans. For several releases now, Tesseract has had the ability for mods (or admins) to directly ban/unban a user from a community (Community Modal -> Ban/Unban User -> Enter username -> Ban/Unban).

Now, there's an extra option to allow issuing either action in bulk for every community you moderate.

Highly useful if a known troll is roaming about (you probably already know which one I'm talking about) and you want to quickly ban them from all of the communities you moderate (whether they've posted there or not).

I'm all about being proactive, so if a known troll is making rounds, I see no reason for them to have to make a mess first when I can simply prevent the mess (or further messes).

Example: You're scrolling /all and see some vile, racist troll posts from a brand new account. Rather than having to wait on an admin to ban them or waiting for them to hit your communities before you can do anything about it, you can simply click their username and [pre] ban them from everything you moderate. Easy peazy.

Basically, every time "that guy" goes on a trolling spree, Tesseract's mod tools adapt and get more powerful. A less polished version of this feature has been in my "private" build for a while now, but since "that guy" shows no signs of buggering off, I figured it was time to mainline it and give everyone else the same defensive capabilities I've thus far hoarded for myself.

Note: Please do not use this feature as an "I really don't like this person" button. In the wrong hands it's got high potential for abuse, I admit, but the benefits it offers outweigh the risks of a few bad mods going on a power trip.

This is a powerful feature. Please use it responsibly.

If time passes and it seems like I've handed loaded guns to a bunch of toddlers, I'll absolutely yank this feature and move it back to my private build.

Modes of Operation

It works a little differently depending on where it's invoked and whether you're a moderator and/or an admin.

In all cases, the expiration date, reason, and whether to remove content applies to all communities (i.e. the API is called for the same user with the same options and loops through the list of communities you moderate).

User Profile Modal

New option in the user profile modal to ban/unban that user from all of your moderated communities. Available to Mods + Admins

This button is also available in the Moderation Modal as well as the quick actions on the moderation reports.

Ban Instance Modal (Admins) With Option to Ban from all Remote Communities They May Moderate

For admins, there's a new option in the "Ban User..." form to "Ban All Remote Communities". Will issue community bans for all remote communities you may be moderating in addition to the instance ban for your home instance. The "remote" filter is to avoid spamming the modlog in case you're an admin of a large instance (technically you moderate all local communities you're subscribed to).

Community Profile Modal:
The "Ban/Unban" option has been extended to allow optionally banning/unbanning the supplied user from all the communities you moderate. Available to Mods and Admins.

Here, the user is not pre-populated and you can enter the username in any of the following formats:

• Actor ID: https://instance.xyz/u/username
• @ Format: @[email protected]
• Lemmyverse Link: https://lemmyverse.link/u/[email protected]

While "Ban" is the action shown in the screenshots, these work in reverse as well to unban them from all. The only thing that's not automated is restoring content if "remove content" was selected during the initial ban. I'm working on that, but there's no clean way to do it without restoring everything, even things that were removed prior to the ban action. As always (since this is the case for all UIs with mod tools), take care when selecting "Remove content" when issuing bans.

---

Note for admins: Since you technically moderate all communities on your instance, it will only issue bans for communities on your instance that you are subscribed to. The preferred flow for admins is to just instance ban them and select the option to "Ban All Remote Communities" if needed/applicable. Care should also be taken to not select that if they violate a local instance rule but not a remote community/instance rule.

---

Get Tesseract

Docker

• ghcr.io/asimons04/tesseract:1.4.26
• ghcr.io/asimons04/tesseract:v1.4.26
• ghcr.io/asimons04/tesseract:latest

Github: https://github.com/asimons04/tesseract

Hosted Instance https://tesseract.dubvee.org

1.4.23

This is a minor feature release. Nothing new for regular users, but there are some new capabilities and major improvements for admins to make handling registration applications easier and more powerful.

See: https://github.com/asimons04/tesseract/issues/9 for additional context and screenshots.

Bugfixes

None discovered since 1.4.22 :)

New Features

Tweaked Admin Area

Got rid of the sub-navbar menus to select which admin section is active. Now uses a button bar like is used in the user profiles.

New Registration Application Manager

What started off as simply adding a text field to the registration applications so the deny reason could be recorded turned into just flat-out re-writing the whole registration application manager.

It makes me sad that I think this is a cool feature update and very few people will actually see it or know it exists lol.

Changes include:

• More compact/dense as it now uses the inbox / report form factor (expandable accordions)

• Much needed visual / design overhaul

• Can now specify the reason when denying an application

• There's a button which will let you search for alts of the same username. Very useful if you want to see if they're instance hopping and want to check if they're a good fit for your instance. Also useful to see if someone is spinning up lots of alts rapidly (e.g. spammers).

• A colored badge on each entry indicates the application's status:

  • Pending action (Grey)
  • Approved (Green)
  • Denied (Red)

• Option to create a modlog entry when approving/denying the application. Disabled by default, accessible via button and/or toggle.

  • Denying an application creates a "ban user" event using the deny text as the reason. This is useful in case denial emails are still not being sent out and the user wants to check their application status.
  • Approving an application will intelligently unban a user if they're banned (i.e. from a mistaken denial).
  • Approving an application with a modlog entry will be a user un-ban (even if they're not banned, it'll still log it)
  • Approve unban message is Registration application approved.
  • Deny ban message is Registration application denied: ${REASON_YOU_SUPPLIED}

• More information about the applicant:

  • Signup email address
  • Whether the email address has been verified
  • Whether the signup email address is to a known disposable/temporary email provider

Other UI Tweaks

• Crosspost items have less padding and rounded borders now

Get Tesseract

Docker

• ghcr.io/asimons04/tesseract:1.4.23
• ghcr.io/asimons04/tesseract:v1.4.23
• ghcr.io/asimons04/tesseract:latest

Github: https://github.com/asimons04/tesseract

Hosted Instance https://tesseract.dubvee.org

Cross-posted from "1.4.21 Released [Release Notes]" by @[email protected] in [email protected]

---

1.4.21

I'm happy to finally have this to the point I'm comfortable releasing it. I have a time-sensitive need to switch to "infrastructure" mode for a while, so I'm glad to have this release off my plate so I can do the needful on that side of things.

The TL;DR of this release is: Now supports Loops and everything else is either under the hood or a subtle UI tweak.

Overview

This release could probably be considered 1.5.0 rather than a 1.4.x point release, but I'm going to wait until I raise the minimum supported API level before bumping the minor version. Currently, I do have support for 0.19.4+ features, but they're limited to a few minor things here and there (see README.md for specifics). I've also added the capability to automatically enable/disable features that require different API versions, so I'll likely be adding some more 0.19.4+ user-facing features in the coming releases. The newer admin/mod features, if any, will need to wait until my own instance is updated past 0.19.3 since I will be unable to test those (I can test the user-level stuff against a different instnace with one of my alt accounts there).

Most of the work in this release has been re-writing core components, getting rid of some legacy stuff, and stanardizing any redundant sections with shared components. All of this is to make the upcoming task of porting to either Svelte 5 or React easier (haven't decided which yet; I'm annoyed that Svelte has so many breaking changes. We also use React at work which is more stable in the long term).

Bugfixes

• Added missing padding on placeholder initials if there is no site logo

• If replying to a post/comment removal via a comment reply, send the reply before removing the item otherwise the reply will fail. (when I wrote that in the 0.18.x days, you could reply to removed comments and I just never used that feature since the behavior changed in 0.19.x)

• When switching instances or loading the site info for another instance into the site sidebar, the taglines would sometimes get stuck on the previous instance's values.

• Images would fail to render if @[email protected] or [[email protected]](/c/[email protected]) were in the alt text since it would trigger the pre-processor to convert them into user/community links.

• Memory optimization hacks; good lord Svelte is a hoarder and refuses to let go of shit. This is a huge reason why I'm probably going to port Tesseract to React instead of going to Svelte 5. Even if the memory leaks are fixed in Svelte 5, they basically turned it into React anyway, so might as well use that.

• Fix bug where overlap in hashtags (e.g. #Photography and #Photo) would mangle the longer tag.

• Markdown inside of code blocks is no longer pre-processed. This should fix quirks when viewing code snippets and some of the includes get incorrectly turned into hashtags. It also let me simplify some of the regex patterns since they no longer have to account for code blocks with look aheads/behinds.

• Linking to a community on another instance (e.g. if you want to show the community on that instance rather than just linking to the community) no longer turns into a community action badge.

• Bugfixes for bugs introduced during the rewrites have been omitted, but a lot of time was spent tracking those down and squashing them.

Bugfixes for Image Loading and Image Proxy

For efficiency, Tesseract tries to request webp versions of non-animated images at sizes appropriate for their use. e.g. 128px for icons, 256 for thumbnail images, etc. Usually this works, but sometimes remote pict-rs gets all pissy about it. Before, this would cause the image to fail to load until opening it with the Zoom which requested the raw image URL. Now, I've added error handlers for images to fallback automatically/gracefully:

[Desired Resolution and Format] -> [Desired Resolution] -> [Raw URL at default resolution] -> [Static Placeholder Image]

Similarly, if media proxying is enabled, it will use the same fallback path but via the image proxy. Depending on the user-defined fallback behavior, it will either try the raw URL or return a placeholder image.

I've also added apng animated PNG to the list of supported images.

---

Guide: Optimizing Browser Settings for Tesseract

When using "click to play" on media posts (the default setting), the "autoplay" flag is implicitly set on the embed to prevent you from having to click multiple "play" buttons. However, any player besides YouTube (e.g. Invidious, Piped, PeerTube, etc) requires you to click the video again after it switches from thumbnail to embed. This is annoying, and YouTube only seems to get a default pass in Chrome/ium because Google says so.

To remedy this:

• In Firefox, this mostly works with the default settings and no settings changes are needed. However, you can set the site permissions when a media tries to play (can't seem to get to that setting otherwise?) and change autoplay to "Allow audio and video" if needed.
• In Chrome(ium): In the Tesseract tab, go into "Site Settings" and change Sound from "Automatic (Default)" to "Allow". This is very counter-intuitive, but it does address the problem.
• If running as a Chrome(ium) PWA, the app permission settings will be at: [Three Dots Menu] -> App Info -> Settings -> More Settings and Permissions

New Features

Initial Support for Loops Videos

This has been a feature request since Loops first went live, and I finally came up with a satisfactory way to integrate Loops media. The media itself is easy to integrate. The problem is that the metadata returned for a Loops video link does not include the video URL, and there's no way to derive the video URL from the available metadata. In some cases, I can use the thumbnail image and massage that into a working video link, but more often than not, the thumbnail URL was to a pict-rs cached image rather than the value returned from Loops.

Right now, the Loops support is very "beta" but functioning well. There are a few limitations:

• It can break at any time if Loops decides to go user-hostile and block non-browser requests via Cloudflare or something. Tesseract does a server-side lookup to basically scrape the video URL and then caches that for re-use.

• It can also break if Loops decides to crack down on "hotlinking" the videos.

• It only works with the main loops.video domain. For now, this is fine since Loops hasn't released its stack for self-hosting yet. Like Piped/Invidious, I'm basically going to have to have a list of Loops instances to detect. While this is great for decentralization, it's a huge pain in the ass when you want to make a nice client to integrate with them all.

• Loops videos are not "eligible" to always shows as embeds and must use click to play. This was a choice on my end to avoid hammering Loops with requests for videos that may or may not be watched. The lookup to get the video URL is only invoked when you "click to play" from the post thumbnail image.

• I've reached out to the Loops team to see if they would add the oc:video tag to the page metadata so the embed video URL can be obtained properly without such hacks. If they ever do add that, then the integration should work cleanly like with PeerTube and without the clunky requirement to have a list of known Loops instances and then scraping the video URL from those.

Alt Text Now Supported in Post Form

If the connected Lemmy instance is on API 0.19.5 or higher, the post form will now have an "alt text" field if the URL points to an image or video (uploaded or remote URL). If the URL is not an image or direct video, or the API is below 0.19.5, the alt text field will not show up.

When crossposting, the original alt text will be used if present; you can edit it as desired/if needed.

Under the Hood Highlights

• Storage Compression: When data gets stored to sessionStorage, it's compressed first. This has yielded quite a bit of savings and is a workaround for the 5 MB per-key limit on local and session storage in the browser. 5 MB sounds like a lot when it's all text data, but since there's a lot of redundancy in the data returned from the API (e.g. two posts to the same community will each have a full copy of the community details, sidebar info, etc), it fills up fast when you're taking snapshots of the current state (which his how Tesseract keeps your position in the infinite scroll feeds). In the future, I plan to move to IndexedDB which does not have this limitiation and comes with additional benefits. The current plan is to use PouchDB as the wrapper library which opens the door to syncing with a Couch DB add-on to Tesseract's server component and allowing state to be maintained across devices :)

• More Caching: For data that doesn't change often, such as site and community info, the loaders have been updated to first see if there is a cached record for that data. If so, it will be used to fulfill the API call. If not, it's requested from the server as before and cached until needed. Currently, site (local and remote) and communitiy details are cached. I'm looking into other places data can be cached, perhaps with a shorter validity period.

• Initial Support for 0.19.4+ API Functions: Tesseract is still designed for 0.19.3 as its baseline. However, I updated the JS client to the latest one for 0.19.7 since it's backwards compatible. While I don't have all the newer features built-in yet, I do have some that become available when the API level supports it.

Preview Community and User Feeds in Modals

You can now view a user's or a community's feeds in their respective modals when clicking a user or community link.

The preview has also been added to the moderation modal. However, in the moderation modal, it limits the feed to just the user and community relevant to the item that initiated the mod modal. e.g. if you click the mod button for a post/comment in the FoodPorn community by user Bob, the only submissions that will be shown are Bob's submissions to FoodPorn. This should help with performing mod actions as you can check for patterns of rule-violating behavior without having to leave the mod tool.

Another use case is previewing new communities when you click on a pill-button link. e.g. if someone comments about a cool community and uses the [[email protected]](/c/[email protected]) format (as they should), you can click on it which will resolve it automatically. From there, you can click "Browse Community..." to see what kinds of posts it has before commiting to subscribing (okay, that's a very tiny commitment, lol, but you get my point).

New Feed Capabilities

The feeds were re-written as components to be more modular and consistent. Mostly, if I did my job right, you won't think I did anything at all. That said, they do have a few new tricks:

• Feed filter options for "Show Only [Liked | Disliked | Saved] Posts".
• Feed filter options for "Show Hidden", "Show NSFW", and "Show Read Posts". Requires 0.19.4+ for show hidden and 0.19.6+ for "Show NSFW" and "Show Read"
  • Those options will be hidden if the instance is below the required API version.
• Can hide/unhide posts; accessible from the post action menu (three dots, top-right). Requires 0.19.4+.
• Better state preservation. The snapshot subsystem has been overhauled, and the data is now compressed before being stored into session storage
• Refreshing the browser will now clear the snapshot for the current feed and re-fetch from the API. i.e. refreshing the app/page will pull the data from the API as expected instead of reloading a stale cache / requiring to manually press the app's refresh button.
• Manual pagination is now bi-directional. You can page back without having to use the browser's 'back' button.
• Switching between communities will remember your position and sort options in each (until the snapshot expires. Currently 15 minutes)

UI Tweaks

• Clicking a community link to bring up the modal will now allow you to browse the community from within the modal (nice for previewing communities)
• Clicking the @[email protected] in the user profile modals will copy the username to the clipboard
• New vote buttons
• Redesigned comment count button on posts in feed; now shows unread count
• Redesigned crosspost container
• Moved thumbnail image to the left on link previews
• Moved 'debug' button into post/comment action menus (removed dedicated button)
• Instance names in the site cards are now clickable. Eventually they will open an instance modal with nice options (similar to user and community modals), but for now, it just goes to /site/{instance} to view the instance details in a nice page (rather than a cramped sidebar).
• Clicking "Home" in the sidebar will take you back to your previous scroll position.

Moved More Menus Out of the Sub-Navbar

I still like the UI element, but too many of the options got moved into dropdown menus in the sub-navbar. Based on feedback, that seems to have sacrificed function for form. In this release, I've moved many of the selectors closer to the elements they manage.

• Community Browser instance selector, sort, and type menus have been moved above the community list.

• The sort and type selector menus in user profiles have been moved into the feed component itself.

• In the Inbox, the subnavbar elements have been removed completely, and there is a sidebar to the left of the inbox (similar to an email inbox)

• In the Moderation/Reports area, the subnavbar selector has been removed; like the Inbox, there's now a sidebar with the relevant filtering options.

• The main feed still has them in the subnav bar, though, since there's plenty of room on the left-hand side.

---

Removed Features :(

Only Specific Forms of User and Community Links are Turned into Action Badges

There's so many wild and inconsistent ways people reference communities and users. I originally tried to cover them all, but there were too many edge cases, overlaps, and times it's not desirable to do so that it became impractical.

Now, only three forms of user/community links will be turned into action badges; the rest will remain unmodified links or plain text.

Valid Community Link Examples:

• https://instance.xyz/c/community
• [[email protected]](/c/[email protected])
• [Text](https://instance.xyz/c/community)

Valid User Link Examples:

• https://instance.xyz/u/user
• @[email protected]
• [Text](https://instance.xyz/u/user)

No Longer Valid / Won't Be Badge-ified:

• /c/community
• /c/[email protected]
• /u/user
• /u/[email protected]
• https://instance.xyz/c/[email protected]

The https://instance.xyz/c/[email protected] format was removed because sometimes it is useful to link to a community on another instance to see differences due to federation, moderation, etc. In those cases, changing it to a local link is not desirable. The rest were removed because they were proving problematic to support with all the different ways people make user/community links.

As of this release, only the formats in the valid lists above will be matched and turned into action badges (load the modal for info about the community/user). Other formats, or ones that are already linked, won't be touched.

Note that the ! and @ formats do not need to be manually linked in most Lemmy clients.

Browsing Favorites / Groups as a Feed

This capability was always experimental. The initial implementation wasn't great, but it worked well enough, and I had a plan to improve it. Unfortunately, before I could put that into motion, the Lemmy devs, in their infinite "knows better than everyone else / if Lemmy UI doesn't use it, no one should" wisdom, removed the post ranking metrics from the API. This meant I could no longer do any kind of sorting beyond score and date.

So, since then (0.19.0 or thereabouts), the custom feeds feature has remained in place, crippled, and begging for death. In 1.4.21, I finally decided to put it out of its misery.

Community groups and favorites are still available, but they're only used for organizing communities now. Favorites give you quick access to your most-visted communities, and groups are still useful to keep tabs on your subscribed communities.

I do have a plan to resurrect the feature, but it's going to require backend support. I have a partial Tesseract API server, but I've not worked on it in a good while. Even still, if I do dust that off and go that route, custom feeds will only work for the "default" instance Tesseract is deployed to and only if the admin runs the API service for it. Not sure how practical that will be, but since it's something I would want to offer on my own instance, I may still work toward it, though at a low priority.

Option to Disable Automatic Timestamp Updates

I changed the way the timestamps on posts/comments, etc update. Prior to this release, each had its own setInterval in the component and operated independently. In this release, I introduced a system timer that dispatches events at an interval. The date components now simply listen for this event and recalculate. With this change, the option to disable them doesn't really provide any benefit.

---

Changes and Enhancements

Community Explorer

• Moved listing type, sort options, and keyword search out of sub-navbar and into the "feed" area.
• State is now maintained in the URL, so paging back and forward will keep the state correctly (it didn't maintain any state previously)
• Calls to local and remote getSite are cached in session storage to reduce bandwidth (used to populate the site sidebar)
• Tweaked the 'subscribe' buttons
• Added a dedicated button to go directly to the /c/{community} page for each entry
• Clicking the community name will open the community modal for additional options
• The selected instance is now route-based rather than URL param or internal state variable. e.g. /communities/{instance}
• Your home instance now has a "home" icon indicator in the instance dropdown

User Profile Pages (including local profile)

• Uses the new, component-based feed rather than the bespoke one used previously.
• User banner, stats, "about" info, and moderates list is now above the feed rather than in the sidebar (except local profile; that's still to the side except on mobile)
• "Moderates" list is no longer a separate accordion. That list has been moved into the "About Me" section (similar to user profile modals)
• Sidebar is now populated with the home instance details for the user (banner, icon, name, stats, admins, site description, legal, etc). Non-local profiles only.
• Sidebar site info is now cached in the browser's session storage to reduce network traffic and load on remote servers
• Better state preservation when navigating in/out. Right now, the snapshot validity is 5 minutes for user profiles versus 15 minutes for the main feed and communities.
• Integrated search. No longer just a shortcut to the /search page with the user pre-set.
• The sort options and type (posts/comment/all) menus have been moved from the sub-navbar to above the feed.
• Lots of under the hood changes, none should be visible except what's listed :)

New Inbox

• Looks/behaves much more like an email inbox
• Inbox items are collapsed into accordions. Open to view the message.
• Configurable default inbox: can be "all " or "unread". Setting is in Settings->General->Default Inbox
• Collapsible side menu to switch between message types, all, and unread. Also has convenience pagination buttons. The "mark all as read" button has also been moved here.
• Removed the dropdown menus from the sub-navbar; those are now in the collapsible side menu
• The envelope icon to the left of the message container is the "mark as read/unread" button.

New Moderation/Reports Manager

• Removed the custom buttons from the sub-navbar. Filters are now in its sidebar.
• Now uses the same layout as the inbox
• Has a sidebar for switching between unread/all and filtering by community. Also includes pagination.
• The check button to the left of the collapsible report is the resolve/unresolve button. Green check = resolved, white check is unresolved.
• Unread reports are bolded
• Can filter reports by community
• Removed the moderation action form since it's a brute to maintain and has received mixed reviews from users.
• Each item has a few quick action buttons for mod tasks. Use the "All Mod Actions..." button to bring up the moderation modal to access all options.
• Looks less awful on mobile :)

Known Quirks

• Changing any of the infinite scroll options (or switching between infinite and manual pagination) requires any existing feed snapshots to be cleared. If you switch options from the quick settings menu, it will automatically refresh the browser as a workaround hack. If you switch them from the main settings page, you'll need to manually refresh the feed or the browser to clear them. Again, I have a way to deal with this, but I'm not certain it's the most graceful (though it's more graceful than force-refreshing the browser lol).

Twitch Videos (Not Possible)

I also had a feature request to support Twitch embeds. It seemed possible (they provide the video embed player URL in the link metadata), but I can't make them embeddable because Twitch cockblocks embedding except from the "big" social media sites. So, no Twitch video embeds for Lemmy, but not for lack of trying.

Refused to frame 'https://player.twitch.tv/' because an ancestor violates the following Content Security Policy directive: 

"frame-ancestors https://reddit.com https://www.reddit.com https://old.reddit.com https://new.reddit.com https://www.redditmedia.com https://twitter.com https://cards-frame.twitter.com https://tweetdeck.twitter.com https://discordapp.com https://discord.com https://embedly.com https://cdn.embedly.com https://facebook.com https://www.facebook.com https://vk.com https://x.com".

---

Get Tesseract

Docker Tags:

• ghcr.io/asimons04/tesseract:1.4.21
• ghcr.io/asimons04/tesseract:v1.4.21
• ghcr.io/asimons04/tesseract:latest

Github: https://github.com/asimons04/tesseract

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

cross-posted from: https://sh.itjust.works/post/29038131

I'm a decent developer, but with only a couple years' professional experience and no formal training. I'm looking for open source projects to contribute to (ideally pick one or two and get dedicated to them).

I'm open to small or large projects.

I'm using this as my source of options:

https://fediverse.party/en/miscellaneous/

But I'm curious if there are other ones, or if you all have ideas about which ones are needing and deserving help.

Thanks!

Voyager F-droid/Github/Standalone releases on lemmyapps.com say last updated 9 months ago, but that's not right

Looking for an alternative to Sync, because I'm tired of not getting updates from LJD despite it being a paid app. Unfortunately, thus far I've tried about half a dozen apps and none of them quite give me as much customisation options as Sync did, especially on the feed view. Few of them even come close. Does anybody have a recommendation for a highly-customisable app?

Cross posted from: https://lemmy.world/post/22382916

What the title says. I tried different lemmy apps and home only shows the last community I subscribed to. I can't find a way to fix this via the settings and searching online did not turn up anything useful. Where should I report this?

cross-posted from: https://lemmy.world/post/22173524

This is a relatively small update to address a few issues with v0.4.2.3.

The biggest issue this update addresses is scrolling behavior and performance. The previous release had a bug that would cause poor scrolling performance in post feeds, and issues sizing cells to fit their content. This update addresses this, and offers a significant improvement to scrolling in Arctic.

This update also adds support for native instance blocking, finally. Instance blocking was added to Lemmy in v0.19, after Arctic already had instance blocking built up in. This version will now use the native blocking feature for instances running v0.19+, and fallback to internal blocking on older instances. This update will also automatically migrate your instance blocks from Arctic, to Lemmy.

You can now use search in Arctic’s settings. I know Arctic has a lot of settings, and it can be difficult to find exactly what you're looking for, you can now search for most options. This is still a work in progress, and not all options are searchable yet. I’ll be improving on this in future updates.

Arctic for macOS open TestFlight

---

Arctic is now officially in beta for macOS. I know some users with silicon macs have been using the iPad version of Arctic for a while now, but macOS is now supported on intel macs as well. This version offers a lot of Mac specific fixes and improvements over using the iPad version on Mac. Note that this is the first Mac beta, and there will be bugs. There is still a ton of changes coming for Mac, primarily with the UI to improve support for the use of a mouse or trackpad, and make better use of the larger screen space.

v0.4.2.4 Changelog

New Features

---

• Added action menu to user and community buttons on post and comment cells/
• Added options to toggle haptic feedback for various actions/
• Added support for instance blocking using native Lemmy API, this will fall back to internal blocking on instances running versions older than v0.19.x.
• Added support for searching Arctic's settings /
• Added support for opening links to options in Arctic's settings e.g., arctic://settings.root/Settings/Appearance#App%20Theme Will open Arctic to the theme settings.
• Added options button to theme cells in the theme browser/
• Added color descriptions in the theme editor.
• Added option to configure the swipe action angle threshold/

Changes

---

• Updated support for stripping Markdown in push notifications.
• Updated toast messages appearance and improved dismiss gestures.
• Updated link preview generation to prioritize links in the order they will be displayed
• Updated scrolling behavior to reduce stutters and jumps while scrolling.
• Updated behavior when blocking, or subscribing. These actions should now be represented immediately in action menus.
• Updated large post default settings to display community button on the top of post cells.
• Updated default swipe action threshold to reduce false triggers while scrolling.
• Updated markdown and HTML parsing for link preview descriptions.

Bug Fixes

---

• Fixed an issue allowing Spoilers to be shown in push notifications.
• Fixed an issue allowing Spoilers to be shown in post feeds.
• Fixed a layout issue allowing voting buttons to be compressed on post cells.
• Fixed an issue where link previews in comments would display an extra line of compressed text.
• Fixed an issue preventing paged gallery views from responding to taps when contained in a crosspost view.
• Fixed an issue where cells would not resize when a link preview was loaded.
• Fixed an issue preventing post cells from sizing properly when new content is loaded.
• Fixed an issue that could allow system swipe actions to display, even if custom swipe actions are enabled.

Links

• Website: getarctic.app
• TestFlight: testflight.apple.com
• App Store: apps.apple.com
• Issues: github.com
• Community: [email protected]

It's still in early development stage, but I think it's coming together rather nicely and it's pretty snappy. Thoughts?

As the title says, i want to be able to set it up so that when i open the app i ONLY see the stuff from the instance at the start and not from any federated one until i tab away or something, to use with a tiny private instance. Does this exist?

Bonus points if it's a FOSS one on FDroid.

Hi all, I’m excited to introduce redgazer.com to the community - a new, streamlined way to browse photos in Lemmy communities.

Key Features

• Gallery View: Browse photos in a clean, Pinterest-style masonry layout
• Quick Preview: View full-resolution images and discussions without leaving your feed
• Multi-Instance Support: Connect to any Lemmy instance seamlessly
• Minimalist Design: No distractions – just the content you want to see

I’ve been working on this for a few months and would love to hear your feedback!

Edit: a few examples:

• [email protected]
• [email protected]
• [email protected]

Cross-posted from "v1.4.20 Released" by @[email protected] in [email protected]

---

This is a fairly large release packed with lots of UI refinements, removal of a lot of legacy cruft (though sadly not all yet), new features, better moderation workflow, and lots of bugfixes. This is probably the most overhaul the basics of the UI have seen in one release since the first versions.

Probably my favorite new feature is the configurable "hybrid" view. In hybrid view, all posts default to compact mode, and you can configure which post types should display as cards by default. e.g. Image posts (memes, pictures, etc) will default to cards with everything else remaining compact. You can also, optionally, keep posts that are marked read in compact view.

Additionally, all posts (except text-only posts; there's no difference) can be toggled individually between compact and card now. Previously, this was only possible when the view was set to 'compact'.

Get Tesseract

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

Docker Tags:

• ghcr.io/asimons04/tesseract:1.4.20
• ghcr.io/asimons04/tesseract:v1.4.20
• ghcr.io/asimons04/tesseract:latest

The hosted instance defaults to Lemmy World but is unlocked to connect to any Lemmy instance.

Bugfixes

Bugfixes: Minor

• May only have been an issue for admins, but administratively hidden and removed communities will now no longer show up in community autocomplete results.
  • They will still (intentionally) show up when filtering for a community in the modlog though (though only admins should be able to see those results)
• Fixed full URLs not truncating properly when "Show Full URLs" option is enabled
• Fixed issue with click-to-play not working on post pages if media is disabled on post pages.
• Disable "reply" button if post is removed or deleted
• Disable 'report' post action if post alredy removed (I think deleted posts can still be reported, though. Need to double-check the API behavior.)
• Disable 'report' comment action if comment already removed.
• Fixed Gifs not previewing if just 'url' is present (i.e. no thumbanil_url or embed_video_url)
• Indicate post's removed/deleted/lock state in the comment item component when viewing profiles
• When "Match Crossposts on Title" is enabled, posts with the same title but different URLs will no longer be erroneously rolled up
• "Distinguish" now only shows on your own comments if you are a moderator. This matches the stupid API behavior because...the Lemmy devs don't listen to anyone. (Wow I really can't go one release without throwing shade at them, can I?)
• Modlog now shows hide/unhide and remove/restore community events.

Bugfixes: Major

Image Cache Housekeeping

Fixed image cache housekeeping not working correctly.

There were changes to fs/promises that I missed, and some functionality changed along with a few of the member variables being deprecated. This was causing the directory content calculations to silently fail safe (returned 0 rather than crashing).

As a result, nothing was ever getting evicted from the cache.

If you are using the cache functionality of the image proxy, you will likely notice that startup takes a bit longer this time if you have housekeeping set to run at startup (recommended). This is because it will be housekeeping all of the cached objects it should have been housekeeping all along. Once the initial cleanup of the backlog has completed, further startups should complete in the normal/expected amount of time.

If startup takes too long, you can always delete all of the .cache objects manually from the mounted cache folder. See the Media Proxy docs for configuration options.

New Features / Changes

"Hybrid" Post View

Rather than a binary choice of "card" or "compact", hybrid view will let you set a list of post types (image, video, article, etc) that you want to render as cards while displaying everything else as compact. This is the new default view.

This is useful, for example, to let memes and news articles co-exist without having to expand every meme image manually in compact view or view every article thumbnail card-sized.

The behavior and post types can be configured from Quick Settings -> Post Style -> Hybrid and then clicking the link for "Configure" -or- from Settings -> Feed- > Hybrid View Configuration

By default, only image posts are expanded to cards.

In addition to setting the types of posts that should render as cards, you can optionlly keep read posts collapsed into compact view when they would otherwise be cards if they were unread. This is enabled by default, but can be easily disabled.

There is also a new regular view called "Compacter". It is the same as compact but post body is fully collapsed. Similar to "More Compact" but not full width.

Post Form Now Automatically Searches for Crossposts/Duplicates

When you are creating a post, the URL will be searched to see if you're posting something that's already been posted. It should do this automatically when the URL field changes or the URL is set and the community changes. The behavior is slightly different depending on if a community is defined:

1. If the community is not set, then it will search for any posts on your instance matching that URL. The label will be "Crossposts".

2. If the community is set, then it will do a remote API call to search the home instance of that community for any posts to that community with that URL. The label will be "Existing posts".

The latter behavior is particularly useful if you want to avoid accidentally posting a duplicate that may have been posted by someone you've blocked or by someone your instance doesn't federate with. Those posts may not be visible to you locally, so the remote search should help identify them so you don't clutter up the feed and/or add extra work for the moderator who usually removes duplicate posts.

If for whatever reason it doesn't trigger automatically, the "Magnifying Glass" icon to the right of the URL field can trigger the search manually.

Also note that behavior #2 only works if you're posting to a Lemmy community since it makes a remote API call to the community's home instance using the Lemmy API. Thus, it cannot search a remote Kbin/Piefed, etc instance.

Can Now Vote on Crossposts Without Clicking Into Them

Vote buttons have been added to the crosspost items, so you can now vote on them from the feed and post.

In the feed, since the cross_posts are rolled up manually from regular post objects, the voting works as expected.

Unfortunately, when clicked into a post, the API call does not add the my_vote variable to the cross_posts array. So while you can vote on the crosspost, and the vote will be correctly recorded, your vote will only display correctly while you're on that page. Since the API doesn't return the vote you cast, on refresh or subsequent loads, the vote button will not indicate which way you voted. If you try to vote again, the score will not necessarily change. Yet another feature I want to implement hampered by dumb API decisions.

DailyMotion Video Embeds Now Supported

I forgot Dailymotion existed until someone posted a link a while back. Upon inspection, they have an embed API, so I figured why not add support for it.

Moderation Menu Has Been Replaced With New Moderation Modal

The moderation menu on posts and comments has been removed. The reason is that the menus were getting cluttered when new things are added, especially for admins who have more options available than regular mods. Rather than creating sub-menus (yuck!) or introducing separate UI elements for admin controls, I've just scrapped the whole thing and started over.

The "mod" button will now open a modal containing all the mod tools that are appropriate for the item.

The cool thing about the new mod modal is that all of the tools are packaged into it. It doesn't open separate modals for banning/unbanning, removing/restoring, etc. It even has the community details available so that mods can reference the rules when issuing actions without leaving the item they're working with.

Current Capabilities and Features

• A mini-banner heading showing the current community with its icon and the creator of the item and their avatar/info.
  • Both communtiy and user are clickable to bring up their respective profile modals to get more info (these pop up in separate modals and aren't integrated into the mod modal)
• Pin/Unpin the post to the community
• Feature/Unfeature the post on the instance (admins only)
• Lock/Unlock the post
• View the community details relevant to the current item (post or comment)
• View the votes for the item (admins only until whatever version of Lemmy lets mods do this for their communities)
• Remove/Restore the post or comment (shows the post meta header or the comment meta header and comment previews)
• Send a DM to the post/comment's creator
• Purge the post or comment (admin only)
• Ban/Unban the user from the community
• Ban/Unban the user from the instance (admins only)
• Distinguish/undistinguish mod comments
• View the user's modlog history
  • Defaults to their history in the community relevant to the current item
  • Can toggle between their modlog history in the community and their full modlog history
  • Also has link to the full modlog viewer filtered for that user.

All tools stay within the same modal, and it shrinks/expands to accommodate the various integrated tools.

Improved Community Modals

To reduce clutter, the "Subscribe/Unsubscribe" (RSS Icon), "Favorite/Unfavorite" (Star), "Add/Remove to Group" (3 People) buttons have been moved to the modal title bar as icon-only buttons.

"Create Post" is no longer a link to the community's create post page. It now shows the create post form right in the modal. There is a button in the upper-right which will take you to the /c/{community}/create_post page if you want to use the old form ( 🖼️ 👩🏻‍🦰 🖼️ it's the same form).

For admins, "Remove/Restore Community" and "Hide/Unhide Community" have been integrated. They will also now prompt for an optional reason to show in the modlog.

The "Community Details" is now a panel (like in the moderation modal) rather than being an accordion. Same functionality, different packaging.

You can now view the community's modlog directly in the modal.

Added the direct ban/unban user tool to the community modal. Instance admins and community moderators can now manually ban/unban users from the community without having to dig up a submission. Useful to revisit an old ban or to ban a known troll making the rounds before they hit your community.

Improved User Modals

The "Copy Lemmyverse Link" and "Copy Actor ID" buttons have been moved to the modal's title bar as icon-only buttons.

• The "Share" icon is for Copy Lemmyverse Link. This is used to share an instance-agnostic link to a user.
• The "Link" icon is for Copy Actor ID.
• The box with arrow in top right icon will take you to the user's profile.

Can view user's modlog history directly in the modal

Can send a message to the user directly from the modal

For admins, the "ban/unban user" form is now integrated directly into the modal.

Piped/Invidious Support Changes

Since YouTube has gone to war against alternate frontends (and is sadly winning), most public instances no longer work. However, I believe that private/small instances may still function as expected.

Since the public instances are pretty much all broken or only partially working, Invidious/Piped support has been modified to only be enabled if the user supplies their own instance.

The distinction between Invidious and Piped has also been removed since the link formats are interchangeable. Now, in Settings, the YT frontend has been changed to just "YouTube" and "Custom". The custom instance list can contain Invidious and/or Piped instances.

The alternate link selector for YouTube videos will now also only show "Invidious/Piped" option if you have defined at least one.

As before, multiple custom instances can be defined but one will need to be selected as the default. That one will be used for the alternate source selector and, optionally/separately, as the embed player.

Note: You can keep YouTube as the default embed player while also adding a custom Invidious/Piped instance to act as alternate links in the alternate source link menu.

The internal lists of public Invidious and Piped instances has been combined and are only used for detection; formerly, these could be selected as frontends.

On the admin side of things, the env var PUBLIC_CUSTOM_PIPED has been deprecated. For now, it will simply be combined with the PUBLIC_CUSTOM_INVIDIOUS list. Eventually the Piped list will be removed, but that is TBD. Those lists are also only used for detection and are no longer presented as possible frontends for the user to select.

If a user wants to use Invidious/Piped, they must supply their own instance in their settings.

Long, Non-Comprehensive List of Various UI Tweaks

• Lots of UI polish all around. Too numerous to list individually.

• Legacy user and community menus in /u/{user} and /c/{community} cards have been removed. The functionality has been moved into the respecctive user/community modals.

• Community link pill buttons are now gray instead of orange. The orange was just...too much. User link buttons are still blue.

• Better display of metadata from posted links

• Cleaner compact view (also incorporates metadata display better)

• Feed images are limited to a maximum of 40% viewport height. This still gives the nice "card" effect while also not making posts massive. They were formerly limited to 80vh, but even this is no longer needed since the ZoomableImage component was integrated.

• Removed user settings for post and feed image sizes since they're no longer needed with the new compact and card view tweaks described above.

• Post body images are now hidden in the feed and a link shown in their place. Clicking the link will open them in a preview modal. Unless the option to disable inline images is turned on, then they will still show as embeds when opening the post. This should help compact mode stay compact rather than some of them being massive with one or more post body images slipping through.

• Direct video (mp4, webm, etc) posts now use the video metadata for the thumbnail if OP didn't post a custom one. Also works in compact view now.

• Bandcamp embeds are now smaller.

• All media renderers now show the embed metadata alongside the post details.

• Direct audio links (MP3, etc) now have renderers; they only rendered in the markdown post body and comments previously. Now if the post URL is an audio link, a player will embed.

• Show link selector, link, and MBFC even if metadata fails to load in preview modal. Also show that info while fetching metadata.

Better Error Handling and Integration with Pifed/Mbin/etc

When clicking a link that goes to a post or comment, Tesseract will massage the URL to attempt to render it locally (extract the instance and post ID and do a remote API call to fetch it for local rendering). This works great for Lemmy, but non-Lemmy services which use the same /post/{id} and /comment/{id} URL format don't work with Lemmy API calls.

Before, this would throw a generic 500 "Failed to fetch post" error. The UX has been improved in this release by showing a clearer error message as well as a button to visit the post on its home instance.

Additionally, if a local post fails to load, there's now conditional verbiage to indicate a local post may have been removed by its creator or removed by a moderator, and there is no button to visit it on the home instance (since it is the home instance).

Cross-posted from "[release] 1.13.0-beta03 available for testing" by @akesi_[email protected] in [email protected]

---

Hi folks, a new beta has been release today! It contains some updates to the "App information" dialog (e.g. the link to the new Matrix room) and a fix for the selection of the feed type in the home screen, which incorrectly opened the instance selection.

I'm continuing the migration of all bottom sheets to Material 3 modal bottom sheets, there are just 9 left for the refactoring to be complete.

Thanks to everyone for continuing using the app, have a nice weekend and remember #livefasteattrash 🦝🦝🦝

I need to pump up my contribution numbers to match Flyingsquid’s to further dispel that Reddit urban myth that “Lemmy is not active that’s why I’m not currently using the platform”

It seems like Voyager and Thunder have quite a few features the others don’t have such as advanced search, gif support and user labels.