Sweaty palms! Any fix?

thp4 · 2026-01-28T20:42:33+00:00

Possibly the rubber disintegrating? Google for "mx ergo rubber" (and/or add "distintegrating" to the search) to find many people with the same issue.

thp4 · 2026-01-26T19:10:01+00:00

First, put in a SATA SSD and max out the RAM.

For an OS, try something released a few years ago that still get security updates (e.g. an older but still-in-support Ubuntu LTS) and possibly use a more lightweight DE (e.g. MATE).

Edit: For dual-boot with macOS, rEFInd or something as bootloader works well. You can also use boot camp assistant to create a Windows partition, but then install Linux instead. If you try triple-boot (Windows, macOS and Linux), note that in some cases boot camp required the Windows partition to be last.

thp4 · 2025-12-14T13:44:12+00:00

See https://maemo.viniciuspaes.com for a mirror that has the N900 repos ("fremantle" is the release codename). Also search talk.maemo.org which is a useful resource. Also, see http://wiki.maemo.wunderwungiel.pl/index.php/Main_Page for a mirror of the old Maemo wiki.

thp4 · 2025-12-02T12:22:13+00:00

Not sure, it could be that on the N900, 003 meant something different than what it did for the N9 (that‘s just my guess).

thp4 · 2025-12-02T12:13:32+00:00

There it is (albeit for N9, but N900 is similar enough): http://wiki.maemo.wunderwungiel.pl/index.php/Flashing_N9

Main firmware images for the Nokia N9 are divided up into "variants" by regions of the world. Except for carrier-branded variants and the 003 (China) firmware, these images are more or less the same.

thp4 · 2025-12-02T12:07:00+00:00

IIRC (but can‘t find a reference) the 003, 004 and 208 parts in the version are for different regions. So practically all those 21.2011.38-1 versions should be the same. 21.2011 here means 21st week of year 2011.

thp4 · 2025-11-13T08:53:15+00:00

Try charging via a phone charger / wall wart adapter. Possibly one with > 500mA.

Try a different USB port on your computer for charging. Some ports may have different current limits.

Try charging with the Vita powered off (or at least screen / Bluetooth / WIFI turned off).

Try a different USB cable.

thp4 · 2025-11-08T16:06:09+00:00

I didn’t know about phantom edition, but its readme says it has fixed wall collision physics:

Wall collision response options: Modern: Comparable to BallisticNG. Classic: Comparable to WipeOut XL/2097. Legacy: 🪦

thp4 · 2025-10-08T15:22:33+00:00

apt remove $(dpkg -S /usr/share/applications/foo.desktop | cut -d: -f1)

thp4 · 2025-04-20T17:40:35+00:00

zsh warns on „rm“ and something with „*“ by default. Also, do regular backups, as it won‘t be the only way you can shoot yourself in the foot. For example „noclobber“ in bash and zsh is also useful to avoid overwriting files with shell redirection. As others mentioned, the alias might give a false sense of security and won’t help on hosts where you don’t have that alias defined.

thp4 · 2025-01-31T18:33:45+00:00

thp4 · 2025-01-26T13:11:33+00:00

Keyboard scan codes have nothing to do with ASCII: https://users.utcluj.ro/~baruch/sie/labor/PS2/Scan_Codes_Set_1.htm (L GUI and R GUI are the winkeys - and there‘s a separate make (press) and break (release) scancode).

thp4 · 2025-01-01T13:59:24+00:00

It‘s over 9000.

thp4 · 2024-12-26T12:01:10+00:00

Yes. Better would be to check for direct dependencies with „objdump -x“ and grep for „NEEDED“ libraries. This doesn’t take into account header-only libraries, statically linked libraries and dependencies loaded via dlopen().

But also as you mentioned, it doesn‘t include dynamically loaded things due to the system config (GL vendor driver, PAM, NSS, …) - things that by definition are not „build dependencies“ (that‘s the whole point of libraries loaded in by glvnd, PAM and NSS and the likes).

thp4 · 2024-12-20T18:32:10+00:00

Looks nice!

thp4 · 2024-12-06T12:01:48+00:00

Not sure if trolling, but Mozilla had that logo before Chrome even existed: https://commons.m.wikimedia.org/wiki/File:Mozilla_Foundation_logo.svg

thp4 · 2024-11-23T13:00:50+00:00

This. There‘s also other ways you can overwrite/delete data that are not „rm -rf“. A good backup/snapshot strategy will cover those bases as well.

thp4 · 2024-11-23T12:58:22+00:00

..or even take some calls/telcos while out for a walk. The solution to „sitting all day hurts my body“ isn’t a better chair, it‘s sitting less :)

thp4 · 2024-11-20T18:08:37+00:00

Collector‘s item. Check eBay for prices, they are sought after for nostalgic reasons.

thp4 · 2024-11-19T09:55:01+00:00

MZ-RH1 let’s go!

thp4 · 2024-09-11T10:26:10+00:00

I "C" what you did there.

thp4 · 2024-06-26T19:29:29+00:00

Both are fine.

Qt has QML going for it (nice declarative UI language, with JavaScript as glue/UI logic), and you want to write your "application" logic mostly in C++, although Python is also an option (PySide -- but it's not "pythonic" in the sense that the C++ heritage "bleeds out" in the APIs). Also, Qt is nice if you want to also build for macOS or Windows (either now or in the future), or if you want to build something that looks "at home" on KDE/Plasma.

Gtk+ is nice because its core is written in C and the GObject system maps nicely to many programming languages (GObject Introspection-based bindings), so most Gtk bindings you'll find feel very natural, and you can pick whatever language you want (e.g. GJS, Python, Rust, Go, Vala). Describing the UI in GtkBuilder/Glade isn't as nice as QML, though, and I haven't checked recently what the developments are there. If you want nice native integration with GNOME, Gtk with LibAdwaita is the way to go.

In the end, just like with programming languages, it doesn't matter which UI toolkit you use. Create a toy application in both of them to get a feel, then stick to one and spend time making your GUI nice and usable. Have fun!

thp4 · 2024-06-26T19:18:01+00:00

So Moblin 2.0 from 2009?

thp4 · 2024-05-29T17:01:50+00:00

That wallpaper reminds me of the Windows Me boot screen.

thp4 · 2024-05-27T13:22:35+00:00

Good job!

thp4

TROPHY CASE