Monthly Archive:: January 2026

The first year in crypto often feels unfamiliar and fast-paced for new participants. Many decisions appear technical at first glance, while price movement adds pressure to early choices. Clear rules help replace uncertainty with structure. A guided approach helps beginners move forward with clarity rather than confusion. A reliable Australian platform such as Swyftx plays a practical role during this stage by offering clear access and structured tools. This article outlines ten clear do’s and don’ts that shape disciplined habits in the first year. Each rule explains what to follow and what to avoid. The “Do’s”: 5 Rules to Build a Strong Foundation A disciplined allocation strategy limits the size of any single trade to a small fraction of the total balance. This rule ensures that a single market move does not impact the entire account. Consistency in this approach builds a sustainable habit for the long term. Practice environments offer a safe space to explore various features of a platform. Swyftx’s Demo Mode allows users to execute trades with mock funds in a live environment. This feature builds confidence as users see how orders work in real time. Dollar-cost averaging follows a fixed schedule for purchases. Equal amounts enter the market at regular intervals. This habit removes pressure from timing decisions. Many beginners prefer this method due to its simple framework. Attempting to predict price peaks and troughs often leads to frustration for a novice. Market timing requires constant attention and a high level of technical skill. In contrast, a steady schedule provides a calm path through market cycles. It allows a person to participate without the stress of daily price checks. This method rewards consistency over the course of the first year. Automation removes the manual effort from a regular purchase plan. Swyftx’s Recurring Orders feature handles these tasks on behalf of the user. Bitcoin and Ethereum provide clear use cases and established histories. Bitcoin digital currency serves as a store of value and is the original pioneer of the space. Ethereum introduces the concept of smart contracts and decentralized applications. A firm grasp of these two projects provides a clear context for the rest of the market. Safety measures act as a shield for a person’s digital wealth. Two-factor authentication (2FA) adds a vital layer of protection to an account. This proactive stance ensures that the focus remains on growth. A total refusal to sell can lead to missed opportunities for liquidity. Markets move in cycles, and prices do not stay at peaks indefinitely. A balanced approach involves a mix of long-term hold and periodic sales. This strategy provides a sense of accomplishment as the portfolio grows. Clear goals remove the guesswork from the decision to sell an asset. These targets provide a roadmap for the year ahead. They help a participant stay objective when the market becomes volatile. Australian tax rules require accurate records. Trade dates, amounts, and values matter. Clear documentation supports smooth reporting. Consistent tracking avoids confusion later. Swyftx offers comprehensive reports that track every transaction on the account. These documents export easily into formats that an accountant can use. This feature removes the burden of manual data entry for the user. The “Don’ts”: 5 Common Mistakes to Avoid This emotional response drives people to buy an asset after a large price jump. It stems from a desire to match the success of peers in the space. Online platforms often buzz with talk about the next big digital asset. Much of this talk lacks a basis in fundamental research or actual value. A person should verify all claims through independent study and reliable sources. Digital assets experience large price swings within very short time frames. These movements are a standard feature of the current market environment. Acceptance of this fact leads to a more relaxed approach to the market. Daily price charts often create a sense of urgency that is not helpful. A wider view of the market reveals a different perspective on price moves. Exchanges serve as the primary place for the trade and purchase of assets. Personal wallets allow a person to hold their own private keys and control their assets. Each option has a specific place in a well-rounded management plan. The move of assets to a private wallet is a significant step for a newcomer. This process involves the transfer of coins from an account to a personal address. This skill is easy to learn with a bit of practice and attention to detail. Each transaction on a platform carries a small cost in the form of a fee. These costs add up quickly when a person trades multiple times a day. Over a month, these fees can represent a large portion of the initial capital. A simple strategy with fewer moves is easier to manage and track. It allows a person to focus on the performance of a few key assets. This method reduces the chance of a mistake during the execution of a trade. Digital assets represent a shift in how the world views and moves value. A person should view their participation as a multi-year project. This mindset helps to weather the ups and downs of the early stages. The ability to wait is a rare and valuable trait in the modern world. Those who remain calm while others act on impulse often find the most success. Conclusion The first year in the world of digital assets is a period of immense discovery. Adherence to these ten rules provides a clear framework for a positive experience. A focus on education, security, and discipline leads to a solid foundation. Platforms such as Swyftx stand as a reliable partner for those who wish to explore this space with confidence. Success comes to those who prepare and act with a clear purpose in mind. Each rule serves as a guidepost on the path to a successful digital asset journey.

I totally forgot you could do this, but back in the Windows 9x days, you could hold down shift while clicking restart, and it would perform a sort-of “soft” restart without going through a complete reboot cycle. What’s going on here? The behavior you’re seeing is the result of passing the EW_RESTART­WINDOWS flag to the old 16-bit Exit­Windows function. What happens is that the 16-bit Windows kernel shuts down, and then the 32-bit virtual memory manager shuts down, and the CPU is put back into real mode, and control returns to win.com with a special signal that means “Can you start protected mode Windows again for me?” The code in win.com prints the “Please wait while Windows restarts…” message, and then tries to get the system back into the same state that it was in back when win.com had been freshly-launched. ↫ Raymond Chen There’s a whole lot more involved behind the curtains, of course, and if conditions aren’t right, the system will still perform a full reboot cycle. Chen further notes that because WIN.COM was written in assembly, getting back to that “freshly-launched” state wasn’t always easy to achieve. I only vaguely remember you could hold down shift and get a faster “reboot”, but I don’t remember ever really using it. I’ve been digging around in my memories since I saw this story yesterday, and I just can’t think of a scenario where I would’ve realised in time that I could do this.

Have you noticed how it seems like how the “light mode” of your graphical user interface of choice is getting lighter over time? It turns out you’re not crazy, and at least for macOS, light mode has indeed been getting lighter. You can clearly see that the brightness of the UI has been steadily increasing for the last 16 years. The upper line is the default mode/light mode, the lower line is dark mode. When I started using MacOS in 2012, I was running Snow Leopard, the windows had an average brightness of 71%. Since then they’ve steadily increased so that in MacOS Tahoe, they’re at a full 100%. ↫ Will Richardson While this particular post only covers macOS, I wouldn’t be surprised to discover similar findings in Windows, GNOME, and KDE. The benefit of using KDE is that it’s at least relatively easy to switch colour schemes or themes, but changing colours in Windows is becoming a hidden feature, and GNOME doesn’t support it out of the box at all, and let’s not even get started about macOS. I think “light mode” should be “grey mode”, and definitely lament the lack of supported, maintained “grey modes” in both KDE and GNOME. There’s a reason that graphical user interfaces in the era of extensive science-based human-computer interaction research opted for soft, gentle greys (ooh, aah, mmm), and I’m convinced we need to bring it back. The glaring whites we use today are cold and clinical, and feel unpleasant to the point where I turn down the brightness of my monitor in a way that makes other colours feel too muted. Or perhaps I’m out of touch.

If only it was that simple – cue the rollercoaster ride. What an absolutely garish state of affairs lies behind this simple radio button on a website. I’m also well aware OSNews has a certain amount of complexity it might not need, and while I can’t fix that, I am at least working on a potential solution.

There’s cursed computing, and then there’s cursed computing. It turns out that you can render GNOME’s windows with the compositor from Windows 7, dwm.exe. Yes. tl;dr of how this clusterfuck works: this is effectively just x11 forwarding an x server from windows to linux. the fun part is a) making gnome run with an already existing window manager (namely dwm.exe lol), b) making gnome run over x11 forwarding (it is Not a fan, last time it tried running gnome on windows this is what broke it and made it quit trying), and c) actually ripping out parts of the gnome compositor again to make dwm instead of gnome render window decorations to achieve ✨️aero gnome✨️ ↫ ⬡-49016 at Mastodon This is already one of the most cursed things I’ve ever seen, but then things got so much worse. How about Windows 7’s dwm.exe, but composited by GNOME? I need an adult.

Virtualisation is a lot older than you might think, with (one of?) the first implementation(s) being IBM’s VM/CMS, the line of operating systems that would grow to include things like System/370, System/390, all the way up until IBM/Z, which is still being developed and sold today; only recently IBM released the IBM z17 and z/OS 3.2, after all. The VM series of operating systems is designed exclusively for mainframes, and works by giving every user their own dedicated virtual machine running on top of the Control Program, the hypervisor. Inside this virtual machine the user can run a wide variety of operating systems, from the simple, single-user classics like IBM’s Conversational Monitor System, to more complex systems like Linux or AIX. Early versions of VM were released as open source and are now in the public domain, and enthusiasts have continued to build upon it and expand it, with the latest incarnations being the VM/370 Community Edition releases. They contain the Control Program and Conversational Monitor System, augmented by various fixes, improvements, and other additions. You can run VM in an emulator like Hercules, and continue on from there – but what, exactly, can you do with it? That’s where Fun things to do with your VM/370 machine comes in. This article will give you an introduction to the system, and a number of first and later steps you can take while exploring this probably alien environment. If you’ve always dreamt of using an early IBM mainframe, this is probably the easiest way to do so, because buying one is a really, really bad idea.

This is a book intended to teach someone the Java language, from scratch. You will find that the content makes heavy use of recently released and, for the moment, preview features. This is intentional as much of the topic ordering doesn’t work without at least Java 21. ↫ Modern Java GitHub page Some light reading for the weekend. This sure is one hell of a detailed book.

Since Wayland is still quite new to a lot of people, it’s often difficult to figure out which features the Wayland compositor you’re using actually supports. While the Wayland Explorer is a great way to browse through the various protocols and their status in various compositors, there’s now an easier way. The Wayland protocols table makes it very easy to see what your favourite compositor supports, which compositors support the protocol you really want supported before leaving X11 behind, and much more. Roughly speaking, there’s a set of stable core Wayland protocols, as well as a slew of unstable core Wayland protocols that are still in development, but may already be supported by various compositors. On top of that, compositors themselves also have a ton of protocols they themselves introduced and support, but which aren’t supported by anything else – yet, as they may be picked up by other compositors and eventually become part of Wayland’s core protocols. Keeping tabs on specific protocols and their support status is mostly only interesting for developers and people with very specific needs, since mature compositors provide a complete set of features most users never have to worry about. Still, that doesn’t mean there aren’t really cool features cooking, nor does it mean that one specific accessibility-related protocol isn’t incredibly important to keep track of. These websites provide an easy way to do so.

Speaking of NixOS’ use of 9P, what if you want to, for whatever inexplicable reason, use macOS, but make it immutable? Immutable Linux distributions are getting a lot of attention lately, and similar concepts are used by Android and iOS, so it makes sense for people stuck on macOS to want similar functionality. Apple doesn’t offer anything to make this happen, but of course, there’s always Nix. And I literally do mean always. Only try out Nix if you’re willing to first be sucked into a pit of despair and madness before coming out enlightened on the other end – I managed to only narrowly avoid this very thing happening to me last year, so be advised. Nix is no laughing matter. Anyway, yes, you can use Nix to make macOS immutable. But managing a good working environment on macOS has long been a game of “hope for the best.” We’ve all been there: a curl | sh here, a manual brew install there, and six months later, you’re staring at a broken PATH and a Python environment that seems to have developed its own consciousness. I’ve spent a lot of time recently moving my entire workflow into a declarative system using nix. From my zsh setup to my odin toolchain, here is why the transition from the imperative world of Homebrew to the immutable world of nix-darwin has been both a revelation and a fight. ↫ Carette Antonin Of course it’s been a fight – it’s Nix, after all – but it’s quite impressive and awesome that Nix can be used in this way. I would rather discover what electricity from light sockets tastes like than descend into this particular flavour of Nix madness, but if you’re really sick of macOS being a pile of trash for – among a lot of other things – homebrew and similar bolted-on systems held together by duct tape and spit, this might be a solution for you.

If you’re only even remotely aware of the operating system Plan 9, you’ll most likely know that it takes the UNIX concept of “everything is a file” to the absolute extreme. In order to make sure all these files – and thus the components of Plan 9 – can properly communicate with one another, there’s 9P, or the Plan 9 Filesystem Protocol. Several Plan 9 applications are 9P file servers, for instance, and even things like windows are files. It’s a lot more complicated than this, of course, but that’s not relevant right now. Since Plan 9 wasn’t exactly a smashing success that took the operating system world by storm, you might not be aware that 9P is actually implemented in a few odd places. My favourite is how Microsoft turned to 9P for a crucial feature of its Windows Subsystem for Linux: accessing files inside a Linux VM running on Windows. To put it briefly: a 9P protocol file server facilitates file related requests, with Windows acting as the client. We’ve modified the WSL init daemon to initiate a 9P server. This server contains protocols that support Linux metadata, including permissions. A Windows service and driver that act as the client and talks to the 9P server (which is running inside of a WSL instance). Client and server communicate over AF_UNIX sockets, since WSL allows interop between a Windows application and a Linux application using AF_UNIX as described in this post. ↫ Craig Loewen at Microsoft’s Dev Blogs This implementation is still around today, so if you’re using Windows Subsystem for Linux, you’re using a little bit of Plan 9 as glue to make it all come together. Similarly, if you’re using QEMU and sharing files between the host and a VM through the VirtFS driver, you’re also using 9P. Both NixOS and GNU Guix use 9P when they build themselves inside a virtual machine, too, and there’s probably a few other places where you can run into 9P. I don’t know, I thought this was interesting.

Despite December being the holiday month, Haiku’s developers got a lot of things done. A welcome addition for those of us who regularly install Haiku on EFI systems is a tool in the installer that will copy the EFI loader to the EFI system partition, so fewer manual steps are needed on EFI systems. Support for touchpads from Elantech has also been improved, and the FreeBSD driver compatibility layer and all of its Ethernet and WiFi drivers have been updated to match the recent FreeBSD 15 release. Of course, there’s also the usual long list of smaller fixes, improvements, and changes. As for a new release milestone, beta 6 seems to be on the way. Not quite. There has been some discussion on the mailing list as the ticket list gets smaller, but there’s still at least some more regressions that need to be fixed. But it looks like we’ll be starting the release process in the next month or two, most likely… ↫ Haiku’s December 2025 activity report To be fair, though, Haiku’s nightly releases are more than able to serve their duties, and waiting for a specific release if you’re interested in trying out Haiku is really not needed. Just grab the latest nightly, follow the installation instructions, and you’re good to go. The operating system supports updating itself, so you’ll most likely won’t need to reinstall nightlies all the time.

It’s no secret that the Windows 95 installer uses a heavily stripped-down Windows 3.10 runtime, but what can you actually do with it? How far can you take this runtime? Can it run Photoshop? It is a long-standing tradition for Microsoft to use a runtime copy of Windows as a part of Windows Setup. But the copy is so stripped-down, it cannot run anything but the setup program (winsetup.bin). OR IS IT? A mini-challenge for myself: create a semi-working desktop only based on runtime Windows 3.10 shipped with Windows 95 installer but not using any other Microsoft products. ↫ Nina Kalinina A crucial limitation here is that Kalinina is not allowing herself to use any additional Microsoft products, so the easy route of just copying missing DLLs and other files from a Windows 95 disk or whatever is not available to her; she has to source any needed files from other sources. This may seem impossible, but during those days, tons of Windows (and even DOS) applications would ship with various Microsoft DLLs included, so there are definitely places to get Windows DLLs that aren’t coming directly from Microsoft. As an example, since there’s no shell of any kind included in the stripped-down Windows 3.10 runtime, Kalinina tried Calmira and WinBar, which won’t work without a few DLLs. Where to get them if you can’t get them straight from Microsoft? Well, it turns out programs compiled with later version of MSVC would include several of these needed DLLs, and AutoCad R12 was one of them. WinBar would now start and work, and while Calmira would install, it didn’t work because it needs the Windows Multimedia Subsystem, which don’t seem to be included in anything non-Microsoft. It turns out you can take this approach remarkably far. Things like Calculator and Notepad will work, but Pain or Paintbrush will not. Larger, more complex applications work too – Photoshop 2.5.1 works, as does Netscape, but without any networking stack, it’s a little bit moot. Even Calmira XP eventually runs, as some needed DLLs are found inside “Mom For Windows 2.0”, at which point the installation starts to look and feel a lot like a regular Windows 3.x installation, minus things like settings panels and a bunch of default applications. Is this useful? Probably not, but who cares – it’s an awesome trick, and that alone makes it a worthwhile effort.

The PDP-10 family of computers (under different names) was manufactured by Digital Equipment Corporation between 1964 and 1983. Designed for time-sharing, batch and real-time systems, these computers were popular with universities, scientific companies and time-sharing bureaux. Several operating systems were available, some from DEC and some built by its users. It had a large influence on operating system design, artificial intelligence (especially at MIT and Stanford), programming languages (LISP, ML), applications (TeX, Emacs), online communication (ARPANET, Compuserve), games (Advent, Zork) and even helped development of Microsoft’s first version of BASIC. ↫ Rupert Lane The importance, impact, and legacy of the PDP series of computers cannot be understated, running like a red thread through the early days and development of several important and crucial technologies. Lane is going to cover a number of the operating systems created for the PDP-10, so if you’re interested – keep a bookmark.

Are you an author writing HTML? Just so we’re clear: Not XHTML. HTML. Without the X. If you are, repeat after me, because apparently this bears repeating (after the title): You are not required to close your <p>, <li>, <img>, or <br> tags in HTML. ↫ Daniel Tan Back when I still had to write OSNews’ stories in plain HTML – yes, that’s what we did for a very long time – I always properly closed my tags. I did so because I thought you had to, but also because I think it looks nicer, adds a ton of clarity, and makes it easier to go back later and make any possible changes or fix errors. It definitely added to the workload, which was especially annoying when dealing with really long, detailed articles, but the end result was worth it. I haven’t had to write in plain HTML for ages now, since OSNews switched to WordPress and thus uses a proper WYSIWYG editor, so I haven’t thought about closing HTML tags in a long time – until I stumbled upon this article. I vaguely remember I would “fix” other people’s HTML in our backend by adding closing tags, and now I feel a little bit silly for doing so since apparently it wasn’t technically necessary at all. Luckily, it’s also not wrong to close your tags, and I stick by my readability arguments. Sometimes it’s easy to forget just how old HTML has become, and how mangled it’s become over the years.