Blaming this on the user is a bit like blaming someone for doing their banking on their regular day to day computer instead of an air gapped machine.
18,642 karma · joined July 25, 2012
Blogging about annoying software at https://annoying.technology. Sometimes blogging at https://blog.notmyhostna.me.
Find me on Mastodon (https://mastodon.social/@dewey) and less likely on X (https://x/tehwey).
Email: hn@notmyhostna.me
---
1dH0mfghoB
meet.hn/city/de-Berlin
Socials: - github.com/dewey
---
Blaming this on the user is a bit like blaming someone for doing their banking on their regular day to day computer instead of an air gapped machine.
Or use the open-source version that is used by a lot of big companies and enterprises and has the enterprise features they actually need. Some of these will also have their own security team and would be flagging security issues to Gitlab in a hopefully responsible way.
There's no such thing as "just get the source and make sure there's no security issues". If it would be that easy don't you think Forgejo would've already done that?
"Just a few prompts" is the new "can do that in a weekend". In reality it still takes a while to build everything, think about what features you want to have and how to prioritize them, how to build a good UX / UI, set up payment providers etc.
Just continue to share interesting links, comment on topics you care about and don't worry about the silly internet points.
That's the reason why there's a "second chance" pool where things can be revived.
It literally just launched in 2-3 markets only, and it has the baking of banks, EU, regulatory bodies. Which is a big hurdle to clear and Taler is not even at the first hurdle yet, they got rejected in fact.
Having it integrated in every banks app is actually better, so people don’t have to set up another app and register for something. Why should they, if it’s build for being interoperable…just like using your banks Visa or Mastercard like right now.
Just give it some years, it also took a while to get instant transactions or Apple Pay and other mobile payment systems. It’s not like a web app you just deploy and you are online worldwide.
That's just not true, and I'm not talking about "you can pay with Bitcoin in the store" use case but the stable coin use case for settlement, which you can see Stripe expand a lot in the past years.
I'd rather point the agent at and authentication gem and tell it to use that, vs telling it "build authentication, make no mistakes".
Their c-levels wrote blog posts about the current state and why it happens, pretty sure they know what's going on.
Have you considered that you don't have the full context of the problem and it's not "just" a few small tweaks?