stewie410

Maybe including something like Windows’ OOBE; rather than defining a user before installing?

My last svn interaction was last week – boss is committed to sticking with subversion until the end of time.

This may also come down to hardware support generally; we ran into an issue upgrading an OS from CentOS 7 to Rocky 9; where RH had dropped support for our hardware during the RHEL 8 releases.

Debian, on the other hand, still had drivers available.

It was fun enough to play through early into EA; though once I started to scale up for a MAM, the performance became untenable… Though, that’s what you get for EA I guess.

Guess I was a little confused; at least their repo, change log and project website still point to Mozilla (in droidify, anyway).

Isn’t fennec maintained by Mozilla, though?

I no longer have access to a Samsung device, but found an old reddit thread recommending “Smart Switch to PC”. At a minimum, may make it possible to convert the tags to exif tags directly?

Might be worth a shot, anyway.

TBF, your previous post reads to me the opposite way

I was concerned with this, but seems my attempt to not sound like a KF supporter was unsuccessful.

It’s also not lost on me that I’m probably being pedantic.

I’m saying classifying it just as “hate” isn’t doing justice to what KF is. I would probably classify Xwitter generally as a “hate” site (these days, anyway); but KF is much worse. In a similar vein, I always wouldn’t say 4chan is a “hate” site, as that doesn’t quite cover it.

From my admittedly third person perspective, I wouldn’t classify it a “hate site”. A “lolcow” (or who they classify) tracking/doxxing hub, sure. Completely unhinged, sure, but I dunno if I’d consider it a “hate site” specifically…I’d also saying writing it off as just hateful really doesn’t do it justice, for how bad it really is.

If anyone’s interested in a broad overview of the history/point of KF, I’d recommend reading the first paragraph of Section 2.

My partner is a mechanic and is often underneath a vehicle when a notification comes through; so for him, the watch acts like an extension of his phone that he doesn’t have to worry about falling out of his pocket.

And while he does have to worry about damaging the watch, this would still be true if it was a phone in his pocket; but would just be more surface area to get knocked into things.

Personally, I work at a desk all day; so outside of a few phone calls a month, I probably don’t even need a phone…

deleted by creator

They’re expensive, but I’ve been using Mous cases on my last couple of phones, including my Pixel 7.

At work we’re using Bitwarden for the group benefits; though I still have KeePassXC running to simplify SSH keys (Windows, naturally) for native & PuTTY.

Personally, I use KeePassXC & KeePass android (currently); and sync’d through GDrive; which is good enough for my needs.

As @leetnewb@beehaw.org mentioned, I’m not sure either is what you’re necessarily looking for.

Yeah, I know, “RTFM.”

Sorry, I didn’t mean to come across in a condescending way, if that’s how it read. I’ve only ever used rclone for Google Drive, and its been quite a while since I’ve personally set it up, as I no longer daily-drive linux (outside of WSL).

A “remote” presumably means a remote folder/share/whatever in the cloud, in this case on Proton Drive, yes?

Yes, following the documentation, you would run rclone config, then answer as follows:

• Create/Edit/Quit: n
• Name: proton
• Storage: protondrive
• User: username@protonmail.com
• Password: y to enter your password; then enter your password twice as prompted
• 2FA: If you have 2FA configured, enter the 6-digit OTP; else press <Enter> to skip
• Keep this “proton” remote?: y

This should create a proton-drive remote called “proton”, which you can reference in further rclone commands. For example:

# Check if out of sync
rclone check 'proton:' ~/proton 2>&1 | grep --quiet ' ERROR :'

# Sync local/remote
rclone sync 'proton:' ~/proton

If I want to set Rclone to automaticlly sync, say, my home folder to Proton Drive, Rclone has to run as a service on startup for this to work.

In the past, I wrote a script to handle the check/sync job, and scheduled it to run with crontab, as it was easier for me to work with. Here’s an example of the script to run rclone using the proton: remote defined above:

#!/usr/bin/env bash

# Ensure connected to the internet
ping -c 1 8.8.8.8 |& grep --quiet --ignore-case "unreachable" && exit 0

# If in-sync, skip sync procedure
rclone check 'proton:' "${HOME}" |& grep --quiet ' ERROR :' || exit 0

# Run sync operation
rclone --quiet sync 'proton:' "${HOME}"

If scheduling with crontab, running crontab -e will open your user’s schedule in the $VISUAL, $EDITOR or /usr/bin/editor text editor. Here, you could enter something like

0,30 * * * * /home/your_user_name/proton_sync.sh

Which would try to sync once every 30 minutes (crontab-guru).

you can use systemd to set up rclone as a system or user service

This is also an option, assuming your system is using systemd; which most distributions have moved to – you typically have to go out of your way to avoid it. I also don’t have much experience in writing my own service/timer files; but it looks like systemd-run may have you covered as well (source):

# Run every 30 minutes
systemd-run --user --on-calendar '*:0/30' /home/your_user_name/proton-sync.sh

While I know writing config files and working with the terminal can be intimidating (it was for me in the beginning, anyway); I’d really recommend against running random ‘scripts’ you find online unless you either 100% trust the source, or can read/understand what they are doing. I have personally been caught-out recently from a trusted source doing jank shit in their scripts, which I didn’t notice until reading through them…and Linux Admin/DevOps is my day job…

Looks like they have an official tutorial.

I’ve also heard good things about bitwig, though it’s not FOSS, annoyingly.

We’re primarily a CentOS (6/7, kill me) and Rocky 8+ shop at work, with Debian handling our webservers. My Boss We like Rocky so much, it’s even our base image for all of our containers (ugh).

My experience so far is that RHEL (and derivatives) are pretty solid, and not a bad choice. Though, I’d generally want to avoid the complexity that is SELinux in selfhost endeavors.

Make sure you dye your hair a fun color when you get to a comfy point with Rust, that way people know you’re a serious Rust dev (/s).