#and I just wish i hadnt been plagued by the fact that i didnt want my m*m to know i hadnt graduated | Explore Tumblr Posts and Blogs

viktorsluvr · 2 years

Text

atsumu x male reader

summary: f/n is in love with atsumu. atsumu has a girlfriend.

cw: f/n means first name, angst i guess, incomplete(?)

every day, f/n thought the same thing.

i love you.

i love you...!

he knew he'd would never be able to say it. in fact, he would probably look at f/n disgusted if he ever found out he loved him. f/n wished he didnt.

—

"oi f/n!" f/n could hear atsumu shouting towards him from a little distance, as well as his twin mumbling something, though he could only see his mouth moving and without some impressive lip-reading skills, f/n could only barely guess he was scolding atsumu for being so loud. not that 'tsumu cared, anyway.

f/n waved slightly, not wanting to gain any more attention than he already had on him due to one of the famous miya twins screaming hi. when they reached him, astumu sat beside f/n, pressed together on the semi uncomfortable seats of the bus stops. "ya seem off. what'cha thinking 'bout?" f/n shook his head and looked down at the phone in your hand. it wasnt on and he wouldnt dare turn it on while the screen was right in his field of vision.

"i'm still so fucking tired. didnt sleep well." even if that wasn't the real reason he was off, f/n did in fact not sleep well the night before. then again, he often didnt sleep well because of the many overwhelming thoughts plaguing his mind. this time osamu replied, "same. couldn't get my eyes closed once, this dumbass was on his phone all night talking with some girl." "ya said yer wouldnt tell no one!!" osamu shrugged.

suddenly, f/n's mood sank even further down the drain. "you have a girlfriend or something?" f/n tried to put on a teasing smile to mask his disappointment, not sure of it working. the twins didnt notice, atsumu already started talking about that girl and osamu was on his phone, ignoring his brother. "well i guess it doesnt matter since 'samu already told ya. her name is aoi, she's like-" f/n tuned out the rest.

f/n moved his phone in a way that atsumu couldnt see what was on the screen. f/n always wanted to buy one of those screen protectors that hide your screen from the side angles, but in the end he didnt want to spend 15 dollars on some foil he sticks onto his phone. once his phone was completely out of atsumus view and he turned it on, what he was greeted with was a picture of the man himself. no, not a picture of f/n with atsumu, just atsumu.

f/n wasn't sure why, but he remembers the exact moment of taking this picture. it was just when practice was done; atsumu was still wearing his sports clothes. he was talking with his brother (who f/n cropped out – sorry 'samu!) and had the prettiest smile on his face.

no, really. that had to be the most beautiful thing f/n has ever seen.

so, f/n made that his lock screen. normally, this would've been what motivated him for the day, but right now it only seemed depressing. he was so close, but so out of reach.

he quickly unlocked his phone, going on inarizaki's website to check what subjects he would have today. he knew he had school until four and had to come to practice, but he was feeling nauseous just thinking about going there. this morning i was feeling just fine. why couldnt he just shut up? with the amount of force he was holding his phone with, there should've been a crack.

—

when lunch break finally came around, f/n hadnt gotten the events of that morning out of his head. yeah, normally he'd be overthinking stuff too, but the fact that atsumu had a girl he liked made him want to cry. or rip something apart.

when did atsumu even start liking girls? from what f/n knew, 'tsumu treated girls like shit. from the confessions under cherry blossom trees to fangirls at his games, he always hated them. what made him change his mind? part of f/n wanted to think the girl used some sort of love potion on atsumu, but then again, he didnt want to blame the girl.

it wasnt her fault after all.

well, maybe they just clicked. f/n wanted to laugh. he and atsumu clicked. but not in the same way, apparently. lost in his thoughts, f/n wasnt aware that he was the only one left in his classroom except for the twins. "you good?" f/n wanted to answer 'nah' just to match atsumus energy, but he couldnt get himself to do that.

instead, he shook his head. "it's fine."

f/n didnt take his lunch with him.

—

f/n dreaded what came after school. during lunch, atsumu kept talking about his girlfriend and no matter how hard he tried to drown his voice out, it didnt work. the only time where f/n wouldnt be caught up in his thoughts was in class when he was taking notes, but his my melody pencil he got from atsumu a few months ago kept trying to tear his thoughts away from school. just great!

after school activities. f/n had never wanted to skip practice this bad. the whole day - aoi this, girlfriend that - sure, f/n was happy for atsumu, but then again he was not. he wouldnt be able to deal with another two hours of atsumu bragging and talking about that girl.

f/n held his stomach in an uncomfortable way, trying to signalise that he had a bellyache, even if he didnt. osamu noticed, "are yer fine f/n? somethin' wrong with yer stomach?" f/n nodded, and explained how he mustve eaten something wrong. atsumu and osamu guaranteed him that they would tell the team about his predicament and he could go home early.

as soon as they were both out of sight, he let go of his stomach to get out of the hunching, uncomfortable position. nothing hurt, except for f/ns aching thoughts.

#atsumu miya #haikyuu!!#haikyuu x male reader #x male reader #atsumu x male reader #osamu miya #inarazaki

131 notes · View notes

ispybluesky · 5 years

Note

1, 6 (abt torredaga maybe?? i always see u tag it and wonder!!!), 19 aaaand 31 !!!

1. Tell us 3 useless facts about your favourite OC!: I CANNOT POSSIBLY PICK A FAVORITE OC I AHVE…..SO MANY but i’ve been thinking abt dorado a lot recently while i try to assemble her story so!

1) loves to be up high

2) has a little pipe that doubles as a measuring spoon for one of the chemicals that runs her plane, the pipe is an old one that was a gift

3) knows how to sail!

6. Tell us about a setting/world you’ve created!: torredaga is the world that me and my friends are (were??) playing a tabletop rpg in!! i say “were” because we technically just finished the whole campaign but we may go back someday, AND i can talk about it for this question anyway cause we built the world together!! torredaga is actually the name of a tiered city built into the side of a cliff and its where a lot of the game takes place, other notable locations are the empire and its capitol helios (which the god ilios founded near the end of his life after searching for a cure to the rat plague), the pelisian islands (which the goddess reylith became the goddess of after landing there on her search for the cure and starting a relationship with a local selkie who was ruling the main island), and erdash’s stronghold (which the deity erdash founded on their quest for a cure and where most of the dwarves live/come from/have relatives)(it also has very stringent anti-rat-plague measures so theyve never had an infection i think). in this world most if not all dwarf names start with ‘er’ to honor ‘erdash’, so there’s erdan, ermax, ermia, erlaz, etc. magic in this world is done through ghosts and crystals (which have ghosts in them): to do magic, you draw a circle. the type and design of the circle varies depending on what you want your magic to do. the concept is kind of a mix between fma alchemy circles and the magic system in the bartimaeus trilogy. my character, noonday, does a lot of experimenting with magic, so she’s invented ghost mics, which are little earpieces that use the power of a ghost to be essentially the same as walkie-talkies, teacups with circles in the rim that when broken will explode or will trap someone briefly, etc etc! in this world is also The Vanta, or (as our KidZ named her) “vanessa”, who was an elf that was left behind when the elves left torredaga to keep an eye on the four remaining elves who DIDNT leave (who became the four gods). she got stuck in a knife at some point but also founded a weird underground refugee city of children (called neverland) where if you drink the water you become a furry and have to join the army. theres SO much in torredaga i love the world i could talk about it for HOURS ask me more questions about torredaga

19. What are some of the coolest or most interesting (to you!) hobbies/pastimes your OCs have?: OK HONESTLY noonday’s hobby of being a, like, magic scientist, or just like constantly fucking around with new ideas of what to do with magic and coming up with a ton of weird and useful shit along the way, is SO fun and cool and interesting to me, i love it, it was one of my favorite parts of playing her. also my oc sonia from this too shall pass (that was my….2013 nanowrimo) makes rings and i think thats dope as fuck

31. On a scale of one (tucks them in softly and lets them Rest) to ten (murders their whole family before their eyes) how bad do you treat your OCs?:

SGJGDKSLNFDNGJFN I TEND TO……….ive become nicer to my characters in recent years which is probably like a positive expression of my internal state, or something? MY HISTORY OF KILLING CHARACTERS IS STORIED, i killed half the entire cast in the first chapter of my 2015 nano and then worked backwards through their timeline while their reincarnated counterparts worked forwards chronologically which in hindsight was a super cool way to write a story i wish bitter order hadnt been so absolutely horrible in every other conceivable way….i was gonna say that at least one main character in all of my nanos 2010-2015 dies BUT in nano 2012 TECHNICALLY none of the main characters died and the main character turnadot was only transported to the realm of the gods to spend a lonely immortal life maintaining its borders to protect the fabric of the mortal world SO. but as far as meanness goes i like happy endings so i tend to put my characters through a lot of like…..emotional and mental turmoil in the form of like dangerous quests or interpersonal conflict or internal conflict, and then try to resolve it in a fun and satisfying way SO OVERALL I WOULD RATE MYSELF AT A MAYBE 6 OR 7

#ask #nerice #long post #ask meme #THANK U FOR ASKING QUESTIONS AAAA <3 <3

4 notes · View notes

itsjessicaisreal · 5 years

Text

Almost 60% of marketers haven’t implemented AMP, see why (and why it’s no excuse)

When it comes to page speed, a few seconds of slowdown can cost you. Slow load times cripple conversion rates, raise the price you pay for ad impressions, and even drive qualified traffic to your competitors.

All this being true, Accelerated Mobile Pages (AMP) would seem like the hail mary pass that marketers have been waiting for. Essentially, AMP is a Google-backed framework for creating web pages that deliver near-instant load times, even on mobile. I say “near-instant” here, but I like how the AMP Project itself puts it: AMP pages are “so fast they appear to load instantly.”

What does AMP mean for marketers? Faster delivery of your content, for one thing. The end of waiting altogether, maybe. Ultimately, AMP can result in a significant uptick in traffic and improved conversion rates overall.

So, naturally, every marketer is planning to adopt it in 2019, right? Right!?

*record scratch*

Marketers have been slow to adopt AMP for a variety of reasons (via Unbounce’s 2019 Page Speed Report).

Wait, wait, I can explain. As part of our 2019 Page Speed Report, we asked marketers if they planned to implement AMP in the near future. 57% of them told us they have no plans to implement it, while 23% are still considering it.

Those who haven’t adopted the framework have a range of reasons why, but they fall into three broad categories:

AMP requires a significant investment of developer resources.

AMP is poorly understood (or perhaps poorly messaged).

Google’s past behavior has made some people wary of AMP.

I’ll explore these reasons in further detail below. For now, it’s worth saying that each has some validity. But I don’t think any of them—alone or together—should be your excuse not to implement AMP for your marketing campaigns.

In the long run, businesses who overcome these objections will be better positioned than those who don’t, despite perceived drawbacks. As I wrote elsewhere, “Turbo-charged landing pages result in more traffic and higher engagement, boosting conversions and helping PPC campaigns win increased ad impressions for less.” The AMP framework helps you achieve this kind of performance, even on a smartphone.

Want more insights about page speed? You can explore all the findings in the complete 2019 Page Speed Report for Marketers here. Access is free and ungated, so take a look.

Reason 1: Limited development resources

A significant hurdle that marketers face when it comes to adding AMP to their site has to do with technical resourcing. Four of the answers to our survey question touched on this problem:

Developers are not experienced with coding for AMP (12% of respondents)

No developer capacity to implement it (32% of respondents)

Too time-consuming to implement it (12% of respondents)

Validation issues with AMP pages we did create (2% of respondents)

It’s no secret that AMP comes with a steep-ish learning curve.

By using a restricted version of HTML and a custom JavaScript library, the framework ensures an optimized (read: fast-loading!) experience. Using Google’s AMP Cache (a content delivery network that stores your page on Google’s servers) further accelerates your pages.

But it also requires your developers to dedicate time to learning and mastering AMP-HTML and the AMP JavaScript library. And since Google’s AMP Cache requires validation once you’ve built an AMP page, there’s really no “good enough” moment here. Either your page works and goes live, or it doesn’t and you need to find your error. Who feels motivated to learn under those conditions?

AMP validation in action—or should I write, “inaction”? (via The AMP Project).

By its very nature, the limitations of AMP also demand a certain, let’s say, technical dexterity. Because bloated scripts tend to be a major contributor to slowdown, AMP’s JavaScript library puts the brakes on the third-party scripting that people have gotten used to using. (And AMP HTML comes with its own quirks.) Working within these constraints can often produce innovation, but it’s also a source of frustration for many who just wanna get stuff done.

Finally, poor analytics has been significant speed bumps on the road to AMP adoption. Tracking and analyzing visitor behavior is an integral part of running an online marketing campaign, but early in its life, AMP asked us to go blind. No thank you.

Why time and dev work are no excuse…

First, let’s be real: the AMP framework is a set of restrictions. That’s the point. So wishing for an AMP without any limitations at all doesn’t make sense.

In addition, many of the difficulties that plagued developers in the early years of AMP are no longer an issue. Tracking, for instance, has improved dramatically since AMP launched in 2015. Today, by using the AMP Analytics tag, you can isolate and analyze AMP traffic in Google Analytics. Though it can’t yet do everything that standard tracking can, it will collect data about users, pages, browsing, and (most significantly) events. As Search Engine Journal points out, “for most content marketers, that’s sufficient.” Not a ringing endorsement, sure, but tracking is now good enough for most marketing purposes.

As AMP development has continued, scripting has also become more robust, and the options available have expanded. Unfortunately, many people rely on scripts from third parties for tracking and integrations, but a lot of companies have been slow to deliver AMP-compatible versions. As adoption has increased, however, so too has the pressure on these companies to deliver.

That said, some of what AMP asks us to leave behind is also inessential. Pages clogged by unoptimized script may soon be looked upon we look at the tailfins on the back of a 50’s Cadillac. (Or, hey, remember the heady days when every site seemed to require Macromedia Flash? When it comes to the web, more isn’t always better.)

Reason 2: Some marketers really don’t get this whole AMP thing

Despite having a mouth to Google’s megaphone, the AMP Project has struggled to be heard beyond web development or publishing circles. When we asked marketers in The Page Speed Report, we discovered the following:

There’s a lot of misunderstanding when it comes to AMP (via Unbounce’s 2019 Page Speed Report).

While 54% of the digital marketers said they have some understanding of AMP, the rest assuredly did not. A quarter of ’em hadn’t even heard of Accelerated Mobile Pages before taking our survey.

Why misunderstanding is no excuse…

First, AMP is hardly floundering, despite the fact that you may not have heard about it. It has the combined might of Google, Pinterest, Twitter, WordPress, and Bing backing it. And AMP already covers more than 31 million domains serving billions of AMP pages. If you browse the web on your smartphone, in other words, chances are very strong you’ve visited an AMP page.

AMP pages appear in the search results with a lightning bolt icon.

Second, if you hadn’t heard of AMP until you read this article, no worries—because now you have. That gives you an advantage over the 24% of marketers who’re still in the dark. It’s always best to think competitively about page speed. Knowing about AMP (and implementing it) can put you out in front of your competitors by dramatically improving your load times.

EDITOR’S NOTE. There’s a lot of misinformation or misunderstanding out there about AMP. You can read more about AMP and its myths in this blog post from Unbounce’s Larissa Hildebrandt.

Reason 3: Google is “evil” now

Even before they stripped the “don’t be evil” clause from their official code of conduct last year, Google earned a reputation for shady doings.

With the launch of the AMP Project in October of 2015, though, they stirred up a controversy that they didn’t seem to anticipate. Critics were quick to argue that AMP represents yet another move to lock down the web, gallingly disguised as an open-source project.

Many of these accusations point to the Google AMP Cache, which speeds up delivery of content by storing your pages on Google’s servers. AMP doesn’t actually require using Google’s cache—people can create their own—but this tends to be how it’s done. In most cases, the content lives with Google, and a searcher may never touch your actual website. As Daniel Miessler puts it, this is potentially “poisonous to the underlying concept of an open internet.”

Why it’s no excuse…

The language of dissent can get a little, uh, heated (see Barry Adam’s colorful “Google AMP Can Go To Hell”) but a free and open internet is a public good we should be all getting behind. Keeping Google from controlling the entire universe is a definite good for free speech and democracy. (And it’s better for business too.)

But so is delivering fast speeds so that more people can access the web. And AMP helps with that, big time. Remember, the loss of net neutrality means providers can potentially throttle speeds, offering “slow” and “fast” lanes depending on what customers can afford. And 70% of connections globally will remain 3G or slower through 2020 regardless. For these reasons, AMP seems downright necessary, and that’s why news organizations—like The Guardian and The New York Times—were among the first to adopt it.

For what it’s worth, Google has pled innocent in the court of public opinion. In September they took steps to distance themselves from the AMP Project by adopting a new governance model that includes other companies. What this means is that—though Googlers conceived and shepherded AMP—its future is now squarely in the hands of a group that may not always act in the tech giant’s interests. That’s a very good thing.

Why marketers should implement AMP

It’s well-known that delays can create anticipation. But make no mistake, your sluggish website in no way resembles the slow, sultry, seductive pour of Heinz ketchup onto a plate of golden french fries. In fact, the experience has more in common with waiting for your number to be called at the DMV.

By making prospects sit through delays, you’re serving up a heaping helping of frustration, annoyance, and uncertainty. All before they ever even see your content…

…or, rather, if they ever see your content. Because many of ’em won’t make it that far. In Unbounce’s 2019 Page Speed Report for Marketers, a majority of consumers told us that they’ll wait 4-6 seconds before giving up on a slow page.

A majority of consumers say they’ll wait 4-6 seconds before clicking away (via Unbounce’s 2019 Page Speed Report).

Data gathered by Google says the actual number is closer to 3 seconds. After that, many consumers told us they close their browser or even go to a competitor’s site instead. 45% of them told us that a slow loading site makes them less likely to make a purchase. If you want to get fast—like, really, really fast—AMP can get you there.

Unbounce + AMP

It’s no secret we’re bullish on AMP at Unbounce. That’s because Accelerated Mobile Pages have many tangible benefits as a quick way to create a near-instant visitor experience. Not only can they have a dramatic effect on your conversion rates, but they can also increase organic traffic overall and improve Quality Scores in Google Ads.

We were surprised to learn in the Page Speed Report how many marketers are avoiding AMP due to difficulty with developer resources. So, as part of our initiatives to improve page speeds, we’ve sought to make AMP friendlier to the non-developer, reducing or eliminating frustration. You can now drag and drop together AMP experiences, and we’re walking you through what AMP is, why you need it, and how to implement it.

So what’s the ultimate reason you no longer have an excuse for not implementing AMP?

Because we’re making it much easier.

In the coming weeks, we’ll be making AMP landing pages available to all Unbounce customers. Using them can still mean choosing efficiency over flashy scripts, but we’ve already seen our beta test community finding new ways to balance beauty and speed. We’re excited to hear how AMP landing pages impact your conversion rates when they hit. And I’m excited to start sharing some success stories (and actionable takeaways) with readers of this blog.

from Marketing https://unbounce.com/online-marketing/why-marketers-should-implement-amp/ via http://www.rssmix.com/

0 notes

roypstickney · 5 years

Text

Almost 60% of marketers haven’t implemented AMP, see why (and why it’s no excuse)

So, naturally, every marketer is planning to adopt it in 2019, right? Right!?

*record scratch*

Marketers have been slow to adopt AMP for a variety of reasons (via Unbounce’s 2019 Page Speed Report).

Those who haven’t adopted the framework have a range of reasons why, but they fall into three broad categories:

AMP requires a significant investment of developer resources.

AMP is poorly understood (or perhaps poorly messaged).

Google’s past behavior has made some people wary of AMP.

Want more insights about page speed? You can explore all the findings in the complete 2019 Page Speed Report for Marketers here. Access is free and ungated, so take a look.

Reason 1: Limited development resources

A significant hurdle that marketers face when it comes to adding AMP to their site has to do with technical resourcing. Four of the answers to our survey question touched on this problem:

Developers are not experienced with coding for AMP (12% of respondents)

No developer capacity to implement it (32% of respondents)

Too time-consuming to implement it (12% of respondents)

Validation issues with AMP pages we did create (2% of respondents)

It’s no secret that AMP comes with a steep-ish learning curve.

AMP validation in action—or should I write, “inaction”? (via The AMP Project).

Why time and dev work are no excuse��

First, let’s be real: the AMP framework is a set of restrictions. That’s the point. So wishing for an AMP without any limitations at all doesn’t make sense.

Reason 2: Some marketers really don’t get this whole AMP thing

There’s a lot of misunderstanding when it comes to AMP (via Unbounce’s 2019 Page Speed Report).

While 54% of the digital marketers said they have some understanding of AMP, the rest assuredly did not. A quarter of ’em hadn’t even heard of Accelerated Mobile Pages before taking our survey.

Why misunderstanding is no excuse…

AMP pages appear in the search results with a lightning bolt icon.

EDITOR’S NOTE. There’s a lot of misinformation or misunderstanding out there about AMP. You can read more about AMP and its myths in this blog post from Unbounce’s Larissa Hildebrandt.

Reason 3: Google is “evil” now

Even before they stripped the “don’t be evil” clause from their official code of conduct last year, Google earned a reputation for shady doings.

Why it’s no excuse…

Why marketers should implement AMP

By making prospects sit through delays, you’re serving up a heaping helping of frustration, annoyance, and uncertainty. All before they ever even see your content…

A majority of consumers say they’ll wait 4-6 seconds before clicking away (via Unbounce’s 2019 Page Speed Report).

Unbounce + AMP

So what’s the ultimate reason you no longer have an excuse for not implementing AMP?

Because we’re making it much easier.

0 notes