Papallona_Daurada

The amazing digital yuri

this is NOT because of blocking screenshots, it's because of HOW streaming sites use your computer's hardware to optimise performance, which means the thing rendering the video and the thing capturing your screen aren't the SAME thing. so they can't talk together.

basically the amazing digital circus

Two limits! You can have a maximum of 4,096,000 characters in 1 [one] tumblr post. I would work out how many combinations this is, but 26^6,000 is already considered to be "Infinity" by most calculators, and a program I wrote threw an error code.

26^95,000 is already over 134,000 characters long - which would take 33 different text blocks to convey via tumblr. Whenever somebody says we're running out of posts, don't forget that tumblr is needlessly designed for MASSIVE amounts of information [no matter how detrimental it may be for mobile phones].

Though I'm not certain if that character count includes spaces, unfortunately, as I got that figure by googling "how many letters are in lord of the rings" and came upon a TikTok that counted the number of letter characters in LotR in order to figure out how many Spaghettios cans would be needed to re-write the entire thing, if one were to cut and paste each individual letter from the cans blackmail-letter style.

For those curious, the numbers are 2,261,081 letters in LotR, which calculates out to 8,795 cans of Spaghettios needed, which would cost about $12,225.

So, those are the theoretical limits, yeah. But in practice, the editor is not even close to be optimized to handle these kinds of huge posts: there is a point, far far away from the size of the lord of the rings, that your browser would just crash.

So if you are planning to post long fanfiction, or anything, you better work on something that's optimized for long form (locally, or some alternative to Google docs) and then post in chunks.

For the first post (first book only) there was no issue. Edit loaded, I could add the tag, press Save and done. Note: this was on a PC using Chrome

For the second post (all three books) it worked the same way as the API. I could load up the page and edit it, but when pressing save I'd get an error message. However the edit did go through actually and the tag is now there.

Haven't tried to edit the text itself, but don't think it would make a difference - if your browser can load it'd just work.

(On mobile on a low/mid-range Android the App could open up the post without problems, but haven't tried editing. Using a mobile browser - Firefox in my case - the page could load but it was super slow, and buggy, and it also did crash once)

Also as a public service announcement: if you want to filter the post out from your dash the tag is #full-lotr-test

the "milkman" is a common figure in stories depicting a woman's infidelity and adulterous affair.

this implies that the ability to provide milk would both decrease the likelihood of a man abandoning his wife and children, as it would eliminate the need for leaving to get milk AND would secure that man's marriage, as his wife would have no need to seek milk from an extraneous source.

therefore, all men should produce milk, through various means such as:

- being a cow

- being an almond

- being a woman

- being a coconut

- being in the omegaverse

- being an oat

(list is exemplary and not finite)