zie

4 ms·

31.
by zie 4mo ago
Very different risk profiles. Bonds are about steady cash flow, not about total return. "stable" dividend stocks are almost never really stable when the financial world crashes.
32.
by zie 4mo ago
Their definition of long run and your definition of long run are probably different. Also, it should be noted, just because it's the optimal to have the most $'s that shouldn't be the goal. The goal should be to survive your
33.
by zie 5mo ago
I'm with you, once an RCE is known, it's usually just a matter of time before it gets script-kiddied and easy to run. Don't put yourself through the pain, just upgrade nginx. I just finished upgrading a weird embedded box tha
34.
by zie 5mo ago
I would think you could do this with a comma.ai device too.
35.
by zie 5mo ago
<3
36.
by zie 5mo ago
Just depends on if that's something grandparents/kids can/want to afford. Personally, If the hardware is working great, seems like a waste of money replacing it, just to upgrade software. Especially with Debian oldstable -&g
37.
by zie 5mo ago
Yes, a bonus would be more context, but already this can show stuff you know you don't want. If you see doubleclick.net for instance you know it will be ad-ridden disasters, or whatever. With just the domain, you can search the code re
38.
by zie 5mo ago
Yes, for sure. More context is a bonus. like clicking a link takes you to the code that calls out to github.com. Or for some sites like github, instead of just showing the domain, it shows the repo in question or it's a gist or somethi
39.
by zie 5mo ago
I love that under disclosures "Plugin might make requests to 1 external domain", if you click on it, it shows the domain: "github.com". great work! Example from https://community.obsidian.md/plugins/
40.
by zie 5mo ago
Clearly you disagree with the debian stable perspective. That's fine, it's not for everyone. You can just run debian unstable or debian testing, depending on where exactly you draw the line. If you want the rolling release like di
41.
by zie 5mo ago
You forgot to use https://www.random.org/ as your source of randomness :)
42.
by zie 6mo ago
I just use send(formerly FF send) and share a URL via chat or whatever: https://github.com/timvisee/send With a CLI tool as well: https://github.com/timvisee/ffsend
43.
by zie 6mo ago
Barman has been around since 2011, released under the GPL. If it does get ruined by someone, I'll replace it in my stack or fork it for maintenance myself. I'm not very worried though. EDB has been in private equity(PE) hands sinc
44.
by zie 6mo ago
See the documentation: https://www.postgresql.org/docs/current/backup.html all of these various 3rd party backup tools use these things. Mostly it's QOL stuff that you get from a 3rd party tool. We use barman
45.
by zie 6mo ago
I dunno how they compare, but we have been using barman for a long time very happily. We test our backups every night, by restoring from barman into a _nightly DB. which we then give out to users as a training/testing spot, so that we
46.
by zie 6mo ago
> It provides everything you need or want or don't know you want except a decent text editor. That's what evil is for :P
47.
by zie 6mo ago
Ah, nice!
48.
by zie 6mo ago
I have family I need to support, so I use 1password. It also helped that work gives me a 1P family plan free. The practical differences to me: * 1P is aimed at non-tech users more than Bitwarden. * 1P lets you easily store things
49.
by zie 6mo ago
I think you had to have installed the CLI during that time-frame, then ran the brand new installed CLI to be vulnerable. Assuming you had it already installed, you would be safe.
50.
by zie 6mo ago
It's typescript and pretty sure all of the Official Bitwarden clients are written in it. I wrote a version in Python and then rust back before the official CLI was released. Now you can use https://github.com/doy/r
51.
by zie 6mo ago
I wish you lots of success. That's a giant amount of work though. Good Luck!
52.
by zie 6mo ago
I have had many of these machines at various points in time, some even running on the public internet. They are a giant PITA to keep running and alive. This is why they don't usually last very long if they ever even get to public acces
53.
by zie 6mo ago
At work we just got a quote to upgrade a couple servers, original price a few years ago was ~ $150k. Essentially the same hardware, just newer, is now quoted at ~ $450k. We decided to just keep our current hardware for now and extend a supp
54.
by zie 6mo ago
Ya, I don't see any point in systemd adding this, but they did it already. Near as I can tell most of the laws just want to know a rough age category that can be provided by the OS. Seems to me an `echo "adult" > ~$USER&
55.
by zie 6mo ago
Systemd seems to have only implemented a place to store a birthdate. I doubt they will do anything else.
56.
by zie 7mo ago
If you need to use these, set the history retention to like no time. That would help a lot. They could still get the contents from the person you are communicating with, but it would require more work on their part. Humans are generally fai
57.
by zie 7mo ago
I have like 20-ish[0] people using my Migadu account and I've only hit the hard limit once, and it was because one of them was trying to do a mailing list.... Once I got them on a better path, I haven't had any issues. I don'
58.
by zie 7mo ago
I must have missed that in the comment stream. It's not really any different than using pgbouncer or something similar. All it buys you is not having to use the PG protocol on the client. There is no extra security here though. One cou
59.
by zie 7mo ago
Agreed, in Multi-tenant, where the user/customer owns the data, I always reach for SQLite first. Each user/customer gets their own SQLite DB. Then you have a common PG/SQLite DB for any common metadata, billing, etc. That way
60.
by zie 7mo ago
Correct, but you have yet to mention any other solution where there is more than one boundary at the data access layer. Because there really isn't any. You can code it yourself in your bespoke app, have your vendor maintain it with the

More ›