It's clearly not big enough. Might have to make it bigger.
And no. I am not going to begin unrelated news articles with a Gateway snippet just for you guys. Not checking the front page isn't on me, it's like trying to pin something on me because my article was made under the Temp Light theme when the dark theme kids can't read.
Now, now - let's not exaggerate here.
The point here is that the only thing we
could do to satisfy the
"need" for information about this 100% would be to leave a huge, permanent sticky on the top of the frontpage with all the information about bricks that's been gathered so far, and that's not convenient to anybody. It would make navigation difficult and it would prevent people from reading about actual, new and exciting news because the headlines would be pushed to the bottom of the page - we don't want that.
GBATemp.net is slowly progressing towards becoming a gaming and homebrew news portal, and that's a good thing. We want to provide our users with exciting developments from the industry as well as the scene, but we're only human. We do our best to keep the frontpage both consistent and readable and we believe that we've done enough to inform our users about the dangers involving the use of Beta firmware.
We sincerely appreciate the research done by
gamesquest1, it sheds a new light on the matter and narrows down the issue, but we simply don't have evidence to support:
- A) That there's actually bricking code in the Launchers, because we don't have the source code or any snippets of it
- B) That this issue is related to the alleged bricking code and not a separate glitch altogether
- C) That it was put into the firmware deliberately and not by accident
- D) That it's the sole reason for the bricks
We're at the stage of gathering information about the issue and we'd like to see what the Gateway Team has to say. As a News outlet, we need to remain impartial, we can't put water on a rumour mill, however legitimate the rumour seems to be. We want to have statements from both sides and we
sincerely encourage further research into the matter. I, for one, would like to see if the same issue occurs on
different Gateway firmwares. Does the same thing happen in 1.2 or 2.0B1? I'd like to know, because if it does, the whole thing might be a separate glitch altogether. Those concerns, among others, are the reason why we're not posting this on the frontpage
yet. Once we're better-informed, we'll consider improving upon more all-encompasing articles. Believe me when I say that when the word from Gateway's out, we'll be the first to frontpage it. In other words...
Keep Calm and Carry on GBATemping, people!