a editor

"you're not man enough, not feminine enough"

so gender is something we can fail?

that means gender is not genetic and absolute and unchangeable

but something we can build and perform, and fail at (the standards they set) but also redefine?

if i can fail at being a woman, does that mean i'm not a woman? so does that make me another gender?

so many posts on so many different forums are about to break

“We will be focused on removing old, unused, and inactive content that is not tied to a user account from our platform as well as nudity, pornography, & sexually explicit content,” the page reads. “Most notably, this would include explicit/pornographic content.” Imgur notes that it will “employ automated detection software” alongside human moderators to identify explicit content.

unpretty:

unprettyextra:

so many posts on so many different forums are about to break

In case you hadn’t heard…

If you need a place for fanart:

Squidge is free, and has a TOS that’s about the same as AO3’s.

from a glance, Squidge looks promising..

image

HOWEVER it is hosted by ONE person?? what happens when that person dies, or their personal circumstances change?? 

image
image

Squidge is not a trustworthy long-term alternative.

Squidge.org has recently registered as a nonprofit, like the OTW.
(I’m on the board.) (This is very new and very tiny.) https://www.squidgeworld.org/ is the first/only AO3 clone on the internet right now.

And there are agreements in place - if something disastrous happens to the owner, the OTW takes it over. (The OTW may not be able to do much with the image side of things. But they’ll be able to keep it stable.)

Squidge has been around over 20 years. It’s as stable as fan-run sites get. And he’s aware that it needs more stability than “I’ll keep the servers up,” so he’s recently made changes that allow for long-term viability.

Also: Like the OTW, he owns the servers. He’s not beholden to Amazon or Google’s TOS for content permissions.

He has a tumblr! @squidgiepdx if this is still you

Yep! Squidge.org has been run by me for 29 years (!!!). But now we’re a nonprofit with a board and plans for Squidge to outlive me.

had a dream that I put the washing machine on but forgot to add the detergent. what sort of fucked up shit

If this was literally anyone else this would just be a normal tumblr post, but because it’s you this stands in stark contrast to things like clown meat

oi don't bring clown meat into this, clown meat was a vivid but overall entertaining experience, i deeply enjoyed having my consciousness temporarily banished to the clown meat dream universe, being arrested for selling artificial clown deli meat was a thousand times more fun and less stressful than the complete nightmare recounted in my original post

whenever elon pulls some new nonsense over on twitter dot com the ONLY scrap of joy I can get out of it is to read all the replies and qrts calling him an idiot baby and threads from smarter people than me detailing how exactly he’s being an idiot baby this time, and now he’s robbed me of even that. Rate Limit Exceeded. Unbelievable.

source: prokopetz
funnypoeple asked:
"

Unsure if you are aware of this update, but apparently someone got into the Twit api and believes that the "rate limiting" is actually a cover up by Elon bc they accidenlty pushed an update DDOSing their own site, which is why he says its "temporary" in his tweet. Not sure if Elon is actually trying to cover-up, or if the DDOS is an unintended side effect of the change

"

(With reference to this post here.)

As far as I can tell, the folks advancing that theory have it perfectly backwards. The rate limit isn’t an effort to address the self-DDoS situation: the rate limit is causing the self-DDoS situation.

In a nutshell, when you load up Twitter in your browser, two things are happening:

  1. In response to your initial request, Twitter’s server sends your browser the information it needs to construct the website’s user interface (UI).
  2. Once the UI has been constructed within your browser, it instructs your browser to dispatch a separate request, via the Twitter API, requesting content (i.e., tweets and ads) to fill itself with.

(It’s actually a little more complex than that, because the response to the initial request may come pre-filled with a portion of the required content in order to speed things up the first time you visit your dashboard, but that’s the gist of it, anyway.)

So, what happens now that the rate limit is in place?

Well, the rate limit doesn’t affect the first request – it’s not using the API, so your browser is able to construct the Twitter UI just fine. The moment you try to scroll your Twitter dashboard, however, that triggers the Twitter UI that’s been constructed within your browser to ask the Twitter API for more content so you can keep scrolling – and that request is subject to the rate limit.

If you happen already to have exceeded your rate limit, that request is going to receive a response along the lines of “Error 429 – Rate Limit Exceeded”. Here’s the trick: while Twitter did update the UI to reflect the addition of a rate limit (i.e., they’re not complete idiots), it turns out they did an incomplete job, and certain dashboard widgets don’t know what to do with an error 429.

Now, the fun part: apparently, what the affected Twitter dashboard widgets are coded to do when they receive a response they don’t recognise is simply to ignore it and try again. Further, nobody thought to impose a delay between attempts, so they retry immediately upon receiving the unrecognised error 429. For users with snappy Internet service, this can result in their browser making multiple attempts per second to retrieve content for the affected Twitter dashboard widgets, receiving (and ignoring) the same error code each time.

And that’s how Twitter ended up accidentally ordering its own users to DDoS its API.