brinox

I was just wondering if pg_parquet could be combined with pg_azure_storage to write Parquet files to Azure Storage.

I had problems with pg_azure_storage in the past, because the roles pg_read_server_files and pg_write_server_files are unassignable on Azure PostgreSQL databases which makes the use of `COPY {FROM,TO}` impossible.

Running signed binaries neither is as long as the corresponding keys leak all the time [1].

Anyone can just get their malware signed by just throwing some dollars at it.

[1] https://bugs.chromium.org/p/apvi/issues/detail?id=100

`docker-compose` is the old style of doing it.

Newer versions of Docker have Compose available as a CLI plugin, so the command `docker compose` with space is correct.

Mastodon.

Do you also audit / control web browsers the clients are using?

Congrats, you've just discovered referential transparency :-)

Such a nice feature of functional programming languages, like excel formulae.

> You Still Need Third-Party Antivirus With Windows 11

At that point I stopped reading.

> PCMag security expert Neil Rubenking states that you still need third-party antivirus software.

Please stop suggesting snake oil software to the folks out there calling yourself an "expert".

Good, one fewer snake oil product on the market.

It's very convenient, yes.

If your Bitwarden vault is compromised however, you only have a single factor, because both the password and the TOTP secret are stored in the same place.

It would be really nice to always spell out the abbreviation once, put in in brackets and then use it afterwards. That would save so many people precious time.

You can configure the message size limit on your gRPC server, doesn't that fix your issue?

I don't want to know what other security holes exist in applications that don't even support TLS 1.2.

ZetaSQL[1] seems like it could be a fit for your use case. I've worked with Apache Calcite in the past and found it to be very complex to work with. I found ZetaSQL to be a little easier to use.

[1] https://github.com/google/zetasql

Even if your certificate expires after 3 years, the certificate renewal process should be automated. The long validity of 3 years leads many people to not consider this necessary.

If the certificate is only valid for three months however, many people will automate the renewal right away, because nobody wants to do this manually every couple weeks.

From a security POV, shorter lifetimes require more periodic checks for the server's identity. E. g. a Letsencrypt-issued certificate using the ACME protocol will validate the server really belongs to the given domain more often, which is a nice property I think.

Why should my grandma use a VPN anyway? I could not think of any reason.

I think this would be nice to wait for a socket to be available instead of doing `sleep n`.

You can just type in anything you'd like as when using Ctrl+R and then just press the up arrow key to perform a fuzzy match in your history.

I'd recommend to at least give the option to have the text rendered in a font suitable for long texts, which is a font with serifs.

I like monospace font for programming tasks but it is just not the right choice for long reads.

I can only speak for Germany, where it's definitely not.