I haven’t powered it up in several years, but I keep an old Windows XP machine with my DAW software on it. I just always ran it offline and moved files with a thumb drive. That said, I never did try a native Linux solution.

Eh, my last Asus ran Linux fine. Though until Ubuntu 18.04 came out, I had to patch the i2c driver and recompile the kernel in order to make the touchpad work lol.

windows subsystem for Linux to work in my windows VM on my Linux machine.

Ignoring the blasphemy of that, the fact it doesn’t work may prove that we are, indeed, living in a simulated universe. lol

but I have a tendency to jump into a new game for like 3 weeks and then off to the next like the horrid ADHD having fuck that I am

That’s basically why I stopped gaming. Have saved so much money from not filling up my Steam library with games I’ll never finish. lol

Yeah I’m not as much of a fan of PopOS as I thought I’d be. I have it on my daily driver laptop, and every system update seems to introduce some wacky bug/glitch or another. Nothing major, just random small annoyances that usually get fixed in the next update.

It dual boots Pop and Debian, and Debian performs flawlessly. It’s a Thinkpad, so Linux support has always been fantastic. I’m thinking of just dropping the PopOS partition and going back to my original love, Debian.

I almost went back to Mint on my last rebuild, but ended up going with Debian + Cinnamon. So far so good.

Unless you run some really niche software or are a heavy gamer, you’ll likely have no problems and enjoy it. Most software that you need for daily use has a FOSS equivalent that’s equal or better. Usually those are also available straight from the package manager (if not there, then most likely Flatpak).

Just stick with a well supported distro like Fedora, Ubuntu, Debian, or PopOS, and it’ll be super easy.

I’m actually looking forward to the perfectly good Linux boxes that are bound to be popping up at yard sales or on ebay once that happens.

I stopped Lemmy to run it, but that was because I had already stopped it to take a full backup first. I was also removing a very large, active community. I don’t think it was necessary, and I’ve removed other communities with Lemmy running. Just see the caveat about restarting Lemmy to make sure it “forgets” the community.

The triggers will only be disabled for the run of that script in that session. So you don’t have to worry about turning them back on because they were never turned off for any other DB sessions.

I wrote this guide for doing it through the DB. It may not work if you’ve already removed the communities and they got re-created with a different id in the DB, though.

https://dubvee.org/post/64240

🤦‍♂️ Yep. Updated comment.

Got nothing to suggest but just wanted to call out that you’re an awesome dad parent.

The last few updates to nextcloud and PHP 8 have drastically improved performance for me. I’m not using the Mail app but SnappyMail, and everything works pretty well.

Older versions and PHP < 8 were pretty slow even with all of the optimizations.

I haven’t but I definitely should. Just refreshed my laptop with pop os and have been using the default mail client with it (Geary?). It is really responsive and works well with the tiling plugin.

Same for me. I’m a die-hard Thunderbird fan (it’s ugly but it works lol).

Used to use TB at work until we switched to Google Workspace and they globally disabled IMAP access. Now I’m stuck with webmail and my productivity went to absolute shit.

I use SnappyMail which is a fork of Rainloop. It works great, has a version available for Nextcloud, AND it has a working sieve editor.

Will that work for US split-phase “220” where the voltage is 110v on each leg? I was always worried that would fry the PSU since it’s not true 220V.

One thing I didn’t mention, the registration applications page was empty, but after both admin and non-admin users are verified, I’m able to see and approve the applications.

That’s correct. The applications won’t show up there until the email is verified (if verification is enabled). I guess it’s a deliberate choice by the devs as a spam prevention method.

The queue probably got cleared when the postfix container was recreated as it’s spool directories weren’t attached to a persistent volume .

Probably the easiest would be to manually set email_verified to true in the local_user table for those users (basically assume the email addresses were correct).

I don’t think there’s a way to re-trigger the email verification without going through the sign-up process, so your option #3 is likely what you’ll need to do.

You could do one of the following if you don’t want to blanket-allow the existing signups:

Option 1: Go into the email_verification table and get the email and local user ID to look up the account and send the verification token manually to them using the email account you configured with Lemmy:

Subject:  Verify your email address for {your-domain}

Please click the link below to verify your email address for the account @{username@your-domain}. Ignore this email if the account isn't yours.

, [Verify your email](https://{your-lemmy-domain}/verify_email/{verification_token})

Option 2: Note the username and email address from the local_user and person tables, delete those, and recreate the accounts for them. They’ll have to reset their passwords since you’ll have to set one on their behalf, but that should be manageable. Just make sure the password you set for them is completely random, complex, and very long (not sure if the length is still 60 characters or not).

Option 3: Delete the records as in option 2 but send them an out-of-band email from your Lemmy address saying they’ll need to re-register.

Let’s see what all my bullshit detector finds on just the title and description alone:

1. Telling me I need what they’re pitching: ✔
2. Mentioning that it’s free: ✔
3. “Free” is in all caps: ✔
4. Free money? ✔

Gonna go ahead and pass on whatever that is.

Just to confirm, is the -o eth0 in the second command essentially the interface where all the traffic is coming in?

That is the interface the masqueraded traffic should exit.