On May the 13th 2005 I released NoScript 1.0.
I'm currently scrambling to release version 13 within this week, and properly celebrate 20 years of @noscript π₯
Follow https://todon.eu/@ma1
for latest news about NoScript and web browser security. Use NoScript to protect yourself against malicious web content.
On May the 13th 2005 I released NoScript 1.0.
I'm currently scrambling to release version 13 within this week, and properly celebrate 20 years of @noscript π₯
Technical hint : it may occur that a link is shared by @spaceflight which asks you to accept #cookies. You may avoid that using @noscript https://en.wikipedia.org/wiki/NoScript#Active_content_blocking
#Android : https://addons.mozilla.org/en-US/android/addon/noscript
Just released, emergency @torproject 14.0.8 update for #Windows users only, with a critical and urgent Firefox security fix:
Better up-to-date than sorry!
If you're using an old @torproject browser (< 13.5.13) upgrade now, before @noscript and the security levels break.
THANK YOU to our community for ensuring people worldwide are able to exercise their right to speak, browse, and search with freedom and privacy. Today we celebrate our combined efforts of raising $816,141.70 this 2024 year-end fundraising campaign. https://blog.torproject.org/celebrating-2024-yec/
A key mark of totalitarianism is government and party ownership and control of the means of speech and information. The party, through its main apparatchik, owns Twitter. The government wants to own TikTok. The only free speech is the fascists' speech.
π₯Starting 2025 with a bang:
NoScript 12.1.1 is the first stable release sharing the same code branch across Manifest V2 (Firefox π¦, @torproject π§
) and Manifest V3 (Chromium-based) browsers.
It also fixes 11.5.2/12.0.x bugs caused by the new stateless architecture both browser families share.
Many thanks to opentech.fund for supporting this effort! β€οΈ
Coming soon, more bug fixing and UX improvements, on track to celebrate our 20th birthday on May the 13th with NoScript 13 π.
Happy new year! π
Now is your final chance to ensure that people worldwide can exercise their right to speak, browse, and search with freedom and privacy. Join the thousands of people like you who have made a gift to the Tor Projectβs year-end fundraising campaign.
https://torproject.org/donate/donate-md-yec2024
For a rundown of the work you'll be supporting, catch up with Tor's 2024 in review ποΈππͺ© https://blog.torproject.org/2024-year-in-review
PSA for @noscript beta-testers on Firefox: please manually install NoScript 12.1.901 if you want to stay on the development channel - https://noscript.net/getit#development-build
Unfortunately a NoScript 12.0.901 bug prevents it from receiving updates on the development channel.
12.0.901 users will be automatically updated to 12.1.1 (stable channel) as soon as it's published on AMO.
If you (hopefully) wish to keep receiving early betas, please manually install latest https://noscript.net/getit#development-build
Thank you!
PSA for beta-testers on Firefox: please manually install NoScript 12.1.901 if you want to stay on the development channel - https://noscript.net/getit#development-build
Unfortunately a NoScript 12.0.901 bug prevents it from receiving updates on the development channel.
12.0.901 users will be automatically updated to 12.1.1 (stable channel) as soon as it's published on AMO.
If you (hopefully) wish to keep receiving early betas, please manually install latest https://noscript.net/getit#development-build
Thank you!
Wait, what's that?!
@noscript #browser #security #google #chrome #MV3 #ComingSoon #StayTuned
#NoScript 11.5.x is out (#Firefox & @torproject only) π₯
Main news:
β‘ Minimum compatibility bumped from Firefox 59 to 115, allowing for huge code modernization opportunities (11.4.44rc1 is still available for older browsers and #chrome in forced MV2 mode)
β‘ Switched NoScript and the NoScript Commons Library to a fully stateless architecture: a major step toward #MV3 compatibility (coming with NoScript 12.0 alpha for #chromium-based browsers later this month)
@grabbi_it @noscript monocultures are bad for the ecosystem. Google is already a de-facto (and now de-iure) monopoly on the Web, and if Gecko dies nothing could ever stand in its way. Also, more to the technical point, https://noscript.net/usage/#limitations-on-chromium
These comments under @noscript's Chrome Web Store entry just made my day β€οΈ
However: I'm pretty positive NoScript isn't going away from there (MV3 transition is underway), BUT switching to a non-Chromium browser is a smart and sensible move anyway, for your own good and for the Web's sake π¦π§
β οΈ PSA: @noscript 11.4.34 got accidentally broken on Firefox 78 and below. Therefore I've just marked it as incompatible with older browsers, automatically downgrading them to 11.4.31, which can also be manually installed from https://noscript.net/feed.
I plan to restore retro-compatibility in 11.4.35, but I'm also genuinely curious: why so many apparently security conscious people are still using ancient, outdated and vulnerable browsers?
@dragonarchitect @ublockorigin @internetarchive no, not yet... I still haven't gotten used to the interface for whitelisting with UBO; it was so much more intuitive with @noscript...
βοΈ Running a Snowflake browser extension is the easiest way to support censored internet usersβanyone can do it! Learn more about how to opt-in and enable your extension here: https://forum.torproject.org/t/snowflake-browser-extension-requires-opt-in-consent/13232