What board/connector is affected? At worst, a replacement connector and a soldering iron should be able to replace the damaged connector and get your printer in a functional state.
UPDATE: if you are referring to certain mainboard connectors, it may be best to replace the mainboard if you don't have the tools for replacement. I see surface-mount connectors for some things on the mainboard that can be difficult to replace correctly without more unique tools.
Systemd is both in a lot more large distros than just Fedora, RHEL and has limited viable alternatives (OpenRC as a partial replacement, no others I can think of that come close). While it has its issues particularly with the extra bundled services of mixed quality, SystemD is generally a flexible and suitable option for service management on Linux.
Not to mention how inflammatory the parent comment is.
NMap through a terminal emulator like Termux?
GrapheneOS only publishes updates for devices with active security updates. Your device is EOL and therefore won't receive any further mainline updates. It still will receive extended support from the Android 14 legacy branch with whatever security patches arrive in upstream AOSP, but unlikely to see device-specific patches nor firmware patches. Your device isn't getting the same care and attention that active devices are receiving nor will it receive any future versions of Android through GrapheneOS.
The last update to the game destroyed the usability of its positional audio among other things. The developers have remained silent on all channels beside their Discord about future game updates or content. The game hasn't been updated for about a year now.
Additionally, ome people have complained about getting banned from the in-game chat for allegedly "no reason". No idea if even half of these people are being truthful or were actually banned for things like saying racial slurs.
Before buying anything to supplement your hotspot, it may be worth checking to see if your issues are even caused by poor signal strength. Depending on the cause, buying better antennae or a signal booster relay may not provide any tangible benefit. As you say you live in a rural area, your issues may be unsolvable by different hardware as your device may be throttled by your carrier instead.
I ended up using CADQuery to fully recreate the project I was working on in Ondsel, and actually finish the project. Overall, I think this choice will be the software I run with for CAD projects going forward. Updating main post to explain my decision shortly.
I did a bit of digging into the feature search for OpenSCAD. I noticed things like bezier curves, lofted surfaces aren't native functions in OpenSCAD, but individual users have made helper libraries for defining such surface features. Is there a shortlist or general repository for premade helper libraries for use with OpenSCAD?
For what it's worth, I do think OCIS is worthy of switching to if you don't make use of all of the various apps Nextcloud can do. OCIS can hook into an online office provider, but doesn't do much more than just the cloud storage as of right now.
That said, the cloud storage and UX performance is night and day between Nextcloud/Owncloud and OCIS. If you're using a S3 provider as a storage backend, then you only need to ensure backups for the S3 objects and the small metadata volume the OCIS container needs in order to ensure file integrity.
Another thing to note about OCIS: it provides no at-rest encryption module unlike Nextcloud. If that's important to your use case, either stick with Nextcloud or you will need to figure out how to roll your own.
I know that OCIS does intend to bring more features into the stack eventually (CalDAV, CardDAV, etc.). As it stands currently though, OCIS isn't a behemoth that Nextcloud/Owncloud are, and the architecture, maintenance is more straightforward overall.
As for open-source: OCIS released and has still remained under Apache 2.0 for its entire lifespan thus far. If you don't trust Owncloud over the drama that created Nextcloud, then I guess remain wary? Otherwise OCIS looks fine to use.
Persistent keep alive is configured per connection by all peers (server and client typically). As I understand it, Wireguard's peer-based architecture will let both client and server peers define an optional persistent keep alive timer in order to send heartbeat packets on interval. Otherwise Wireguard on either peer may keep opening and closing connections for inactivity (or get its connections forcefully closed externally) if traffic isn't being regularly sent. This can occur even though the network interfaces for Wireguard on both communicating peers remain up.
I do agree that running some kind of health-check handshake service over the Wireguard tunnel is an easy enough way to periodically check the state of the connection between peers.
Depending on how your connection is negotiated, it may partially not be possible due to the architecture of Wireguard. There is likely some way to hook into capturing handshakes between clients (initial handshake, key rotations). To determine disconnects and reconnects however is a challenge. There are no explicit states in the connection. The closest thing to disconnect monitoring is utilizing a keep alive timeout on the connections. There are some caveats to using a keep alive timer, however. Additionally, not every connection may use a keep alive timeout, making this a full solution infeasible.
Detailed information about Wireguard session handling can be found in section 6 of this PDF.
On my mobile Lemmy client (Eternity), I already keep a multicommunity group for finding tech support posts in case I have something to offer in response. As it stands with !linux@lemmy.ml, there aren't too many posts that are pure conjecture or information and thus doesn't really clog my feed. If this community grows to have more of these kinds of posts showing up, it may be worth having a split. As it stands currently though, I feel it would mostly serve to significantly lessen what gets posted to this community.