I make tons of aliases. For instance my quick “got log” and “git log <branch[SS]>”:

alias gl="git log --graph --abbrev-commit --no-decorate --date=format:'%Y-%m-%d %H:%M:%S' --format=format:'%C(8)%>|(16)%h  %C(7)%ad  %C(8)%<(16,trunc)%an  %C(auto)%d %>|(1)%s' --all"
alias glb="git log --graph --abbrev-commit --no-decorate --date=format:'%Y-%m-%d %H:%M:%S' --format=format:'%C(8)%>|(16)%h  %C(7)%ad  %C(8)%<(16,trunc)%an  %C(auto)%d %>|(1)%s'"

For me, the pinned issue keeps me from using it: https://github.com/vogler/free-games-claimer/issues/183

And for GOG you can have something refresh a link daily and it grabs whatever is there.

I’m all for GIMP, but logos should be raster for sizing and SVG use, Inkscape only please 😉

I just made the switch for a few reasons.

For background, I was a Lifetime Plex Pass user since it launched, created the POC exploit for token theft (a couple of months before they implemented SSL), and built a clustering/sync application (a few months before they released sync, patterns much?).

I did not think Jellyfin was up to task a few years ago. It is now. All the missing features like themed visuals and audio, chapters, thumbnails on seek, all exist now.

Why I switched:

• API: I have scripts that do different things with different media and they were super easy to recreate with the API. An example would be moving ytdlp videos from my Youtube Watch Later folder to a deletion folder if they’ve been watched.
• LDAP: I now have user control via my Samba AD.
• Privacy: I never wanted my media list stored with a third party to begin with.
• Plugins: I have a library I tag with filenames, like ==Tag--Tag==filename.ext. It took me a half day to make a Jellyfin plugin that converts these to Genres. It was a nightmare of DB hacking to do it in Plex. Not to mention there are waaaay more existing plugins that are supported. Jellyfin is where this happens now, not Plex.
• Fine grain control: Transcoding settings, bandwidth settings, etc are are open and transparent.

A lot of people commenting on this seem to have gaps in their knowledge of what happened. I highly recommend reading the linked email, as it is both short and has valuable context.

Thanks! Yea, it was a really fun project to make back before there were any real options. And I’m glad the PiKVM team could expand upon it.

Somewhere along the way I lost the “based on” credit, likely whenever they fully modernized the stack. I wasn’t really keeping track, but did find it humorous when LTT said the creator complained someone based another project on them. I was like “Hmmmmmmm…” but just laughed because I didn’t make it for it to stagnate like it had been with me.

Yup, I use PiKVM, too. Fun fact, PiKVM’s first content commit is a clone of my DIY IPMI repo 😉

Look, it’s’a me: https://github.com/pikvm/pikvm/commit/70eebd5c59da26dc3f6ad56730adbb616055f4e5#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R4

This is why IPMI is so important.

Whew, this is why I pin on sha256. I fear for the latest crowd.

Edit: At least it seems updating the container doesn’t break things:

Replacing any v5 image (2024.07.0 and earlier) with a v6 image will result in updated configuration files. These changes are irreversible.

At the end of the day, they are just digital things. You had some great learning experiences with them. Now it’s time to put those skills to use, and learn what’s next that makes you happy.

Yea other commenters don’t seem to be making that “top” connection. This project is fantastic, thanks!

This is for the feed. OPs project is for “top”, leveraging the up vote alg.

Is this a Thinkpad? And of so, is the BIOS s3 on “Linux” or “Windows and Linux”?

Also are you running Wayland? If so ot might be worth trying to log in with Xorg instead (bottom right when logging in).

Oops, just me misreading.

Glad that worked out for you 😉 What is Gnome doing exactly?

What kind of issues, and which trackpad driver?

Had not realized this, thanks!

Will have to look into this, thanks!

Could be internal to kernel? Try updating /etc/default/grub to include: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash atkbd.reset" and run sudo update-grub. This will cause a full keyboard reset on resume.

If you have not run BIOS updates, that could be it, too.

Great idea. My poor mans version idea was an encrypted data set inside another encrypted data set to require two people, but Shamir’s seems like a much better option.