cipherzero
Joined 16 years ago
Joined 16 years ago
As DuckDB is an analytics database, it has only minimal support for transactions and parallel write access. You therefore couldn’t use it in applications and APIs that process and store input data arriving arbitrarily. Similarly when multiple concurrent processes read from a writeable database.P.s. love the user name.
I guess I’m confused what point you’re making?
> And our reinstatement, based on new information that showed the project was not circumventing a technical protection measure (TPM)
Since it is clearly circumventing a “TPM.”
You can configure views, filtering, sorting, summary’s, and foreign keys with roll ups....
That’s not something trivial to build, however I’d be pleasantly surprised if obsidian eventually got there.
I fear it encourages you to hide or down play an incident, if possible, when issues do happen. Instead you’d rather want to encourage transparency and some way to prove you’re following good practices and have a good track record. Maybe some incentives like car insurance companies claim to follow: better driving record, reduced insurance costs. (Not that I think car insurance is a successful/good example.)
Failure cases (like data breaches and ransomware attacks) are certainly easier to measure though, so maybe this is the best we can hope for...
I’ve used Zola and love the build speed and power that it has. My only real complaint is common mark as the markdown engine. I prefer the tera/jinja2-esque template syntax over ramhorn/mustache-esque that’s used here.
I’ll have to try and port a theme to blades to give it a fair assessment.
Given how many weird loopholes it contains it’s no wonder that they don’t have enough horsepower to compete with the lawyers of the ultra rich...
That and as others have mentioned I’m sure they’d love everyone to always be logged in for ad tracking purposes...