I wanted to create a caching snap proxy and it turns out you have to register it with canonical to get a cert.

You were just boycotting before it was cool.

Lots of governments want it. But its no excuse doing it in a stupid way. For example EU IDs should have a function that just verifies someone is over 18 without any other info being send. At least the German one does. But its not being used.

This feels like a hacky solution.

Why not use VLANs? You can have just one physical interface and then have VLAN interfaces. You can then use a bridge to have every container have their own interface and IP that is attached to a specific VLAN.

Depends on how important it is. Looking for a hint for a puzzle game: never. Trying to find out actually important info: always.

They make it easy though because after every statement it has these numbered annotations and you can just mouse over to read the text.

You can chose different models and they differ in quality. The default one can be a bit hit and miss.

I use kagi assistant. It does a search, summarizes, then gives references to the origin of each claim. Genuinely useful.

They wrote this without googling anything.

Orca slicer, bambu studio

To be clear: that’s their issue.

Yes absolutely. The results are actually useful, they don’t have an incentive to keep you from finding what you are searching for. There is way less copywritten content and if there is, you can just block it.

Whenever I have to go back to “free” alternatives I am shocked by how much worse it is.

I’ve seen this haven’t tried it out though

https://timelinize.com/

Upgraded my gaming system. Feels much snappier.

Everything should run under their own user when possible. This software is not using a privileged port (< 1000) so it doesn’t need root.

The docs seem a bit lazy if that is not recommended, possibly it will try to access some files it does not have access to.

The threat model is that all communication is recorded and will be decrypted once the technology becomes available. The question then becomes for how long you want your data to be secure. If its for example 40 years, you need to chose an algorithm today that is still secure in 40 years.

I would recommend something like stalwart, which is just a single binary and works. Gives you a web interface and a zonefile you can just copy paste into your DNS including all correct DMARC DKIM SPF and autodiscovery records.

Setting postfix, dovecot etc. up from scratch can be a bit time consuming and annoying.

Deliverability depends on where it is hosted, many VPC providers IP space is completely blocked in spam filters.

Ultrasonic cleaner. Cleans all the stuff that’s hard to get to usually. Also great for glasses.

I understand this, but this is inconsistent behavior. You now use 22 inside your network and something else outside. Whenever you create inconsistent behavior, everyone using it has to have an awareness of all these inconsistent behaviors.

Also, it is hard to troubleshoot because the tool most admins would want to use (netstat) will not give you useful information to understand the situation.

If you have a drink that creates a nice tingling sensation in some people and make other people go crazy, the only sane thing to do is to take that drink off the market.

I’m not sure LLMs can do this. The reason is context poisoning. There would need to be an overseer system of some kind.

If you change it, definitely change it on the server so it shows up in netstat and is consistent.

The idea behind keys is always, that keys can be rotated. Vast majority of websites to that, you send the password once, then you get a rotating token for auth.

Most people don’t do that, but you can sign ssh keys with pki and use that as auth.

Cryptographically speaking, getting your PW onto a system means you have to copy the hash over. Hashing is not encryption. With keys, you are copying over the public key, which is not secret. Especially managing many SSH keys, you can just store them in a repo no problem, really shouldn’t do that with password hashes.