All posts by TheOneFootTallBrickWall

<div class="quote"><i> <p>Chuck123456 wrote: </p> <div class="quote"> <p>TheOneFootTallBrickWall wrote: I'm not saying I don't like it. I am saying if it is a huge hassle for everyone, why not end it until some regulations are placed. Just a suggestion. </p> </i></div>
<p>But the regulations just were placed. </p> </div> <p>What I am saying is that it seems like there is some discord here with the new rules, so in my opinion, it should be halted until it can be addressed at the convention. </p><p><span style="color: #367588;">TheOneFootTallBrickWall</span> <small> <span style="color: #367588;">(sign!)</span> </small> 07:34, November 9, 2017 (UTC) </p>

<p>I'm not saying I don't like it. I am saying if it is a huge hassle for everyone, why not end it until some regulations are placed. Just a suggestion. </p><p><span style="color: #367588;">TheOneFootTallBrickWall</span> <small> <span style="color: #367588;">(sign!)</span> </small> 05:23, November 9, 2017 (UTC) </p>

<p>can we like maybe cancel H&H all together? </p><p><span style="color: #367588;">TheOneFootTallBrickWall</span> <small> <span style="color: #367588;">(sign!)</span> </small> 05:19, November 9, 2017 (UTC) </p>

<div class="quote"><i> <p>Oprah Side wrote: How about just getting rid of game threads altogether? </p> </i></div>
<p>Can we please? </p><p><span style="color: #367588;">TheOneFootTallBrickWall</span> <small> <span style="color: #367588;">(sign!)</span> </small> 20:04, October 22, 2017 (UTC) </p>

<div class="quote"><i> <p>Chuck123456 wrote: It's not fun when there are so many of them. The number of game threads is really overwhelming nowadays and I think users should calm down with them a bit. There's so many of them they flood the wiki activity. I miss the times when the game threads were quality over quantity. </p> </i></div>
<p>Could not have said it better. </p><p><span style="color: #367588;">TheOneFootTallBrickWall</span> <small> <span style="color: #367588;">(sign!)</span> </small> 22:16, October 21, 2017 (UTC) </p>

<p>Can we like not have as many game threads in general? </p><p><span style="color: #367588;">TheOneFootTallBrickWall</span> <small> <span style="color: #367588;">(sign!)</span> </small> 22:03, October 21, 2017 (UTC) </p>

<p>You have 270 mainspace edits. </p><p><span style="color: #367588;">TheOneFootTallBrickWall</span> <small> <span style="color: #367588;">(sign!)</span> </small> 05:03, October 19, 2017 (UTC) </p>

<p>-10 SpongeBot, -5 onion </p>

<p>We should do a convention. </p><p><span style="color: #367588;">TheOneFootTallBrickWall</span> <small> <span style="color: #367588;">(sign!)</span> </small> 20:26, October 16, 2017 (UTC) </p>

<p>I have the invite, if you want it. </p><p><span style="color: #367588;">TheOneFootTallBrickWall</span> <small> <span style="color: #367588;">(sign!)</span> </small> 22:39, August 28, 2017 (UTC) </p>

<div class="quote"><i> <p>Original Authority wrote: Not to jump in on this discussion, but in my opinion, the utter disrespect that some of the users on this community are showing to others is ridiculous. </p> <hr><p>Furthermore, you seem to misunderstand the whole concept of what FANDOM staff are. You seem to think that, because you have a "proposal system" that staff are bound by it; <i>they are not.</i> Staff do not have to do something because you said so, it just doesn't work like that. And to point-blank refuse when they have given you an opportunity is also hugely disrespectful. </p> <hr><p>Additionally, this whole situation <i>is a violation of FANDOM ToU</i>. You have been told that by using the CTab in the way you are is impairing the Mercury skin and the way information is displayed on mobile, by blocking it from being displayed. I do believe that this violates: </p><blockquote>Not to intentionally block, remove, or otherwise obstruct the proper functioning and view of advertisements, and/or user interface and functionality</blockquote> I do believe that you are, obstructing the functionality, and intentionally blocking it. <hr><p>Just to add to this: </p> <div class="quote"> <p>No, that's not how it works on this wiki. Necessity is when proposals should be most used. If you or FishTank disobey the rules, then I will ask a staff member to demote you/him. </p> </i></div>
<p>This is the weirdest thing I've ever seen on the whole time I've been on FANDOM. You've been told something you don't like so you're sulking to another member of staff? </p> </div> <p>It does break the rules. Therefore, it needs to be fixed. </p><p><span style="color: #367588;">TheOneFootTallBrickWall</span> <small> <span style="color: #367588;">(sign!)</span> </small> 18:43, August 27, 2017 (UTC) </p>

<p>Can we move back to the original conversation, please? Thanks. </p><p><span style="color: #367588;">TheOneFootTallBrickWall</span> <small> <span style="color: #367588;">(sign!)</span> </small> 18:28, August 27, 2017 (UTC) </p>

<div class="quote"><i> <p>120d wrote: </p> <div class="quote">Original Authority wrote:
<div class="quote"> <p>This isn't about the CTab. I fully agree that that needs to change. This is about the infobox. Do you see anything wrong with the current infobx? </p> </i></div>
Yes; there are about a million tabbers nested within one another. The Mr Krabs article took 10 seconds solid to load. Additionally, what are you giving up? What do you have now that you can't have with PI? </div> <p>We would be giving up the tabbers. That has been my whole point. Also, did you just complain that it takes ten seconds to load a page? I am pretty sure ten seconds is a great speed. </p> </div> <p>120d, are you sure you know what you are talking about? 10 seconds is not remotely a good time to load a page. </p><p><span style="color: #367588;">TheOneFootTallBrickWall</span> <small> <span style="color: #367588;">(sign!)</span> </small> 18:18, August 27, 2017 (UTC) </p>

<p>120d, it's gonna happen if it's not fixed. Period. You won't change that. At all. </p><p><span style="color: #367588;">TheOneFootTallBrickWall</span> <small> <span style="color: #367588;">(sign!)</span> </small> 18:15, August 27, 2017 (UTC) </p>

<div class="quote"><i> <p>Original Authority wrote: Not to jump in on this discussion, but in my opinion, the utter disrespect that some of the users on this community are showing to others is ridiculous. </p> <hr><p>Furthermore, you seem to misunderstand the whole concept of what FANDOM staff are. You seem to think that, because you have a "proposal system" that staff are bound by it; <i>they are not.</i> Staff do not have to do something because you said so, it just doesn't work like that. And to point-blank refuse when they have given you an opportunity is also hugely disrespectful. </p> <hr><p>Additionally, this whole situation <i>is a violation of FANDOM ToU</i>. You have been told that by using the CTab in the way you are is impairing the Mercury skin and the way information is displayed on mobile, by blocking it from being displayed. I do believe that this violates: </p><blockquote>Not to intentionally block, remove, or otherwise obstruct the proper functioning and view of advertisements, and/or user interface and functionality</blockquote> I do believe that you are, obstructing the functionality, and intentionally blocking it. </i></div>
<p>Exactly, thank you Original Authority! Could not have said it better myself. </p><p><span style="color: #367588;">TheOneFootTallBrickWall</span> <small> <span style="color: #367588;">(sign!)</span> </small> 18:10, August 27, 2017 (UTC) </p>

<p>This is not up for debate, if it's not fixed by the deadline, then it will be fixed, regardless of what the community says. They are going to do it if it's not fixed. So deal with it, or find a solution to fix the infoboxes. </p><p><span style="color: #367588;">TheOneFootTallBrickWall</span> <small> <span style="color: #367588;">(sign!)</span> </small> 18:07, August 27, 2017 (UTC) </p>

<div class="quote"><i> <p>120d wrote: </p> <div class="quote">FishTank wrote:
As an example, the "respective gallery page" would be the existing gallery subpage relative to the main article. Different communities may have different terms for it. E.g.: SpongeBob_SquarePants_(character) => SpongeBob_SquarePants_(character)/gallery. <p>If it's the beginning of a plan, then we know where to start. Let's outline it. ? </p> </i></div>
<p>No, you know where to start. I will not be participating in your plan when I don't want you to mess with the infoboxes. </p> </div> <p>Perfect. You don't need to participate in the conversation, then. </p>

<p>It is everyone's wiki. You can't say it's not his because it is his, and yours, and mine. He works for the website, so if we don't meet the requirements by the time stated, he can fix the wiki. He is not taking over. He is helping the community. </p>

<div class="quote"><i> <p>Sawpog46 wrote: </p> <div class="quote"> <p>FishTank wrote: Avoiding a wall of text, and will be succinct. Thank you to all parties that have contributed comments. </p><p></p><blockquote class="quote">Those issues (navigation with no content hiding, nested tabbers in the infobox) must be resolved. If your community chooses to make the effort, please do so by 2017-09-15. Otherwise, FANDOM will need to intervene directly and make the changes needed in a manner we feel is best. Not resolving these issues hurts your community significantly, and blocking parts of the articles to force desktop views is not an acceptable compromise.</blockquote> <p>There's nothing at all in there about Portable Infoboxes. FANDOM is not promoting PIs on ESB at this time, though internal parties are. Discussion of Portable Infoboxes here is a distracting conflation. </p><p>Discussion on how the remaining issue (down from two, due to coordination in this thread) will be resolved is encouraged. If it will be resolved is predetermined; one way or another it will be. The line of thought that problems shouldn't be fixed has gone on far longer than it should. </p><p>Please move the nested tabs from the infoboxes into galleries on the respective Gallery pages, or I will do so myself on or after the 15th. You can preclude that by coming up with a workable alternative in this thread. </p> </i></div>
<p>Why is there a deadline? Discussions on this wiki are revisited multiple times and brought back up. Hell a discussion on "Krusty Krab" vs "The Krusty Krab" went on for a *long* time. You can't just come in here and demand a deadline. </p> </div> <p>Actually, he can. It is hurting the wiki. </p>

<div class="quote"><i> <p>Speedit wrote: There's hundreds of thousands of visitors on mobile each month, and you will lose a lot of them if 363 images all load on the page. It would also cost mobile data users money. </p><p>Workarounds, like searching the character name, or requesting the desktop page, are kinda unwieldy. It's not really what an average reader would do. The tabs may not show, but as FishTank said, the images will still load and bog the mobile browser down. </p><p>Mercury has much clearer text and layout than Oasis. It is <i>the</i> mobile experience, and it would do well if it wasn't for the way the tabbers disrupt that. FANDOM isn't likely to change how it directs users in order to avoid these pitfalls. </p><p>About #16, I didn't make it to the content on the main character pages, and there was no direction to bypass the large bunch of images and get to that content. So I didn't see the main body of the article, and felt excluded from the wiki's content. </p><p>I'll probably be told I have no evidence for this, considering FishTank has a lot more access to FANDOM's statistics (as nearly everything has anonymous tracking). Still, it seems like mobile users are 61% more likely to bounce off the wiki than desktop users: </p>

• 441.5K monthly mobile visitors vs. 272.1K desktop ones.
• 1.3M views from mobile visitors and 1.3M from desktop visitors.
• Comparing mobile & desktop views per visitor: (1.3/441)/(1.3/272) = 0.62.
• The inverse of that is visits per views (likeliness to leave): 1/0.62 = 1.612.
• So mobile users are probably 61.2% more likely to leave.

<p>Assuming that users will work around these content portability issues is a massive stretch that isn't really backed up. These issues are harming the mobile experience. </p> </i></div>
<p>Exactly. Thank you Speedit. </p>