3 ms·

This is becoming much more common. A YouTube channel I created to poke fun at rap music was brigaded after I submitted it to a popular group on Reddit. They rep

This is becoming much more common. A YouTube channel I created to poke fun at rap music was brigaded after I submitted it to a popular group on Reddit. They reported so many of my videos so quickly that before I could finish the appeal of a single community guideline I had 3 strikes and my channel was permanently deleted before I ever received any feedback or appeal.

ballenf 8y ago
Crazy. More details please, especially how long between first strike and deletion?
- ddtaylor 8y ago
  First strike: Mon, Jul 9, 2018 at 8:53 PM Second strike: Mon, Jul 9, 2018 at 10:36 PM Third strike: Mon, Jul 9, 2018 at 11:31 PM The last / third strike came with a "Your YouTube account has been terminated" and any attempts to login or view any of my videos gives a page missing and the Google account associated with it doesn't even appear in any of my menus. I don't really care that much it was a dumb joke channel I made to poke fun at how often profanity is used in rap music. The part I find pretty perplexing is that I _removed_ the profanity from the music and the channel was flagged for offensive content.
  - josephorjoe 8y ago
    No recourse perma ban within 3 hours? Sounds like a recipe for griefing.
    - kayfox 8y ago
      Its great for griefing. Its also heavily automated, so the griefers can just work the system into doing it whenever they want.
  - dzhiurgis 8y ago
    Any chance that was actually a copyright infringement?
    - ddtaylor 8y ago
      No they have a different process for this which prevented my videos from being monetized, which I wad fine with. They clearly break down the strikes and your account status in a page near the creator studio.
walrus01 8y ago
As a network engineer, with 'enable' on a lot of the bare metal devices that actually run the cloud... This is why I don't put anything that I care about on a service or system I don't control. If I want to host videos I care about staying online, they live on a VM configured for a pretty common LAMP stack which exists on a hypervisor that I own and control down to the bare metal and the contract for the colo rack space and 208VAC power. Using this example, that same 1RU system has a connection to an ISP that I know and trust. It's not going to go offline unless I were to do something so terribly abusive (in terms of network abuse) or illegal that it would cause them to admin down the 1000BaseT port facing it. Or it could theoretically go offline if I used it for illegal outbound network activity and somebody from the local FBI field office showed up with a warrant to take it (again highly unlikely, because I don't do that shit). Those are just about the only circumstances in which a third party could bring it offline.
- excalibur 8y ago
  > Those are just about the only circumstances in which a third party could bring it offline. This sounds like a challenge. Does the winner get a bottle of scotch?
  - walrus01 8y ago
    Well I'm certainly not going to post the IP addresses of its public netblock for anyone to DDoS. Though my upstream, and its upstreams, do have DDoS mitigation services in place. :) edit: actually, yes, the winner would get a bottle of scotch. I have had people that I know and trust, with my permission, attempt to gain external access to it, without success. Not claiming I'm any sort of netsec wizard, just that I have a layered defense of most common security precautions for anything that has a public static IP address these days. Nobody has been successful yet. It could theoretically be brought down by: a) social engineering the ISP it's hosted at (unlikely, they know me, I know them) b) physical removal (its reverse DNS gives no indication of where it's physically located other than within a major metro area, could be at one of about twenty different datacenters. all of which have reasonably good physical security in place). c) false legal claims causing some legal authority to bring it down, theoretically possible, but unlikely given the strong EFF/ACLU supporting political stance of the owners of the ISP it's hosted at. They would fight anything short of a court order that they could be held in contempt of. d) Extensive sustained DDoS. I don't have any enemies that would be interested in wasting a DDoS on this, but its upstreams have a LOT of extra peering and transit capacity to absorb DDoS up to the 150Gbps range. e) hardware failure, it's not perfectly 1+1 redundant in everything. but I have backups of every VM that can be brought up fairly quickly on a temporary dedicated server in a new, different, geographically diverse location fairly quickly. f) some terrible unknown zero day exploit on one of the few daemons that listens to the public interface, through which some method of accomplishing a user and then su/sudo root shell might be possible.

ballenf 8y ago

Crazy. More details please, especially how long between first strike and deletion?

ddtaylor 8y ago
First strike: Mon, Jul 9, 2018 at 8:53 PM Second strike: Mon, Jul 9, 2018 at 10:36 PM Third strike: Mon, Jul 9, 2018 at 11:31 PM The last / third strike came with a "Your YouTube account has been terminated" and any attempts to login or view any of my videos gives a page missing and the Google account associated with it doesn't even appear in any of my menus. I don't really care that much it was a dumb joke channel I made to poke fun at how often profanity is used in rap music. The part I find pretty perplexing is that I _removed_ the profanity from the music and the channel was flagged for offensive content.
- josephorjoe 8y ago
  No recourse perma ban within 3 hours? Sounds like a recipe for griefing.
  - kayfox 8y ago
    Its great for griefing. Its also heavily automated, so the griefers can just work the system into doing it whenever they want.
- dzhiurgis 8y ago
  Any chance that was actually a copyright infringement?
  - ddtaylor 8y ago
    No they have a different process for this which prevented my videos from being monetized, which I wad fine with. They clearly break down the strikes and your account status in a page near the creator studio.

walrus01 8y ago

As a network engineer, with 'enable' on a lot of the bare metal devices that actually run the cloud... This is why I don't put anything that I care about on a service or system I don't control. If I want to host videos I care about staying online, they live on a VM configured for a pretty common LAMP stack which exists on a hypervisor that I own and control down to the bare metal and the contract for the colo rack space and 208VAC power. Using this example, that same 1RU system has a connection to an ISP that I know and trust. It's not going to go offline unless I were to do something so terribly abusive (in terms of network abuse) or illegal that it would cause them to admin down the 1000BaseT port facing it. Or it could theoretically go offline if I used it for illegal outbound network activity and somebody from the local FBI field office showed up with a warrant to take it (again highly unlikely, because I don't do that shit). Those are just about the only circumstances in which a third party could bring it offline.

excalibur 8y ago
> Those are just about the only circumstances in which a third party could bring it offline. This sounds like a challenge. Does the winner get a bottle of scotch?
- walrus01 8y ago
  Well I'm certainly not going to post the IP addresses of its public netblock for anyone to DDoS. Though my upstream, and its upstreams, do have DDoS mitigation services in place. :) edit: actually, yes, the winner would get a bottle of scotch. I have had people that I know and trust, with my permission, attempt to gain external access to it, without success. Not claiming I'm any sort of netsec wizard, just that I have a layered defense of most common security precautions for anything that has a public static IP address these days. Nobody has been successful yet. It could theoretically be brought down by: a) social engineering the ISP it's hosted at (unlikely, they know me, I know them) b) physical removal (its reverse DNS gives no indication of where it's physically located other than within a major metro area, could be at one of about twenty different datacenters. all of which have reasonably good physical security in place). c) false legal claims causing some legal authority to bring it down, theoretically possible, but unlikely given the strong EFF/ACLU supporting political stance of the owners of the ISP it's hosted at. They would fight anything short of a court order that they could be held in contempt of. d) Extensive sustained DDoS. I don't have any enemies that would be interested in wasting a DDoS on this, but its upstreams have a LOT of extra peering and transit capacity to absorb DDoS up to the 150Gbps range. e) hardware failure, it's not perfectly 1+1 redundant in everything. but I have backups of every VM that can be brought up fairly quickly on a temporary dedicated server in a new, different, geographically diverse location fairly quickly. f) some terrible unknown zero day exploit on one of the few daemons that listens to the public interface, through which some method of accomplishing a user and then su/sudo root shell might be possible.