Meh, I tell it "use uuidgen and get your randomness from that". Of course, that won't work on ChatGPT web, but works well enough on the command line.

Explained in the article:

> A producer sends a backing track to a performer - SyncDNA adds a slight delay to the outbound feed

The "backing track" is probably the beat or something similar.

I still fail to understand why this is a thing. Two possibilities:

1) the beat is created live by a human performer who can't meaningfully hear the other performer(s) in time. He / she is stuck with playing blindly.

2) the beat is pre-recorded - sampled or electronically generated on a sequencer. Then what's the use case in the first place? The other performer can download it offline and play on it live.

All this is done to get something that mimics a live performance (but isn't, because the band components can't hear each other in real time) to someone listen-only at the end of the chain. What's the advantage in doing so? What's the use case?

I do the "same thing", but using PostgreSQL `EXPLAIN ANALYZE`. EXPLAIN ANALYZE has information about the number of rows returned, which means I know exactly which node in the query plan failed to return expected values.

don't mean to push the goalpost (didn't mention the following in the above post)

these functions can also be exposed in admin ui's making it easier for the general admin users/support users.

another very useful use case is when row level security (RLS) is enabled.

Not for function though unless you specify it as a debug flag inside the function?

This has some overlap with Overmind / foreman / Procfile. To wait for another process to be started, I resort to using plain `sleep` or `dockerize -wait`.

Good job on building this!

In the article, it is mentioned that « we can grant temporary access to cardiac-related data » (paraphrased). This is where it gets difficult: how am I to know that some data is cardiac-related or not? Is it important to share my thyroid levels or not? This is a very difficult problem. I wouldn’t know what to share for medical history.

Our[1] solution to that is to use a hierarchical semantic systems approach such that you can give access to a subsystem or entire biological systems.

[1] https://graphmetrix.com/trinpod-server

The requester would know what to request.

And he would request all you have... like many apps do today ( in case of permissions)... and refuse to provide service if not given all.

We have laws regulating what personal information you are allowed to ask for, and what you're allowed to do with it. These laws have teeth too, at least in the EU.

Passively snooping on health info you have no business looking on gets health personnel sanctioned regularly in the present system. It would be even more risky if they actively had to ask for the information they didn't need.

Of course, for medical information there often has to be emergency overrides because you might need immediate help and you (or your designated trusted person) might not be accessible and capable of giving active consent.

But doesn't this obviate the use of a specific protocol? The protocol itself does very little to help with this problem – only laws with teeth do that.

Meh, there's workarounds to the GDPR framework if you're a company outside the EU. I'd say if you had a big company outside the EU, like the US, you'd have even less regulation than EU companies have to adhere to.

Sorbet is nice, but for data structure enforcement and data validation, I much prefer the dry-rb ecosystem.

I've used dry-rb a bit but had problems with breaking changes that put me off.

I love some of the ideas but they seem a bit too heavy for my taste.

e.g. I think (project) standardised results are a fantastic idea but I don't need the weight of Dry::Monad for that.

I think I can get enough benefit from built in features like .then and throw..catch with tags for signaling without an extra dependency and the risk of the API breaking on upgrade.

Heroku's 25 hours comes to mind... this is so infuriating and annoying.

You still need the timezone name to map back to UTC, in case you want to make some types of computations, usually along the lines of "how long ago was this" and "remaining time until this thing happens".

You may argue that we can use local time to make the computations and be done with it, but during DST transitions, local time jumps so the number of actual seconds won't be consistent.

I use an older iPad and the page crashed so hard the Home button didn’t do anything for about 30 seconds. The iPad eventually turned off, because I had pressed the power button, to no avail, a couple of times.

C, C++, C#, and probably Rust. There’s a section about that. There’s a link to the FAQ I. That section.