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: !arctic@lemmy.world

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:

• pics@lemmy.world
• wallpapers@lemmy.world
• mobilewallpaper@lemmy.world

Cross-posted from "v1.4.20 Released" by @ptz@dubvee.org in !tesseract@dubvee.org

---

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_seli@lemmy.world in !raccoonforlemmyapp@lemmy.world

---

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.

cross-posted from: https://lemmy.world/post/21303389 > This has been something I've been wanting to do for a while. The app has been pretty stable recently so I can take a moment to work on a simple website for it. The purpose of the website is to have an official "front page" for the app.

Bugfixes

Flairs in Post Titles

It was pointed out that words in brackets meant to act as clarifying text were being converted to flairs and making some post titles hard to read. This is because the [tag syntax] is the same as is used for clarifying text, so there was some overlap causing that behavior.

Now only bracketed text at the beginning and end of the title will be converted into a flair. This should allow flairs using the [tag syntax] to co-exist with all but a few edge cases of clarifying text.

Example:

[Flair] [Flair 2] The title [of the book] goes here [Published 2022] -> The title [of the book] goes here with the flair tags being Flair, Flair 2, and Published 2022. The clarifying text in the middle remains unrendered.

The other bug I discovered in this area was that if the whole title was inside brackets, it would be converted into a big flair tag. Now, if there is no title text left after extracting the flairs, the title will be used as-is.

Example:

[Jaws theme intensifies] would have been converted to a flair before. Now it will render as text (as likely intended by the creator).

Misc Bugfixes

• [26d26798] Add error handling in case bad URL sent to isImage, isAudio, isVideo helper functions.
• [6b99e0cd] Fixes issue where post was not being marked as read correctly on newer API versions since it was sending a single post ID instead of an array.

---

New Features in 1.4.16

Can Automatically Mark Posts as Read While Scrolling

Per user request, a new option and feature has been added that will automatically mark posts as read as you scroll past them in the feed. This is disabled by default, but can be enabled in Settings -> Feed -> Mark Posts Read on Scroll

Currently, a post will mark as read when 60% of it is in the viewport for more than 1.5 seconds.

Better Crosspost Attributions

Crossposts are great from a user standpoint as they reduce clutter, but they often bury other communities since it's not easily apparent where it was cross-posted from and by whom. The link also typically takes you away from your home instance (depending on UI, anyway).

Now, when crossposting, the default cross-post header has been updated to give better visibility to the original:

Cross posted from "ORIGINAL_TITLE" by @ORIGINAL_USER@instance.xyz in @ORIGINAL_COMMUNITY@instance.xyz

The title is linked to the canonical AP URL of the original post (same as before but with text applied instead of a bare link). The original user and original community links are in the standard user/community link format. In Tesseract, both of those are clickable to view the user and community profiles.

Since Tesseract will automatically resolve unknown communities if you're logged in, this should give a visibility boost to communities that may go overlooked.

Note that since the crosspost header info is just prefixed into the new post body, this will have no effect on old crossposts. It will also not change anything for crossposts made via other UIs nor will it affect the crosspost behavior in general since those are all based on the post's URL.

!

Sidebar Community List

General

The sidebar with the subscription list has been completely overhauled. I'm now using standard CommunityLink components which have the benefit of opening the community modals. The community buttons are still buttons and will take you to the community page. Clicking the community text will open the modal while clicking the button around that will take you to the community page.

The inline menu buttons have been removed since all of those functions are also available from the community modals. This saves a good chunk of memory since a discrete menu is not required for each element now.

The instances for each community are now also shown by default. You can disable this by turning off Settings -> General -> Show Instance Names in Sidebar.

Community List Filtering

I've also re-implemented the filtering of the subscription list. It is now more granular and can accept modifiers as well as take the instance into account.

Default

By default, the filter query will be a case-insensitive contains comparison against the community's display name (or system name if display name is undefined).

It will now also accept an instance if you include it after an @. The instance is compared with a case-insensitive startsWith against the actor id of the community.

• Example 1: new will return any community containing new in its display name (or name if display name is not set)
• Example 2: new@lemmy. will return News@lemmy.word, LegalNews@lemmy.zip, etc.

Filter by Name (rather than display name)

If you want to filter the list by the community's system name rather than the display name, prefix the filter with an !.

The instance is also accepted here if it is provided after an @.

• Example 1: !new will return any community whose system name begins with new such as news@dubvee.org, news@lemmy.world, newcommunities@instance.xyx, etc
• Example 2: Using the same example from above, !new@lemmy. will return news@lemmy.world but not LegalNews@lemmy.zip
• Example 3: Can be used if you want an exact match based on the community link syntax (!community@instance.xyz)

Filter by Instance

To filter by instance, prefix the filter with an @. This will only show communities belonging to the specified instance. This filter method uses a startsWith, case-insensitive comparison against the hostname of the community's actor id.

This is particularly helpful if you want to see what communities you're subscribed to on a particular instance. AFAIK, there is no way to get that info from the API.

UI Tweaks

Independent Preview Button in Post Create/Edit Form

Rather than previewing the entire post, including thumbnail and embed metadata, you can now also preview just the markdown of the post body.

The old behavior was more of an intentional choice that didn't work out well in practice / real-world use. You can still preview the entire post (that hasn't gone away); you just have more granularity in what you preview.

Added "Fact Check" Section to Alternate Source Link Menu

There are one or two "Fact Check" options available in the alternate source link menu now.

• MBFC, if avaialble
• SpinScore.io (shows on all links)

I'm not a fan of AI-generated summaries and analysises anything, so I probably won't be using that, but it's an option if you want to use it.

Direct Video Embeds Now Support Custom Thumbnails

If a custom thumbnail is provided for a post where the URL is to a video, the thumbnail will now be used for the click-to-play overlay.

Other Stuff

• [7c8c96fb] Update MBFC dataset
• [c6ce2213] Update MBFC removal template
• [c908b886] Add option to disable automatically refreshing dates in the RelativeDate component (post/comment published/edit times, etc)
• [135ed9cd] Changed animation on menus to slide instead of scale

---

Get Tesseract

• Github
• Docker:
  • ghcr.io/asimons04/tesseract:1.4.16
  • ghcr.io/asimons04/tesseract:v1.4.16
  • ghcr.io/asimons04/tesseract:latest

Update: The dependency issue was my fault. I left out a dev dependency and had apparently been relying on implicit inclusion that worked up until Svelte 5 was released and vite-plugin-svelte updated for that. Updated the package.json and republished. The Docker tags should work fine for x86 (I did them on my dev machine), but the arm64 builds should be finished from the Github actions in the next 10-15 minutes. If you typically build from the repo, you should be good since I published the fix to the dependencies.

cross-posted from: https://eventfrontier.com/post/150886

> I'm pleased to announce the release of Echo for Lemmy! Echo is a Lemmy client for iPhone that I've been working on for a while and I'm excited to finally share it with you all. > > Echo for Lemmy is a fully native iOS application built using fully native Apple SDKs. This means it feels right at home on your iPhone and is designed to be fast, efficient, and easy to use. No overhead from web views or cross-platform frameworks. > > Here are some of the features available in Echo for Lemmy: > > - Connect with communities based on your interests. > - Sort your feed by most active, trending posts, new posts, and many more. > - Upvote and downvote posts & comments. > - Powerful search experience to find the content you're looking for. > - Create posts using share extension from any app on your device. > - Bookmark posts to easily find later. > - Fully native application with dark mode support & accessibility features. > > Echo for Lemmy is available for free on the App Store, with subscription plans available for Echo+. You can download it here: Echo for Lemmy on the App Store. > > You can also join the official Echo Lemmy community at !echo@eventfrontier.com. > > I'm excited to hear feedback, suggestions, bug reports, and feature suggestions. Feel free to comment here, or create a new post! You can also reach out via email at support@rrainn.com. > > This is only the beginning. Much more to come! > > --- > > Download Echo for Lemmy: https://echo.rrainn.com/download/iphone > > Echo Lemmy Community: !echo@eventfrontier.com > > Echo Mastodon Profile: @echo@mstdn-social.com > > --- > > !Screenshot of Echo for Lemmy on an iPhone showing a list of posts in your home feed.

I've been on a bit of a development hiatus the last couple of months, but I'm starting to work on the project again. One thing I've been wanting to address is the broken support for Invidious/Piped.

With Youtube seemingly hellbent on making sure those no longer work, should I remove support for them in Tesseract or give those projects a while longer to find a workaround? I don't closely follow development of either of those, but last I checked, it seemed pretty much dead because of YouTube's shenanigans.

The code could be a lot cleaner if I removed that support, but if there's a chance of either of them coming back, I'd be willing to leave it in.

Questions for the Community

1. Is it just public Invidious/Piped instances that are broken?
2. Do private instances still work?
3. Do you think either project will come up with a medium to long term workaround?

I'm thinking if private instances still work, I may just remove the public list and only enable the option if the user specifies a custom instance in the app settings. For historic posts, I'll just have it rewrite any Invidious/Piped links to canonical YouTube links or the user-defined custom Inv/Piped instance if defined. If not, then I may just remove that support entirely and only rewrite old links to go through YouTube directly so they still work.

Thoughts?

does anyone know any ios apps that allow us to group communities into custom feeds like multireddits? thx

Even if you don't use Photon and have only heard of it, your answers can be useful for some questions!

cross-posted from: https://lemdro.id/post/13579151 >I'd like to learn about the community that uses Photon, so I've decided to make a survey! You can answer it if you like. In about a week I'll collect the responses and see if anything's interesting, and then I'll make a post showing any discoveries. > > The survey just has a few questions about demographics, Lemmy usage, and knowledge of Photon's features.