> 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).
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.
Maybe the closest things are chroot jails and pledge/unveil, both of which are application-specific or built in to the package. (I'm agreeing with you.)
In GNU utilities, option arguments can come after (or between) positional arguments. Personally I find this small convenience invaluable, because I'm used to it.
As a Unix graybeard I always place options first. Options last feels like Windows command prompt, so nothing I want to see...
I always tell younger colleagues who place options in the end, it might work with some commands, but just don't do it. I did not know that "some" includes all of GNU coreutils? A single common code style is a virtue, even in interactive use if there are onlookers. So I guess I will continue to point it out.
Even many command line parsing libraries support it and scan the entire argv for options. You should always terminate the options with "--" if it's in a script and any of the positional arguments are variables that might or might not start with a dash.
That’s basically just Lemmy/kbin. Those two services can even interconnect with Mastodon thanks to ActivityPub.
As I’ve said elsewhere in this thread, moving text around on the Internet has been a solved problem ever since NNTP. And that was 1986!
The only problem is that there’s not a lot of money in it, which is why having the ability to federate a bunch of smaller services together is such a good solution (at least on a technical level).
Because PostgreSQL major version upgrades are hard and for large databases, requires some level of downtime. Given that that major version releases are on an annual release cycle, staying evergreen is really really annoying.
Under some elementary scenarios (and using some Postgres offerings), you can do a full major upgrade using logical replication (even with replicas). It depends on your situation, generally I agree, any sophisticated use of Postgres (lot of views, materialized or not, fast changing schema, large objects, and so on) makes upgrades a pain and is generally somewhat of an unresolved problem in my opinion.
Agreed. I also see PG 16 is scheduled for release later in the fall. Also, you don't want to put the first 16.0 version on a production system, rather wait until 16.1, 16.2 etc.
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).