1500100900's comments

1500100900 | 6 months ago | on: Recreating the US/* time zone situation

> Your backend needs to store location because places can switch time zones.

For the event, your backend only needs to store the timestamp in a timestamptz field and make sure that clients set the correct time zone on session start (this you might want the backend to store in the database too, but probably in the users table).

1500100900 | 2 years ago | on: OpenBSD Workstation Hardening

I'm surprised that not only is there no application firewall for any of the BSDs, there doesn't even seem to be any need for it. There is OpenSnitch, but only for Linux.

1500100900 | 3 years ago | on: PostgreSQL 15

Not for free (have to pay EnterpriseDB for that). Every free option here is basically "glue pieces together to build your own HA".

1500100900 | 3 years ago | on: Ushering out strlcpy()

> The BSD answer to the problems with strncpy() was to introduce a new function called strlcpy()

Not BSD, it was OpenBSD specifically.

1500100900 | 3 years ago | on: Technical reasons to choose FreeBSD over GNU/Linux (2020)

> Don't know what keeps him going. A desire to see FreeBSD fix those defaults?

And when they do fix any of those things, what is his reaction going to be? So far it's been "it took them so much time to fix this, let's keep that in mind".

The point of it is clearly to convince people to use OpenBSD instead of FreeBSD.

1500100900 | 3 years ago | on: Use one big server

How is backup restoration any easier if your whole PostgreSQL cluster goes back in time when you only wanted to rewind that one tenant?

1500100900 | 3 years ago | on: Use one big server

Cassandra may be great when you have to scale your database that you no longer develop significantly. The problem with this DB system is that you have to know all the queries before you can define the schema.
page 1