A modern OS running with low RAM (e.g. an RPi with 2G) is going to fill the RAM pretty quickly just in normal operation, so a larger swap space will allow it to run more efficiently as it regularly moves things in and out of swap. You still want to have some overhead to allow for storing the live RAM for hibernation, which with a small amount of RAM is likely to be near 100%. Therefore, running with 3x RAM for swap space is recommended.

it only needs to be at least the size of RAM

Yes, technically it only needs to be the size of the RAM, but no matter how much RAM you have some of the swap space will be used at any given time for the swap file during system operarion. If you only have exactly as much swap space as RAM, there won’t be enough available swap space to store the entire live RAM for hibernation.

The size of the swap file and the size of the live RAM image at any point is unpredictable, therefore 1.5x RAM is the lowest recommended value that is probably safe for hibernation, assuming the swap file is not being used heavily enough to be 50% of the RAM. If you can’t provide at least that much disk space for swap, you should disable hibernation.

I want the Centrino Nano Duo

This is the best simple guideline: https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/10/html/managing_storage_devices/getting-started-with-swap#recommended-system-swap-space

Basically, if you want your system to be able to hibernate then you need enough swap space to sustain both the active swap file and a full image of the live system RAM (hibernate = suspend-to-disk, and uses the swap space). The swap file could be as large as the RAM, so a safe value is 2x the RAM. If you don’t want to dedicate that much disk space to swap, the safe option is to disable hibernation but note that suspend-to-disk is safer for system recovery in the event of power failure.

If you’ve ever had a Linux system go into hibernate and fail to awake, lack of swap space was probably the reason.

In Red Hat’s chart where they recommend 1.5x RAM for 8-64 GiB, basically you’re hoping that your system is never completely using all of the RAM. If you do cap out the RAM such that the swap file plus the in-use memory is greater than 1.5x RAM, and the system goes into hibernate, it will not recover because there isn’t enough free swap space to store the in-use memory. You have to make a judgment call when you set up your system about how you’re going to use it - whether you expect to be using 100% of the RAM at any point, whether you’ll remember to close some running applications to free up memory every time you leave the system idle long enough to go into hibernate, whether other users will be using the system (if they’re logged in then they are partially using the RAM and the swap), etc.

Deciding how much swap space you need is a risk management decision based on your tolerance for data loss, application stability, and whether or not you need hibernation.

Assuredly, we must all hang together, or assuredly, we shall all hang separately.

At the moment it’s experimental, so no.

And just to be clear, this cannot be used to move information faster than the speed of light, ever.

In theory it might have application as a sort of tamper-evident seal for digital encryption.

In the November study, the researchers successfully “beamed” polarization between a photon pair, and they could do this because the particles were entangled.

Equating quantum (information) teleportation with physical teleportation of objects really just reveals that the author has no idea what they’re talking about.

Hmm…

Especially if you’re an Active Directory shop. Switching out that infrastructure is a heavy lift.

Win12 will be decent again

Windows 12 may stabilize a lot of the functional problems occurring in 11, but it will also have all of the new AI-powered end-user surveillance features they’re currently trying to implement fully integrated.

I do admit that I run Win10 IOT in VirtualBox for a few small programs that won’t run under Wine. Once a week, for a few minutes. I’m sorry. I don’t wear the shirt, because I feel like a fraud. Please forgive me.

Dude, virtualize all the things! In open source land, you run whatever code you want to because you can, and you don’t feel embarrassed about it.

Whatever you do, and whoever you end up working with, document document document. Take notes.

And I mean on paper, in a notebook, something that can’t crash or get accidentally deleted and doesn’t require electricity to operate.

You’re doing this for yourself, not for a boss, which means you can take the time to keep track of the details. This will be especially important for ongoing maintenance.

Write down a list of things you imagine having on your network, then classify them as essential vs. desired (needs and wants), then prioritize them.

As you buy hardware, write down the name, model and serial number and the price (so that you can list it on your renter’s/homeowner’s insurance). As you set up the devices, also add the MAC and assigned IP address(es) to each device description, and also list the specific services that are running on that device. If you buy something new that comes with a support contract, write down the information for that.

Draw a network diagram (it doesn’t have to be complicated or super professional, but visualizing the layout and connections between things is very helpful)

When you set up a service, write down what it’s for and what clients will have access to it. Write down the reference(s) you used. And then write down the login details. I don’t care what advice you’ve heard about writing down passwords, just do it in the notebook so that you can get back into the services you’ve set up. Six months from now when you need to log in to that background service to update the software you will have forgotten the password. If a person you don’t trust has physical access to your home network notebook, you have a much more serious problem than worrying about your router password.

Because they want step-by-step guidance and support, and design help, and long-term support, not just a few questions answered.

This is a job. The kind of work that IT consultants get paid for. A fair rate would be US$100/hr, minimum, for an independent contractor.

You can just use openssl to generate x509 certificates locally. If you only need to do this for a few local connections, the simplest thing to do is create them manually and then manually place them in the certificate stores for the services that need them. You might get warnings about self-signed certificates/unrecognized CA, but obviously you know why that’s the case.

This method becomes a problem when:

1. You need to scale - manually transferring certs is fine maybe half a dozen times, after that it gets real tedious and you start to lose track of where they are and why.
2. You need other people to access your encrypted services - self-signed certs won’t work for public access to an HTTPS website because every visitor will get a warning that you’re signing your own encryption certs, and most will avoid it. For friends and family you might be able to convince them that your personal cert is safe, but you’ll have to have that conversation every time.
3. You need to implement expiration - the purpose of cert expiration is to mitigate the damage if the cert private key leaks, which happens a lot with big companies that have public-facing infrastructure and bad internal security practices (looking at you, Microsoft). As an individual, it is still worthwhile to update your certs every so often (e.g. every year) if for no other reason than to remind yourself how your SSL infrastructure is connected. It’s up to you whether or not it’s worth the effort to automate the cert distribution.

I’ve used Letsencrypt to get certs for the proxy, but the traffic between the proxy and the backend is plain HTTP still. Do I need to worry about securing that traffic considering its behind a VPN?

In spite of things you may have read, and the marketing of VPN services, a VPN is NOT a security tool. It is a privacy tool, as long as the encryption key for it is private.

I’m not clear on what you mean by “between the proxy and the backend”. Is this referring to the VPS side, or your local network side, or both?

Ultimately the question is, do you trust the other devices/services that might have access to the data before it enters the VPN tunnel? Are you certain that nothing else on the server might be able to read your traffic before it goes into the VPN?

If you’re talking about a rented VPS from a public web host, the answer should be no. You have no idea what else might be running on that server, nor do you have control over the hypervisor or the host system.

This looks like either underextrusion causing gaps in the surface, or the filament sticking to the nozzle a little too much and tearing as the nozzle passes over it.

Simple things first:

• check that the extruder clamp screw (that holds the filament against the extruder drive gear) is still tight - it’s possible that the filament is just not being pressed against the extruder drive, allowing it to slip

• is your nozzle clean on the outside? or does it have a clump of plastic buildup on it? if there’s plastic stuck on the outside of the nozzle, the extruded plastic may be sticking to it and tearing

• is this a filament that you’ve used on this printer before? have you done a temperature tower? have you done a flow rate calibration?

• do you have more pictures of your test prints? other angles?

The problem is that many employers are requiring employees to use them.

Hey, would you like to buy some dehydrated water?

Easily produce your own water whenever you need it!

To make 1 liter of water, just add 1 liter of water!

This is basically eBay.

I understand that starting your own business is hard

It’s worse than that, starting your own business is sales.

Are you working in some niche field where you have a good idea of who your customer base is already? Do you know 5 people right now who would buy your product today? Why would they buy from you vs. an established software company that also has a customer support team? Do you look forward to working with these customers to integrate your software into their existing workflow? Do you look forward to auditing your software for cybersecurity compliance?

You need to be able to answer these questions. It doesn’t matter how good a programmer you are or how complex your software product is, what matters is what makes buying from your company better than another.

And so did Rimworld, and there’s room for more.

Yes, that would be the point.