teknopurge

what tool are you using for this wonderful data?

I've seen the exact opposite - many projects are going back towards monolithic structures and then decoupling a minority of components that need to horizontally scale.

upvoted and +1. Theo has been an important leader in OSS for decades: his brevity and impatience is a net positive. also he is usually correct.

individuals / companies that cannot afford their own workflows will fine-tune models with heavy preexisting biases. The upper-class of the market will train their own models, producing advantaged outcomes. Data is the moat.

>> Almost nobody will also train their own models ...

If the value is in better training data then everyone will train their own models. We should have a goal where we have domain-specific models that make us more efficient, but also constantly train a context-aware model based on individuals. Model composition is the future.

> According to the sources and the February 2021 bank record seen by Reuters, Binance mixed customer money and company revenues in a third Silvergate account, belonging to a Zhao-controlled Cayman firm. Binance converted money from this third account into the dollar-linked token BUSD, according to the person with knowledge of Binance’s group finances and company messages

> These accounts were not used to accept user deposits; they were used to facilitate user purchases” of crypto, said spokesperson Brad Jaffe. “There was no commingling at any time because these are 100% corporate funds.” When users sent money to the account, he said, they were not depositing funds but buying the exchange’s bespoke dollar-linked crypto-token, BUSD. This process was “exactly the same thing as buying a product from Amazon,”

The article has a lot of details and infographics - but ends with no conclusion, just guesswork. I appreciate the work and time that went into an article like this - it would be nice if it was more factual and less "blind-sourced" extrapolated hypothesis.

The content in article doesn't even satisfy the headline/title. The quotes in the article specifically state what the accounts are for but the author hand-waves on what "could" be if many hypotheticals are reality. Do better Reuters.

^this. What a blown marketing/product opportunity. There should at least be some easter eggs for Don Clipp....

this is cool. edge and decentralized applications are going to be a topic of focus (IMO) in the next 5 years.

I was going to post similar. I respect all builders - but why. Similar to the Postgres WASM in a browser post from the other day. Why....

Adobe already had xD - a direct competitor to Figma. Adobe purchased Figma for many reasons; if you want a single reason why Adobe purchased Figma it's because Figma was successful: all the things that go into executing a vision at scale.

I'm not adding insight to this thread, but I love the OpenBSD project. Theo and the team are goat engineers and industry advocates.

security. I dabble with system programs and it's nice to get the speed/portability of native optimized code and know most memory issues won't occur.

This is great - will be experimenting with one weekend soon...

mootools was awesome. I always wondered why it was so fun(for me at least) to use.

yes. flutter has a nice approach and feels like it has a viable future. javafx seemed to fill that spot - not sure what happened to it.

There is such a thing as a bad idea; this is a bad idea.

yes.

this is great. thank you.

thank you for posting this.

yep. Those solutions aren't there yet, and arguably too early, but the market direction is clear. In five years I would not be surprised to see some form of transactional data store(high TPS, blob store) on a decentralized layer.

Crazy to talk about different FS compression schemes when trying to optimize business/app logic higher up the stack. should be abstracted away by now. (yea, I know it's not, but should be)

crypto.

this thread is relevant to my interests.

The author did a good job, but these were(are) known issues for quite a while. TLDR: implementation bugs with known countermeasures.

https://www.usenix.org/system/files/conference/usenixsecurit... (from 2012)

We've implemented SAML for 10s of millions of users and devices. The spec is verbose, but the approach solves common business issues. My suggestion is to use SAML simply: federations and passing attributes between trusted parties, allowing to verify the payloads. SAML can do a lot, but keep it simple and use OOB services for more orchestration/metadata.

All *nix does this. Also try piping to lp then a device.

Sorry to be cheeky, but welcome to 1977. ;)

BYOH - Bring You Own Handle

The purpose is not to assume what the developer wants, but provide access to all the resources(and manipulation) they need.

If you need guardrails there are 10s of languages designed for specific purposes.

Honestly not trolling - I disagree with the "ticking time bombs" comment. If you feel that way the devs should be using Rust.

C is a sharp knife with no handle; this is it's purpose as a language and tool.

cc: theo@openbsd.org

Makes me wonder if any of the NASA staff played SDI on the amigas when no one was watching.. :)

I've been using node-red for around 7 years now for all sorts of generic web-service integration.

Fantastic app and excited to see what's next.

I've recently started working with rust and wasm - I love the esoteric nature of it - I also hate the surface area that it's creating on the client.

The paper is indeed correct - we did this 20 years ago - same architecture except with JVM instructions.

I'm entirely neutral on the merits of this tech supercycle - there are some great things being built, there are also old potholes getting uncovered that will end with some lessons re-learned.