Any naming convention is fine as long as it’s meaningful to you. But it’s a good idea to keep your own repos separate from the random ones you clone from the internet.

What I see is an inexperienced developer who instead of systematically debugging the issue keeps trying random stuff hoping that it will somehow work.

Roguelikes: DCSS, Shattered Pixel Dungeon, Nethack

Costs a lot less than therapy too.

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!

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.

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.

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

After typing in a bunch of programs on my 1KB Sinclair ZX-81 I wanted to understand how they worked and wanted to make some of my own.

Maybe other tools support this too but one thing I like about xdiskusage is that you can pipe regular du output into it. That means that I can run du on some remote host that doesn’t have anything fancy installed, scp it back to my desktop and analyze it there. I can also pre-process the du output before feeding it into xdiskusage.

I also often work with textual du output directly, just sorting it by size is very often all I need to see.

Looking at the code it seems to be getting the feed from the mastodon.social instance’s federated timeline. So it’s definitely not streaming “the fediverse” but a decent chunk of it.

I am on Gentoo. It’s not really a goal for me to stick with it, I am pretty pragmatic about these choices. What I value about Gentoo is the flexibility and the lack of magic. The ability to fully own and understand my system. I know what’s installed, what’s running and why. It’s up to me if I want to use systemd or something else, do I want pulseaudio, pipewire or just plain ALSA, X11 or Wayland, what type of desktop environment to use (if any). I can easily apply local patches if needed, I can build a package from git or stick to some old version if I prefer. I know how I want things to work and Gentoo lets me get there. If I found a better way to do it I’d switch. Maybe something like NixOS someday but I am not ready for those trade-offs yet.

The reason I’ve been maintaining the same image for so long is that I didn’t have a reason to rebuild it. I’ve always been able to make the changes I needed. I re-did the image when going from 32 to 64 bit because it was less work.

That’s something that beginners do to entertain themselves. My desktop image has been rolling forward since 2013 (when I switched to 64 bit userspace) and it has survived through several generations of hardware.

The last paragraph notes this is not X11 specific, Wayland is affected too it’s just that a bug prevents it from working when the FF window is not focused.

The comment was talking about dired which is a file manager that runs inside Emacs and Emacs can be used in terminal mode.