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

[PR #19] [MERGED] [nitter] Allow Usage of Custom Nitter Instances #26

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

📋 Pull Request Information

Original PR: https://github.com/feeddeck/feeddeck/pull/19
Author: @ricoberger
Created: 10/3/2023
Status: ✅ Merged
Merged: 10/3/2023
Merged by: @ricoberger

Base: main ← Head: nitter-allow-usage-of-other-nitter-instances

📝 Commits (1)

  • 1032005 [nitter] Allow Usage of Custom Nitter Instances

📊 Changes

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

View changed files

📝 app/lib/widgets/source/add/add_source_nitter.dart (+3 -0)
📝 supabase/functions/_shared/feed/nitter.ts (+57 -15)

📄 Description

It is now possible to use a custom Nitter instances. This means a user must not rely on our Nitter instance and can instead use his own instance. To use a custom Nitter instance a user must provide the full RSS feed url for the instance.

🔄 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/19 **Author:** [@ricoberger](https://github.com/ricoberger) **Created:** 10/3/2023 **Status:** ✅ Merged **Merged:** 10/3/2023 **Merged by:** [@ricoberger](https://github.com/ricoberger) **Base:** `main` ← **Head:** `nitter-allow-usage-of-other-nitter-instances` --- ### 📝 Commits (1) - [`1032005`](https://github.com/feeddeck/feeddeck/commit/1032005ed4e5c6f1fe3a08b8268be4ae51b957bf) [nitter] Allow Usage of Custom Nitter Instances ### 📊 Changes **2 files changed** (+60 additions, -15 deletions) <details> <summary>View changed files</summary> 📝 `app/lib/widgets/source/add/add_source_nitter.dart` (+3 -0) 📝 `supabase/functions/_shared/feed/nitter.ts` (+57 -15) </details> ### 📄 Description It is now possible to use a custom Nitter instances. This means a user must not rely on our Nitter instance and can instead use his own instance. To use a custom Nitter instance a user must provide the full RSS feed url for the instance. <!-- 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:55:53 -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#26
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?