Nothing, it’s a 5% bobcat problem. The card processors can force the merchants to eat it and there’s nothing you can do save not accepting cards, which loses you the other 95% of the market.
That's fine for some things but my grandma is not going to buy from an online store that only takes crypto. Crypto as a payment option works well for computer-related merchants or for privacy-focused merchants. Like it wouldn't be uncommon to rent a VPS with crypto but it would be strange for an online candy store to accept it.
> That's fine for some things but my grandma is not going to buy from an online store that only takes crypto.
Of course not, unless it becomes mainstream, crypto usage will always be by early adopters and technologists. I don't care if you accept cards as well, I just want to be able to pay privately with Monero.
You're right that for chargebacks specifically the only way to eliminate them would be 100% crypto, not the option of card and crypto together, which is significantly more likely. But there are other benefits for customers(privacy), which is why I use it.
Piracy never stopped the music industry, and the folks who were harmed the most by music piracy were the poor, cash-strapped billion-dollar corporations whose entire operating models already depended upon sucking wealth out of the actual, struggling artists who do all the work.
I'd posit that the book industry will turn out to be the same. Piracy will harm the bottom line of the companies already at the top while giving exposure to the authors at the bottom. The latter being the ones who often strong-armed into terrible financial deals just to gain access to book-industry's four big gatekeepers, and who likely need that exposure to help keep a roof over their heads.
Anecdotally, I'm one of those folks who end up purchasing many of the books I pirate or otherwise obtain for free, and I'm sure I'm not the only one who does this.
"Gemini researches" has been my go-to for awhile (although GPT seems to have gotten better recently in this category?).
Essentially, I use it when I truly only need an "Advanced Google" to find lots of document or website references based on only some partial understanding of "X". I don't like having it do anything with those things. Only when I need to find those things.
Claude, especially, seems to absolutely hate doing research when there are major ambiguities in your question. It's the only one of the major models that keeps playing 20 questions with me when I neither know nor care what the answers to those questions are.
“It deleted my LinkedIn account — my connection to fellow thought leaders — without warning. No confirmation. No ‘are you sure?’ No second chances. Gone.”
Naw, we just want people to know. We followed all Cursor rules, thought we had protected all API keys, and trusted the backups of a heavily used infrastructure company. Cautionary tale sharing with others.
It’s a good cautionary tale -- in hindsight the danger signs are clear, but it’s also clear why you thought it was OK and how third parties unfortunately let you down.
The “agent’s confession” is the least interesting and useful part of the whole saga. Nothing there helps to explain why the disaster happened or what kind of prompting might help avoid it.
The key mistake is accidentally giving the agent the API key, and the key letdown is the lack of capability scoping or backups in the service.
The main lessons I take are “don’t give LLMs the keys to prod” and “keep backups”. Oh, and “even if you think your setup is safe, double-check it!”
It sucks that there were a bunch of people downstream who were negatively affected by this, but this was an entirely foreseeable problem on his company's part.
Even when we consider those real problems with Railway. Software engineers have to evaluate our tools as part of our job. Those complaints about Railway, while legitimate, are still part of the typical sort of questions that every engineering team has to ask of the services they rely on:
What does API key grant us access to?
What if someone runs a delete command against our data?
How do we prepare against losing our prod database?
Etc.
And answering those questions with, "We'll just follow what their docs say, lol," is almost never good enough of an answer on its own. Which is something that most good engineers know already.
This HN submission reads like a classic case of FAFO by cheapening out with the "latest and greatest" models.
these are much better questions for an audit sheet than for engineers to come up with at integration time, mind you.
to an extent, its a good job for an agent reviewer for figuring out how screwed your setup is, other than the risk of it mucking things up as part of the review
All of the things listed that he learned could've also been learned from reading the work produced by, y'know, other Software Engineers. I learned all of those principles by reading Sandi Metz's POODR and by following prolific experts at the time, like Scott Hanselman.
But I suppose, learning things the constructive way is boring. No one wants to write the article that says, How I Learned To Do Things Right By Listening To People Who Do Things Right.
reply