schizanon

In the web3 value chain, the profits don't all go to the assemblage as they do in Web2.0. All the money doesn't go to Facebook and Google here if this vision sees reality. Creators will take home the profits, and those who own scarce digital assets whose value may increase with time, supported by large, decentralized exchanges will take their rightful share of the profits.

The #SEC’s one-two punch of #Coinbase and #Binance couldn’t have come at a better time for #HongKong and #Singapore, as #US #crypto firms look to shift to friendlier shores, writes Hamilton Keats of Krayon Digital.

Recent moves by #SaudiArabia, #Russia and #China have raised fears that the #USdollar could lose its preferred status for #oil trading. And yet alternative national #currencies aren’t that appealing. Could a #Bitcoin-like #currency do better?

the bike industry is experiencing a supply chain overload. Many companies forecast continued demand where none materialized, and so shops are full of stuff and low on cash. A cursory glance around the market will tell you that a whole lot of stuff is on sale, and this is the WRONG time of year to be discounting new gear.

Prolly Trees and their cousin #Merkle Search Trees are new ideas but are already used by #ATProto / #BlueSky, #Dolt, and others.

In the existing implementation in the C++ library, the code does a series of tests to see how many items it needs to sort and calls the dedicated sorting function for that number of items. The revised code does something much weirder. It tests if there are two items and calls out to a separate function to sort them if needed. If it's greater than two items, the code calls out to sort the first three items. If there are three items, it returns the results of that sort.

If there are four items to sort, however, it runs specialized code that is extremely efficient at inserting a fourth item into the appropriate place within a set of three sorted items. This sounds like a weird approach, but it consistently outperformed the existing code.

The Web Applications Working Group has published Web Share API as a W3C Recommendation. This specification defines an API for sharing text, links and other content to an arbitrary destination of the user’s choice. The available share targets are not specified here; they are provided by the user agent. They could, for example, be apps, websites or contacts.