You have pictures of the surrounding location?

Water evaporates pretty quickly from the top soil, and everything below 1" should drain quickly for pepper plants.

If you have dense clay soil, it may be retaining water and keeping things wet. You need to mix it up with Soil Amendment every year between plantings to ensure you have well mixed and balanced soil.

Yup!

I’ve never seen this “just” happen, but have seen it during events like switching from headphones to speakers and such.

You may also have your app volumes linked to your master channels, meaning when you lower the sound on your master with something like a key combo, then it lowers the individual app volumes as well, which is generally not something you’d want enabled.

Apps at full, and using PCM/Master channel for general volume is pretty much the “default”.

Literally explained in the link.

Unless there is an above average drive controller on board, it wouldn’t be getting out into read-only and still accessible without triggering an error in online drive checks.

Check your drive: https://wiki.archlinux.org/title/S.M.A.R.T.

This is a cm2002 post, so most assuredly not their project, but some notes:

1. This thing is a hodgepodge of random things. Focus on one thing or maybe closely related things. Do it well.
2. This is a notes taking app. Why the fuck would you need “AI” bullshit?
3. This is a notes taking app. Why the fuck would it need to play YouTube videos?

Good

First time I’m hearing about them, but what was your draw?

Corn works pretty great for Crispy Tacos

This possibly belongs in @foodcrimes

Have to give it a try again. It wasn’t in great shape earlier this year.

Any type of distributed service, really. There are many, and there are tiers of service as well. Meshtastic is probably going to be the most useful in the Lora arena, since anything can be a repeater.

Dude is nominated for like 4 Grammy’s now. Crazy.

Pruning clears cached blobs and unlinked objects. It 100% will not clear history unless you’re forcing a specific depth to be achieved, which, again, is not something that people who want a functional repo would do.

Not entirely the point, but your skepticism is not unfounded by any means.

Mirroring is exactly that: a copy

If the thing you are mirroring does something you don’t like, you can’t stop. Literally imagine standing in front of a mirror and trying to stop the reflection from doing something you don’t like. Not happening.

The thing about git is that it keeps all history, even in a force push situation, unless they actively clear previous history, which is… difficult.

What you can do is lag proxy whatever the main branch is to catch it in time, or just keep revisions of your mirror that you script and tag yourself. It’s like a daily backup you can go back and look into.

It’s going to waste a ton of space and time, but it would effectively create a stop-loss on someone nuking history, which generally is just not a thing that people do because it’s entirely stupid.

I mean…it makes sense in some ways, but absolutely fails in others. This will be problematic to start for sure.

https://www.baeldung.com/cs/semantic-versioning

Jail time and civil penalties are available through suing, though the jail time would require a government entity to prosecute which clearly won’t happen in Texas or at the Federal level…right now. Nothing stopping this from happening in the future, and it can’t be pardoned away, though.

Gonna have to stop you here and downvote this…this is a horrible idea for a lot of reasons.

1. There is a reason that a “distro” is a distro. All the components fit together and make a cohesive environment. Providing privileged access to whatever the base is to operate as if it were simply some tool running will 100% break the host OS in time. It’s not even a question.

2. The abstractions of tools in tools on top of tools is just stupid. The effort needed to manage, recognize, and log where the interactions happen is just absolutely insane.

3. Simplicity in operation ties into #1. New users would have no idea WTF is even going on here, would find no docs to help them if they run into trouble, or find any other users who are running the same combo of stacks-on-stacks to be able to even attempt to help them out. Advanced users would be able to just pick up a tool from one distro, and drop it another. Makes no sense in either case.

4. Recovery: should something bad happen, you’d have ZERO way to even attempt to fix it. Again, containerized tools would be make operative changes to the Host OS, and any tools with the Host would be useless to repair them, because they’d only be expecting to work within their own ecosystem…again, what makes a distro distinct.

Here’s a simple example: I run whatever Host OS, and then I go and run another container OS that intends to operate on my Host, BUT, it’s missing a GCC version that is expected. You poke around a bit, and in an attempt to solve for a missing dependency, now your host gets an incompatible GCC version installed into itself and gets borked.

No coming back from that in any simple way.

Again, who is this intended to appeal to?

Edit: Also, just reading the end, this is like Homebrew with extra steps and more stupidity.

They’ve been doing this since the beginning of the year.

It starts with jokes…