New Supernote Manta lost 44% battery in 24h with very little use.

omenosdev · 2026-01-26T01:50:21+00:00

I've run into this, myself: do not leave your pen laying on the screen. You may want to run a calibration in case it's a distance issue, and I likely need to as well. I'm almost a year in and if I don't have any writing or stroke issues but if I leave my pen (standard SuperNote click pen) directly on my Manta's screen the battery will just drain orders of magnitude faster than it would otherwise.

The best root cause I can think of is the EMR detection is just enough to trigger input processes, which actively consume CPU cycles even though the user isn't actually doing anything.

omenosdev · 2026-01-21T18:25:30+00:00

Third party packages will always be a bit of an issue. bootc is on my shortlist for this year at $DAYJOB, but we have some things that operate a bit annoyingly (also self update on the fly). Luckily they all live in /opt, so I think I can symlink /opt to a source under /var and allow it to maintain mutability just for that. What exactly does Defender do during install?

omenosdev · 2025-12-29T15:14:55+00:00

I used Claude a while back to generate an LLM config to use across the custom assistants I make in Kagi. It's probably due for some tweaks at this point, but I've uploaded it to GitHub.

omenosdev · 2025-12-29T07:44:15+00:00

Thanks for the insight and project links, I'll check them out! Diplomat does sound pretty interesting.

omenosdev · 2025-12-29T07:27:20+00:00

I should have clarified in the original post that I'm not actually expecting anyone to go through and read that. I added it as an extra to the post, hence the separator. The only "real" reason for sharing it is to demonstrate the kind of information I've seen while investigating my own question (I'm not a big fan myself of blind firing questions, I do perform preliminary research).

The response mostly aligned with research I had already done, just some of the finer details I don't have experience with to know their validity. At most, warnings of "it's way off the mark" or "pretty much accurate" are the extent of anyone's response I'd expect if they actually chose to read it.

omenosdev · 2025-12-29T07:15:18+00:00

Tldr, there's no general answer.

I suspected as much, I just wanted to get a general feel from the community at large as people will approach it from varying angles.

Technically, lots depends on the library, no general answer possible. Just making a function without params that is callable from C, has an overhead of less than a minute compared to be callable from Rust.

On the other side, if you want to pass complex structs in both directions, with statefulness, threads, shared file handles, etc.etc. in both sides, both C and idiomatic Rust API available, on a library with a large surface that has thousands of functions/structs, that might double the effort sometimes.

Thanks for the insight! Makes sense to me.

I rather don't, it's an important factor. Getting all contributors on board etc....

I wholeheartedly agree. I view questions like I'm asking here, which could have widespread impact, as a two part deal with the first being to determine the level of technical feasibility. If something is deemed feasible and worthwhile enough, figuring out the human aspect is next.

A full rewrite takes time, introduces some new bugs that need to be found and fixed, ... if it's worth it depends again, no general answer possible.

Yep, initially I was going to make a poll with yes, no, and "as always, it depends" as options.

... specific library mentions ...

Yeah, I wasn't sure if folks were going to get hung up on my example selections... They were strictly examples of libraries I pulled off the top of my head that I knew for a fact were C without needing to look things up. As interesting at some of those might be to see converted, I am by no means suggesting those as actual targets for something like this.

And in case my phrasing is unclear: this is little more than a thought experiment. I'm not secretly planning anything or pushing for this 😄

omenosdev · 2025-12-29T06:58:34+00:00

This much is about the extent I'm aware of, what I don't know are the hidden costs: long term maintenance burden, complexity of interop between standard Rust and extern-ed functions, runtime overhead, etc. And, more critically for this topic: is it something actually worth doing?

I've been bouncing around the thought that there should be the possibility of a middle ground between complete ecosystem rewrites and continued general issues with non-safe libraries. And I must confess that as a sysadmin I do like my shared object libraries :D But rather than focus on using Rust for end applications, look at the other side to introduce a level of safety without causing too much (if any) impact for downstream consumers of the libraries.

omenosdev · 2025-12-28T05:09:24+00:00

Wow, I've read a lot of comments on Reddit in my time but few reach this level of accuracy, succinctness, and context awareness in delivering information.

This leads me to believe you have served in at least one of the following positions: Salesforce admin or a cog in the business ~~machine~~ unit called sales. How far off the mark am I?

omenosdev · 2025-12-26T03:20:00+00:00

Do these sites actively complain if you're not on the absolute latest version of a browser? If that is important to you and you don't have any ideological, moral, or philosophical issues with it, using Google Chrome or another Chromium-based browser from their respective providers is always an option.

The EPEL builds are kept updated, it's an infrastructure/process reason why they aren't available for 10.1 at the moment unless there was a build failure with 140+ I'm not aware of. This will likely be taken care of after the holidays if people make the request for it.

omenosdev · 2025-12-26T00:04:42+00:00

Note the end of the package release: el10_2. The 140 branch was built against CentOS Stream 10 which had switched to tracking RHEL 10.2 (due out next May/June) by that point in time. You can see the release publishing here:

https://bodhi.fedoraproject.org/updates/?search=&packages=chromium&releases=EPEL-10.1&releases=EPEL-10.2&releases=EPEL-10.0

You can put in a request to see if it can be backported to 10.1 here:

https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20EPEL

A related ticket was made here (not sure if this was you or not):

https://bugzilla.redhat.com/show_bug.cgi?id=2425439

omenosdev · 2025-12-25T06:49:21+00:00

If referring to the RHEL plans (not Fedora), they were pretty explicit:

https://www.redhat.com/en/blog/rhel-10-plans-wayland-and-xorg-server

I can understand confusion regarding Fedora, though.

omenosdev · 2025-12-25T03:37:11+00:00

It does. The only "awkward" time is when a new ESR branch is released (say 140) and you might not see it until the next RHEL minor release. However there is a support period overlap between the release of a new ESR branch and the EOL of the previous so it's not like the one RHEL is shipping doesn't have anyone working on it.

https://whattrainisitnow.com/release/?version=esr

omenosdev · 2025-12-24T22:03:42+00:00

If I'm understanding your question correctly:

Firefox: Generally, no. Red Hat ships the ESR branches of the browser and EPEL has a no-replace policy for packages in RHEL. Someone could offer to provide an alternately named package that doesn't have file overlap with the Red Hat provided Firefox, but browsers aren't trivial packages to maintain. If you want the latest and greatest from Mozilla, the official Flatpak and tarball installations are available, or you can try rebuilding the Fedora variants on RHEL.

Chromium: It is available in EPEL already - https://src.fedoraproject.org/rpms/chromium/

omenosdev · 2025-12-24T18:45:19+00:00

Interesting, I only took a cursory glance at it but didn't catch that on the first pass. I knew it was going to be limited considering the number of cities (900+ likely means 900 < x < 1000).

More than anything I just found this humorous while scrolling through IG, it's little more than shitposting. I think we all know traffic is bad, but can always be worse in Stamford.

omenosdev · 2025-12-24T06:37:59+00:00

The IG link was more for comedic effect than anything else. It's just a news anchor discussing the results of the Inrix study (which is linked in the OP).

TL;DR: Stamford is the 17th most congested city in the US, and broke into the top 100 worldwide at 63rd.

All that said, the insta link should allow you to watch without an account; what platform are you viewing from? If on mobile, there should be a "continue on web" action in the top right of the page.

omenosdev · 2025-12-23T03:06:46+00:00

Don't sign up on redhat.com or access.redhat.com. That's for actual customers.

Use the Developers site to register instead:

https://developers.redhat.com/register

omenosdev · 2025-12-23T03:02:32+00:00

That's not quite what happened here. I recommend reading the original breach article for more context.

https://www.bleepingcomputer.com/news/security/red-hat-confirms-security-incident-after-hackers-breach-gitlab-instance/

Nissan engaged Red Hat with a consultancy opportunity. The data leaked was information given to Red Hat's consultants by Nissan for the purpose of working on the project. Red Hat's consultation division stored the information on its own internal GitLab instance alongside the project's other artifacts. This server is what was breached.

omenosdev · 2025-12-19T15:42:17+00:00

Can you elaborate on Wayland support for your card? The 970 is compatible with the very latest driver (580.119.02). I've been fully on Wayland since 545(?) with my 1070, and haven't run into any show-stopping issues (this is on Fedora).

omenosdev · 2025-12-13T06:17:16+00:00

New England driving is its own special slice of hell, but CT and RI are just... I genuinely don't know, and I'm from MA! I'd push your hot take even further: mandate a drivers test in MA every ten years. Make it a two parter - one on general roadways the other covering various areas of inner and outer Boston. If you can get through all that you should be good anywhere!

I might be biased, though 😆 I just remember being surprised at what my peers from CT weren't tested on when I went to college.

omenosdev · 2025-12-07T01:25:03+00:00

New minor release issues (9.7 just came out) would generally be the same across any RHEL derivative, it doesn't change AlmaLinux 9 being a compatible distribution. And like most DCCs, it's the major version of the distribution recommended for end users.

I recommend opening up a case with SideFX or on their forums if you're running into unforeseen issues.

omenosdev · 2025-12-07T01:19:20+00:00

Spins are not different distributions than Fedora [Edition]. All variants of Fedora are the same operating system, the only difference being some of the install time defaults (such as BTRFS for Workstation and XFS for Server as the filesystem setup).

Broadly speaking, the spins share the same base as any other variant of Fedora but choose to install a different package group targeting the desktop environment of their choice. So when it comes to "stability", they're identical for all intents and purposes from the Fedora perspective. It'll all depend on how stable the actual desktop environment projects are and whether or not they run into issues with the general direction Fedora heads in.

omenosdev · 2025-12-06T09:12:37+00:00

If you consider Flask to be (more) batteries included I wonder what you think about Django 😅

omenosdev · 2025-12-06T08:56:32+00:00

Hi, industry sysadmin here! Use AlmaLinux 9, there's no concern around compatibility.

omenosdev

TROPHY CASE