#Greg Kogan

[shadowfreak98]

yeah I took a lot of sketches that I had and just lined and colored. pfft. i like how it turned out

[forgot the white in Qrow’s hair... uhm... whoops?]

[worstshippoll]

WORST SHIP POLL 2023 BRACKET

ROUND ONE: PART ONE, consisting of the LEFT side of the bracket, will begin on 4/18 at 2PM PST.

This post will be edited as rounds progress with results and dates/times for the next round.

Plain text list (including abbreviated series names) under the cut.

Dazai Osamu/Nakahara Chuuya (BSD) VS Crowley/Aziraphale (GOOD OMENS)

Steve Harrington/Eddie Munson (STRANGER THINGS) VS Reylo (STAR WARS)

Star Butterfly/Marco Diaz (SVTFOE) VS Spamton/Jevil (UTDR)

Harrier Du Bois/Kim Kitsuragi (DE) VS Herbert West/Daniel Cain (REANIMATOR)

Catra/Adora (SPOP) VS Akira Kurusu/Goro Akechi (P5)

Lapis/Peridot (SU) VS Tenth Doctor/Rose Tyler (DR WHO)

Cole Cassidy/Hanzo Shimada (OVERWATCH) VS Takami Keigo/Todoroki Enji (BNHA)

Beauregard Lionett/Jester Lavorre (CRITROLE) VS Raiden Ei/Yae Miko (GI)

Katsuki Bakugou/Izuku Midoriya (BNHA) VS Jack Hakrness/Ianto Jones (TORCHWOOD) 

Marisa Kirisame/Reimu Hakurei (TOUHOU) VS Rhys Strongfork/Handsome Jack (BORDERLANDS)

Kaname Madoka/ Homura Akemi (PMMM) VS Alhaithem/Kaveh (GI)

Ryuki Kuruto/Date Kaname (AI Somnium) VS Ethan Winters/Chris Redfield (RE7/8)

Hunter/Willow Park (TOH) VS Childe/Zhongli (GI)

John Watson/ Sherlock Holmes (BBC SHERLOCK) VS Dimple/Arataka Reigen (MP100)

Azula/Ty Lee (ATLA) VS Zuko/Katara (ATLA)

Nico Yazawa/Maki Nishikino (LL) VS Dean Winchester/Castiel (SPN)

Sasuke Uchiha/Sakura Haruno (NARUTO) VS Vriska Serket/Terezi Pyrope(HS)

Benry/Gordon Freeman (HLRVAI) VS Keith Kogane/Lance Mcclain (VLD)

Kazuhira Miller/Revolver Ocelot (MGS) VS Jotaro Kujo/Noriaki Kakyoin (JJBAP3)

Dave Strider/Karkat Vantas(HS) VS Sonic the Hedgehog/Shadow the Hedgehog(STH)

Mako/Korra (ATLA) VS The Onceler/The Onceler (THE LORAX)

Lavernius Tucker/Agent Washington (RVB) VS Chris Hartley/Josh Washington (UNTIL DAWN)

Piers/Raihan (PSWSH) VS Natsuki/Yuri (DDLC)

Greg House/James Wilson (HOUSE MD) VS Callie Torres/Arizona Robbins (GREY'S ANATOMY)

Kazuma Kiryu/Goro Majima (YAKUZA) VS Light Yagami/Misa Amane (DEATH NOTE)

Chell/GLaDOS (PORTAL) VS Adam Faulkner-Stanheight/Lawrence Gordon (SAW)

Tom Wambsgans/Greg Hirsch (SUCCESSION) VS Ryo Asuka/Akira Fudo (DEVILMAN)

Tsukasa Tenma/Kamishiro Rui (PRSK) VS Qrow Branwen/James Ironwood (RWBY)

Batman/The Joker (BATMAN) VS Getou Suguru/Satoru Gojo (JJK)

Mark Hoffman/Peter Strahn (SAW) VS Iki Hiyori/Yukine (NORAGAMI)

Jayce/Viktor (ARCANE) VS Hannibal Lector/Will Graham (HANNIBAL)

Dirk Strider/Jake English (HS) VS Ash/Serena (POKEMON)

[is-your-blorbo-a-bottom]

Welcome to Is Your Blorbo a Bottom?

This is a polling blog to vote if you favorite characters are a bottom, top, or switch!

Submission rule

- please only characters 18+

- please give me characters name and what they are from

- only one character per ask (you can submit as many as you want just separate them into their own asks)

- check under the cut for any characters already submitted

Please submit all your favorite characters!

Characters submitted in alphabetical order (by first name)

A

Anakin Skywalker- Star Wars

Astarion- Baldur’s Gate 3

B

Blitzø- Helluva Boss

Bucky Barnes- the MCU

C

Castiel- Supernatural

Chris Redfield- Resident Evil

Cole- Lego Ninjago

Crowley- good omens

D

Dean Winchester- supernatural

Death- Discworld

Double Trouble- She-Ra

E

Eleanor Shellstrop- The Good Place

G

Gale Dekarios - Baldur's Gate 3

Gallagher - Honkai Star Rail

Greg House- House MD

H

Hawks from My Hero Academia

I

Isami Ao- Bang Brave Bang Bravern

J

Jace Beleren- Magic the Gathering

Janus Sanders- Sanders Sides

Jolyne Cujoh- JoJo's Bizarre Adventure

K

Kazi- The Dragon Prince

Keiji Shinogi- Your Turn to Die

Keith Kogane- Voltron

L

Lammio- the Unknown Soldier

Laois- dungeon meshi

Leonard Church- Red vs Blue

Leone Abbacchio - JoJo's Bizarre Adventure

Loona- Helluva Boss

Lucien La'chance- Oblivion

Lucifer- Hazbin Hotel

M

macaque- lego monkie kid

maglor- the silmarillion

Merlin- BBC Merlin

Miles Edgeworth- Ace Attorney

N

Needles- The Magnus Protocol

Nori Doorman- Murder Drones

O

Oko- Magic the Gathering

Optimus Prime- Transformers: Prime

P

PIXAL- Lego Ninjago

Prince Sidon from Legend of Zelda: Breath of the Wild

Q

Quentin Coldwater- The Magicians

R

Reiner Braun- attack on titan

Rei Suwa- Buddy Daddies

Rikiel- jojos bizarre adventure

ryomen sukuna- jujutsu kaisen

S

Sampo Koski - Honkai Star Rail

Senshi- Delicious in Dungeon/Dungeon Meshi

Seth Gordon- All For The Game

Shin Tsukimi- Your Turn to Die

Stolas - Helluva Boss

T

The Lamb - Cult of the Lamb

The tenth Doctor - Doctor Who

Tomura Shigaraki - My Hero Academia

V

Vash the Stampede- Trigun

Virgil Sanders- Sanders Sides

Vox- Hazbin hotel

W

Will Halstead- Chicago Med

William Birkin- Resident evil 2

Wolf on the Cookie Crisp Cereal Box

[naeldeus]

jjk 245

Gege gives me nothing and every week I'm still disappointed.

It's weird being excited to watch the anime every week to then go to the manga and just be saddened that it all leads to nothing.

I thought we would get some Yuuji-Sukuna interaction, something we could chew on for a bit, slow down the action for a moment, but we skipped right past it for a downright nonsensical conclusion.

The more I think about it, it does seem to be a trend. Gege always focuses on really obscure things that seem detrimental to the overall story. The focus on the Culling Game ruleset, only for it to not matter because Kenjaku threatened Kogane into doing what he wants, the random comedy fight with Takaba, last week's Law&Order episode* only for Greg to speed run the court. It's not even fun to theorize anymore, he just skips right past anything meaty every time. Where is Gege's editor in all this, seriously?

*This one is particularly bad because the more Gege zooms past any emotional beats, the more I keep thinking the JujuHigh crew really sent Gojo out like a lamb to slaughter and thought nothing of it, which is really fucked up.

Favorite reddit comment this week:

At least I got to see my boy Yuuji this week!

[tak4hir0]

It starts with someone posting an AWS press release in the company chat. “AWS Announces FooBar,” the headline reads. The announcement skirts around technical details, as usual, but contains a worrying amount of buzzwords that overlap with the company’s product. Somebody responds with a grimace emoji 😬. Others reply with all the ways AWS FooBar is totally not like our product and, anyway, ours is better, and, and… The flurry of replies betrays their true collective emotion: We’re screwed. They’re right to be worried. As a marketing consultant to enterprise software startups for the past six years, I’ve helped companies navigate and succeed in this scenario at least eight times.[1] In this article I explain why every software startup should be prepared for this scenario, why the initial panic is justified, and how to position products against alternatives from “Big Cloud” (AWS, Azure, GCP). Every Software Startup Should Be Prepared to Compete Against AWS, Azure, and GCP Even if you’re not competing with Big Cloud today, there’s a good chance you will soon. This is especially true if your product is in the serverless, stream processing, machine learning, containerization, IoT, data warehousing, or batch processing space. Those are the fastest growing cloud services—according to a survey from Rightscale—and Big Cloud companies know it. Big Cloud companies earn the bulk of their revenues from metered billing of storage, compute, and streaming. Having turned those infrastructure workloads into commodities, the Big Cloud companies are in a race to provide differentiated products higher in the stack just to bring more customers onto their infrastructure. That is evident in the sheer size of their product portfolios and pace of product releases: AWS has 182 products and made 83 major product announcements (launches or major releases) in 2018.[2] You Should Worry When Big Cloud Launches a Similar Product There is a tendency, upon learning of a Big Cloud intrusion, to bury our heads. Internal emails will include explanations for why the Big Cloud product “is not really competitive,” “is not as good as ours,” and “can only take a small piece of the market.” Maybe those things turn true, but there are good reasons to at least take the competition seriously: 1. Resource Imbalance Big Cloud companies can win by brute force: Pouring obscene amounts of resources into engineering, marketing, and sales until they outrun or outlast the competition. It won’t be enough to have a better product by a smidgen, or to have a small head start in the market. 2. Complicated Relationship Startups participating in Big Cloud partner programs, such as the AWS Partner Network, will find themselves sharing sensitive information and valuable resources with the competition. For them, leaving the program would mean relinquishing a potentially significant acquisition channel. Meanwhile, Big Cloud wouldn’t flinch at losing a startup partner, and therefore has no incentive to be prudent with the information it obtains. 3. Broad Reach and Influence AWS can get on stage and influence a thousand people, or send an email and influence a hundred thousand, or play a TV commercial and influence millions. Using their broad reach and brand recognition, Big Cloud can influence how people perceive the market and make their decisions. 4. Captive Audience Even better than a reachable audience is a captive audience. Big Cloud companies have millions of users, already running on their platforms and familiar with their products. They can reach this audience to upsell and cross-sell products in a few clicks. 5. Pricing The objective for most Big Cloud products is not to make profit, but to bring customers onto the platform and increase infrastructure usage (compute, storage, streaming). Therefore the products can be users as loss leaders: Priced at very low or no cost, provided they drive increased infrastructure usage. For startups, at best this eliminates the option to compete on price, at worst it forces them to lower prices with no way to make up for it. 6. Easy Access Engineers at companies already running on AWS can buy, deploy, and integrate an AWS product before their coffee cools. Metered billing means there are no upfront costs or negotiations. Being on the same platform means seamless integration between tools and services. 7. Early decision In the past, decision makers had to choose whether to build a solution in-house or purchase software from a vendor. Today, the low prices, easy access, and brainshare of Big Cloud offerings create a new option for decision makers: Use what their cloud platform is offering. It used to be “buy vs build.” Now it’s “buy vs build vs big cloud.” For software startups, this means they can be ruled out even earlier in the buying process, before any conversation, evaluation, or feature comparison takes place. How to Win Against Big Cloud Prepare Attend trade shows, seek out insiders who might tip you off about looming competition, and generally keep an ear to the ground. Advance warning will allow you to dredge a wider moat, prepare a response, and avoid company-wide panic when the press release hits. Having a pre-emptive strategy for competing against Big Cloud will make it possible to ride the initial wave of hype following their announcement, leveraging their campaign to bring attention to your own product, and pulling away from other startups who will be caught by surprise. With the right strategy and execution, the launch of a competitive product from Big Cloud could be turned into a positive inflection point for the startup and its market. Even if you are not competing against Big Cloud now, good preparation will improve reaction time and chances of succeeding when the moment comes. If your product even remotely encourages more use of cloud compute, storage, or streaming, then you should prepare. Support Multi-Cloud According to the same survey by Rightscale, 84% of enterprise organizations have applications and workflows scattered across on-prem, private cloud, and public cloud environments. If you are “the #1 solution for X on AWS,” and AWS launches a solution for X, you become a distant second choice. If your product works across a variety of environments, then it will remain a viable—and probably better—option for buyers that want to solve an organization-wide problem. Those buyers will need a solution that works across their entire infrastructure, not just the part on AWS. Support for multi-cloud and hybrid environments is one of the most common reasons I hear from decision makers for why they bought software instead of using the cloud offering. Multi-cloud and hybrid-environment support could be a decisive advantage over Big Cloud offerings. And, unlike a small lead in features, this advantage will last a while: Big Cloud companies have little incentive to make products for other platforms. With options like Kubernetes and Gravity, adding that capability to products may not require a monumental engineering effort. Think Twice Before Open-Sourcing While it helps with awareness and credibility, open-sourcing products in whole or in part lowers the barrier to entry for competitors. For any new and sufficiently popular open-source product X, it is trivial for Big Cloud to introduce a “Managed X” offering, as AWS did with Elasticsearch, or to pair it with their security products and package it as “X for Enterprise,” as AWS did with MongoDB and as Google did with Kubernetes. (The Kubernetes story has a few fun twists in it: First, the company Docker released an open-source containerization product. By the time they launched a paid container management service, Google already developed and open-sourced their own container management solution, Kubernetes, which won the market. Then, after Docker released an enterprise solution for managed containers, Google beat Docker once again with the launch of Google Kubernetes Engine.) For example, when AWS launched a “Fully managed, scalable, and secure” packaging of the open-source software Elasticsearch, it led the makers of that software to admit: “… Amazon competes with us for potential customers, and while Amazon cannot provide our proprietary software, the pricing of Amazon’s offerings may limit our ability to adjust the price of our products.” The questionable benefits of open-core business models, combined with the vulnerability it opens to competition from Big Cloud companies—who are not ashamed of taking advantage—is why I advise companies to guard their product and not go open-source, or to limit their vulnerability if they already open-sourced, as Confluent did by changing their licensing when AWS pulled the same maneuver with Kafka, the open-source software from Confluent. Position Against the Category, Not the Product Now that companies decide between “build vs buy vs big cloud” before doing side-by-side comparisons of products, startups must position their product as a better alternative or complement to the entire “big cloud” category of solutions. Don’t talk about who has the better features. First, given the engineering resources available to Big Cloud companies, any feature advantage will be short-lived. Second, buyers make feature comparisons much later in the buying process, after ruling out the majority of options based on their perception—not features—of those products. So why is your product better than Big Cloud, despite the (likely) higher cost and time to deploy? Here are common answers I have found from my interviews with buyers, that may or may not apply to your product: Works Anywhere with Anything “Our product deploys, runs, and integrates with applications on any infrastructure. Organizations running applications hybrid or multi-cloud environments can use the product without restrictions and without consolidating to one cloud provider.” Self-Service for Non-Technical Users “Products from Big Cloud providers often serve the users closest to infrastructure work, such as engineers, operators, architects, developers. Our product lets non-technical users such as […] do their work without being blocked by or burdening technical teams.” End-to-End Solution “Our product is an end-to-end solution that does not require engineering work to glue parts and other systems together. Big Cloud products act more like building blocks that work well with other parts of their platform, but are not that useful or even usable on their own.” Purpose-Built “Our product was made—and continues to be developed—to solve the unique needs of your industry. It integrates seamlessly with people, workflows, tools, and systems you already have, such as […].” Expert Partners “In addition to documentation and examples relevant to your use cases, we provide expert support and consultation to all customers, regardless of their size.” Customer-Driven Development “We are laser-focused on making the best product for […], constantly making improvements based on input and emerging needs of people like you.” If you’re still unsure how to explain your advantage over Big Cloud products, ask the buyers who chose you over AWS, Azure, or GCP, like I did for Gravitational and for Netlify. After developing new positioning to compete against Big Cloud, turn it into new or updated messaging, align the company on that messaging, and bring it to market through your sales and marketing channels. Conclusion The entry of Big Cloud is not always a death knell, but it’s serious. Startups that acknowledge the threat from Big Cloud companies, prepare accordingly, and react with the right strategy and sense of urgency could not only survive but thrive. Maybe even long enough to be acquired by one. [1] An incomplete list: I was consulting FoundationDB when AWS launched Aurora; Scalyr when AWS launched its Elasticsearch service (often used for searching through logs); Gravitational when Google launched GKE; Domino Data Lab when AWS launched Sagemaker; Etleap when AWS launched Glue; Nexla when Google acquired Alooma and as AWS launched AWS Lake Formation; Netlify when Google acquired Firebase and when GitHub (owned by Microsoft) launched Actions. In one case I saw things from the other side: When the startup Particle launched their IoT solutions, I was consulting AT&T on launching their own IoT platform and marketplace… True to form, AWS also launched an IoT platform that year. [2] Product counts are approximate, and do not include general business product groups such as G Suite or Office 365. Sources: 1, 2, 3, 4, 5, 6, 7, 8. ◼ PS - Liked this article? I write one every month or so, covering lessons learned on B2B startup growth. Don't miss the next one:

[campcamelot]

Something that breaks my cold, dead heart is when characters of shows I watch don't know their own worth.

Do you know how PAINFUL it is to watch my favourite characters doubt themselves while I watch helplessly and cry into my pillow at 3am?

[epikowlofficial]

Did this, and it was great fun! I swear I’ll drawing anything people request. 

Don’t try me on that.

[shirogane-prince]

Two very valid fathers

[soni-dragon]

Some drawings from Inktober l like. Watch out for the beast 🍂

[dammitadolfnomorecake]

Great... now I need a name for him...

Is he a Jeremy? I don’t think he looks like a John... or a Joshua... he’d definitely not a Greg or a Craig. And he doesn’t feel like a Tony... Is he a Peter? He doesn’t feel like a Peter... maybe a Pete? But I know a Peter in real life... Michael? Or is he a David?

Kenneth? Or Daniel... or James... or is he a Jon with no “h”... or maybe a “Joon” Joon Lee Kogane?

I have too many options

[worstshippoll]

Hi. Remember when I promised a second wave in June of last year? I forgot.

ROUND ONE, PART ONE of the BEST OF THE WORST SHIP POLL will begin on JANUARY 19TH at 2 PM PST. It will consist of the LEFT side of the bracket.

Propaganda IS allowed for this iteration of the poll, but will ONLY be posted to this blog if directly submitted. I WILL NOT post anything mean-spirited, inflammatory, or legitimately weird, please keep that in mind when submitting.

The bracket is listed in plain text under the cut.

(LEFT SIDE)

Dazai Osamu/Nakahara Chuuya (BSD) VS Crowley/Aziraphale (GOOD OMENS)

Steve Harrington/Eddie Munson (STRANGER THINGS) VS Reylo (STAR WARS)

Star Butterfly/Marco Diaz (SVTFOE) VS Spamton/Jevil (UTDR)

Harrier Du Bois/Kim Kitsuragi (DE) VS Herbert West/Daniel Cain (REANIMATOR)

Catra/Adora (SPOP) VS Akira Kurusu/Goro Akechi (P5)

Lapis/Peridot (SU) VS Tenth Doctor/Rose Tyler (DR WHO)

Cole Cassidy/Hanzo Shimada (OVERWATCH) VS Takami Keigo/Todoroki Enji (BNHA)

Beauregard Lionett/Jester Lavorre (CRITROLE) VS Raiden Ei/Yae Miko (GI)

Katsuki Bakugou/Izuku Midoriya (BNHA) VS Jack Hakrness/Ianto Jones (TORCHWOOD) 

Marisa Kirisame/Reimu Hakurei (TOUHOU) VS Rhys Strongfork/Handsome Jack (BORDERLANDS)

Kaname Madoka/ Homura Akemi (PMMM) VS Alhaithem/Kaveh (GI)

Ryuki Kuruto/Date Kaname (AI Somnium) VS Ethan Winters/Chris Redfield (RE7/8)

Hunter/Willow Park (TOH) VS Childe/Zhongli (GI)

John Watson/ Sherlock Holmes (BBC SHERLOCK) VS Dimple/Arataka Reigen (MP100)

Azula/Ty Lee (ATLA) VS Zuko/Katara (ATLA)

Nico Yazawa/Maki Nishikino (LL) VS Dean Winchester/Castiel (SPN)

(RIGHT SIDE)

Sasuke Uchiha/Sakura Haruno (NARUTO) VS Vriska Serket/Terezi Pyrope(HS)

Benry/Gordon Freeman (HLRVAI) VS Keith Kogane/Lance Mcclain (VLD)

Kazuhira Miller/Revolver Ocelot (MGS) VS Jotaro Kujo/Noriaki Kakyoin (JJBAP3)

Dave Strider/Karkat Vantas(HS) VS Sonic the Hedgehog/Shadow the Hedgehog(STH)

Mako/Korra (ATLA) VS The Onceler/The Onceler (THE LORAX)

Lavernius Tucker/Agent Washington (RVB) VS Chris Hartley/Josh Washington (UNTIL DAWN)

Piers/Raihan (PSWSH) VS Natsuki/Yuri (DDLC)

Greg House/James Wilson (HOUSE MD) VS Callie Torres/Arizona Robbins (GREY'S ANATOMY)

Kazuma Kiryu/Goro Majima (YAKUZA) VS Light Yagami/Misa Amane (DEATH NOTE)

Chell/GLaDOS (PORTAL) VS Adam Faulkner-Stanheight/Lawrence Gordon (SAW)

Tom Wambsgans/Greg Hirsch (SUCCESSION) VS Ryo Asuka/Akira Fudo (DEVILMAN)

Tsukasa Tenma/Kamishiro Rui (PRSK) VS Qrow Branwen/James Ironwood (RWBY)

Batman/The Joker (BATMAN) VS Getou Suguru/Satoru Gojo (JJK)

Mark Hoffman/Peter Strahn (SAW) VS Iki Hiyori/Yukine (NORAGAMI)

Jayce/Viktor (ARCANE) VS Hannibal Lector/Will Graham (HANNIBAL)

Dirk Strider/Jake English (HS) VS Ash/Serena (POKEMON)

[artwh0r3]

Keith isn't white. He's mixed. Half Galra, half JAPANESE. You don't get a last name of Kogane from being white. Steven is ALSO mixed. The whole show revolves around him being of mixed heritage. But SheRa? I don't have any defense for that. Either way, stop calling Asian people or people of Asian descent white.

ok this was longer than i thought it was gonna be so here’s a read more i promise i get insightful on this

Well the thing is, while Keith was Japanese in the Voltrons of ‘80, ‘90, and 2011, they never specified just what human race he is in the newest, arguably most popular one. Like, they never ACTUALLY gave him a last name as a hint or anything, at least from what I’ve found officially. Most people, including myself, just tag with Keith Kogane cuz that makes it obviously Voltron. Also yeah, Steven’s mixed, just like Keith is. It’s an integral part of their identities, I’m not denying that in any way. But Steven is kinda obviously just a cute chubby white passing kid. And their mixed part is alien, which is outside of human bigotry in terms of race. There’s bigotry WITHIN the alien races, but it’s metaphorical at that point in terms of storytelling. Not “technically” rep in any deep degree (apart from body posi with Steven?? I dunno). I have no real opinions on She Ra cuz I don’t plan on watching it, but I’ve read enough to get the gist of people’s issues with it.

It’s one of those things where it’s safe to assume that the writers didn’t want it to matter, but people will assume regardless that they’re white kids. The sad thing with animation is that you kinda have to be OBVIOUS when you want something to be specific (darker skin, certain features, manerisms and actions, names, etc.). And sometimes animators won’t add those hints BECAUSE they want it to maybe feel a bit more universal. You might read them as latin@, or polish, or literally any other race/mix under the sun, but as long as they white pass, they’ll be seen as white by the general public because that’s just the “standard.” Not saying that’s right, but that’s how it be. Some people even only see them as white just to have a reason to dislike them, because that’s a crazy mentality that exists. 🙃

It’s because of that that I agree with that post, cuz regardless of headcanons and fan interpretation, the fact that it’s open enough to see it that way can be an issue to some in regards to what they consider “proper representation.” Especially when the character in question is definitely surrounded by people and beings that are not white or white coded.

I’m normally not bothered by this stuff anyway, unless the treatment of the other characters is abhorrent, and bad things can be said of all of those shows, soooo yeah. I get it and I reblogged it cuz it was funny. I’m sorry if I offended you in my support for that post, but I hope you get where my mind was. I’m not trying to erase Asian bodies or call them what they’re not. I’m just seeing things how they are. We can’t expect everything to be spelled out for us, but being vague doesn’t always help either, and it’s telling of the quality of a show when these things turn into an issue.

I personally like to headcanon Keith as being an eastern Asian/white mix already from his dad’s side, since I’m attached to the Kogane name, and we don’t get enough genuine mixed rep nowadays. And Greg just really seems like an Irish/Italian mix to me, with the combo of laid back, great fluffy hair, and horrible suntans. Very white. Love the guy. A+ dad.

[antheus007-blog-blog-blog]

“Hoyt Kogan”   ph. Greg Gorman

Greg Gorman is an acclaimed American portrait  photographer, born in Kansas City, Missouri in 1949. The artist is notorious  for photographing almost every Hollywood celebrity  under the sun. Michael Jackson, Sophia Loren, Johnny Depp and  Michael Jordan are just some of the names he worked with. His photographs  have been published in Vogue, GQ, Esquire, Rolling Stone, Vanity Fair, Time  and the London Sunday Times. For me a photograph is  most successful when it doesn’t answer all the questions and it leaves  something to be desired, says Gorman about his work.

(via cirsiumpalustre)

Source: nudemeninart

[sharpxshootcr]

          The reason why Papa Kogane is dead is bc he would have thought to work the old Kogane charm à la Greg Universe and tried to single-handedly win over the enemy Galra.

[mysuits]

Hoyt Kogan by Greg Gorman 

[mogulinteriororlando]

Fashion for all by denisee-denisee featuring a cropped trousers ❤ liked on Polyvore

Ella moss top 3,235 INR - modalist.com

Greg Lauren cropped trousers 129,325 INR - modalist.com

Chloe Gosselin black leather sandals 27,265 INR - modalist.com

3 1 Phillip Lim leather crossbody handbag 57,415 INR - modalist.com

Nora Kogan ring 19,885 INR - modalist.com

Kate Spade leather jewelry 11,225 INR - modalist.com

EF Collection 14k jewelry 95,905 INR - modalist.com

Vintage charm 49,395 INR - modalist.com

Zero Gravity marble iphone case 1,525 INR - modalist.com

RetroSuperFuture round lens glasses 11,485 INR - modalist.com