due to twitter's forced redirect from twitter.com to x.com, the extension no longer works

[Loch32]

as described above. twitter.com is now force redirected to x.com and attempting to access twitter.com once it has changed for you will show the "browser not supported" page. this braks the extension as it is now unable to read data from x.com as it is looking for twitter.com

Desktop.2024.05.15.-.12.51.39.03.trim.mp4

[rougetimelord]

On my end going to x.com still redirects to twitter.com, so maybe this is a rolling change on their end? Pretty easy fix to add x.com to the permissions.

This isn't super neccessary, but could you open the network tab of your browser's devtools, filter for JSON, and tell me the URL for the first request? (Like https://twitter.com/i/api/1.1/jot/client_event.json) I'm curious if they've also started moving their APIs to x.com

[superusercode]

i'm not the reporter but my network tab in firefox gave me https://x.com/i/api/1.1/jot/client_event.json

[Baramanga]

Yeah uh it's all x.com now. The and the Blue Blocker is now no longer picking up accounts.

[cooljeanius]

Yeah uh it's all x.com now. The and the Blue Blocker is now no longer picking up accounts.

Yeah I got hit by this last night too

[bb115]

yeah mine stopped working as well hopefully you all working on a patch great extension btw

[Kannamoris]

Can confirm that this is indeed the case.

[cooljeanius]

This ought to be fixed once #267 is merged and 0.4.2 is released

[namkwal]

confirming this as well... ive been trying to add x.com to permission but brave's ui is insanely wacky

[WineKitty]

How do i make it work again i have 0 coding knowledge but hate browsing twitter without this add on

[rougetimelord]

How do i make it work again i have 0 coding knowledge but hate browsing twitter without this add on

If you have git and node installed, you can checkout the 0.4.2 branch, and then follow the development instructions in the readme.

[rougetimelord]

Popping in again to say that the 0.4.2 branch does work, we're currently testing it to make sure we don't have a bunch of bugs in the public version. If you want to help test it, please comment any issues you run into on the pull request (#267)

[alcayaga]

As a workaround you can access the old domain using the variable mx in the url:

https://twitter.com/home?mx=1

[Baramanga]

Popping in again to say that the 0.4.2 branch does work, we're currently testing it to make sure we don't have a bunch of bugs in the public version. If you want to help test it, please comment any issues you run into on the pull request (#267)

Hey uh, maybe I'm just being obtuse but how do I install the extension on Firefox before it's officially "released" on the store front? The version I have rn is the same as on the store front, which is 0.3.5. Is there like a folder, with the zip file I can download the extension with the firefox signature?

[kheina]

Popping in again to say that the 0.4.2 branch does work, we're currently testing it to make sure we don't have a bunch of bugs in the public version. If you want to help test it, please comment any issues you run into on the pull request (#267)

Hey uh, maybe I'm just being obtuse but how do I install the extension on Firefox before it's officially "released" on the store front? The version I have rn is the same as on the store front, which is 0.3.5. Is there like a folder, with the zip file I can download the extension with the firefox signature?

I just added binaries to the release https://github.com/kheina-com/Blue-Blocker/releases/tag/v0.4.2

[kheina]

though, for now, I would recommend @alcayaga's solution

As a workaround you can access the old domain using the variable mx in the url:

https://twitter.com/home?mx=1

the next version should be available soon, it's just waiting on firefox to approve and it will go out automatically