Yep, original is Java and uses libGDX. Slay the Spire is mentioned in the showcase.
Yep, original is Java and uses libGDX. Slay the Spire is mentioned in the showcase.
Roguelikes: DCSS, Shattered Pixel Dungeon, Nethack
For spot checks I just run sensors
or watch sensors
.
sar -m TEMP | grep amdgpu
when I want to see history (needs the sysstat cronjob configured to collect sensors data).
How visible is this to the average user? Just wondering because I have yet to see any spam at all in my Mastodon feeds. Big thanks to the admins for being on top of it!
Yep, that’s the only answer that makes sense to anybody who actually plays and likes roguelikes.
As a rule of thumb I like say that if it needs a pause button it’s a 'lite. This doesn’t come close to covering the criteria but it’s a good shortcut to weed out a lot of them.
If you care about privacy, which I understand, you probably want to leave quickly.
Just because you care about privacy it doesn’t mean that you have to stay indoors all the time. You can still hang around on the town square you just have to be conscious about what you do where.
A big part of caring about privacy is understanding how the platforms you use work and using them accordingly. With proprietary platforms this is often opaque and the rules can change. Open platforms are transparent and you can actually understand them - if you make the effort.
gotosocial might we worth checking out. It provides Mastodon-compatible APIs (so you can run Mastodon clients and UIs against it) but it’s less resource hungry and easier to deploy (in my experience). The caveat is that it’s less mature.
Subscribe to a post: just mention the bot in the comments.
Not a huge fan of the noise this adds to the threads. Would be nice if Lemmy frontends could provide better ways to interact with bots. For example custom buttons that would PM the bot with the appropriate message to trigger the action.
Imagine the person (or more likely a whole group) who has spent weeks designing and iterating over those arrows.
Interesting that they went with the possessed teletubby look.
Autotype is already solved - ydotool, wtype and dotool exists (and possibly others as well).
These tools work by creating a virtual keyboard so they don’t let you send input to a specific window. The input goes to whatever happens to be focused at the moment. This makes them less reliable than the X11 equivalents and unusable for tasks where you need to guarantee that the right window gets the input.
Those of us who use the autocd feature of shells “execute” directories all the time. For example I’d type just /usr/bin RET
if I wanted to cd to /usr/bin.
not having kludges 42 levels deep
There are already almost a hundred extension protocols and you need dozens of them to implement just barebones desktop functionality. If you look under the surface the Wayland ecosystem is arguably already more complex than X11 ever was and it’s only going to get worse.
There is a fairly compact Thinkpad USB keyboard which would be much easier to connect if you can make it fit somehow. It has the trackpoint but no trackpad.
Yeah, I ended up doing something similar but using my own Dockerfile where I specified ebook-convert
as the entry point.
Yep, I realized that as soon as I posted and tried to ninja-delete but too late :)
If I sum up the numbers from March 2022 it’s 26% AMD and 38% NVIDIA.
I would like the ability to do a CLI-only build since I only really use the ebook-convert
command. Never felt the need to “manage” my ebooks.
deleted by creator
If you have an email workflow that you like then something like rss2email might be an option. You simply feed your incoming rss into your email. You’ll want to auto-tag (or otherwise organize) these emails to keep them separate from regular emails. Then you use your usual email tools to organize them further.
I’ve been using such a setup for the past 15 years.