hrdwdmrbl

Blockchain people have always hated chargebacks, but any successful payment rail needs a system for dispute resolution.

I run e-commerce business and I’ve received bullshit chargebacks before. But I’m also a consumer and I’ve filed legitimate chargebacks before.

Related: I’ve also had my bank send money to the wrong place before.

There must be some means of reversing transactions in some cases. Some arbitration mechanism. Some dispute resolution procedure. Some means of doing escrow.

It does still compare well against the others: https://www.vals.ai/benchmarks/swebench-2025-08-27

I remember Notion talking about adding this YEARS ago. It has literally taken them YEARS to build this. So yes, very complex

And Mint should be combined with Pop OS?

Can someone compare their tech to the current research frontier of ZK-p tech?

The reason I ask is that I know that many teams working in the b-word field are _regularly_ making great progress. So I'm just wondering if this work is actually novel / useful or whether it's Google releasing something that is already stale.

But actually released in 2024?

CBDCs and privacy don't necessarily need to be at odds!

Cryptography makes it possible to have both! We can have a payment system run by the government and at the same time not need to give up our privacy!

Likely why the article said that it wouldn’t lead to any immediate applications.

Cause from the headline, one would get all excited about the applications

I felt like this link is missing some important context.

History: Initially started by Mozilla in 2012. They laid off the team off in 2020 and transferred the project to the Linux Foundation. Source: https://en.wikipedia.org/wiki/Servo_(software)

2025 Roadmap: https://github.com/servo/servo/wiki/Roadmap

Just because of job availability, I've been a JS (Node, React, Next, etc.) dev for almost a decade now. I still feel much more productive with Rails.

Rails isn't the right tool for every job, but I find that it's the right tool more often than not.

Rails is architected really well. Many decisions don't need to be made at all, and everything has a place. Plus, it's very friendly to extensibility and has a healthy ecosystem. It's mostly about the code that I don't need to write. It's really years beyond most other frameworks. Next will get there, but it will take it another 5 years. No shade on others, but Rails is just well built software with many years of learning and improving.

For highly reactive or "dynamic" systems, it probably isn't the right tool. Building a Figma or Notion. As @graypegg said in their comment, most websites work best as "CRUD forms". Though I would have said the same about email, but Hey.com exists so YMMV...

You could try cmd+f their ToS to see if there is a legal appeals process. Do whatever it says to do when there is a dispute. If disputes must be resolved through arbitration, then demand arbitration. I've had this work with 2 different companies in the past. Legal teams seem to always be real humans who reply :)

It's surprisingly small! In order to deliver enough light, I would have assume it would need to be maybe half the size of the area it needs to illuminate.

Would it ever make sense to build one for ones own home? I guess it must be far enough away for the light to spread out enough...

What is the magnitude of the effect size? The readme provides no information about what kind of results should be expected or might result.

I think this is the one that broke Time Machine for everyone with a third-party firewall wall

Some of these rules do support autocorrect

It does help at some margin to make code more readable. Humans just aren't that great at reading and understanding code. It has been said: "Write for humans, not computers because computers will understand what you wrote no matter how badly written". So if you're writing code on a team, do your co-workers and your future-self a favour and write code that's easy to read. It won't run any better or with fewer bugs, but it will be easier to understand later, easier to be understood by others, and "wishful thinking here": easier to debug.

Why does it matter when there is auto-fix-on-save? I just write whatever, hit ctrl+s and the code is fixed. The result: The code is "fixed" based on whatever rule and it doesn't cost me a thing. I don't think about it and I don't lift a finger.

But I do personally appreciate the tidiness of code-consistency.

It isn't mentioned, but I would think that this works for cryonics... the ice crystals were one of the biggest sticking points. Well, aside from the original cause of death of course

Also, there's no indication when a pin is 1 or multiple deaths

I would really like to know why he continues to work a day-job. Does he enjoy writing technical documentation that much?

Yes

This telling by Toner has the ring of truth to it over the reason for Sam's ouster. It matches. Whatever I think of Sam personally, I would likely have done the same thing in her shoes. The CEO lying to and deceiving the board multiple times is a pretty serious red line.

is a gold mine*

present tense :)

Yes, 2 out of how many? The denominator is important here.

It seems like a major lapse in product innovation that Github has not come out with something like this. They don't even have something to help you when the indentation changes, they usually just show it as a giant add & remove. Their diff viewer can and should be smarter.

Any idea how this compares with UTM in terms of features or what it's intended use-case or strengths are?

This is the horseshoe theory of... radical extremes?

Fun tinkering like that is not about saving money. It's about the journey, not the destination.

+1 for the Nx00 series of chips. I just bought myself a pre-built mini pc with an N100. Low power, good price, great performance.

I wonder if in a few years they might not eat the whole mini PC market. If the price can come down such that they’re competitive with the various kinds of Pis…

Others have said that RAG is only good up to a few 100s of files, eh? And since this is based on IndexLlama which is RAG-based, this would have the same limitation, eh?