github-starred/feeddeck
2
0
Fork 0
mirror of https://github.com/feeddeck/feeddeck.git synced 2026-03-10 07:32:05 -05:00
Code Issues 5 Packages Projects Releases 8 Wiki Activity

[PR #143] [MERGED] [lemmy] Add Support for Piped Videos #143

New Issue
Closed
opened 2025-10-31 16:58:11 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-10-31 16:58:11 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/feeddeck/feeddeck/pull/143
Author: @ricoberger
Created: 2/14/2024
Status: ✅ Merged
Merged: 2/14/2024
Merged by: @ricoberger

Base: main ← Head: lemmy-add-support-for-piped-videos

📝 Commits (1)

  • 3b802f4 [lemmy] Add Support for Piped Videos

📊 Changes

2 files changed (+15 additions, -1 deletions)

View changed files

📝 app/lib/widgets/item/details/item_details_lemmy.dart (+9 -0)
📝 supabase/functions/_shared/feed/lemmy.ts (+6 -1)

📄 Description

If a Lemmy post contains a Piped video it can now by played directly in the app, similar to how it is handled for Nitter posts.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/feeddeck/feeddeck/pull/143 **Author:** [@ricoberger](https://github.com/ricoberger) **Created:** 2/14/2024 **Status:** ✅ Merged **Merged:** 2/14/2024 **Merged by:** [@ricoberger](https://github.com/ricoberger) **Base:** `main` ← **Head:** `lemmy-add-support-for-piped-videos` --- ### 📝 Commits (1) - [`3b802f4`](https://github.com/feeddeck/feeddeck/commit/3b802f4d16768887b752ce9c2ba0caf7ef16ab86) [lemmy] Add Support for Piped Videos ### 📊 Changes **2 files changed** (+15 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `app/lib/widgets/item/details/item_details_lemmy.dart` (+9 -0) 📝 `supabase/functions/_shared/feed/lemmy.ts` (+6 -1) </details> ### 📄 Description If a Lemmy post contains a Piped video it can now by played directly in the app, similar to how it is handled for Nitter posts. <!-- Keep PR title verbose enough and add prefix telling about what source it touches e.g "[rss] Add feature xyz" or if the the PR is not realated to a source use "[core]", e.g. "[core] Fix xyz". If you add a breaking change within your PR you should add ":warning:" to the title, e.g. ":warning: [core] My breaking change" --> <!-- Description of what have been changed. Please also reference an issue, when available. --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-10-31 16:58:11 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/feeddeck#143
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?