libredirect / browser_extension

A browser extension that redirects popular sites to alternative privacy friendly frontends

https://libredirect.github.io

GNU General Public License v3.0

3.22k stars 119 forks source link

Issues to import here #17

Closed ghost closed 1 year ago

ghost commented 2 years ago

I think these are some fundamental issues that need to be imported from the Main repo and Make it available on Libredirect.

Here are the Issues : 344, 340, 320, 313 (Imgur to Imgin) [Private alternative to Imgur] must be looked in, 290, 271, 260, 251, 236, 210, 287, 101, 43, 35, 201, 194, 156, 139, 114

https://github.com/SimonBrazell/privacy-redirect/issues/___ (View the Issues by replacing ___ with the numbers for eay access) Sorry, I cannot link for that because I'm on the move.

These are the Issues I think that needs to be implemented in Libredirect. These are in No Particular Order.

ManeraKai commented 2 years ago

https://github.com/SimonBrazell/privacy-redirect/issues?q=344++340++320++313+290+271+260+251+236+210+287+101+43+35+201+194+156+139+114

ManeraKai commented 2 years ago

Till now: https://github.com/SimonBrazell/privacy-redirect/issues?q=313+271+260+236+210+43+35+201+194+139+114+

ghost commented 2 years ago

@ManeraKai Any new issues to be closed here ?

ManeraKai commented 2 years ago

They're really unique and weird ideas. I try to look them every time. I didn't found one to close.

ghost commented 2 years ago

I understand. May @alefvanoon could help out. But he's dead in Online here.

ManeraKai commented 2 years ago

https://github.com/SimonBrazell/privacy-redirect/issues?q=313+236+210+43+35+201+194+139+114

ManeraKai commented 2 years ago

https://github.com/SimonBrazell/privacy-redirect/issues?q=313+236+210+43+35+201+139+114

ManeraKai commented 2 years ago

https://github.com/SimonBrazell/privacy-redirect/issues?q=313+236+210+43+35+201+139

Mennaruuk commented 2 years ago

ThirtyFive/AMP issue is interesting.

Apps like DeAMPify work "by first being set as the default URL handler for AMP-specific URLs. Once you open a link with the application, DeAMPify scrapes the AMP’s HTML for the page’s original URL." Not a great approach to scrape the HTML of all pages.

Chrome extension Redirect AMP to HTML initially worked by setting an opt-out Cloudflare cookie that forced sites to serve the non-AMP links, but that was deprecated after Cloudflare announced a new way where AMP can be served while showing the original URL. Not only is this outdated, but Cloudflare raises a red flag for some privacy advocates.

There is an extension called Aelisya that has a bunch of rules blocking AMP Project links.

But it's AmputatorBot that has the most potential. It claims to have a 97% success rate at blocking AMP links. The rules block links containing /amp, amp/, .amp, amp., ?amp, amp?, =amp, amp=, &amp, amp&, %amp, amp%, _amp, amp_.

ManeraKai commented 2 years ago

@Mennaruuk Isn't this really out of scope do you think?

I agree with him: https://github.com/SimonBrazell/privacy-redirect/issues/35#issuecomment-628915244

Mennaruuk commented 2 years ago

When I looked into the post you linked, there were people who said that redirections away from AMP fall under privacy redirection. In my opinion, I definitely agree with you, it's superfluous. I'm wondering how a desktop user stumbles upon an AMP link, that's like a needle in the haystack, virtually all of AMP conversions are on mobile, and there are extensions dedicated to serving the desktop user an AMP link. If anyone wants to de-AMPify links, they can install an extension like Redirect AMP to HTML or Aelisya for MS Edge. I keep thinking about the purpose of the project: a web extension that redirects popular sites to alternative privacy-friendly frontends and backends. To me, de-AMPifying doesn't fall under this.

ManeraKai commented 2 years ago

https://github.com/SimonBrazell/privacy-redirect/issues?q=313+236+210+43+201+139

IkelAtomig commented 2 years ago

https://github.com/SimonBrazell/privacy-redirect/issues?q=236+210+43+201+139

ManeraKai commented 2 years ago

https://github.com/SimonBrazell/privacy-redirect/issues?q=236+210+201+139

IkelAtomig commented 2 years ago

https://github.com/SimonBrazell/privacy-redirect/issues?q=236+201+139+

IkelAtomig commented 2 years ago

@ManeraKai Any ETA on this Issue - https://github.com/SimonBrazell/privacy-redirect/issues/210 ?

Because, I am stuck in consent.youtube.com when copying and pasting link from an app and I hate doing so. Issue present only in Chromium not in Firefox.

Will Update after the New Update arrives on MS Edge store.

IkelAtomig commented 2 years ago

Any updates on this ?

ManeraKai commented 2 years ago

No.

IkelAtomig commented 2 years ago

I think this is fixed - https://github.com/SimonBrazell/privacy-redirect/issues/201 - Right ?

ManeraKai commented 2 years ago

No? I didn't touch it. I didn't even understand the problem too much.

IkelAtomig commented 2 years ago

I sort of understand it will test and report it here or matrix.

ManeraKai commented 2 years ago