truthfultemporarily

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.

This is actually really interesting!

This taxable individual, Kokott explains, was found to have bought and resold through "various forums, groups, and platforms such as Facebook, Discord, and Skype" enough RuneScape gold to earn €415,484—approximately $488,000 USD—between 2021 and 2023.

They then were ordered to backpay VAT because they made above 45k. Defendant says trading virtual currencies is like trading crypto, and VAT exempt. Government says its like selling a voucher instead.

Its corner cases like this one that make taxes complicated for regular people.

I also find it hilarious that tax lawyers and accountants will have to read that court decision.

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.

You only go to Valhalla if you died in battle or hang yourself from an ash tree.

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.