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

[PR #163] [MERGED] [nitter] Disable Adding of new Sources #163

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

📋 Pull Request Information

Original PR: https://github.com/feeddeck/feeddeck/pull/163
Author: @ricoberger
Created: 4/6/2024
Status: ✅ Merged
Merged: 4/6/2024
Merged by: @ricoberger

Base: main ← Head: nitter-disable-adding-new-sources

📝 Commits (1)

  • 1722582 [nitter] Disable Adding of new Sources

📊 Changes

3 files changed (+24 additions, -32 deletions)

View changed files

📝 app/lib/widgets/source/add/add_source.dart (+11 -6)
📝 landing/app/page.tsx (+0 -19)
📝 supabase/functions/_cmd/scheduler/scheduler.ts (+13 -7)

📄 Description

This commit disables the adding of new Nitter sources, because Nitter is deprecated 😞 and adding new sources is not working anymore. Nitter sources are also not updated anymore, because the update for Nitter sources isn't working as well. To ensure that the Nitter sources are not updated anymore the sources with type nitter are skipped in the scheduler.

The Nitter source isn't removed completly, because we would also have to cleanup the database and their might be items, which are bookmarked by users.

See https://github.com/zedeus/nitter/issues/1155#issuecomment-1913361757

🔄 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/163 **Author:** [@ricoberger](https://github.com/ricoberger) **Created:** 4/6/2024 **Status:** ✅ Merged **Merged:** 4/6/2024 **Merged by:** [@ricoberger](https://github.com/ricoberger) **Base:** `main` ← **Head:** `nitter-disable-adding-new-sources` --- ### 📝 Commits (1) - [`1722582`](https://github.com/feeddeck/feeddeck/commit/172258227ea090a278efda8274fa29e141119266) [nitter] Disable Adding of new Sources ### 📊 Changes **3 files changed** (+24 additions, -32 deletions) <details> <summary>View changed files</summary> 📝 `app/lib/widgets/source/add/add_source.dart` (+11 -6) 📝 `landing/app/page.tsx` (+0 -19) 📝 `supabase/functions/_cmd/scheduler/scheduler.ts` (+13 -7) </details> ### 📄 Description This commit disables the adding of new Nitter sources, because Nitter is deprecated 😞 and adding new sources is not working anymore. Nitter sources are also not updated anymore, because the update for Nitter sources isn't working as well. To ensure that the Nitter sources are not updated anymore the sources with type `nitter` are skipped in the scheduler. The Nitter source isn't removed completly, because we would also have to cleanup the database and their might be items, which are bookmarked by users. See https://github.com/zedeus/nitter/issues/1155#issuecomment-1913361757 <!-- 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:36 -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#163
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?