Keep OSNews alive by becoming a Patreon, by donating through Ko-Fi, or by buying merch!

9front “THIS TIME DEFINITELY” released

The operating system I’m not cool enough to run has pushed out a new release: 9front “THIS TIME DEFINITELY” is now available. 9front is a fork of plan9, created after plan9 languished at Bell Labs. This release enables gefs, the new file system, in the installer, “ip/ipconfig now support dhcpv6 dynamic allocations and handles prefix expirations”, and it comes with some smaller changes, too, of course.

Despite every piece of evidence to the contrary, I am simply not cool enough to run 9front. Maybe one day they’ll notice me, and I get invited to the cool table where the Puffs eat lunch. Who doesn’t want to ring a bell in the headmaster’s office at midnight?

Right to root access

I believe consumers, as a right, should be able to install software of their choosing to any computing device that is owned outright.

This should apply regardless of the computer’s form factor. In addition to traditional computing devices like PCs and laptops, this right should apply to devices like mobile phones, “smart home” appliances, and even industrial equipment like tractors.

In 2025, we’re ultra-connected via a network of devices we do not have full control over. Much of this has to do with how companies lock their devices’ bootloaders, prevent root access, and prohibit installation of software that is not explicitly sanctioned through approval in their own distribution channels.

We should really work on changing that.

↫ Medhir Bhargava

Obviously, this is preaching to the choir here on OSNews. I agree with Bhargava 100%. It should be illegal for any manufacturer of computing devices – with a possible exception for, say, things like medical implants, certain aspects of car control units, and so on – to lock down and/or restrict owners’ ability to install whatever software they want, run whatever code they want, and install whatever operating system they want on the devices that they own. Computers are interwoven into the very fabric of every aspect of our society, and having them under the sole control of the biggest megacorporations in the world is utterly dystopian, and wildly dangerous.

Personally, I would take it a step further: any and all code that runs on products sold must be open. Not necessarily open source, but at the very least open, so that it can be inspected when malice is suspected. This way, society can make sure that the tech billionaire oligarchs giving nazi salutes aren’t in full, black-box control over our devices. Secrecy as a means of corporate control is incredibly dangerous, and forcing all code to be open is the perfect way to combat this. Copyright is more than enough intellectual property protection for code.

The odds of this happening are, of course, slim, especially with the aforementioned tech billionaire oligarchs giving nazi salutes effectively running the most powerful military in human history. Reason is in short supply these days, and I doubt that’s going to change any time soon.

How UNIX spell ran in 64kB RAM

How do you fit a 250kB dictionary in 64kB of RAM and still perform fast lookups? For reference, even with modern compression techniques like gzip -9, you can’t compress this file below 85kB.

In the 1970s, Douglas McIlroy faced this exact challenge while implementing the spell checker for Unix at AT&T. The constraints of the PDP-11 computer meant the entire dictionary needed to fit in just 64kB of RAM. A seemingly impossible task.

↫ Abhinav Upadhyay

They still managed to do it, but had to employ some incredibly clever tricks to make it work, and make it work fast. Such skillful engineers interested in optimising and eeking the most possible performance out of underpowered hardware still exist today, but they’re not in any position to make lasting changes at any of the companies defining our technology today. Why spend money on skilled engineers, when you can just throw cheap hardware at the problem?

I wonder just how many resources the spellchecking feature in Word or LibreOffice Writer takes up.

Introduction to GrapheneOS

GrapheneOS (written GOS from now on) is an Android based operating system that focuses security. It is only compatible with Google Pixel devices for multiple reasons: availability of hardware security components, long term support (series 8 and 9 are supported at least 7 years after release) and the hardware has a good quality / price ratio.

The goal of GOS is to provide users a lot more control about what their smartphone is doing. A main profile is used by default (the owner profile), but users are encouraged to do all their activities in a separate profile (or multiples profiles). This may remind you about Qubes OS workflow, although it does not translate entirely here. Profiles can not communicate between each others, encryption is done per profile, and some permissions can be assigned per profile (installing apps, running applications in background when a profile is not used, using the SIM…). This is really effective for privacy or security reasons (or both), you can have a different VPN per profile if you want, or use a different Google Play login, different applications sets, whatever! The best feature here in my opinion is the ability to completely stop a profile so you are sure it does not run anything in the background once you exit it.

↫ Solène Rapenne

I switched to GrapheneOS on my Pixel 8 Pro as part of my process to cleanse myself of as much Big Tech as possible, and I’ve been incredibly happy with it. The additional security and privacy control GrapheneOS brings is amazing, and the fact it opted for a sandboxed Google Play Services basically means there’s no compatibility issues, unlike when using microG, where compatibility problems are a fact of life. GrapheneOS’ security and other updates are on par or even faster than the stock Google Pixel’s Android, and the overall user experience is virtually identical to stock Android.

The only downside is the reliance on Pixel devices – it’s an understandable choice, but does mean giving money to Google if you don’t already own a Pixel. A workaround, if you will, is to buy a used or refurbished Pixel, but that may not always be an option either. For me personally, I’ll be sticking with my Pixel 8 Pro for a long time, but if it were to break, I’d most likely go the used Pixel route to avoid enriching Google. For pretty much anyone reading OSNews, GrapheneOS would be a great choice, and if you already have a Pixel, I strongly urge you consider switching.

Linux 6.13 released

Linux 6.13 comes with the introduction of the AMD 3D V-Cache Optimizer driver for benefiting multi-CCD Ryzen X3D processors, the new AMD EPYC 9005 “Turin” server processors will now default to AMD P-State rather than ACPI CPUFreq for better power efficiency, the start of Intel Xe3 graphics bring-up, support for many older (pre-M1) Apple devices like numerous iPads and iPhones, NVMe 2.1 specification support, and AutoFDO and Propeller optimization support when compiling the Linux kernel with the LLVM Clang compiler. Linux 6.13 also brings more Rust programming language infrastructure and more.

↫ Michael Larabel

A big release, with a ton of new features. It’ll make its way to your distribution soon enough.

MorphOS 3.19 released

It’s been about 18 months, but we’ve got a new release for MorphOS, the Amiga-like operating system for PowerPC Macs and some other PowerPC-based machines. Going through the list of changes, it seems MorphOS 3.19 focuses heavily on fixing bugs and addressing issues, rather than major new features or earth-shattering changes. Of note are several small but important updates, like updated versions of OpenSSL and OpenSSH, as well as a ton of new filetype definitions – and so much more.

Having a release focused on fixing bugs and addressing smaller issues isn’t exactly a bad thing though – I’ve used MorphOS on my 17″ 1.25Ghz PowerBook G4 often enough to know MorphOS is quite complete, stable, and a ton of fun to use, and much more capable than it has any right to be considering what must be its relatively small developer team and user base. That being said, I do wish MorphOS was available on hardware newer than 20 year old PowerPC Macs, because as much as I like me some classic hardware, the world’s moving on and even basic web browsing requires much more performant hardware now.

Maybe I should try and buy one of the supported Apple PowerPC G5 machines to see just how much better MorphOS runs on that than on my G4.

Google begins requiring JavaScript for Google Search

Google says it has begun requiring users to turn on JavaScript, the widely used programming language to make web pages interactive, in order to use Google Search.

In an email to TechCrunch, a company spokesperson claimed that the change is intended to “better protect” Google Search against malicious activity, such as bots and spam, and to improve the overall Google Search experience for users. The spokesperson noted that, without JavaScript, many Google Search features won’t work properly and that the quality of search results tends to be degraded.

↫ Kyle Wiggers at TechCrunch

One of the strangely odd compliments you could give Google Search is that it would load even on the weirdest or oldest browsers, simply because it didn’t require JavaScript. Whether I loaded Google Search in the JS-less Dillo, Blazer on PalmOS, or the latest Firefox, I’d end up with a search box I could type something into and search. Sure, beyond that the web would be, shall we say, problematic, but at least Google Search worked. With this move, Google will end such compatibility, which was most likely a side effect more than policy.

I know a lot of people lament the widespread reliance on and requirement to have JavaScript, and it surely can be and is abused, but it’s also the reality of people asking more and more of their tools on the web. I would love it websites gracefully degraded on browsers without JavaScript, but that’s simply not a realistic thing to expect, sadly. JavaScript is part of the web now – and has been for a long time – and every website using or requiring JavaScript makes the web no more or less “open” than the web requiring any of the other myriad of technologies, like more recent versions of TLS. Nobody is stopping anyone from implementing support for JS.

I’m not a proponent of JavaScript or anything like that – in fact, I’m annoyed I can’t load our WordPress backend in browsers that don’t have it, but I’m just as annoyed that I can’t load websites on older machines just because they don’t have later versions of TLS. Technology “progresses”, and as long as the technologies being regarded as “progress” are not closed or encumbered by patents, I can be annoyed by it, but I can’t exactly be against it.

The idea that it’s JavaScript making the web bad and not shit web developers and shit managers and shit corporations sure is one hell of a take.

Dillo 3.2.0 released

We’ve got a new Dillo release for you this weekend!

We added SVG support for math formulas and other simple SVG images by patching the nanosvg library. This is specially relevant for Wikipedia math articles.

We also added optional support for WebP images via libwebp. You can use the new option ignore_image_formats to ignore image formats that you may not trust (libwebp had some CVEs recently).

↫ Dillo website

This release also comes with some UI tweaks, like the ability to move the scrollbar to the left, use the scrollbar to go back and forward exactly one page, the ability to define custom link actions in the context menu, and more – including the usual bug fixes, of course. Once the pkgsrc bug on HP-UX I discovered and reported is fixed, Dillo is one of the first slightly more complex packages I intend to try and build on HP-UX 11.11.

Hands-on graphics without X11 using NetBSD’s wscons

Now, if you have been following the development of EndBASIC, this is not surprising. The defining characteristic of the EndBASIC console is that it’s hybrid as the video shows. What’s newsworthy, however, is that the EndBASIC console can now run directly on a framebuffer exposed by the kernel. No X11 nor Wayland in the picture (pun intended).

But how? The answer lies in NetBSD’s flexible wscons framework, and this article dives into what it takes to render graphics on a standard Unix system. I’ve found this exercise exciting because, in the old days, graphics were trivial (mode 13h, anyone?) and, for many years now, computers use framebuffer-backed textual consoles. The kernel is obviously rendering “graphics” by drawing individual letters; so why can’t you, a user of the system, do so too?

↫ Julio Merino

This opens up a lot of interesting use cases and fun hacks for developers to implement in their CLI applications. All the code in the article is – as usual – way over my head, but will be trivial for quite a few of you.

The mentioned EndBASIC project, created by the author, Julio Merino, is fascinating too:

EndBASIC is an interpreter for a BASIC-like language and is inspired by Amstrad’s Locomotive BASIC 1.1 and Microsoft’s QuickBASIC 4.5. Like the former, EndBASIC intends to provide an interactive environment that seamlessly merges coding with immediate visual feedback. Like the latter, EndBASIC offers higher-level programming constructs and strong typing.

EndBASIC’s primary goal is to offer a simplified and restricted DOS-like environment to learn the foundations of programming and computing, and focuses on features that quickly reward the learner. These include a built-in text editor, commands to manipulate the screen, commands to interact with shared files, and even commands to interact with the hardware of a Raspberry Pi.

↫ EndBASIC website

Being able to run this on a machine without having to load either X or Wayland is a huge boon, and makes it accessible fast on quite a lot of hardware on which a full X or Wayland setup would be cumbersome or slow.

Microsoft adds “AI” to Microsoft 365 and raises prices to pay for it

Up until now, if you were subscribed to Office 365 – I think it’s called Microsoft 365 now – and you wanted the various “AI” Copilot features, you needed to pay $20 extra. Well, that’s changing, as Microsoft is now adding these features to Microsoft 365 by default, while raising the prices for every subscriber by $3 per month. It seems not enough people were interested in paying $20 per month extra for “AI” features in Office, so Microsoft has to force everyone to pay up. It’s important to note, though, that your usage of the features is limited by how many “AI credits” you have, to really nail that slot machine user experience, and you’re only getting a limited number of those per month.

Luckily, existing Microsoft 365 subscribers can opt out of these new features and thus avoid the price increase, which is a genuinely welcome move by Microsoft. New subscribers, however, will not be able to opt out.

Finally, we understand that our customers have a variety of needs and budgets, so we’re committed to providing options. Existing subscribers with recurring billing enabled with Microsoft can switch to plans without Copilot or AI credits like our Basic plan, or, for a limited time, to new Personal Classic or Family Classic plans. These plans will continue to be maintained as they exist today, but for certain new innovations and features you’ll need a Microsoft 365 Personal and Family subscription.

↫ Bryan Rognier at the Microsoft blog

Microsoft wants to spread the immense cost of running datacentres for “AI” to everyone, whether you want to use these features or not. When not enough people want to opt into “AI” and pay extra, the only other option is to just make everyone pay, whether they want to or not. Still, the opt-out for existing subscribers is nice, and if you are one and don’t want to pay $35 per year extra, don’t forget to opt out.

Venture: cross-platform GUI tool for parsing and analyzing Windows event logs

Venture is a cross-platform viewer for Windows Event Logs (.evtx files). Built with the Tauri, it is intended as a fast, standalone tool for quickly parsing and slicing Windows Event Log files during incident response, digital forensics, and CTF competitions.

↫ Venture GitHub page

Neat tool. It makes sense that it would be possible to build third-party viewers for Windows event logs, but I never stopped to think about it and just defaulted to the one built into Windows.

Google announces it’s going to intentionally violate EU law

Google has told the EU it will not add fact checks to search results and YouTube videos or use them in ranking or removing content, despite the requirements of a new EU law, according to a copy of a letter obtained by Axios.

[…]

In a letter written to Renate Nikolay, the deputy director general under the content and technology arm at the European Commission, Google’s global affairs president Kent Walker said the fact-checking integration required by the Commission’s new Disinformation Code of Practice “simply isn’t appropriate or effective for our services” and said Google won’t commit to it.

↫ Sara Fischer at Axios

Imagine if any one of us, ordinary folk told the authorities we were just not going to follow the law. We’re not going to pay our taxes because tax law “simply isn’t appropriate or effective for our services”. We’re not going to follow traffic laws and regulations because doing so “simply isn’t appropriate or effective for our services”. We’re not going to respect property laws because doing so “simply isn’t appropriate or effective for our services”. We’d be in trouble within a heartbeat. We’d be buried in fines, court cases, and eventually, crippling debt, bankruptcy, and most likely end up in prison.

The arrogance with which these American tech giants willfully declare themselves to be above EU laws and regulations is appalling, and really should have far more consequences than it does right now. Executives should be charged and arrested, products and services banned and taken off the shelves, and eventually, the companies themselves should be banned from operating within the EU altogether. Especially with the incoming regime in the US, which will most likely grant the tech giants even more freedom to do as they please, the EU needs to start standing up against this sort of gross disrespect.

The consequences for a corporation knowingly breaking the law should be just as grave as for an individual citizen knowingly breaking the law.

Offer: Volunteer labor for your open source project

OSNews Sponsor OS-SCi is educating the next generation FOSS engineers, and as part of their coursework, they’re looking for worthy open source projects to which they can contribute their time and effort. In addition to the work they provide during their studies, these volunteers will be encouraged to continue to be involved after they finish their courses and proceed into the workforce. If you are involved in an open source project and would like some help, please register here. Also, please leave a comment below to share some details about your project with the OSNews community. Perhaps we can use this forum to bring some OSNews readers together as long term collaborators.

In other news, OS-SCi is organizing an international Open Source Hackathon on 21-22 February online and on multiple university campuses. Register for the hackathon here. Read more details here.

Microsoft will also stop supporting Office applications on Windows 10 after October 14

It seems we’re getting a glimpse at the next stick Microsoft will be using to push people to buy new PCs (we’re all rich, according to Microsoft) or upgrade to Windows 11. In a blog post extolling the virtues of a free upgrade from Windows 10 to 11, the company announced that with the end of support for Windows 10, Microsoft will also stop supporting Office applications on Windows 10, otherwise known as Office 365.

Lastly, Microsoft 365 Apps will no longer be supported after October 14, 2025, on Windows 10 devices. To use Microsoft 365 Applications on your device, you will need to upgrade to Windows 11.

↫ Microsoft’s Margaret Farmer

Of course, the applications won’t stop working on Windows 10 right away after that date, but Microsoft won’t be fixing any security issues, bugs, or other issues that might (will) come up. It reads like a threat to Windows users – upgrade by buying a new PC you probably can’t afford, or not only use an insecure version of Windows, but also insecure Office applications. I doubt it’ll have much of an impact on the staggering number of people still using Windows 10 – more than 60% of Windows users – so I’m sure Microsoft has more draconian plans up its sleeve to push people to upgrade.

Nepenthes: a dangerous tarpit to trap LLM crawlers

If you don’t want OpenAI’s, Apple’s, Google’s, or other companies’ crawlers sucking up the content on your website, there isn’t much you can do. They generally don’t care about the venerable robots.txt, and while people like Aaron Schwartz were legally bullied into suicide for downloading scientific articles using a guest account, corporations are free to take whatever they want, permission or no. If corporations don’t respect us, why should we respect them?

There are ways to fight back against these scrapers, and the latest is especially nasty in all the right ways.

This is a tarpit intended to catch web crawlers. Specifically, it’s targeting crawlers that scrape data for LLM’s – but really, like the plants it is named after, it’ll eat just about anything that finds its way inside.

It works by generating an endless sequences of pages, each of which with dozens of links, that simply go back into the tarpit. Pages are randomly generated, but in a deterministic way, causing them to appear to be flat files that never change. Intentional delay is added to prevent crawlers from bogging down your server, in addition to wasting their time. Lastly, optional Markov-babble can be added to the pages, to give the crawlers something to scrape up and train their LLMs on, hopefully accelerating model collapse.

↫ ZADZMO.org

You really have to know what you’re doing when you set up this tool. It is intentionally designed to cause harm to LLM web crawlers, but it makes no distinction between LLM crawlers and, say, search engine crawlers, so it will definitely get you removed from search results. On top of that, because Nepenthes is designed to feed LLM crawlers what they’re looking for, they’re going to love your servers and thus spike your CPU load constantly. I can’t reiterate enough that you should not be using this if you don’t know what you’re doing.

Setting it all up is fairly straightforward, but of note is that if you want to use the Markov generation feature, you’ll need to provide your own corpus for it to feed from. None is included to make sure every installation of Nepenthes will be different and unique because users will choose their own corpus to set up. You can use whatever texts you want, like Wikipedia articles, royalty-free books, open research corpuses, and so on. Nepenthes will also provide you with statistics to see what cats you’ve dragged in.

You can use Nepenthes defensively to prevent LLM crawlers from reaching your real content, while also collecting the IP ranges of the crawlers so you can start blocking them. If you’ve got enough bandwith and horsepower, you can also opt to use Nepenthes offensively, and you can have some real fun with this.

Let’s say you’ve got horsepower and bandwidth to burn, and just want to see these AI models burn. Nepenthes has what you need:

Don’t make any attempt to block crawlers with the IP stats. Put the delay times as low as you are comfortable with. Train a big Markov corpus and leave the Markov module enabled, set the maximum babble size to something big. In short, let them suck down as much bullshit as they have diskspace for and choke on it.

↫ ZADZMO.org

In a world where we can’t fight back against LLM crawlers in a sensible and respectful way, tools like these are exactly what we need. After all, the imbalance of power between us normal people and corporations is growing so insanely out of any and all proportions, that we don’t have much choice but to attempt to burn it all down with more… Destructive methods. I doubt this will do much to stop LLM crawlers from taking whatever they want without consent – as I’ve repeatedly said, Silicon Valley does not understand consent – but at least it’s joyfully cathartic.

Microsoft releases 161 Windows security updates

Speaking of Microsoft shipping bad code, how about an absolutely humongous ‘patch Tuesday’?

Microsoft today unleashed updates to plug a whopping 161 security vulnerabilities in Windows and related software, including three “zero-day” weaknesses that are already under active attack. Redmond’s inaugural Patch Tuesday of 2025 bundles more fixes than the company has shipped in one go since 2017.

↫ Brian Krebs

Happy new year, Windows users.

A Microsoft change to the Linux kernel caused major breakage, but was caught in time

A change to the Linux 6.13 kernel contributed by a Microsoft engineer ended up changing Linux x86_64 code without proper authorization and in turn causing troubles for users and now set to be disabled ahead of the Linux 6.13 stable release expected next Sunday.

↫ Michael Larabel

What I like about this story is that it seems to underline that the processes, checks, and balances in place in Linux kernel development seem to be working – at least, this time. A breaking change was caught during the prerelease phase, and a fix has been merged to make sure this issue will be fixed before the stable version of Linux 6.13 is released to the wider public. This all sounds great, but there is an element of this story that raises some serious questions.

The change itself was related to EXECMEM_ROX, and was intended to improve performance of 64bit AMD and Intel processors, but in turn, this new code broke Control Flow Integrity on some setups, causing some devices not to wake from hibernation while also breaking other features. What makes this spicy is that the code was merged without acknowledgement from any of the x86 kernel maintainers, which made a lot of people very unhappy – and understandably so.

So while the processes and checks and balances worked here, something still went horribly wrong, as such changes should not be able to be merged without acknowledgement from maintainers. This now makes me wonder how many more times this has happened without causing any instantly discoverable issues. For now, some code has been added to revert the offending changes, and Linux 6.13 will ship with Microsoft’s bad code disabled.

Google allows advertisers to fingerprint you for even better tracking

They tried to keep it from prying eyes, but several people did notice it: Google made a pretty significant policy change regarding the use of fingerprinting by advertisers. While Google did not allow advertisers to use digital fingerprinting, the company has now changed its mind on this one.

Previously, Google did not allow advertisers to pass any information to it that

  • Google could use or recognize as personally-identifiable information.
  • permanently identifies a particular device (such as a mobile phone’s unique device identifier if such an identifier cannot be reset).

The second rule has been removed in the new policy. In other words, advertisers may identify users based on the devices that they use and may pass the information to Google for tracking purposes.

↫ Martin Brinkmann at gHacks

Google really tried to hide this change. The main support article talking about the reasoning behind the change is intentionally obtuse and nebulous, and doesn’t even link to the actual policy changes being implemented – which are found in a separate document. Google doesn’t highlight its changes there, so you have to compare the two versions of the policy yourself.

Google claims this change has to be implemented because of “advances in privacy-enhancing technologies (PETs) such as on-device processing, trusted execution environments, and secure multi-party computation” and “the rise of new ad-supported devices and platforms”. What I think this word salad means is that users are regaining a modicum of privacy with some specific privacy-preserving features in certain operating systems and on certain devices, and that the use of dedicated, siloed streaming services is increasing, which is harder for Google and advertisers to track.

In other words, Google is relaxing its rules on fingerprinting because we’re all getting more conscious about privacy.

In any event, the advice remains the same: use ad-blockers, preferably at your network level. Install adblocking software and extensions, set up a Pi-Hole, or turn on any adblocking features in your router (my Ubiquiti router has it built-in, and it works like a charm). Remember: your device, your rules. If you don’t want to see ads, you don’t have to.

FM TOWNS Technical Databook partially translated to English

In recent months, we’ve talked twice about FM Towns, Fujitsu’s PC platform aimed solely at the Japanese market. It was almost entirely only available in Japanese, so it’s difficult to explore for those of us who don’t speak Japanese. There’s an effort underway to recreate it as open source, which will most likely take a while, but in the meantime, a part of the FM TOWNS Technical Databook, written by Noriaki Chiba, has been translated from Japanese into English by Joe Groff.

From the book’s preface:

That is why the author wrote this book, to serve as an essential manual for enthusiasts, systems developers, and software developers. Typical computer manuals do not adequately cover technical specifications, so users tend to have a hard time understanding the hardware. We have an opportunity to thoroughly break through this barrier, and with this new hardware architecture being a milestone in the FM series, it feels like the perfect time to try. Hardware manuals up to this point have typically only explained the consequences of the hardware design without explaining its fundamentals. By contrast, this book describes the hardware design of the TOWNS from its foundations. Since even expert systems developers can feel like amateurs when working with devices outside of their repertoire, this book focuses on explaining those foundations. This is especially necessary for the FM TOWNS, since it features so many new devices, including a 80386 CPU and a CD-ROM drive.

↫ Noriaki Chiba [translated by Joe Groff]

This handbook goes into great detail about the inner workings of the hardware, and chapter II, which hasn’t been translated yet, also dives deep into the BIOS of the hardware, from its first revisions to all the additional features added on top as time progressed. This book, as well as its translation, will be invaluable to people trying to use Towns OS today, to developers working on emulators for the platform, and anyone who fits somewhere in between.

It seems this translation was done entirely in Groff’s free time as a side project, which is commendable. We’re looking at about 65000 words in the target language, of a highly technical nature, all translated for free because someone decided it was worth it. Sending this over to a translation agency would most likely cost well over €10000. Of course, that would include additional editing and proofreading by parties other than the initial translator(s), but that’s definitely not needed for a passion project like this.

Excellent, valuable work.

Let’s talk about bias

When someone says you’re biased against them because you object to their stated goal of removing you from society, they’re not actually asking for fairness — they’re demanding complicity.

It’s the political equivalent of asking why the gazelle seems to have such a negative view of lions.

Think about the underlying logic here: I’m biased because I don’t give equal weight to both sides of a debate about my fundamental rights. I’m biased because I notice patterns in political movements that explicitly state their intentions regarding people like me.

I’m biased because I take them at their word when they tell me what they plan to do.

↫ Joan Westenberg

OSNews and I will always stand for the right of transgender people to exist, and to enjoy the exact same rights and privileges as any other member of society. This is non-negotiable.