FYI: There’s currently an open issue with crossposting on instances using the 0.19.4 lemmy ui.

In a nutshell, the post submission page reloads after it retrieves the community to crosspost to, so everything but the selected community is wiped out.

It’s a bug in 0.19.4. I opened a GitHub issue for this in the lemmy-ui repo.

Try using 1.1.1.1 or 8.8.8.8 as the external DNS in your router for testing. Does it work then?

Also, you may have DNS cached somewhere. You can flush your Windows DNS cache by typing ipconfig /flushdns in a command prompt.

I wonder if you can get the frunk to critical velocity at the touch of a fly by constantly pumping it up like a pump action gun.

From what I researched, the average lifespan of HDs and SSDs is no more than 10 years.

Is this running or not running though? I think a bunch of flash chips, properly stored, would last quite a while

You can host overseas and use a proxy for hosting. I mostly don’t worry about it though because I don’t do anything illegal.

Use encryption if you are concerned.

I’ve used Hyper-V and in fact moved away from ESXi long ago. VMWare had amazing features but we could not justify the ever-increasing costs. Hyper-V can do just about anything VMWare can do if you know Powershell.

MDT works well for Windows environments. Otherwise dd or Clonezilla for Linux.

Here’s a quick method:

Get the IP and set up the dns for the new server. Get a cert via Let’s Encrypt or self sign to get ssl working, and then start your prep.

On the new host create the new directory structure. Note your folders, paths, and permissions. Set the permissions on the pictrs folder as 991 (sudo chown 991:991 /path/to/pictrs/folder even if that user doesn’t exist on your system. It’s for the container.

You’ll need to edit your yml files, docker compose file, and make sure that the paths are updated, the instance name is correct, and federation is disabled (until testing is done).

Copy pictrs and db folders from old host to new. You can skip pictrs if space is a concern, but you’ll lose your instance pics.

Once done, copy over the containers and bring them up.

Check for errors and diagnose as necessary.

Once set, change the federation to on, switch your dns from old server to new, and then perform another sanity test.

I’m doing what you want to do now. I’m running lemmy.fan on a NAS with really good hardware on a fiber connection. My ISP provides symmetric bandwidth and doesn’t block anything, though emails can’t be sent with a local smtp server since most places don’t trust the IP addresses of residential subscribers.

I learned a ton, I’m enjoying running things, and though it’s an open instance I don’t advertise it. I say go for it. Experiment and have fun. If it sucks and you hate it you just stop the containers.

Awesome question.

The operating system, or OS, really does not care about whether it is a hard drive or a solid state drive when moving around the partitions.

Say your hard drives are pools. One is filled with molasses, and the other has water. The partitions are like the ropes in the pool. Perhaps you have no ropes. Maybe you have three, but two are so close to the wall, and each other, that only a small amount of stuff could occupy those lanes.

That leaves you with one really large lane. That’s your data partition.

Water or molasses, the ropes are the same.

What about a background svg image and text area(s)?