Slashdot Mirror


'Why You Should Not Use Google Cloud' (medium.com)

A user on Medium named "Punch a Server" says you should not use Google Cloud due to the "'no-warnings-given, abrupt way' they pull the plug on your entire system if they (or the machines) believe something is wrong." The user has a project running in production on Google Cloud (GCP) that is used to monitor hundreds of wind turbines and scores of solar plants scattered across 8 countries. When their project goes down, money is lost. An anonymous Slashdot reader shares the report: Early today morning (June 28, 2018) I receive an alert from Uptime Robot telling me my entire site is down. I receive a barrage of emails from Google saying there is some "potential suspicious activity" and all my systems have been turned off. EVERYTHING IS OFF. THE MACHINE HAS PULLED THE PLUG WITH NO WARNING. The site is down, app engine, databases are unreachable, multiple Firebases say I've been downgraded and therefore exceeded limits.

Customer service chat is off. There's no phone to call. I have an email asking me to fill in a form and upload a picture of the credit card and a government issued photo id of the card holder. Great, let's wake up the CFO who happens to be the card holder. What if the card holder is on leave and is unreachable for three days? We would have lost everything -- years of work -- millions of dollars in lost revenue. I fill in the form with the details and thankfully within 20 minutes all the services started coming alive. The first time this happened, we were down for a few hours. In all we lost everything for about an hour. An automated email arrives apologizing for "inconvenience" caused. Unfortunately The Machine has no understanding of the "quantum of inconvenience" caused.

45 of 508 comments (clear)

  1. Sorry, but... by Known+Nutter · · Score: 5, Insightful

    If millions of dollars are on the line, you should be running your own systems. Seriously. I'm not an IT expert, data infrastructure guy or anything. I'm just a dumb nerd, and I know that. Never trust your data to a third party when millions are at stake -- let alone critical infrastructure reliability.

    --
    Beware of the Leopard.
    1. Re:Sorry, but... by snapsnap · · Score: 5, Interesting

      As if servers doing down can't happen if you host it yourself. Also, this isn't a problem limited to Google. We've been getting a lot of emails from Amazon lately with the subject " [Retirement Notification] Amazon EC2 Instance scheduled for retirement."

    2. Re:Sorry, but... by Nutria · · Score: 5, Insightful

      As if servers doing down can't happen if you host it yourself.

      But then you're in control, instead of having to rely on some amorphous, anonymous monster that only allows communication via automated email.

      --
      "I don't know, therefore Aliens" Wafflebox1
    3. Re:Sorry, but... by El+Cubano · · Score: 4, Informative

      I came here to say essentially the same thing. Three letters come to mind: S....L....A....

      If you do not have an agreement with the provider that indicates the measures they will take to restore service in the event of an outage, and the escalating penalties on the provider if they fail to restore service according to the agreement, then you really have no business running a revenue-generating production service with that provider. Or, you don't have a business at all, just a hobby.

    4. Re:Sorry, but... by Known+Nutter · · Score: 4, Insightful

      Of course servers go down. But if they are your own, you have many more levels of control than if they're in the "cloud" -- redundancy, as an obvious example. Or at least you have keys to the goddamn data center and don't have to provide the CFO's p-card to resolve the problem.

      In the case of TFA, it sounds like a consumer-grade solution was applied to an enterprise-level problem. Maybe that's Google's fault, maybe that's the customer's fault -- sounds like there's plenty of stupid to go around.

      --
      Beware of the Leopard.
    5. Re:Sorry, but... by Anonymous Coward · · Score: 5, Insightful

      That's why you also configure a failover at a secondary location. This server punching guy sounds like a damn idiot. With millions on the line why is there no disaster recovery plan outside of "call the CFO for his credit card?"

    6. Re:Sorry, but... by Junta · · Score: 4, Insightful

      Ah, but SLAs cost money, and part of the cloud movement has been "see, these vendors can make hosting cheaper than it used to be", precisely because all they have to do when they screw you over is say "whoops, sorry", and as such don't need to invest in *too* much resiliancy and don't have to worry too much about liability.

      --
      XML is like violence. If it doesn't solve the problem, use more.
    7. Re:Sorry, but... by Joce640k · · Score: 4, Insightful

      Google cloud isn't supposed to be enterprise grade? I bet that's news to google.

      If you read the fucking summary it doesn't say the servers went down, it says that some robot shut them down when it detected "suspicious activity". No review was done, nobody at google called the customer, nothing.

      This is clearly 100% Google's fault.

      --
      No sig today...
    8. Re: Sorry, but... by tepples · · Score: 4, Informative

      Why is it "getting harder" to host your own solutions?

      Many applications are not even available for purchase of a copy to run on your server. Instead, they are available exclusively on service as a software substitute (SaaSS) terms, namely that the application runs on an application service provider's server. One example of these is the server for any major MMO game.

    9. Re:Sorry, but... by AmiMoJo · · Score: 5, Insightful

      Google's cloud services are enterprise grade if you pay enterprise prices for them.

      If you pay for it on a credit card assigned to the CFO then you are not an enterprise and you are not paying enterprise prices.

      They chose a cheap, no-SLA no-support service, probably because it was cheap. Then they get upset that they aren't receiving the support they didn't pay for.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    10. Re:Sorry, but... by Anonymous Coward · · Score: 5, Insightful

      As if servers doing down can't happen if you host it yourself.

      But then you're in control, instead of having to rely on some amorphous, anonymous monster that only allows communication via automated email.

      Exactly right. If your servers go down, YOU can fix them immediately and you don't have the problem of trying to get in touch with some support person who may or may not respond quickly, or may not respond at all if you can't even figure out how to get in touch with them.

      That said, this was a case of a company trying to be cheap, and instead of an enterprise account they tried to run critical applications on what is supposed to be a consumer-level account, which is why they started getting e-mails from Google about "suspicious activity".

    11. Re:Sorry, but... by rudy_wayne · · Score: 4, Insightful

      If you read the fucking summary it doesn't say the servers went down, it says that some robot shut them down when it detected "suspicious activity". No review was done, nobody at google called the customer, nothing.

      This is clearly 100% Google's fault.

      Yes, Google was a little too quick to pull the trigger. They should have sent out a couple of e-mails first before shutting things down.

      But

      The "suspicious activity" was due to the cheapfuck customer running heavy, 24/7, critical applications on what is supposed to be a consumer-level account.

      You get what you pay for.

    12. Re:Sorry, but... by Anonymous Coward · · Score: 5, Informative

      I can understand summarily shutting down a customer on a residential Internet connection, or a small business shared web hosting provider. However when providing an "enterprise grade" service, you should be prepared to give your customers the benefit of the doubt. About the only instances I can think of for an enterprise service to shut down a customer is if they are greatly exceeding their allocated resources and/or the activity associated with the customer is actively in the process of harming other customers.

      Cheapfuck customer was running enterprise-level applications on what was supposed to be a consumer-level account. That's why Google Bots detected "suspicious" actitivy and shut them down. If they hadn't tried to be cheapfucks and were using an enterprise account this most likely wouldn't have happened.

    13. Re:Sorry, but... by gweihir · · Score: 5, Interesting

      Ah, yes. And that is at the core of the problem. But since this apparently happened before and they did not learn from that, my guess would be they have far larger problems than the known unreliability of cheap cloud services.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    14. Re:Sorry, but... by Zenin · · Score: 4, Insightful

      That Amazon message is very different. It's basically telling you (days or weeks in advance!) that there's a serious hardware failure and the underlying hardware needs to be pulled from service.

      It's literally as simple as a reboot to move to new hardware. You can even catch the notification easily with a CloudWatch Alarm and trigger the purpose-built auto-recovery action to do it for you the moment the instance goes into that state. Or use an AutoScale group and it'll just cycle the hardware out for you w/o any downtime or manual action. TMTOWTDI

      If you aren't living by the motto, "Everything Fails, All The Time", then you're simply doing Cloud wrong. To be fair, even if you're entirely on your own physical hardware in a datacenter...you're still Doing It Wrong if you aren't counting on your hardware to always be failing all the time.

      --
      My /. uid is better then your /. uid
    15. Re:Sorry, but... by Peter+P+Peters · · Score: 5, Informative

      Google's cloud services are enterprise grade if you pay enterprise prices for them.

      If you pay for it on a credit card assigned to the CFO then you are not an enterprise and you are not paying enterprise prices.

      They chose a cheap, no-SLA no-support service, probably because it was cheap. Then they get upset that they aren't receiving the support they didn't pay for.

      Exactly this. I don't use Google Cloud, but my 'enterprise' AWS service comes with a dedicated account manager and architect who I can call at anytime for help.
      Sounds like this guy cheaped out then is bitching because he received cheap service.

    16. Re:Sorry, but... by RickRussellTX · · Score: 4, Informative

      if your servers go down, YOU can fix them immediately

      Spoken like someone who has never had to fix a server immediately :-)

      One of the strong points of cloud computing is the infrastructure to shift load to accommodate failing hardware. To reproduce that capability with your own hardware & infrastructure requires a tremendous amount of planning and capital investment: in power, servers, and network. It's almost never a simple matter of "fix the server immediately".

    17. Re:Sorry, but... by BronsCon · · Score: 4, Informative

      Because I know someone's going to insist this is not the case and ask how you know differently, I'll step in and say it now: credit card verification.

      In the rare cases where enterprise services are paid for with a credit card, any and all verification for the $10k+/mo in charges is done when the contract is signed in person.

      --
      APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
    18. Re:Sorry, but... by aaarrrgggh · · Score: 4, Informative

      I had a $2million/18 month defense contract paid by credit card via a random accounting person 2000 miles away. I would say you are not quite up with the times... $10k/month can be peanuts.

    19. Re:Sorry, but... by coofercat · · Score: 4, Interesting

      I signed a previous client up for Google Cloud services. I did so using the company credit card. I was in touch with Google pre-sales people throughout, and spoke to some account management as well. In other words, I did it correctly, with their oversight throughout.

      What I'm saying is... you *can* pay for 'enterprise' services from Google with a credit card. Why anyone would want to is another matter, but to get invoice billing does take a few additional steps, which my client actually failed because of a change of business address at about the same time as we were doing the application. It all got resolved, as my client was in generally good standing, but I guess if your company is a bit flaky you might not pass such checks.

      By the looks of things though, this particular company was using a consumer account, which is of course the source of the problem. If it also happened more than once, you'd think they'd have learned by now.

    20. Re:Sorry, but... by shaitand · · Score: 3, Interesting

      "One of the strong points of cloud computing is the infrastructure to shift load to accommodate failing hardware. To reproduce that capability with your own hardware & infrastructure requires a tremendous amount of planning and capital investment: in power, servers, and network. It's almost never a simple matter of "fix the server immediately"."

      Of course you need to pay for the required infrastructure. That is what "host yourself" means. Either you are paying the higher up front cost of building it out for yourself or you are paying the much higher costs to have google/amazon/digitalocean/etc do it for you. As for shifting load to accomodate failing hardware, it doesn't work as well as pitched (which is why these services go down all the time and have such high latency) but it works better and faster on a private cloud implementation. Which is where you've built a cloud stack on your own gear. Just be sure you actually have redundant controllers across the whole thing and didn't just build redundant controllers on a virtualized layer sitting on top of a not redundant system.

  2. Wait by Anonymous Coward · · Score: 5, Insightful

    The first time this happened,...

    Why was there a second time?

  3. Donâ(TM)t trust an ad company. by Anonymous Coward · · Score: 3, Insightful

    Over 90 percent of Google income is adverts. You would be absolutely insane to trust them with your business or educational institution data.
    Iâ(TM)m not saying MS or Amazon is great but at least their revenue model is not based exclusively or largely on data mining of users.

  4. Amazon's cloud s no better by Wycliffe · · Score: 5, Interesting

    Our company tried to use Amazon a few years ago and ran into the same issues. Although google and amazon allow you to
    spin up a single instance, they are really designed for companies that have hundred if not thousands of servers. Amazon
    assumes that you have dozens of fault tolerant servers and if one goes down you just replace it with another one. This works
    great for companies like Netflix but Amazon is a disaster for a company that isn't fully fault tolerant and has critical servers
    that can't go down. Liquidweb, Rackspace, Linode, and even Digitalocean are more reliable when it comes to wanting to
    keep a single server up and running with minimal downtime. Now if you need to keep thousands of servers up and don't care
    if any one server goes down then Amazon works fine.

    1. Re:Amazon's cloud s no better by fahrbot-bot · · Score: 5, Insightful

      ... but Amazon is a disaster for a company that isn't fully fault tolerant and has critical servers that can't go down.

      If your company has "critical servers that can't go down" (wherever they are) and you're not fully fault-tolerant, you're the disaster, not Amazon.

      Not here to pick a fight, just sayin'. (one finger pointing at someone else is also three fingers pointing at yourself)

      --
      It must have been something you assimilated. . . .
  5. Disaster Recovery by tk77 · · Score: 4, Informative

    If an extended system outage can cause "millions of dollars in lost revenue" then you should have a DR plan. Don't put all your eggs in one basket. Have copies of everything at another site (EC2, Azure, Colo, etc) that you can turn on and switch to in this event. If millions of dollars are on the line, then it shouldn't be unreasonable to have such a plan and infrastructure established.

    1. Re:Disaster Recovery by gweihir · · Score: 3, Insightful

      They did not have a DR plan _after_ this happened before. They did apparently not even buy enterprise grade cloud services, you know, those with an SLA. The problem is not the cloud here, but the utter morons that decided to use it in that way.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    2. Re:Disaster Recovery by tk77 · · Score: 3, Insightful

      No.

      Relying on a single company no matter what their internal redundancy is, is not having a good DR plan. Especially when the amount of revenue involved his so high.

      As others have pointed out, the other cloud providers do the same thing. You can have your stuff spread all across the country/world with a single provider and if a glitch in their system says you shouldn't have service, it will all be turned off (as is presented in the TFA and from others suggesting at least Amazon has done the same thing).

  6. Your failure to plan... by kenh · · Score: 4, Insightful

    I have an email asking me to fill in a form and upload a picture of the credit card and a government issued photo id of the card holder. Great, let's wake up the CFO who happens to be the card holder. What if the card holder is on leave and is unreachable for three days?

    Uh, I don't know - take a picture of each and save them on your phone, in case you need them?

    You report everything was back up within 20 minutes once you submitted the requested information - that seems pretty good to me.

    Now, about your decision to only run one instance of your mission critical application suite on exactly one cloud service...

    The story here is you consider it someone else's fault for your failure to plan/prepare for an outage.

    --
    Ken
  7. New scam incoming! by Calydor · · Score: 4, Insightful

    I have an email asking me to fill in a form and upload a picture of the credit card and a government issued photo id of the card holder. Great, let's wake up the CFO who happens to be the card holder. What if the card holder is on leave and is unreachable for three days? We would have lost everything -- years of work -- millions of dollars in lost revenue.

    Somewhere in Russia, India and Nigeria, several callcenters full of scammers came all at once.

    --
    -=This sig has nothing to do with my comment. Move along now=-
  8. Yeah, big warning signs on the user side here by Phil+Urich · · Score: 5, Insightful

    The first time this happened,...

    Why was there a second time?

    So many of the problems here (ex. paying with a credit card and one that has only a single person's name on it? Having no fallback that can be spun up elsewhere?) are foolish if this has never happened before, and utterly, mind-bogglingly idiotic if this in fact has already happened before. It's one thing to be blind of something you should know could be a problem, it's quite another to be blind and wholly unprepared for a problem you've personally experienced! Something seems fundamentally wrong at this company.

    Also, if your entire business can die because it takes an unexpected few days off, then perhaps your business is running a bit too raggedly and doesn't have enough meat on the bones . . .

    --
    I remember sigs. Oh, a simpler time!
    1. Re:Yeah, big warning signs on the user side here by gweihir · · Score: 4, Insightful

      There probably is just one problem here: Utterly incompetent and greedy management that made this demented decision.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  9. Cheap service, cheap results by fyngyrz · · Score: 5, Insightful

    The company thought they could get away with paying less for server infrastructure. They can. But they get less. This is one of the "less" things they get.

    If you value your data, host it yourself, preferably in multiple locations. If you want to go cheap, then you can expect to lose things.

    Like your data, or access to it, or availability of it.

    It's not such a smart thing to cheap out on the important stuff.

    Of course, convincing the bean counters of future risk inherent in what appears to them to be current savings... good luck with that.

    Well, best to get rid of your bean counters. :)

    Here's a maxim of mine I like to drop on the table during discussions like these:

    If you can't afford to do it well, you almost certainly shouldn't be doing it at all.

    --
    I've fallen off your lawn, and I can't get up.
    1. Re: Cheap service, cheap results by Anonymous Coward · · Score: 4, Insightful

      Then take the contract you have with them to court and get your effing money back. What? No contract? You deserve what you get.

    2. Re:Cheap service, cheap results by gweihir · · Score: 4, Insightful

      You get what you pay for. They thought they could get much more than they paid for. 100% their fault. At the very least, they failed to evaluate what they actually got. And, since this is apparently the second time this happens, they also seem to be unable to learn.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    3. Re:Cheap service, cheap results by CaptainDork · · Score: 5, Interesting

      This.

      I'm retired now, but my firm had a plan to replace me with the cloud.

      We were a law firm.

      During my last two weeks, an elderly couple drove in from about 70 miles away to sign some family law papers and they were waiting in the conference room when a partner got hold of me and told me, "The cloud's down again .

      I called the support number and they said they were aware of the problem and that they were working on it.

      After a lot of pressure, I called again and told them to fail-safe over to the mirror that they had bragged about.

      They said the outage got the mirror, as well.

      I informed the partner and she started screaming at me. She yelled, "WHAT IS PLAN B?"

      I said, "Ma'am, plan B is plan A."

      It was quite a shit storm.

      I had argued against the cloud, and I documented their rejection of my recommendations and they signed off on it.

      They spent a a butt load of money bringing all that shit home, and I worked there another 5 years.

      I had full hands-on control of the shit I built. All of it. I was totally responsible and could either fix, or get fixed, anything running in my house.

      --
      It little behooves the best of us to comment on the rest of us.
    4. Re:Cheap service, cheap results by BronsCon · · Score: 5, Interesting

      I have (neigh, had) a client making the same choice right now. All of their infrastructure, under my hand, I could fix as it was fully under my control. We'll see where they are in 5 years.

      I'll happily go back to them when they ask me to clean up the shitstorm their current CTO doesn't see coming. As CTO and for double what I was getting as a contractor, of course.

      Under my lead, they went from everything running on a single unstable server and going down every other day to everything running on a distributed cluster of servers and not a single outage in sight. This, in the matter of under a year, on a site that is their entire business and sees over 500k uniques and serves over 20 million pages per month.

      Their new solution costs them more per month and limits them to 1.5 million pages served per month on the best package they actually list a price for, with no uptime SLA. In short, they'll be paying 15x as much for infrastructure for the capacity the current system has, which more than covers what they're "saving" by not paying me.

      It is what it is, but they thought I was only looking out for my own ass when I pointed all of this out. Well, I was looking out for me but, as they were providing me steady full-time work, a huge part of that was looking out for them in-kind.

      --
      APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
    5. Re:Cheap service, cheap results by pnutjam · · Score: 4, Insightful

      That's what I tell people about the cloud. It's great when it works, but if you have problems you are almost certainly just a small fish. The best you can hope for his your money back, but your services will still be down and your left scrambling to build elsewhere.

    6. Re:Cheap service, cheap results by aquabat · · Score: 5, Funny

      I have (neigh, had) a client making the same choice right now.

      +1 for having the horse sense to move on from that client, after you told them to hold their horses and they didn't listen. I guess you can lead a horse to water, but you can't make him drink. If they're going to get on their high horse and be as stubborn as a mule, then they're going to end up trying to close the barn door after the horse has bolted. When comparing in-house vs cloud, in-house really is a horse of a different colour. Trying to run a tech business on the cloud is just horsing around.

      --
      A republic cannot succeed till it contains a certain body of men imbued with the principles of justice and honour.
    7. Re:Cheap service, cheap results by pr0nbot · · Score: 3, Funny

      Let's rein in the puns, ok? Feels like we're flogging a dead horse.

    8. Re: Cheap service, cheap results by Cytotoxic · · Score: 3, Interesting

      Yeah, he is right about that "single point of failure".

      There are a huge number of companies that fall into that hole between "too small to have our own IT department" and "big enough to have a large IT department with formal procedures and personnel redundancies".

      I was that "one guy who does everything" for a long time. It is easily the most efficient way to run a company. Even when we were a small department with a half-dozen really sharp guys, it was still a high-wire act, dependent on having A players who knew the business and systems well.

      It was only after we hit maybe 15 or so IT employees that we really had full redundancy in personnel and reasonably well documented procedures. And even that was pretty small... we didn't have dedicated QA employees, for example.

      It all depends on what your needs are and what your risk tolerance is. For most growing small companies, the reward of having the "one really smart guy" as a key point of failure is worth the risk. Later, when it comes time to sell out to an investor or go public, that risk/reward equation flips and you have to figure out how to eliminate that red flag on the audit.

      As many here have said, going "cloud" isn't a panacea to fix that problem.

  10. Re:It makes sense why Google is like this by AmiMoJo · · Score: 3, Informative

    A simpler and more likely explanation is that you paid $0 for the service and got your money's worth.

    There are also lots of obvious examples that disprove your conspiracy theory. If it was politically motivated then what kind of politics wants to silence both the far right and progressives and non-political trans make-up videos and help the copyright industry abuse people?

    --
    const int one = 65536; (Silvermoon, Texture.cs)
    SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
  11. Exactly!! Ding, Ding, Ding! by King_TJ · · Score: 4, Insightful

    I may be one of the "old timers" who I'm told is thinking about things in an "old school" way when I say this. But I've *always* warned people that "The Cloud" just means you're giving somebody else the responsibility of handling your data and the systems it runs on.

    That makes sense sometimes. I'm not "anti cloud". But for anything really critically important to a business, I feel you should have it running locally and THEN consider cloud options as hot-failover sites, backup sites, etc. With cloud hosting, the whole thing is off limits to you as soon as your Internet circuit goes down, for one thing. With it running locally, you can still use it just fine anywhere on your LAN.

    But additionally, if the provider hosting your stuff goes bankrupt or merges with someone else, or just plain decides it's not profitable enough without some pricing changes -- where does that leave you? Technically, they can just disappear with your whole software and data configuration overnight. Or they can put trained apes in charge of maintaining things so it suddenly has huge security holes. Who knows?

    When you run things yourself, YOU are where the buck stops if things go wrong. If you're good at what you do, that should be more of a comforting thing than a scary thing. I've seen too many shops trying to cut corners on the I.T. hiring budget by bringing in less experienced people who really can't properly run the systems they're supposed to be caring for. The cloud for them is a crutch ... a way to get things done that are beyond their abilities. But that's not an ideal situation for a business to put itself in.
     

  12. If you look at the first comment in TFA by Chrisq · · Score: 5, Informative
    If you look at the first comment in TFA it turns out that the poster was using a consumer account for a million-dollar mission critical application:

    I highly recommend establishing an enterprise relationship with Google Cloud. It seems you are running a mission critical application on a consumer account and this issue could have been avoided. Reach out to the support team and let them know you want to discuss enterprise options to ensure you have done everything possible to ensure your account is never impacted like this in the future. Ping me if you have any trouble getting through. - Mike Kahn Customer Engineer, Google Cloud. All views and opinions are my own. @mkahn5

    This sounds like asking fro trouble to me!

  13. Re:It makes sense why Google is like this by serviscope_minor · · Score: 4, Insightful

    This is a good time to remind people that XKCD wrote that comic to justify the forceful expulsion from the entire Internet of ordinary people

    No it's a good time to remind people you've gone way off the deep end, mate.

    It does however prove that just aobut anything in favour of gamergate no matter how batshit insane will get modded up here. Like this bit:

    of al-Qaeda.

    Aside: isn't that sort of old news even for the crazies? Aren't ISIS responsible for chemtrails now or are they merely a false flag perpertrated by the deep state t ostop us knowing the truth about how a chemtrail spraying plane actually did 9/11?

    All of that "Gamergate harassment?" There was one tweet.

    Gamergate was one tweet: +3 Insightful. I think that might be a new low for slashdot moderation.

    --
    SJW n. One who posts facts.