Last

Sorry about that, I missed the part about this being for your phone.

What’s that?

Nevermind, I get it now. just had to think about it for more than 2 seconds.

I’ve heard good things about copyq, but I sometimes run into compatibility issues with it for some reason. Clipx is also good, straightforward and easy to understand

I tried running a 1/1Gbps connection over Cat5e at home too, but for some reason, I couldn’t get it to connect properly. Ended up switching to Cat6, and it finally stabilized. I’m still scratching my head over why the Cat5e didn’t work as expected.

What is the cost associated with Immich? I keep hearing about it, but I still don’t know how that really works I guess

Would it be better to route that directly? I’m not really understanding the complexity I guess.

How long can something like that really last, though? I wish we had a better idea of the timeline, before the quasi-demons start freelancing lol

Oh ok, we’re talking about two very different things then. That’s a very strong opinion for a simple question. I understand what you mean a little better now. Docker is better, but Windows has some weirdness going on with Docker Desktop last time I tried using it. WSL + Docker might be even better to avoid the VM stuff altogether

That’s exactly how I’ve been using it all along. I didn’t know it had a name, but I opened a previous conversation and simply asked, 'Review our conversation. Is this rubber duck debugging?

Got this:

Yes, this conversation does align with the concept of “rubber duck debugging,” which is a method where a developer explains their code or problems to an inanimate object, such as a rubber duck, in order to clarify their thinking and uncover solutions.

Key Aspects of Rubber Duck Debugging in Our Conversation:

1. Explaining the Problem: You’ve been explaining issues and errors in your code step-by-step, as well as discussing the structure and organization of your files and directories.

2. Step-by-Step Problem Solving: We went through the process of debugging various issues, such as errors related to missing modules, routing problems, and configuration issues.

3. Clarifying Thought Process: The conversation involved clarifying certain technical aspects, which mirrors how a developer might talk through their code to better understand it themselves.

4. Iterative Troubleshooting: We’ve repeatedly revisited issues and refined our approach, which is characteristic of how rubber duck debugging helps to identify the root cause of a problem.

While the term “rubber duck debugging” typically involves explaining the code to an inanimate object, in this case, you’ve been using me as a “virtual rubber duck” to guide you through the process and help identify errors. This technique is often helpful for developers to slow down, think critically, and uncover solutions they might not have seen otherwise.

Yeah, I agree with that 100%. I need to try smoking only at night and see how that goes.

I completely forgot there were alternatives to this.

You might have a normally functioning brain, though. This is essentially a self-medicating starter pack for people with ADHD.

10+ years of this and never regretted it. Need to use a vape pen when in the office. Synthetic urine exists.

If they’re a beginner, what better way is there to learn? My home lab and their Windows laptop running VirtualBox are two different things. The topic of security is too deep to cover now, but if they don’t open it up to the world, there shouldn’t be much risk. Local access only should be safe enough, and they might try a dozen different services before settling on one—or none at all.

Edit: Sysadmin is boring, I need to create. DevOps or some other automation role would be perfect IMO

Regarding your third point, you might find it helpful to search for beginners’ guides whenever starting a new project. One thing that people don’t seem to tell new users about is the struggles they faced when getting started themselves. Countless thousands of hours could be spent on this before someone decides to get started, while others pick it up in a much shorter timeframe. It just depends on you and what you are looking to get out of it.

It’s much more difficult than many people realize. If you need a space to test things out, I’d recommend installing VirtualBox with a couple of VMs to host whatever services you decide on. You can take a snapshot of the VM at any point in time, so when things go bad, you can simply restore whichever snapshot you like.

For your first point: Work experience, to save money, and just because it’s cool.

There are other benefits that I’ll mention depending on whether I think the person I’m talking to might value them or not, but these are my reasons.

My life got immensely easier when I figured out I did not need any features ZFS brought to the table, and I did not need any of the features K8s brought to the table, and that less is absolutely more.

Same here. Sometimes I get carried away, but overall, a very basic setup is more than fine. Nearly all of my devices run Ubuntu/Debian, and only the work-related stuff gets over-engineered.

It’s helpful for me to have something like a home lab where I can get hands-on experience with many different technologies. I’ve worn many hats, from developer to sysadmin, so a certain segment of my network tends to be built like Fort Knox. However, overall, 90% of my installs are minimalist with common best practices applied.

128TiB, which is about 3k movies with I think 20+ shows. Some of the files are over 100GiB though.

Perfection