Editing User talk:BwE
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 14: | Line 14: | ||
The end goal is to have sections templated, so it can either be linked (like I have done now), or embedded (like the NAND/NOR tables are on the (way too long) Hardware Flashing page. | The end goal is to have sections templated, so it can either be linked (like I have done now), or embedded (like the NAND/NOR tables are on the (way too long) Hardware Flashing page. | ||
This makes it easier to share knowledge/experience and minimalise redunancy. Also, with shorter pages, pageloads are improved. Plus with splitting, the pages can use navigationblocks (like most hardware pages now). That is also why I am splitting off alot of other pages (e.g. Hypervisor Reversing, Flash Page, Hardware pages etc). | This makes it easier to share knowledge/experience and minimalise redunancy. Also, with shorter pages, pageloads are improved. Plus with splitting, the pages can use navigationblocks (like most hardware pages now). That is also why I am splitting off alot of other pages (e.g. Hypervisor Reversing, Flash Page, Hardware pages etc). | ||
The debricking was a confusing (I'll get to that) lengthy text, that assumed one single reason/example and would confuse users even more (there is no limit to user stupidity), because you can replicate the exact errors by at least 5 other hardware or flash faults. For this reason I choose to refer to the main Errorstate page, which then could be used for more indepth problem solving, while keeping an eye on the fact that PS3 has over 1500 components that can flaw anytime. | The debricking was a confusing (I'll get to that) lengthy text, that assumed one single reason/example and would confuse users even more (there is no limit to user stupidity), because you can replicate the exact errors by at least 5 other hardware or flash faults. For this reason I choose to refer to the main Errorstate page, which then could be used for more indepth problem solving, while keeping an eye on the fact that PS3 has over 1500 components that can flaw anytime. | ||
The page edit(s) is/are kept in history, so nothing is lost forever, perhaps it can be handy in future in a reformed way, now our noses point the same way [[User:Euss|Euss]] | The page edit(s) is/are kept in history, so nothing is lost forever, perhaps it can be handy in future in a reformed way, now our noses point the same way [[User:Euss|Euss]] | ||