‘Mass Effect 2’ cumple 11 años de existencia y es por eso que el medio The Gamer ha publicado un curioso artículo en el que se revela que uno de sus personajes terminó siendo censurado a como originalmente fue concebido. Se trata de Jack, quien en la segunda entrega de Mass Effect aparece como compañero de escuadrón del Comandante Shepard.

El personaje se presenta también como una opción romántica que estaba disponible exclusivamente para el macho Shepard, pero esto no fue pensado así en principio. De hecho, Jack fue creado como un personaje pansexual, es decir, que siente atracción sexual, romántica o emocional hacia otras personas independientemente de su sexo o identidad de género. Sin embargo, después del lanzamiento del primer Mass Effect en 2007, Fox News organizó un panel donde atacaba fuertemente al juego por su contenido sexual.

Mass Effect había sido muy dura e injustamente criticado en los Estados Unidos por Fox News, y en ese momento tal vez más personas en el mundo pensaban que había una conexión entre la realidad y lo que se discutía en Fox News. El equipo de desarrollo de Mass Effect 2 era un equipo bastante progresista y de mente abierta, pero creo que había una preocupación a niveles bastante altos de que si [el primer] Mass Effect había sido criticado aunque solo tenía una relación gay, Liara (que en el papel técnicamente no era una relación gay porque ella era de una especie de un solo género); creo que existía la preocupación de que si eso había provocado fuego, Mass Effect 2 tenía que ser un poco cuidadoso.

Brian Kindregan, guionista de Mass Effect 2

Ahí fue cuando se tomó la decisión de censurar la verdadera dimensión romántica y sexual de Jack, algo que terminó sorprendiendo a la actriz que lo interpretó, Courtenay Taylor, pues ella siempre supo que el personaje era pansexual y así le pareció genial. Kindregan quiso dejar bien claro que la decisión no fue porque hubiera alguien homófobo en el equipo de ‘Mass Effect 2’ ni nada de eso, sino que todo respondió meramente a una presión mediática.

89 COMENTARIOS

  1. Pretty nice post. I just stumbled upon your weblog and wanted
    to say that I’ve truly enjoyed browsing your blog posts.
    In any case I’ll be subscribing to your feed and I hope you write
    again soon!

  2. в библии об картах таро, где в библии написано что нельзя гадать к
    чему сниться дальний друг славянский оберег для одинокой
    женщины
    тесты по дате рождения и имени таро семь мечей карта дня

  3. к чему снится тигр нападает на человека как снять самому с себя самую сильную порчу и сглаза суморинская тотемская икона
    божией матери молитва
    факты о созвездиях зодиака совместимость женщины близнеца с мужчиной раком по гороскопу

  4. Great read. It reminds me of the strategy we deployed last quarter. The focus on foundational stability really pays off when the algorithm shifts. Thanks for compiling this.

  5. This aligns with the «Signal Noise» theory we’ve been developing. You need enough noise to mask the signal, but not so much that you lose authority. delicate balance.

  6. Have you considered the impact of mobile-first indexing on these placements? We’ve noticed that some «desktop-safe» strategies are flagging on mobile crawls.

  7. The depth here is impressive. Most guides just skim the surface of link velocity, but your point about «natural variance» hits the nail on the head. It’s exactly what we preach to our clients.

  8. Is there a specific tool you recommend for tracking the velocity? We’ve been doing it manually but it’s becoming unscalable.

  9. I’d argue that the content relevance is even more critical now. We’ve seen perfectly good links get devalued just because the semantic match wasn’t tight enough.

  10. I bookmarked this for my team. The section on avoiding footprints is crucial. We recently audited a site that got hit exactly because they ignored that principle. Good catch.

  11. Does this apply to non-English markets as well? We’re seeing conflicting signals in our EU campaigns compared to what you’ve described here. Would love to hear your thoughts on regional variance.

  12. I’d love to see a follow-up post on how this integrates with social signals. We feel there’s a multiplier effect there that isn’t being fully utilized.

  13. Brilliant articulation of the problem. The industry has been too focused on metrics like DA/DR instead of actual traffic flow and user behavior.

  14. Actually, I have to disagree slightly with the second point. In our testing, we found that over-optimization was less of a factor than pure engagement metrics. It’s interesting to see how different niches react differently.

  15. The shift towards «entity-based» indexing is real. Your strategy seems to leverage that by building entity associations rather than just keyword matches. Smart.

  16. This is a solid breakdown. One thing I’d add is that the impact of these updates often lags by 2-3 weeks. We tracked this across multiple projects and found the recovery phase is where most people give up too early.

  17. This is a solid breakdown. One thing I’d add is that the impact of these updates often lags by 2-3 weeks. We tracked this across multiple projects and found the recovery phase is where most people give up too early.

  18. The analogy of the «immune system» is perfect. You need to build resistance before the virus (update) hits. Too many people react instead of prepare.

  19. I’ve been following this topic for a while, and your analysis on the structural shifts really adds a new perspective. We’ve noticed similar patterns in our internal data at SignalLayer, specifically regarding the volatility timeline.

  20. I bookmarked this for my team. The section on avoiding footprints is crucial. We recently audited a site that got hit exactly because they ignored that principle. Good catch.

  21. This is a solid breakdown. One thing I’d add is that the impact of these updates often lags by 2-3 weeks. We tracked this across multiple projects and found the recovery phase is where most people give up too early.

  22. The analogy of the «immune system» is perfect. You need to build resistance before the virus (update) hits. Too many people react instead of prepare.

  23. This is a solid breakdown. One thing I’d add is that the impact of these updates often lags by 2-3 weeks. We tracked this across multiple projects and found the recovery phase is where most people give up too early.

  24. This is exactly why we moved away from automated PBNs. The risk/reward ratio just doesn’t make sense anymore compared to what you’re describing.

  25. The shift towards «entity-based» indexing is real. Your strategy seems to leverage that by building entity associations rather than just keyword matches. Smart.

  26. Does this apply to non-English markets as well? We’re seeing conflicting signals in our EU campaigns compared to what you’ve described here. Would love to hear your thoughts on regional variance.

  27. I’d love to see a follow-up post on how this integrates with social signals. We feel there’s a multiplier effect there that isn’t being fully utilized.

  28. Brilliant articulation of the problem. The industry has been too focused on metrics like DA/DR instead of actual traffic flow and user behavior.

  29. Actually, I have to disagree slightly with the second point. In our testing, we found that over-optimization was less of a factor than pure engagement metrics. It’s interesting to see how different niches react differently.

  30. Does this apply to non-English markets as well? We’re seeing conflicting signals in our EU campaigns compared to what you’ve described here. Would love to hear your thoughts on regional variance.

  31. This aligns with the «Signal Noise» theory we’ve been developing. You need enough noise to mask the signal, but not so much that you lose authority. delicate balance.

  32. Thanks for the transparency. It’s refreshing to see a strategy that doesn’t rely on black-hat churn and burn. Sustainable growth is the only way forward.

  33. Have you considered the impact of mobile-first indexing on these placements? We’ve noticed that some «desktop-safe» strategies are flagging on mobile crawls.

  34. This is a solid breakdown. One thing I’d add is that the impact of these updates often lags by 2-3 weeks. We tracked this across multiple projects and found the recovery phase is where most people give up too early.

  35. We’ve been A/B testing this exact hypothesis. Group A (your method) is outperforming Group B by 40% in terms of ranking stability. The data speaks for itself.

  36. The shift towards «entity-based» indexing is real. Your strategy seems to leverage that by building entity associations rather than just keyword matches. Smart.

  37. This is the missing piece of the puzzle for us. We had the content and the technical SEO, but the off-page signal diversity was lacking. Thanks for the clarity.

  38. Spot on about the indexing delays. It’s not just about building the link anymore; it’s about the «stickiness» of the placement. We’ve been focusing heavily on that metric lately.

  39. This complements the «Entropy» theory perfectly. If you don’t introduce randomness, you’re just painting a target on your back. Glad to see others advocating for smarter engineering.

  40. We’ve been A/B testing this exact hypothesis. Group A (your method) is outperforming Group B by 40% in terms of ranking stability. The data speaks for itself.

  41. One minor correction: the update rollout was actually 14 days, not 10. But that doesn’t change your main point—the volatility window is getting wider.

  42. This is a solid breakdown. One thing I’d add is that the impact of these updates often lags by 2-3 weeks. We tracked this across multiple projects and found the recovery phase is where most people give up too early.

  43. Spot on about the indexing delays. It’s not just about building the link anymore; it’s about the «stickiness» of the placement. We’ve been focusing heavily on that metric lately.

DEJA UNA RESPUESTA

Por favor ingrese su comentario!
Por favor ingrese su nombre aquí