your Fantasy is my Reality

Sep 30

[video]

browneyesblackcoffee:

shitdickfuckmothafucka:

omgbuglen:

A warning to anybody thinking about getting a husky

You can build yourself a third husky

That’s the spirit

browneyesblackcoffee:

shitdickfuckmothafucka:

omgbuglen:

A warning to anybody thinking about getting a husky

You can build yourself a third husky

That’s the spirit

(via pretty0things)

[video]

[video]

sisterofthewolves:

By Markus Junker

sisterofthewolves:

By Markus Junker

(via arrodynamic)

[video]

Sep 29

tuiteyfruityundead:

toddystuck:

elvenkingthrandy:

thecumbercookieaboveallothers:

mindtriggers:

THIS WILL BE SUCH A LONG MARATHON AND I AM SO READY

That’s prob about 12 hours

extended lotr alone is 11 hours and 22 minutes.

LOTR Extended = 681 minutesHobbit 1 Extended = 182 minutesHobbit 2 Extended = approx. 186 minutesLet’s say Hobbit 3 Extended is at least 185 minutes
The full marathon run time will be around 1234 minutes, or 20 hours 30 minutes.

#perfect that leaves 3 and a half hours for snack runs and pee breaks

tuiteyfruityundead:

toddystuck:

elvenkingthrandy:

thecumbercookieaboveallothers:

mindtriggers:

THIS WILL BE SUCH A LONG MARATHON AND I AM SO READY

That’s prob about 12 hours

extended lotr alone is 11 hours and 22 minutes.

LOTR Extended = 681 minutes
Hobbit 1 Extended = 182 minutes
Hobbit 2 Extended = approx. 186 minutes
Let’s say Hobbit 3 Extended is at least 185 minutes

The full marathon run time will be around 1234 minutes, or 20 hours 30 minutes.

(via duckubus)

[video]

anoia:

what if krogans sleep in a lump. kroglump.  like their legs tuck under and their crest goes under their back shell. 

image

(via goddamnitriot)

rubyetc:

There are two types of people..
(*the catpocalypse is nigh) 

rubyetc:

There are two types of people..

(*the catpocalypse is nigh) 

(via onlyindiecomics)

cooldogpics:

Logged the fuck in

I want this laptop 10/10

cooldogpics:

Logged the fuck in

I want this laptop 10/10

(Source: larvalhex, via friskachu)

karloaf:

askthegeneraless:

sushi-prince:

Wow okay.
Tumblr doesn’t send anymore asks if you send a “.” and a letter or word without a space right after it.

Example: H…hello (doesn’t send it) - H… hello (will send it)

It says it sends the ask but it doesn’t. My gf and I were trying since 2 days now and we just found out what the problem was.
Pass it on.

This explains SO MUCH GRRGHH

the shitty system thinks its a url thats why

(via duckubus)

pleatedjeans:

via

pleatedjeans:

via

(via cheesedemon88)

[video]

appendingfic:

ironcheflancaster:

wedonotpromoteviolence:

heirofspacecore:

sleek-black-wings:

thederpywingedone:

batmansymbol:

by the way did I ever tell y’all about the time I got a blank message from nobody, sent on new year’s eve in 1969, when the internet didn’t exist?
because that happened

What the fuck

Time travel.

Or maybe its from 2069, when we’ve developed the technology to send data to the past. You sent yourself a blank message as a test but as the email address you used to send it doesnt exist yet, it came up as no sender

I… what?

OKAY KIDS, LET’S LEARN ABOUT THE UNIX EPOCH
So back in the early days of computers, when we were trying to build clocks to keep all our computers in sync, we tried a bunch of different ways to synchronize them in ways that both normal people could use and programmers could utilize.
We just tried saying “The current time is THIS date” and just storing that date as some text, but while that was easy for humans, it was a bunch of different numbers that worked together in funny ways and computers don’t play nice with a bunch of random, arbitrary rules.
Not much worked, until we realized that we needed a BASELINE to compare against, and a way to represent the current time that covers everybody. So we came up with Unix time, because Unix was the style at the time. Essentially, Unix time represents any given time by saying “How many seconds ago was 12:00 AM on January 1, 1970 in Iceland somewhere?”. Recent enough to keep the numbers relatively small, far enough that nothing computer-y would fall before it, and consistent enough that there’d be no discrepancy based on where you are.
So what happens when you see the date “December 31, 1969” on a buggy message like this is that the computer received a bunch of zeroes by mistake and went “Oh, this must be a message!” Then when it tried to interpret it, it got to the date, found a zero, and said “Zero seconds since the Unix Epoch? I’ll round down - this was sent at the last second of New Year’s Eve, 1969! They’ll be so happy to finally get their blank message.”
And then the computer traipsed off on its merry way, because computers are fucking ridiculous.

This is frankly more hilarious than the 1969 time traveler theory

appendingfic:

ironcheflancaster:

wedonotpromoteviolence:

heirofspacecore:

sleek-black-wings:

thederpywingedone:

batmansymbol:

by the way did I ever tell y’all about the time I got a blank message from nobody, sent on new year’s eve in 1969, when the internet didn’t exist?

because that happened

What the fuck

Time travel.

Or maybe its from 2069, when we’ve developed the technology to send data to the past. You sent yourself a blank message as a test but as the email address you used to send it doesnt exist yet, it came up as no sender

I… what?

OKAY KIDS, LET’S LEARN ABOUT THE UNIX EPOCH

So back in the early days of computers, when we were trying to build clocks to keep all our computers in sync, we tried a bunch of different ways to synchronize them in ways that both normal people could use and programmers could utilize.

We just tried saying “The current time is THIS date” and just storing that date as some text, but while that was easy for humans, it was a bunch of different numbers that worked together in funny ways and computers don’t play nice with a bunch of random, arbitrary rules.

Not much worked, until we realized that we needed a BASELINE to compare against, and a way to represent the current time that covers everybody. So we came up with Unix time, because Unix was the style at the time. Essentially, Unix time represents any given time by saying “How many seconds ago was 12:00 AM on January 1, 1970 in Iceland somewhere?”. Recent enough to keep the numbers relatively small, far enough that nothing computer-y would fall before it, and consistent enough that there’d be no discrepancy based on where you are.

So what happens when you see the date “December 31, 1969” on a buggy message like this is that the computer received a bunch of zeroes by mistake and went “Oh, this must be a message!” Then when it tried to interpret it, it got to the date, found a zero, and said “Zero seconds since the Unix Epoch? I’ll round down - this was sent at the last second of New Year’s Eve, 1969! They’ll be so happy to finally get their blank message.”

And then the computer traipsed off on its merry way, because computers are fucking ridiculous.

This is frankly more hilarious than the 1969 time traveler theory

(via witchylana)