840 karma · joined April 30, 2016
Why the hell do I need to login to my digital wallet to access a fucking website???
We should start digging into the lives of those pushing for mandated age verification, chat control, and other privacy killing measures to show the world their true face. The public deserves to know who exactly is pushing for the "privacy law for kids" agenda.
My friend said being an engineer is not just writing code, but designing and architecting the system. I agree, but we are also moving that to AI. We are offloading the thought process to a LLM, which confirms our biases and tells us what we want to hear.
Essentially, we are also losing the software architecture and design skills because we aren't talking to other engineers/architects/designers who may approach the problen in a complete different way; we are just asking the AI to confirm our thoughts.
if there are no players, there is no money to be made, developers will be fired.
and besides, I'd rather put someone on the street if this is the multibillionaire CEO that exploits his devs, than a dev itself. And companies can, you know, slash their billionaire salaries and bonuses to comply with the law.
Literally what most expats go through in Europe. I live abroad for 6 years and here, a Central EU country, this also happens. I am trying to learn the language and even then I got told implicitly several times that I will still be treated as a foreigner, no matter how much culture and language I learn from the local country.
I wouldn't be surprised if they made up the statistics to justify the enslopification.
Plus, they also mention they check if fixes are available for the bugs they found. What are the chances they are re-reporting old bugs just to inflate their numbers? Bugs that were already fixed?
And how can we be sure their reassessment is not artifically increasing the severity of the CVEs found just to create FUD and sell their product?
I hate it that we had decades of progress to have computers become a very expensive hobby because some dudes high on fentanyl think some text prediction model that destroys the planet is worth a trillion dollars.
There are financial laws that banks must comply with and one of them require banks to share information with the Central Bank about potential fraudulent transactions. Having a payment system using the CB's infrastructure doesn't change anything. They are still required to comply to bank secrecy laws and can only investigate your transactions after obtaining a warrant.
Enshittificstion incoming.
When sales were bad we didn't have budget cuts. Now that we have stable profit margins, we are cutting costs.
Honestly, if the only way to secure your banking system is by locking down users' devices, there is something really bad going on at your end, security-wise. Your system should be secure even without locking down user hardware.
I can perhaps agree that the idea of SB can be good, but it was designed (and is used) in a bad way. Just look at how many distros do not support SB.
DMCA is abused every. single. time.
We have over 30 years of the world wide web and for these more than 3 decades this was never a problem. Suddenly, we "need" to create new technology that seem to be security features, but are essentially just being used for evil, thus being inherently bad.
It's not like these technologies were created for the greater good and misappropriated by bad actors. They were proposed by bad actors in the first place, they cannot not be inherently good.
Ideally there shouldn't be standards for this. What we have already is enough.
Companies claiming they are closing down their services/devices to protect the users is total BS. Facebook has admitted they get 10% of their ad revenue from scams, and that's the reason they won't go after scammers on their platforms.
Same can be said for Google. They could come up with numerous ways to block bots or make captchas harder for actual bots (while also not flagging every non-Chrome user as a potential bot, like they do nowadays), but they pretend this is an unsolvable problem that requires a nuclear solution, it used to be Web DRM but now it's called Fraud Defense.
Saying something like "the problem is not hardware attestation, but that they don't use ZKP".
You are normalizing the new behavior. You shouldn't. It doesn't matter if they use ZKP or the latest, secure technology for hardware attestation. The issue is hardware attestation. It's the same with age ID. The issue is not that Age ID is prone to data leaks, the problem itself is called Age ID.
None of the alternatives you cited are as complicated as GitHub. Also, GitHub started with this Actions bullshit which is just reinventing the CI wheel and overcomplicating stuff that was already made simple. The one thing I hate Forgejo about is for being compatible with Actions and promoting is as the way to go for CI, when you have much better alternatives like Woodpecker, where you can actually understand the underlying code for your CI/CD pipelines.