At my work we explored a low-code platform. It was not low on code at all. Beyond the simplest demos you had to code everything in javascript, but in a convoluted, intransparend, undocumented environment with a horrendous editing UI. Of course their marketing was something different than that.
That was not the early days of low-code mind you. It was rather recently; maybe three or four years ago.
I looked at Wikipedia; Taler then Blind signature, then looked for docs on GNU Taler where I didn't immediately find any technical overview of how that works. Phind gave me a seemingly reasonable and understandable answer. (Surely sourced from somewhere.)
When we multiply the original message by rere, sign it, and then multiply by r−1r−1, the blinding factors cancel out while preserving the signature.
The success of this process relies on two critical properties:
The blinding factor must be relatively prime to N
The RSA keypair must satisfy the congruence relation red≡r(modN)red≡r(modN)
The magic is that you can
Apply a mathematical operation on your data
Sign that data
Revert/Invert the mathematical operation
and the signature remains valid.
It does sound like magic. But isn't most of cryptography like that?
There's a python example in there as well, with such a calculation. I didn't go through it though.
There's a lot more variance in the specifics, but I think for an overview like this it's certainly missing dual-licensing and "business-open" licenses like "readable but limited now, but free software two years from now".
But I guess with the specific target audience of this post the reduction for simplicity is a good thing.
Performance optimization is hard because it’s fundamentally a brute-force task, and there’s nothing you can do about it.
I think that only takes effect after a certain degree of best practices, knowable practices and effects, and after educated guesses and theories with testing. That's a lot before you reach brute force territory. At least in typical and higher-level programming language development.
Do you want feedback on your website too? I have a big monitor. It's too big, making use of the entire screen width and height, and seemingly scaling to fill proportionally instead of reasonably. I would like to be able to grasp the menu in one glance, not read word for word. I assume the content is a generated presentation. For me, that's unfit for a landing webpage too. Too big.
Seems interesting. But I don't have a use case, no need to make presentations regularly (and without existing templates). The signup is a hindrance, and having to learn a new syntax is too.
No docs regarding syntax or syntax overview/intro either, making it hard to assess. Link to "based on Tufle CSS" is broken. As well as hidden far down but not at the end.
Our focus will be on a smooth and successful Early Access launch on Steam, which is our highest priority. Only once we are happy with the state of the game will we start the process of open sourcing BitCraft.
The HackerOne report that does not even apply has 44 upvotes.
What do upvotes mean on HackerOne?
I guess, at least here, they're mindless "looks interesting" or "looks well worded" or something?