I have been reading Doom Guy by John Romero. It is an excellent book which I highly recommend. In the ninth chapter, John describes being hit by lightning upon seeing Adaptive Tile Refresh (ATS). That made me realize I never took the time to understand how this crucial piece of tech powers the Commander Keen (CK) series. During my research I was surprised to learn that ATS only powered the first CK trilogy. The second trilogy turned out to use something far better. I’ve played all the Commander Keen games as a child over and over again, but being quite young at the time (I’m from 1984, so do the math), it never dawned on me just how much of a technological marvel these games really were.
While most of us are used to this system and its quirks, that doesn’t mean it’s without problems. This is especially apparent when you do user research with people who are new to computing, including children and older people. Manually placing and sizing windows can be fiddly work, and requires close attention and precise motor control. It’s also what we jokingly refer to as shit work: it is work that the user has to do, which is generated by the system itself, and has no other purpose. Most of the time you don’t care about exact window sizes and positions and just want to see the windows that you need for your current task. Often that’s just a single, maximized window. Sometimes it’s two or three windows next to each other. It’s incredibly rare that you need a dozen different overlapping windows. Yet this is what you end up with by default today, when you simply use the computer, opening apps as you need them. Messy is the default, and it’s up to you to clean it up. There are a lot of interesting ideas in what GNOME is working on to address these issues, and it includes a lot of new thinking and new approaches to windowing. I have a lot of reservations, though. I do not like it when windows do something out of their own volition. A window should be where I put it, and manipulating one window should not make any changes to the shape or position of other windows, unless I’m specifically asking the window manager to do so (e.g. using the side-by-side snap feature, which I never do). There’s nothing I hate more than my UI deciding what’s best for me. Windows should be where I put them – until I explicitly instruct my window manager to put them somewhere else. I also do not understand this obsession with fullscreen windows. I just don’t get it. Unless it’s a video or a game, none of my windows ever go fullscreen, whether it be on a small 13″ laptop display, or on my 28″ 4K desktop monitor. I find fullscreen claustrophobic, and it almost never makes any sense anyway since virtually no application actually makes use of all that space. You just end up with tons of wasted space. Designing a UI with fullscreen as a corner stone absolutely baffles me. As such, some of these ideas for GNOME worry me a tiny bit, since they go against some of the core tenets I hold about my UI. I’ll see how it works out when it ships, but for now, I’m cautiously worried.
In my previous article, I described how I managed to install Windows 2000 in DOSBox-X. Even though this experiment was successful, I was not really with the results. While I got Windows 2000 working, I didn’t want to stop there. The final goal for the project was to get Windows XP running instead. However, after multiple attempts I gave up, thinking that Windows XP was impossible to use. Well – I was wrong. I can’t believe this works.
You can become a Patreon, make a one-time donation through Ko-Fi, and now, by popular demand, we have a third option to support OSNews: merch! We’ve just launched our new merch store, currently selling three items – two T-shirts and a coffee mug. First, we have a plain logo T-shirt. It’s a crew (round) neck T-shirt available in ‘Night Sky Navy’ or ‘Herb Green’, with our logo printed top-left on the chest. Second, we have the same logo T-shirt in the same two colours, but with an additional quote printed below it for those of you who really long for the olden days when Eugenia ran this place. This second shirt is a limited edition, and will eventually be replaced by a shirt with a different quote, so get it while supplies last. Both T-shirts are made of 100% organic cotton for that extra soft feel. Each shirt costs $29.99 and ships worldwide. Third, there’s a coffee mug with a logo and a quote for people who are kind of sick of my shit. It’s a mug. It holds coffee (or tea, or gasoline). It’s white. It sells for $19.99 and also ships worldwide. Since I want to be transparent about this – we’re working with a third party store from Richmond, Virginia, US, who produces the shirts and mugs, since we obviously can’t produce them ourselves. The pricing has been carefully set so that for each item sold, OSNews gets about $8. Do note that the items are made-to-order, so shipping takes a little longer than in-stock items from regular stores. I intend to add more items and maybe more colour options in the future (lighter colours are hard with our current logo), but we all have to start somewhere. As always, thanks for all your support – whether it be monetarily or just by being here. It means a lot.
The Android KitKat (KK) platform was first released ~10 years ago and since then, we’ve introduced many innovative improvements and features for Android, which are unavailable on KK. As of July 2023, the active device count on KK is below 1% as more and more users update to the latest Android versions. Therefore, we are no longer supporting KK in future releases of Google Play services. KK devices will not receive versions of the Play Services APK beyond 23.30.99. It’s time.
Last year at Google I/O, we shared some big changes coming to the Play Store for large screen devices. Since then, we’ve seen even more people using large screens for work and play, across millions of active Android devices. Apps and games play a critical role in shaping the on-device experience, so we’ve redesigned the Play Store to help users get the most from their tablets, Chromebooks, and foldables. Today, we’re introducing four major updates to help users find high-quality large screen apps on Play: refreshed app listing pages, ranking and quality improvements, streamlined store navigation, and a split-screen search experience. I’m glad Google seems to be finally doing the things it need to do to make Android applications feel more at home on larger displays. While I believe the problem has been somewhat overblown by tech media, there’s no denying iPadOS has a wider and more optimised tablet application offering, and Google’s got a lot of work to do to catch up.
9to5Google reports: Last year, we reported that Google’s Fuchsia team had renewed its efforts to support smart speakers. Long story short, the team had experimented with a single speaker, ditched that effort, then “restored” it later on. More importantly, the Fuchsia team was found to be working on multiple speakers, the most notable of which was an as-yet-unreleased speaker equipped with UWB. In a newly posted code change, the Fuchsia team formally marked all of its speaker hardware as “unsupported” and altogether removed the related code. Among the hardware now unsupported by Fuchsia, you’ll find the underlying SoCs for the Nest Mini, Nest Audio, Nest Wifi point, a potentially upcoming Nest speaker, and some Android Things-based smart speakers. The Fuchsia team hasn’t shared a reason why its smart speaker efforts were discontinued. One issue that potentially played a role is that the Amlogic A113L chip used in “Clover” – an unknown device that we suspect may be the Pixel Tablet dock – does not meet Fuchsia’s strict CPU requirements. Amlogic’s engineers attempted to work around this issue, seemingly to no avail. It also doesn’t help Google fired about 20% of the 400 people working on Fuchsia. Since its discovery about six years ago, Fuchsia has been on an upward trajectory, but the massive layoffs and now the end of the smart speakers project, one has to wonder what the future of Fuchsia is going to be. Everything seemed to point at Fuchsia one day taking hold in Android and Chrome OS, but that seems farther away now than ever.
Intel has announced two new x86-64 instruction sets designed to bolster and offer more performance in AVX-based workloads with their hybrid architecture of performance (P) and efficiency (E) cores. The first of Intel’s announcements is their latest Intel Advanced Performance Extensions, or Intel APX as it’s known. It is designed to bring generational, instruction set-driven improvements to load, store and compare instructions without impacting power consumption or the overall silicon die area of the CPU cores. Intel has also published a technical paper detailing their new AVX10, enabling both Intel’s performance (P) and efficiency (E) cores to support the converged AVX10/256-bit instruction set going forward. This means that Intel’s future generation of hybrid desktop, server, and workstation chips will be able to support multiple AVX vectors, including 128, 256, and 512-bit vector sizes throughout the entirety of the cores holistically. The basic gist is that these two new instruction sets should bring more performance at lower energy usage.
There’s been a lot of concern recently about the Web Environment Integrity proposal, developed by a selection of authors from Google, and apparently being prototyped in Chromium. There’s good reason for anger here (though I’m not sure yelling at people on GitHub is necessarily the best outlet). This proposal amounts to attestation on the web, limiting access to features or entire sites based on whether the client is approved by a trusted issuer. In practice, that will mean Apple, Microsoft & Google. Of course, Google isn’t the first to think of this, but in fact they’re not even the first to ship it. Apple already developed & deployed an extremely similar system last year, now integrated into MacOS 13, iOS 16 & Safari, called “Private Access Tokens“. Ten bucks this bad thing Apple is already shipping will get far less attention than a proposal by Google.
octox is a Unix-like operating system inspired by xv6-riscv. octox loosely follows the structure and style of xv6, but is implemented in pure Rust. It’s a learning project, so no lofty goals of world domination here.
The “enshittification” of social media started around 2016, but it reached new highs in 2023. All chronological feeds and hashtag importance have given way to narrow-AI algorithms and recommendation engines. The result was that reach has become impossible for the common user, and many art creatives lost their livelihoods. Enter the Fediverse. From Wikipedia: “The fediverse is an ensemble of federated (i.e. interconnected) servers that are used for web publishing (i.e. social networking, microblogging, blogging, or websites) and file hosting, which, while independently hosted, can communicate with each other.“ This system has some advantages: It is almost impossible for governments to shut down in its entirety. User load can be shared among different servers (“instances”). Different instances have different rules, so you join the one you agree best with. Generally no spam and fewer bots. A non-aggressive environment as users get along better. No telemetry or ads. Everything is chronological so there are equal chances to be seen, no weird recommendation engines here. As for the disadvantages: Some instance admins are too twitchy, and can block other servers on a dime (my main gripe with the system). Some users are too sensitive for some topics, and require you to self-censor. The system probably can’t sustain more than 10-20 million active users, because not many people have the expertise to run their own instance and pay for the financial costs before donations start rolling in. If your instance goes down, you’ll have to migrate and re-acquire all your followers from scratch. Your family and friends aren’t on it, and probably never will be. Here are the Fediverse alternatives to the classic options: Alternative to Twitter: Mastodon The biggest federated environment with over 2 million active users. Great for “toots”, and small-sized blogging. Very actively developed. While there’s an official app for it and a third party one called… Shitter, and FediLab, the best way to view it remains the web browser. Alternatives to Mastodon: Pleroma, Diaspora, Misskey/Calckey (they mostly interoperate anyway). Alternative to Reddit: Lemmy Since the latest Reddit shenanigans Lemmy has jumped to become the second most used fediverse service. Still under active development, but it works great and it has all major Reddit features. People there are much nicer too! Alternative to Lemmy: Kbin (they interoperate, so Kbin content is available on Lemmy, and vice versa). Apps: Jerboa, Lemming, LiftOff, Summit, Connect. Alternative to Instagram: Pixelfed A bit slow compared to the other fedi services, but it’s unique in getting the original Instagram experience. As an artist, I love it. PixelDroid is the mobile app for it. Alternative to Youtube: PeerTube Well, there’s TilVids, and then there’s everyone else. TilVids doesn’t want to federate with everyone else, but it does have the most interesting videos (particularly of Linux interest). Spectra.Video and Diode.Zone are also great options to move your videos at. Just note that bandwidth is limited in these free services, so it’s best to upload in 1080p instead of 4k. There are 3-4 mobile apps for it. Alternative to Medium/Wordpress/SubStack: WriteFreely Not much to say here, a very modern editor that acts as blogging and article publishing service. Secure Messaging and IRC/Discord alternatives: Matrix Matrix is secure messaging end-to-end with Element.io being the main provider. It can also act as a community messaging server. Nostr and Jami are the newest such services on the block, but they’re a little bit weird to get into, I still prefer Matrix. Alternative to TikTok: none Thank the Olympian gods! Finally, the best way to deal with some smaller instances going down and losing your account is to get 1-3 different accounts on different instances. I personally have 3 Mastodon accounts, 3 PeerTube ones, and 2 Lemmy/1 Kbin ones. I used an older $70 phone (Moto G5 Plus) where I have installed the free, and very private Murena /e/ OS. It’s a totally de-googled Android OS (more so than LineageOS) that uses the iOS UI paradigm. In it, I use three app stores that only carry open source apps: F-Droid, IzzyOnDroid, and Obtainium. I avoid as much as possible from installing from the Aurora or the included App Lounge app stores that use the Google Play Store. The OS uses the open source microG service to replace the Google Play Services. So, I have almost completely left behind the normal social media and moved on to the Fediverse (apart from FB messenger with my mom, and a couple of special-interest subreddits via my laptop). You see, after leaving OSNews 15+ years ago, I became an artist. And social media was the way to get sales back then. I started with Tumblr, and later Instagram and FB. Overall, I had amassed about 340,000 followers across all social media. Sales were good for a while. Then, the enshittification started. The biggest blow was Instagram removing the chronological feed and hashtag importance, and little by little only superstar accounts were pushed by the recommendation engines. By 2020, it was near-impossible to survive online selling your art. Now, I don’t have any illusions that the Fediverse can replace the golden era of social media (2010-2020). I have calculated that you need a minimum of 100 million active users for various niche business to survive under a fair social media system. And currently, the whole Fediverse only has about 14.5 million accounts, with only about 2.2 million being active. In fact, I don’t expect the fediverse to ever achieve more than 10 million active users… And yet, I prefer to stay on it. It’s simply a more fair system. It’s not a corporation that changes its policies at a whim, or sells your data. I rather use a “lesser” system in terms of reach and maintain my mental health, than battling Instagram’s algorithms all day long (“no, I don’t want to shoot useless vertical short videos”). So, come on and join us on the fediverse. The more the merrier! Note: OSNews is very active on the Fediverse. We have the main OSNews account which posts our stories,
Google’s plan is that, during a webpage transaction, the web server could require you to pass an “environment attestation” test before you get any data. At this point your browser would contact a “third-party” attestation server, and you would need to pass some kind of test. If you passed, you would get a signed “IntegrityToken” that verifies your environment is unmodified and points to the content you wanted unlocked. You bring this back to the web server, and if the server trusts the attestation company, you get the content unlocked and finally get a response with the data you wanted. The web mercilessly mocked this idiotic proposal over the weekend, and rightfully so. This is an unadulterated, transparent attempt at locking down the web with DRM-like nonsense just to serve more targeted ads that you can’t block. This must not make its way into any browser or onto any server in any way, shape, or form. The less attention we give to this drivel, the better.
Ubisoft has confirmed that it is temporarily suspending accounts it deems to be “inactive”, preventing players from accessing their game libraries. Players are then sent an email informing them that their suspended account will be deleted in 30 days unless they click the “Cancel Account Closure” link. Modern gaming.
Ars Technica has a great article about the IBM mainframe. Mainframe computers are often seen as ancient machines—practically dinosaurs. But mainframes, which are purpose-built to process enormous amounts of data, are still extremely relevant today. If they’re dinosaurs, they’re T-Rexes, and desktops and server computers are puny mammals to be trodden underfoot. It’s estimated that there are 10,000 mainframes in use today. They’re used almost exclusively by the largest companies in the world, including two-thirds of Fortune 500 companies, 45 of the world’s top 50 banks, eight of the top 10 insurers, seven of the top 10 global retailers, and eight of the top 10 telecommunications companies. And most of those mainframes come from IBM. In this explainer, we’ll look at the IBM mainframe computer—what it is, how it works, and why it’s still going strong after over 50 years. Whenever I see anything about mainframes, I think of that one time an 18 year old decided to buy a mainframe off eBay to run at home, and did an amazing presentation about the experience.
After many years of effort, I am happy to announce that Debian riscv64 is now an official architecture! This milestone is not the end of the journey but rather the beginning of a new one: the port will need to be rebootstrapped in the official archive, build daemons will have to be reinstalled and handed over to DSA, many bugs will need to be fixed. If everything goes well, the architecture will eventually be released with Trixie. Please note that this process will be long and will span several months. An important step in any architecture’s life cycle is becoming an officially supported Debian architecture.
Thanks to a series of commits by Jonathan Gray (jsg@), -current now has support for microcode (updates) for AMD (amd64 and i386) processors. It’s great to see support for the AMD side gaining equivalence with that for Intel (for which support was added in 2018). Good news for OpenBSD users.
A lot of the cost of a video terminal was the screen. Yet nearly everyone had a TV, and used TVs have always been fairly cheap, too. That’s where Don Lancaster came in. His TV Typewriter Cookbook was the bible for homebrew video displays. The design influenced the Apple 1 computer and spawned a successful kit for a company known as Southwest Technical Products. For around $300 or so, you could have a terminal that uses your TV for output. The wild West days of home computing must’ve been an absolutely fascinating time to live through. I know we have quite a few old-timers in the audience here, so there’s bound to be folks here who used this. Amazing
One of the coolest things to come along in the 68K Mac homebrew community is the ROM Boot Disk concept. Classic Macs have an unusually large ROM that contains a fair bit of the Mac OS, which was true even in the G3 New World Mac era (it was just on disk), so it’s somewhat surprising that only one Mac officially could boot the Mac OS entirely from ROM, namely the Macintosh Classic (hold down Cmd-Option-X-O to boot from a hidden HFS volume with System 6.0.3). For many Macs that can take a ROM SIMM, you can embed a ROM volume in the Mac ROM that can even be mirrored to a RAM disk. You can even buy them pre-populated. How’s that for immutability?Well, it turns out Apple themselves were the first ones to implement a flashable Mac OS ROM volume in 1994, but hardly anyone noticed — because it was only ever used publicly in a minority subset of one of the most unusual of the Macintosh-derived systems, the Apple Interactive Television Box (a/k/a AITB or the Apple Set Top Box/STB). And that’s what we’re going to dig into — and reprogram! — today. I had never heard of this obscure Apple product, so I was like a kid in a candy store reading this. Great weekend material.
Lately I’ve been spending quite a bit of time learning Rust, and as any sane person would do, after writing a few 100 lines programs I’ve decided to take on something a little bit more ambitious: I have written a Java Virtual Machine in Rust. With a lot of originality, I have called it rjvm. The code is available on GitHub. I want to stress that this is a toy JVM, built for learning purposes and not a serious implementation. Toy or not, this is ambitious and impressive.
The Dolphin project has broken the silence regarding their legal tussle with Nintendo and Valve, giving a far more detailed elaboration of what, exactly happened. First things first – Nintendo did not send Valve or Dolphin a Digital Millenium Copyright Act (DMCA) section 512(c) notice (commonly known as a DMCA Takedown Notice) against our Steam page. Nintendo has not taken any legal action against Dolphin Emulator or Valve. What actually happened was that Valve’s legal department contacted Nintendo to inquire about the announced release of Dolphin Emulator on Steam. In reply to this, a lawyer representing Nintendo of America requested Valve prevent Dolphin from releasing on the Steam store, citing the DMCA as justification. Valve then forwarded us the statement from Nintendo’s lawyers, and told us that we had to come to an agreement with Nintendo in order to release on Steam. Considering the strong legal wording at the start of the document and the citation of DMCA law, we took the letter very seriously. We wanted to take some time and formulate a response, however after being flooded with questions, we wrote a fairly frantic statement on the situation as we understood it at the time, which turned out to only fuel the fires of speculation. So, after a long stay of silence, we have a difficult announcement to make. We are abandoning our efforts to release Dolphin on Steam. Valve ultimately runs the store and can set any condition they wish for software to appear on it. But given Nintendo’s long-held stance on emulation, we find Valve’s requirement for us to get approval from Nintendo for a Steam release to be impossible. Unfortunately, that’s that. The post also goes into greater detail about the Wii Common Key that’s been part of Dolphin’s codebase for 15 years. This key was originally extracted from the GameCube hardware itself, and a lot of people online claimed that Dolphin should just remove this key and all would be well. After consulting with their lawyers, Dolphin has come to the conclusion that including the key poses no legal risk for the project, and even if it somehow did, the various other parts of the Dolphin codebase that make emulation of original games possible would pose a much bigger legal threat anyway. So, the team will keep on including the key, and the only outcome here is that Dolphin will not be available on Steam.
