Listening to the TFTC podcast (Marty Bent) with Andrew Torba the CEO of gab.
It just reinforces what I always thought, how can we keep making the same mistake? Having a centralized owner will always be the failure mode of sidestepping invasive control mechanisms of the elite.
The only way to avoid is just to not have an owner.
Why isn't Marty spending an hour talking about mastodon? (or something similar?) gab *will* fail if it succeeds.
I get the distinct impression that all these things like: Plasma (Poon, Buterin), client-side validation/single use seals (Todd), sidechains (many flavours), are all fumbling towards the same general idea: maintain a light ledger, out of consensus, that's actually usable at scale, by committing its state periodically to a heavy/secure ledger.
I'm still not sure what I think about this after spending a lot of time reading.
Sigops limits are getting decidedly non-trivial in tapscript:
Sigops are a really in-the-weeds but important issue in Bitcoin today; the optimisation problem for miners is multidimensional because of it; it's not just "optimal fee per weight" it's "optimal fee per weight with a hard limit on sigops" (kinda like linear programming i guess, if you know about that).
That point is mentioned in sipa's write up but, it's getting more complicated here, unsurprisingly perhaps, because taproot is extending the scope/size of scripts.
Yes, this is perhaps *the* canonical use-case people have in mind for covenants: it's often called in the "literature" (a few papers and blogposts scattered here and there), "vaults".
The basic thing to keep in mind is that in Bitcoin today you cannot place conditions on the *destination* of a coin you pay; you can only restrict the conditions under which it's spent, not where it's spent to. Covenants opens that possibility, but it's a thorny issue as discussed in thread.
Creating and using a custom Linux kernel on Guix System https://www.gnu.org/software/guix/blog/2019/creating-and-using-a-custom-linux-kernel-on-guix-system/
@orionwl there is now a u-boot-sifive package in Debian experimental and also 'opensbi' (RISC-V Open Source Supervisor Binary Interface).
Maintainer of opensbi and u-boot also did a presentation wrt RISC-V in Debian: https://archive.org/details/latch_2019-RISCV_in_Debian
There is now also a section "Setting up a riscv64 virtual machine with u-boot and opensbi" added on https://wiki.debian.org/RISC-V (and some other updates)
There's also reasonable activity on #debian-riscv (OFTC)
Some podcast recommendations!
1: A podcast that might annoy you, possibly, but I'll still recommend it:
the a16z podcast on blockchain stuff recently:
To be clear, I think the theses being discussed here are all quite badly wrong, and it's particularly revealing that they describe Bitcoin as slow and in discussing scaling they mention LN not once. I could go on but you get the picture. Why recommend? You should hear other perspectives.
Some folks like static types for safety, but let's be honest, a lot of the appeal is largely speed (at least in the gamedev industry and etc).
Except... it's actually possible to build a system where dynamic types are just as fast. Lisp machines were like that decades ago. Here's how: tagged architecture CPUs. https://en.wikipedia.org/wiki/Tagged_architecture
Because of this, even such things as network and video drivers were written in dynamically typed lisp, and efficiently too.
Nice touch. Mozilla has also deleted Telemetry data for that period as some users had to enable Telemetry to get the hot-fix.
"In order to respect our users’ potential intentions as much as possible, based on our current set up, we will be deleting all of our source Telemetry and Studies data for our entire user population collected between 2019-05-04T11:00:00Z and 2019-05-11T11:00:00Z."
Nice! with a website being added, the Bitcoin PR Reviews Club seems to be picking up steam.
Working on Bitcoin. INSEAD/Harvey Mudd. Wrote pro games in 6502 assembly as a kid (Quasimodo, Meteor Storm). Assembly C C++ Lisp Ruby Linux Emacs
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!