Submitted by masque in Tech

It used to be that if you tried to view a tweet with javascript disabled, you would be given the option to use legacy twitter. Now I just get a message saying that javascript is required. Ugh.

4

Comments

You must log in or register to comment.

cammie wrote (edited )

nitter.net is still alive and kicking.

You can replace the twitter.com in a twitter URL with nitter.net to get a lightweight, JS-free twitter web client.

Edit: In a similar vein, there are many instances of the invidious lightweight youtube webclient available even though the one run by the dev (invidio.us) is no longer up. see invidio.us for links to some of the instances on the web, and there are some with tor services out there too.

3

celebratedrecluse wrote

indeed, however for the latter all require JS to play the videos i think.

3

cammie wrote

I can't check right now but I think it should work as long as you allow <media> html elements (which may not be the default for NoScript), you may also have to allow iframes or turn on 'proxy vidoes' in the Invidious settings, not sure and ymmv, but I'll reply later when I can confirm.

3

celebratedrecluse wrote

Would appreciate your insight if you have the time. Kind morning to you

3

cammie wrote

Hey sorry it took a while to get back to you on this, but -- at least on my machine -- it does work.

If you are blocking media elements then those will need to be allowed when first using an invidious instance.

One thing to look out for if you're using NoScript is that by default most invidious instances seem to have 'proxy videos' turned off (for settings, check the cog icon at the top), so the media element on the page will point to a googlevideo.com subdomain, and it's likely that you'll have to allow media from various different googlevideo subdomains before it'll actually play anything, and that'll have to be done for every single video, so with NoScript this will mean dealing with a bunch of popups asking if you want to allow media for each subdomain, which might be a hassle.

To avoid this you can either:

Turn on proxy videos which causes the invidious instance to fetch the video itself and send it to you from their own servers, which means only having to allow media from the domain of the invidious instance, and also gives google a little less specific info about who is watching what. But I'm gonna go out on a limb and guess that most invidious instances can't handle the same amount of traffic as google, and so it could be a little slower, that all depends on the instance and what you're watching of course, so ymmv. You can use invidious in 'listen mode' too which would save you having to download the video and may negate any loss in throughput.

or:

Use something like uMatrix instead of NoScript to allow the media elements from the whole googlevideo.com domain regardless of subdomain, this is probably faster for hd video too, but it does provide more specific info to google. And I also don't know if there is a way to just do that for NoScript too, so that may also be an option.

Anyway, hopefully that helps. Hope it works for you too :)

4