Automatic-Update

New stuff for the default Tumblr theme:

  • Four different layouts: Regular, Minimal, Wide, and Grid. 
  • Highly readable reblogs: Same as in the dashboard. Goodbye, blockquotes. 
  • Unique widgets: Say more about yourself by sharing your likes and top photos. 
  • Design tweaks: Little details that make the whole thing better.

As always, your header image, fonts, and colors will automatically match up across the default theme, the dashboard, and the app. How you look is how you look, everywhere.

One more thing: We changed the name of the default theme from “Optica” to “Official,” which makes much more sense. If you’re already using Official, you’ll be automatically updated (as long as you haven’t tweaked the theme code). If you’re not using it…

Jump over to tumblr.com/themes 👉 and hit that install button.

You're Ok

Prompt: Mark and Ty calming Eth down when he’s really stressed/anxious. Thank you @tythaningalltheway for the prompt!!
(Ps I didn’t know if you wanted it to be more shippy or just platonic so I tried to leave it open to interpretation)

Ethan groaned in frustration. All he wanted to do was finish editing this video for his channel so he could start working on some of Mark’s videos. But his computer decided now was the best time to do automatic updates. Ethan wasn’t as pissed as he was worried. He knew he needed to get at least one of Mark’s and one of his own videos done today or else he’ll be behind on editing. Ethan was already not putting out as much content as he thought he should be. Ever since he moved out to LA, his scheduling had been fucked up. He knew the others in the house had tried to make his transition as easy as possible. And it did help some. But it didn’t help that he could only edit when at the office and that Mark made a rule that no one was allowed to edit past 9 pm. Back home, Ethan was use to editing into the early hours of the morning. That was one way how he was able to get two videos out each and every day plus work on a lot of Mark’s content. Now he could only get at least one video uploaded a day and was barely getting through Mark’s videos.

Ethan didn’t realize he was hyperventilating until he felt a hand on his shoulder. Ethan jumped as he whipped around, scaring the other person as much as he scared himself.

“Woah there buddy,” A soothing voice said.
“I need you to breathe. Can you breathe, Ethan?”

It took a minute for Ethan to realize that the voice belonged to Mark.

Ethan’s first instinct was to run. He didn’t really know why, but he felt trapped and needed to get away.
That was, until big muscular arms engulfed him and scooped him up out of his chair. Ethan looked up to see Tyler’s face looking back at him with concern. Ethan wanted to cower away.

“Hey now Ethan.” Tyler said gently.
“You’re okay. Breathe.”

Ethan was a shaking mess by the time Tyler got him to the couch. Tyler started rubbing circles on his back. Ethan almost didn’t notice Mark placing a blanket around him.
Ethan turned his head and looked at him. Mark sighed and wiped his thumb under Ethan’s eye. Ethan was suddenly aware of wetness on his face and realized he must’ve been crying.

“Do you need anything, bud?” Mark ask in a soft tone.

“Could- could I have some water please?” Ethan asked timidly.

“Yeah of course.” Mark smiled.

As Mark made his way to their kitchenette, Ethan leaned into Tyler’s side. Tyler instantly started playing with Ethan’s hair. Ethan let out a little hum and closed his eyes.

“Feeling any better?” Tyler asked.

Ethan nodded.
“A bit. Thanks.”

“Do you wanna talk about what just happened over there?”

“I uh I-” Ethan could feel the anxiety rising back up.

Ethan’s eyes darted around frantically before locking eye contact with Mark.

Mark seemed to realize what was going on, or at least that Ethan needed help, and quickly came over to the couch.

“Here’s your water.“ Mark smiled.

Ethan took it gratefully and gulped it down.

“Its getting late we should head home soon.“ Mark said, looking at his watch.

“Sounds like a good idea to me. Ethan?” Tyler looked at him for a response.

“Huh?” Ethan stopped drinking so he could hear.

“You ready to go to the house?”

“Uh…” Ethan glanced towards his computer.

“The videos can wait. Its ok, Ethan.” Mark said.

Ethan just nodded before standing up. Ethan can sense both Mark’s and Tyler’s eyes on him the entire time. He kept his head down as he went back to his desk to grab his phone.

“You ready?” Tyler placed a hand on Ethan’s shoulder, almost protectively.

“Yeah.” Ethan said, slightly leaning into his touch.

Tyler smiled as he led them to his car.
They piled in. Tyler driving, Mark sitting shotgun, and Ethan in the back looking out the window. Mark and Tyler almost instantly started up a conversation and only a few minutes later, they realized Ethan’s responses had faded out.
They looked back to see Ethan curled up asleep in the back seat.

“Poor kid.” Mark sighed.

Tyler just nodded in agreement.
“Should we wake him or?”

“Nah, I’ll carry him in.”

Mark got out once the car was parked and opened Ethan’s door. Mark carefully slid an arm behind Ethan’s back and an arm under his knees.
Mark carried him bridal style through the house, with Tyler opening doors for him until they made it to Ethan’s bedroom.

“Alright we should get out and let him sleep.” Tyler said from the doorway.

“I’d love to but uh…”

“But what?”

“He’s not letting go.”

Tyler looked over and saw Ethan clinging to Mark’s arm like it was a stuffed animal.
Tyler chuckled.

“Should we take him to the couch then and watch a couple of movies til he wakes up?” Mark suggested.

“Sounds like a plan.”

~time skip~

Ethan woke the next morning to find himself squished between Tyler and Mark.
The tv was left on and there was discarded plates and cups on the coffee table, which led Ethan to believe they didn’t fall asleep there on purpose.
Ethan pulled the blanket that was draped across him up to his chin before snuggling back down.
Ethan had a soft smile on his face as he drifted back to sleep.

anonymous asked:

I feel so down about this safe mode thing, I'm under 18 and this was like, my only gay space and I pretty much discovered and learned to accept my identity (lesbian) on here and now about one out of seven posts are blocked bc they're lgbt-related this is so harmful I hate staff

its really terrible but i believe one workaround is to uninstall the app, and when you redownload the app, choose the previous version from before the update. if you’re using an iphone, make sure you turn off “automatic updates” in the settings if that is on

How to get older Chocobros in Lucis Glitch

Uninstall game updates to revert your game to version 1.0. **on PS4, delete game application data, not saved data. Your game will have to install again (it’s not the updates). **You’ll need to be offline or make sure the update doesn’t automatically download and install again (this only works with 1.0) Start a new game. Get your chocobos to level 7. Sometime before traveling to Altissia, head to Old Lestallum. Park there. 

Climb that cement wall overlooking the city and the bridge. Call chocobos. 

From about the middle of that wall on the left (there’s a cell tower or something there), jump and glide onto the left beam of the bridge. **this can be a bitch. Sprint not far from the wall’s edge, jump at the last second possible, & hold glide. When you land on the beam, I recommend hopping to stay on because your bird probably won’t go straight. 

At the end of the beam, hop immediately to the middle of the bridge. If you continue up the left side you’ll get stuck or fall. 

From the middle of the bridge, jump into the river (you’ll see crab enemies below). Follow the left cement wall along the river until its end. 

Turn left up the hill. Climb. You’ll see the gorge with those trippy arches. Head towards Cape Caem (go through the forest and towards the ocean). 

When you get to the brown rocky area, and the bridge is near, hop down into the water. Make your way over the rocks (tide pools) and into the ocean. 

You’ll want to be slightly left of the lighthouse (you’ll see the boat in the harbor). 

Go straight out into the sea. DO NOT HEAD FOR ANGELGARD. KEEP FAR RIGHT OF THAT ISLAND.

 It’ll take 35-45 mins to swim to the opening / channel in the cliffs across the sea. Pro tip: put a rubber band or hair tie on your controller to keep your chocobo swimming straight and go enjoy life in the meantime. 

Keep the cliffs on your left mostly. You have to go straight a long while until the sorta secret opening in the cliffs to Altissia. Nothing bad will happen if you pass it and have to double back. It’s hard to describe where it is exactly- it’s on the left, though, and you have to go through a second little passage to get there.

 Once you find the statues / city opening, DO NOT JUMP YOUR CHOCOBO ANYWHERE ON THE WATERWAY INTO THE CITY. YOU WILL GLITCH AND HAVE NO CONTROL OVER YOUR BIRD AND YOU’LL FALL OFF THE MAP AND LOSE ALL THAT TIME. I did it twice (second time was an accident and I wanted to fucking die).

You’ll be running on water. It shouldn’t matter where you “land” in the city, but the stairway to the right of the sailboat works well and is probably the first spot.

 Head to the hotel. Speak to Gentiana and get Umbra / the messenger amulet. DO NOT SLEEP AT THE HOTEL. 

Travel back to your car (to Lestallum). 

Once there, talk to the hotel guy and summon Umbra. Travel to past Lucis. 

Continue the game as normal. Now technically you’re doing everything in the past. 

Once you travel from Hammerhead to Insomnia (after the reunion), the guys will be young again. Defeat the first wave of soldiers there and go to the dormitory nearby. Return to the present (lol). 

Voila! Older chocobros. You can save your game and everything. You won’t have the Regalia, though, because it was technically destroyed already. You can get the Regalia by going to Hammerhead and getting Cindy’s quests to improve the car (it’ll spawn 😄…but if you save a file with it and reload, it won’t be there and if you try to tow it, it’s invisible). 

The Sims 4: New Game Patch (June 1st, 2017)

There’s a new Sims 4 update available in Origin. If you have automatic updates enabled in the “Application Settings”, the game will auto-update once you open Origin. If you have auto-updates disabled, you will need to manually update by clicking the game in your library.

To ensure your game is up to date, check the game version found in Documents > Electronic Arts > The Sims 4 > GameVersion.txt. Your game should now read: PC Version 1.30.105.1010 / Mac Version 1.30.105.1210. If you’ve updated but it’s not showing the correct version, delete the GameVersion.txt file, restart, and all will be corrected.

❗ Remove all MODS and Custom Content before updating your game ❗

Update: 06/01/2017 – PC Version 1.30.105.1010 / Mac Version 1.30.105.1210

Hello Simmers.  Just a little tidying up today.

  • If you see some blurry thumbnails in the new Load / Save menu, it’s not you. It’s us.  Rest assured that save slots created after this little tidying episode will no longer have the issue.  To clear up blurriness for existing saves, you’ll need to do a little magic to bring it back into focus:
  • Despite not having the new pack, your stereo will no longer look like it’s playing loud music – even when it’s off.
  • You can now alter alien disguises again with merry abandon.
  • Really, you didn’t want the entire, long, sordid, intricate history of each of your relationships displayed? Ok. Ok. It’s back to how it was before….
  1. rub your eyes twice,
  2. wiggle your nose,
  3. resave your save game, then
  4. viola, all crisp and clear again!

Thanks everyone!  Enjoy and be good to each other!

Cheers,

SImGuruCleaningLady

Typed Notes
Hi all!

Recently inspired by @optomstudies post about Adapting to Uni Studying, I wanted to let you all know just how I personally go about typing my notes and why.

First of all: I use a Chromebook for all of my school work. This is because, Google, in my humble sophomore level opinion, has the easiest platform for creating, sharing, editing, and storing notes.

For my note taking:

I use Google Docs. I can organize all of my notes into individual folders for each subject and then even into subfolders for the units we are covering. I title my notes whatever best describes them. This is so I can easily locate the notes I want for studying later. This semester, in particular, I have two classes that cover many topics within the hour and a half lecture; because of this, I have decided to make large continuing notes for each unit. This is not ideal as my notes are about 13 pages long, but I can easily refer back to the information they are referencing and edit anything that I may have written in the past.

Why do I Type?

I choose to type notes when I have a professor that speaks quickly or covers a lot of information in one class. I am a very visual and a kinesthetic learner so handwriting notes works for me as well. Unfortunately, though I have a difficult time transitioning from spoken word to writing. I simply cannot keep up. For me, typing drastically minimizes this issue. I also cannot spell. I have a very minor case of dyslexia that makes me transpose or just incorrectly transcribe the letters: i, r, b, p, g, j, ou, etc.  This will still happen occasionally while typing but I can move past a mistake, relying on my computer to notice and then fix my errors. When my goal is to take in a much information as possible I don’t want to be constantly correcting my mistakes, or getting distracted with how to spell something.

How I Speed Up My Typing:

Shorthand

  1. Yes. Shorthand is still valid when typing. I have my own key and shorten words that I know will take less time to type. It’s really the same as when handwriting notes.
  2. I add my shortened words to my computer dictionary or turn off the red lines under misspelled words during class.
  3. w/ = with; w/o = without; govt = government; b/c = because; diff = different; etc.
  4. I also make use of my greater than, less than, and equal to keys

Shortcuts on the Keyboard

  1. Learn the shortcuts for typing effects.
  2. ctrl b = bold; ctrl i = italics; ctrl u = underline
  3. In Word, one can create controls for highlight and strikethrough, if those are tools you would like for typing.
  4. REMEMBER ‘ctrl s’ IS YOUR SAVE BUTTON!!! While Google docs and Word will update automatically it is a good habit to just ‘ctrl s’ at every stopping point.

Outline Format

  1. I always use the outline format for note taking. It is easiest while typing as you just need the ‘enter’ and ‘tab’ keys.
  2. If outline format is bad for our learning style, I would still encourage typing if it helped speed you up, keep your notes in one place, or avoid errors (such as spelling or misinformation). You could always transpose your notes later and make them into the pretty aesthetic pictures that go with all studyblrs.

These are just suggestions based on my personal note taking.

I really do like rewriting my notes as it is just one more way to get the information into my brain, but most of the time I want a clear, easy to read form of my notes and don’t have time to be rewriting everything.

open.spotify.com
Music for Programming, a playlist by allaboutdrama on Spotify
Focus enhancing music. Mood enhancing Music. Just Music.

Follow your MUSIC FOR PROGRAMMING playlist on Spotify and enjoy the sounds on-the-go, automatic updates, and latest news!

youtube

So, I get bored sometimes. And I’m a list person… (fuck you Bo, for that one joke)… So I organized 400ish videos of Bo in playlists by venue, by year, by song/bit and by other stuff (interviews, other shows, etc.) and I’m adding new ones as I find them. Oh, and very, very rarely I upload something that is relevant to my interests (also known as ‘everything about Bo’).

You can find it at https://www.youtube.com/user/lios76 and updates post automatically to Bo Burnham Playlists on Twitter. My main account is Bo Nerd, in case you like to get quotes, pictures, GIFs, clips, sightings and other stuff about Bo.

I also maintain a Bo Burnham ‘Fun and Interesting Facts’ post over at Reddit. Stop by when you’re in the neighborhood.

My DM’s on Twitter are always open, in case you want to chat. Do know that I’m 18+… or… well… 40+… and female, in case you are an insecure kid who is afraid to talk to adults. I assure you, I may be an idiot, but I am not creepy.

anonymous asked:

Can you do a blog rec list????

Absolutely! *rubs my evil fly hands together*

@otayuriism - creator of daddybek. my literal father. daddy of all daddies. adhjkgrtgh nO, but posts fantastic otayuri/yoi content, is really lovely and hilarious. definitely go there and check them out! <3

@meimagino - amazing fic writer. really funny and great to chat and plot with. 100% committed to daddybek and WILL drag you with their fic recs and headcanons. go and love them <3

@kittenyuriplisetsky - my lovely small baby. birthed from daddybek, so technically third generation of this strange daddybek family. posts wonderful and adorable Yuri content. great blog that perfectly complements daddybek, catering to your kittenyuri needs (nsfw)

@altisetsky - the first otayuri blog i ever followed! really lovely and has the most hilarious tags i’ve ever read. posts amazing otayuri content. not really into nsfw content, but will provide you with love and fluff <3 

@yoinsfw - a godsend. the beautiful blog we all need and love. posts fantastic and expansive nsfw yoi content and has a great tagging system that’s easy to navigate. absolutely recommended for all your thirsty needs (nsfw)

@nsfw-yurionice - another godsend. mostly posts viktuuri, but also posts some other nsfw yoi content. i’ve found some of the most gorgeous nsfw artwork on here! (nsfw)

@ao3feed-otayuri - a well known blog but i’ll share anyway! fantastic fic recs. automatically updated as soon as new otayuri fics are posted in the tag on ao3

That’s all I can really think of for now! Thanks for sending this in, and please go share the love with the people mentioned <3

anonymous asked:

I'm so excited to see what you come up with for Alex and little Agent Danvers!

“Alex, help me,” Kara begs her sister through her comms, frozen still in the middle of her office. Eyes locked onto her slowly moving target. “I don’t know what to do.”

Okay, look, you need to distract and then subdue—”

Through the comms, Kara picks out Lucy’s voice. “Whoa, guys, we’re talking about a baby here, not an enemy hostile.”

Keep reading

v5.0.0

External image

Wowowowowow npm@5!

This release marks months of hard work for the young, scrappy, and hungry CLI team, and includes some changes we’ve been hoping to do for literally years. npm@5 takes npm a pretty big step forward, significantly improving its performance in almost all common situations, fixing a bunch of old errors due to the architecture, and just generally making it more robust and fault-tolerant. It comes with changes to make life easier for people doing monorepos, for users who want consistency/security guarantees, and brings semver support to git dependencies. See below for all the deets!

Breaking Changes

  • Existing npm caches will no longer be used: you will have to redownload any cached packages. There is no tool or intention to reuse old caches. (#15666)

  • npm install ./packages/subdir will now create a symlink instead of a regular installation. file://path/to/tarball.tgz will not change – only directories are symlinked. (#15900)

  • npm will now scold you if you capitalize its name. seriously it will fight you.

  • npm will --save by default now. Additionally, package-lock.json will be automatically created unless an npm-shrinkwrap.json exists. (#15666)

  • Git dependencies support semver through user/repo#semver:^1.2.3 (#15308) (#15666) (@sankethkatta)

  • Git dependencies with prepare scripts will have their devDependencies installed, and npm install run in their directory before being packed.

  • npm cache commands have been rewritten and don’t really work anything like they did before. (#15666)

  • --cache-min and --cache-max have been deprecated. (#15666)

  • Running npm while offline will no longer insist on retrying network requests. npm will now immediately fall back to cache if possible, or fail. (#15666)

  • package locks no longer exclude optionalDependencies that failed to build. This means package-lock.json and npm-shrinkwrap.json should now be cross-platform. (#15900)

  • If you generated your package lock against registry A, and you switch to registry B, npm will now try to install the packages from registry B, instead of A. If you want to use different registries for different packages, use scope-specific registries (npm config set @myscope:registry=https://myownregist.ry/packages/). Different registries for different unscoped packages are not supported anymore.

  • Shrinkwrap and package-lock no longer warn and exit without saving the lockfile.

  • Local tarballs can now only be installed if they have a file extensions .tar, .tar.gz, or .tgz.

  • A new loglevel, notice, has been added and set as default.

  • One binary to rule them all: ./cli.js has been removed in favor of ./bin/npm-cli.js. In case you were doing something with ./cli.js itself. (#12096) (@watilde)

  • Stub file removed (#16204) (@watilde)

  • The “extremely legacy” _token couchToken has been removed. (#12986)

Feature Summary

Installer changes

  • A new, standardised lockfile feature meant for cross-package-manager compatibility (package-lock.json), and a new format and semantics for shrinkwrap. (#16441)

  • --save is no longer necessary. All installs will be saved by default. You can prevent saving with --no-save. Installing optional and dev deps is unchanged: use -D/--save-dev and -O/--save-optional if you want them saved into those fields instead. Note that since npm@3, npm will automatically update npm-shrinkwrap.json when you save: this will also be true for package-lock.json. (#15666)

  • Installing a package directory now ends up creating a symlink and does the Right Thing™ as far as saving to and installing from the package lock goes. If you have a monorepo, this might make things much easier to work with, and probably a lot faster too. 😁 (#15900)

  • Project-level (toplevel) preinstall scripts now run before anything else, and can modify node_modules before the CLI reads it.

  • Two new scripts have been added, prepack and postpack, which will run on both npm pack and npm publish, but NOT on npm install (without arguments). Combined with the fact that prepublishOnly is run before the tarball is generated, this should round out the general story as far as putzing around with your code before publication.

  • Git dependencies with prepare scripts will now have their devDependencies installed, and their prepare script executed as if under npm pack.

  • Git dependencies now support semver-based matching: npm install git://github.com/npm/npm#semver:^5 (#15308, #15666)

  • node-gyp now supports node-gyp.cmd on Windows (#14568)

  • npm no longer blasts your screen with the whole installed tree. Instead, you’ll see a summary report of the install that is much kinder on your shell real-estate. Specially for large projects. (#15914): $ npm install npm added 125, removed 32, updated 148 and moved 5 packages in 5.032s. $

  • --parseable and --json now work more consistently across various commands, particularly install and ls.

  • Indentation is now detected and preserved for package.json, package-lock.json, and npm-shrinkwrap.json. If the package lock is missing, it will default to package.json’s current indentation.

Publishing

Cache Rewrite!

We’ve been talking about rewriting the cache for a loooong time. So here it is. Lots of exciting stuff ahead. The rewrite will also enable some exciting future features, but we’ll talk about those when they’re actually in the works. #15666 is the main PR for all these changes. Additional PRs/commits are linked inline.

  • Package metadata, package download, and caching infrastructure replaced.

  • It’s a bit faster. Hopefully it will be noticeable. 🤔

  • With the shrinkwrap and package-lock changes, tarballs will be looked up in the cache by content address (and verified with it).

  • Corrupted cache entries will automatically be removed and re-fetched on integrity check failure.

  • npm CLI now supports tarball hashes with any hash function supported by Node.js. That is, it will use sha512 for tarballs from registries that send a sha512 checksum as the tarball hash. Publishing with sha512 is added by npm/npm-registry-client#157 and may be backfilled by the registry for older entries.

  • Remote tarball requests are now cached. This means that even if you’re missing the integrity field in your shrinkwrap or package-lock, npm will be able to install from the cache.

  • Downloads for large packages are streamed in and out of disk. npm is now able to install packages of “”“any”“” size without running out of memory. Support for publishing them is pending (due to registry limitations).

  • Automatic fallback-to-offline mode. npm will seamlessly use your cache if you are offline, or if you lose access to a particular registry (for example, if you can no longer access a private npm repo, or if your git host is unavailable).

  • A new --prefer-offline option will make npm skip any conditional requests (304 checks) for stale cache data, and only hit the network if something is missing from the cache.

  • A new --prefer-online option that will force npm to revalidate cached data (with 304 checks), ignoring any staleness checks, and refreshing the cache with revalidated, fresh data.

  • A new --offline option will force npm to use the cache or exit. It will error with an ENOTCACHED code if anything it tries to install isn’t already in the cache.

  • A new npm cache verify command that will garbage collect your cache, reducing disk usage for things you don’t need (-handwave-), and will do full integrity verification on both the index and the content. This is also hooked into npm doctor as part of its larger suite of checking tools.

  • The new cache is very fault tolerant and supports concurrent access.

    • Multiple npm processes will not corrupt a shared cache.
    • Corrupted data will not be installed. Data is checked on both insertion and extraction, and treated as if it were missing if found to be corrupted. I will literally bake you a cookie if you manage to corrupt the cache in such a way that you end up with the wrong data in your installation (installer bugs notwithstanding).
    • npm cache clear is no longer useful for anything except clearing up disk space.
  • Package metadata is cached separately per registry and package type: you can’t have package name conflicts between locally-installed packages, private repo packages, and public repo packages. Identical tarball data will still be shared/deduplicated as long as their hashes match.

  • HTTP cache-related headers and features are “fully” (lol) supported for both metadata and tarball requests – if you have your own registry, you can define your own cache settings the CLI will obey!

  • prepublishOnly now runs before the tarball to publish is created, after prepare has run.

Uh hey, I just wanted to warn y'all that traumatized-official moved to whitesaviorcomplex.

Thanks,

It updates automatically since we’ve got them blocked, but followers should be warned of this asshole. 

-Mod Siarl