2023.12.09 won't work on X

[nord1]

Twitter aka X no longer lets Basilisk 2023.12.09 in. Wants to move to newer platforms.

[RedRamGT]

If you go into about:config, and modify the user agent for twitter.com to a blank or two, it should work.

[nord1]

If you go into about:config, and modify the user agent for twitter.com to a blank or two, it should work.

Not sure I get what you are saying here. This is what I see in about config which, btw, refers still to twitter.

general.useragent.override.twitter.com

Mozilla/5.0 (%OS_SLICE% rv:6.5) Goanna/20170101 Basilisk/52.9.2023.12.09

[athenian200]

I was kind of freaking out for a moment thinking Basilisk was only working on Wayland randomly somehow... I'm glad it was just Twitter and not X11.

[RedRamGT]

Go into about:config, and find "general.useragent.override.twitter.com". Click Modify, and replace the useragent string with one blank, and Twitter should work.

[nord1]

Go into about:config, and find "general.useragent.override.twitter.com". Click Modify, and replace the useragent string with one blank, and Twitter should work.

RedRamGT

Fantastic... first time you said this, I didn't get it. I was trying to put something (anything) there... finally dawned on me that the key was to put absolutely nothing (blank, as you say) in there and VOILA. I can read twitter posts again.

Much appreciated.

Nick

[axelonpale]

Hey, that useragent tricked worked for me,
Thanks!


Axel

[Basilisk-Dev]

This will be fixed in the next release

[RedRamGT]

For those who were running Basilisk 2023.12.09 and modified the useragent for Twitter so it would work, and have since updated to Basilisk 2024.02.03, it is a good idea to reset the modified useragent for Twitter back to the default.

To do this, go into about:config and scroll down to the useragent entry for Twitter. It can be found at:
general.useragent.override.twitter.com.
Right-Click on the useragent name, and select "Reset". That is all there is to it...

Note: If you do not find the useragent entry for Twitter, it has either already been reset or was not modified.

Twitter does not (at this point in time) need its own useragent - however, if it does in the future it could save a lot of confusion (and frustration) to use the default useragent.

[MoonAgent]

It would be nice to be able to avoid the big, resource-intensive social networks altogether, but unfortunately there's too much there to miss.

I'll have to look for a user agent switcher extension if we have one.

[nord1]

For those who were running Basilisk 2023.12.09 and modified the useragent for Twitter so it would work, and have since updated to Basilisk 2024.02.03, it is a good idea to reset the modified useragent for Twitter back to the default.

To do this, go into about:config and scroll down to the useragent entry for Twitter. It can be found at:
general.useragent.override.twitter.com.
Right-Click on the useragent name, and select "Reset". That is all there is to it...

Note: If you do not find the useragent entry for Twitter, it has either already been reset or was not modified.

Twitter does not (at this point in time) need its own useragent - however, if it does in the future it could save a lot of confusion (and frustration) to use the default useragent.

Thanks, much appreciated. a permanent fix! nice.