Nazi Bronies

Because of course there are.

Many of the show's adult fans genuinely enjoy My Little Pony and the wholesome escapism it provides. Others, however, delight in the irony of their fandom. To them, it's edgy and provocative to be an adult obsessed with cartoon ponies. That's where the Nazis come in. [...]

In supposed deference to principles of free speech and openness on the internet, the presence of self-described Nazis within a fandom that idolizes compassion-oriented cartoon characters has become a coolly accepted fact. The community has sorted itself largely into two camps: those who think anything goes as long as someone finds it funny, and those who would rather ignore toxic elements than admit that not everything is perfect. [...]

Around the same time, a blog called My Nationalist Pony started attracting a readership. Its author, who was known only as Buttercup Dew, wrote at length about My Little Pony as a subculture -- "as implicitly white as NASCAR, country music, and the Republican Party" -- that could be used to spread white-nationalist ideas. The show became an alt-right in-joke, and stayed that way, spreading, for a time, to the little-known white-nationalist spaces on Tumblr as well. [...]

What's clearest from talking with those on either side of the argument is that the My Little Pony fandom has developed a totally nonsensical hodgepodge of values. Many fans who specifically support Black Lives Matter, for example, are also fans of Aryanne, a fan-invented Nazi pony with a pink swastika on her hip. They do not acknowledge a contradiction. "I love Aryanne," a 25-year-old My Little Pony fan named Sam told me. "It's just cute, funny, sexy art." Then he added, "Black Lives Matter art is great. I welcome it." [...]

This idea of what counts as political and what doesn't is another thing the fandom took from 4chan -- where racial slurs are just jokes but anti-racism makes you a "social justice warrior."

Previously, previously, previously, previously.

Tags: , ,

Broken images on ye olde blogge

A few weeks ago I started using Cloudfront to CDN the images and MP4s on this blog, and it seemed to be working out ok, but now I'm occasionally seeing broken images where the CDN has seemingly cached a 503 result and won't let it go. E.g. I'm seeing a 503 on this image.

But you probably aren't, because when I wget that image, it comes through fine. So Cloudfront's cache key must include the particular browser headers or something. (Which is, in itself, stupid and wasteful and costing me unnecessary bandwidth, but that's a problem for another day.)

Surprisingly, if I add "?1" to the end of the URL it does not bust the cache. And when I manually add an "Invalidation" of that URL, it also does not re-fetch it.

I have my 503 Error Caching Minimum TTL set to 30 (along with all other error codes) and yet it seems to cache it forever.

Suggestions?

Previously, previously.

Tags: , , , ,

Gimmes, Ghosts and Dims. SF 2024!



But I'm to believe that Transbay Tube 2 will be done by 2024? Pffffffff, the Central Subway won't even be open by then.
However, they predict that our computers will be Apple Lisas running a DOS box under NeXTstep, so that checks out.

Previously, previously, previously, previously, previously, previously, previously.

Tags: , , , , , , , , , ,

  • Previously