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>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 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.