Most people won't have use for it without a product. Those who do already have access. Join discord and prove yourself to gain access, otherwise you don't really have actual use for it and should stop complaining. Their releases are centered around the common end user (consumers). Don't like it, find the exploits yourself.
Leaks. Stolen exploits. Betrayal. ZzzzzzzzWhy? How is limiting access useful? What do I have to prove and why do I have to prove myself? Why can't I just develop and have fun? Who is this hurting? What does exploit development have to do with system development?
Why create walls and limit knowledge and sharing?
Leaks. Stolen exploits. Betrayal. Zzzzzzzz
Why? How is limiting access useful? What do I have to prove and why do I have to prove myself? Why can't I just develop and have fun? Who is this hurting? What does exploit development have to do with system development?
Why create walls and limit knowledge and sharing?
They create walls to prevent users accessing the tools and exploits that aren't fully developed and safe. It's to prevent idiots from playing with things they shouldn't be playing with and then blasting the devs as if it's their fault.Why? How is limiting access useful? What do I have to prove and why do I have to prove myself? Why can't I just develop and have fun? Who is this hurting? What does exploit development have to do with system development?
Why create walls and limit knowledge and sharing?
Business ethicialty and illegality, and the potential to disrupt good intentions.
The former, we know everything about it, the morality behind it, and the consequences, if caught. (However rare it may practically be.)
The latter is proven to be the most dangerous of them all compared to the former, potentially harmful to the ecosystem. Disruptions include cheating and hacking online games; ruining other players' experiences. (See PUBG online matchmaking criticisms), DDoS exploiting on Nintendo servers; stealing private information and bank accounts, and others.
They create walls to prevent users accessing the tools and exploits that aren't fully developed and safe. It's to prevent idiots from playing with things they shouldn't be playing with and then blasting the devs as if it's their fault.
If you can't get past the wall you likely shouldn't be playing with it.
This all will happen either way thou. It's not an argument to prevent access now and grant it in the summer. Same effect?
I get the argument that you don't want people to walk around with a loaded gun if they don't know how to handle guns. However, there are issues in the logic:
- In the summer, people will start forking and tempering the CFW. They may also brick. No difference.
- That you shouldn't tinker with something because you don't know it and may hurt yourself is a very bad example. In fact you should. This is essential ape-like learning. Try, fail, adapt, learn, retry, combine knowledge. Degrading somebody to a consumer to protect them means to limit people from growing. Keeping them as pets or children. Second class citizens.
- IMO you should warn about the dangers and try to mitigate them by releasing a hardware bootrom de-bricker mod.
Or that I disagree with the model entirely![]()
Well, Atmosphere is open source and they will probably do the same for fusée gelée (coldboot)Business ethicialty and illegality, and the potential to disrupt good intentions.
The former, we know everything about it, the morality behind it, and the consequences, if caught. (However rare it may practically be.)
The latter is proven to be the most dangerous of them all compared to the former, potentially harmful to the ecosystem. Disruptions include, but not limited to, cheating and hacking online games; ruining other players' experiences. (See PUBG online matchmaking criticisms), DDoS exploiting on Nintendo servers; stealing private information and bank accounts (See Sony hack), and most importantly, disrupt game developers' motivation to put forth new games on the new system (See PS Vita and the downfall of 1st/3rd party support).
Yeah, it's just hearsay. Ignore me if you knew all of this.
If you only need to learn, then you can wait until it goes public. You don't need to be doing it along side the active development to learn. So that point is pretty mute.
And in fact I would say taking the completed tools and viewing sources and "deconstructing" them is a much better way to learn than just firing at random with incomplete and inconsistent exploits hoping you figure it out.
And there is a difference between forking a completed project, modifying it, and then bricking versus devs releasing incomplete tools and exploits and people bricking with those. The former would be entirely the user's fault, the later could fall on the dev for making public tools that aren't ready for public.
