People still play this game. Spoilers still spoil experiences for others.
2,097 karma · joined April 22, 2018
Would you please edit your comment, and preface it with a spoiler warning?
I wonder how many players today will resist those temptations now that they're not only trivial to discover and execute, but also widely accepted in gaming culture.
I urge new players to resist spoilers and cheats for as long as they can. This game is full of wonderful details and interactions that are not at all obvious, and they make it exceptionally rewarding to progress when you do so by discovering them on your own.
Of course, my recommended approach will mean dying a lot. If you keep a journal of things you do and notice in each play-through, your eulogy will be more useful. :)
Take heart: Starting over means you're likely to encounter new things in the levels you've seen before, so it won't be boring.
...
*I don't recall why the save files seemed elusive back then. Perhaps the system on which I played put them someplace obscure that I lacked either the motivation or the knowledge to find. Or perhaps they were kept out of reach of the player by unix permissions, requiring setuid for the game to read them. Either way, I'm glad, because the challenge and mystery of playing with only what the game provided made it all the more interesting.
That was about seventeen years ago. I still have the save file. Today's announcement got me excited about the prospect of finally finishing my game, until I saw this:
> Existing saved games and bones files will not work with NetHack 5.0.0.
Drat.
Thankfully, NetHack is not one of those modern, commercial, online-only games that make it difficult to run old versions.
** SPOILER BELOW ** (in someone's reply to me)
https://automotivevehicletesting.com/vehicle-diagnostics/doi...
You seem to be referring to a particular set of binary-focused servers. I am referring to the protocol and network design, as an example of a federated system offering resilience.
(Also, I think your numbers are wrong, but I won't quibble about those because it's the network that's relevant to this thread, not the way some people happen to be using it today.)
> Matrix isn't.
It is. Blocking or shutting down any node in the network only affects that node. Others carry on without it. Another example of a federated system offering resilience.
Usenet and Matrix are notable examples.
Their guide:
https://www.eff.org/files/2026/04/09/condensed-age_verificat...
Unfortunately, their most prominent call to action doesn't seem to address the various state-specific and non-US legislation (focusing on KOSA instead). Here it is:
Beyond that, maybe resilience when a project's host disappears, changes its policies, or gets blocked by a government?
https://zed.dev/blog/videogame#text-rendering
It looks like their approach could nicely solve a problem that's shared by almost every new GUI toolkit I've tried: text looks terrible, or at least out of place when surrounded by applications built with the desktop's native toolkit.
In case you find it useful, I recently stumbled upon this project:
https://github.com/longbridge/gpui-component
"UI components for building fantastic desktop applications using GPUI."
- frequently needed navigation links buried within menus within other menus
- menus labeled by mysterious icons, sometimes with mysterious text, sometimes with no text at all
- authentication system that has failed me in a variety of ways over the years, even locking me out of an account in one case
- client-side script execution required to do anything all, even simply display a file
As I said, I haven't kept a list, but GitLab is very much in the category of interfaces that were built by javascript fanatics who don't understand (or don't care about) ergonomics or privacy. I accept that not everyone is bothered by its many problems, but I avoid it when I can.
Reminds me of IPv6. ;)
Let's also remember that it's infinitely easier to keep a native app operational, since there's no web server to set up or maintain.
With the compiler flags I tried, binary size was close to that of Gova:
https://github.com/mappu/miqt/issues/147#issuecomment-280033...
Qt bindings for Zig, using the same approach as MIQT:
MX Linux also looks interesting. Like Ubuntu, it's a Debian derivative. It offers a supported path for avoiding systemd and has an official KDE Plasma edition, both of which appeal to me. I haven't had a chance to try it yet.
2. Install the kernel from Backports.
I don't think of such a simple process as "fiddling", but to each his own I guess.
If you want more detail, you should ask someone who still uses Gtk-based desktops, or try them yourself. I gave up on Gtk a couple years ago.
Linux Mint is widely praised for being basically Ubuntu without the worst Canonicalisms (such as Snap). They maintain a Debian edition in parallel to their main one, as an exit strategy in case Ubuntu ever becomes unsuitable for their base. Some people already use that as their daily driver.
Just in case you're not aware, the default desktop environment on whatever distro you pick doesn't have to be what you use. I switched to KDE Plasma when Gtk-based desktops became intolerable, and haven't looked back.
If you've pulled in a dependency from outside the base image, there will be no new base image version to alert you to an update of that external dependency. Unless your container regularly runs something like apt update && apt list --upgradable, you will be unaware of security fixes newly available from apt.
Sadly, the purchase would still reward the company for making a spyware screen, and signal that I find it acceptable, which is why I plan to avoid them forever.
What a bizarre leap of logic.
I wonder what disparaging others for using profanity indicates.
One of the things I like about Hacker News is that it provides some exposure of this kind. The SNR in any given post might not always be high, but the tangential discussions often lead to topics just as interesting, expanding my awareness of what I don't know. There are lots of rabbit holes to explore here.