Weird How The Moment My FP Goes To Bed/stops Talking To Me Is The Same Moment My Mood Goes From 100 To

me: why haven't i bought this game yet

me: oh right i forgot i need money to purchase goods and services

*5 minutes pass*

me:

me:

me:

me: why haven't i bought this game yet

So at work today I worked with a new server and she told me and the other servers how much she loved me and how good of a worker I am and that I’d make an amazing server and omg its so nice to see people appreciate my work. My manager thanked me for coming in and doing my job and above and beyond and I was just like “dude I’m just working” lol and he’s like nah you do more than that and I’m just glad they liked my work ethic and that I get a serving job cause that pays more, a lot more. AND it’s a good job until I can do acting full time =‘) and a lot of servers tell me they love me and appreciate me <3 WHICH IS AMAZING CAUSE THEY WILL TIP ME WELL !!!

this week the senate will vote on whether or not to give the fbi warrantless access to your browsing data. this is extremely dangerous and a violation of privacy. not only would the fbi be able to essentially hack into your computers and internet service, but they might also hack into ones overseas. anything on your computers, they’ll be able to have access to. this is an extremely dangerous power the fbi is trying to get, and it CAN be stopped, but only if you guys are willing to put forth the effort.

how do you stop it? first, get the word out. twitter, tumblr, facebook, just get the word out by either making your own status or sharing this link. 

secondly, call your senators. on this website, just enter your phone number and it will give you a script to read off of. it will take you less than 30 seconds, trust me. you can also tweet them, send them emails, etc. all the contact info is on this site here. they will listen. dont know who your senators are? go here and scroll to the bottom. it lists all the senators and who you can call. also, you can tweet at them or send them an email. (all the links in this paragraph lead to the same source)

guys, it is extremely important this bill not get passed. PLEASE reblog this and at least tweet at them? you dont even have to think of anything to type. you literally click the tweet button and it does it for you. please, guys, please.

Leave who you were. Love who you are. Look forward to who you will become.

Unknown (via deeplifequotes)

Invest in yourself in 2016.

(via deeplifequotes)

ive got an affinity for really zoomed in faces as reaction images

Reporter: So, Irma, now that you're a Category 5, what are you going to do?

Irma: I'M DOING TO DISNEY WORLD!

Automating the Publish/Subscribe Pattern in JavaScript

The Publish/Subscribe pattern is one of the most used patterns in software, especially in User Interfaces with JavaScript. It is used whenever 2 pieces of a system need to communicate, but cannot or should not communicate directly. For example, a system receives data from a server at regular intervals that a bunch of components can use (which are added while the system runs):

var Publisher = function() { var self = { subscribers: [] }; self.subscribe = function(callback) { self.subscribers.push(callback); }; self.publish = function(data) { self.subscribers.forEach(function(callback) { callback(data); }); }; return self; } var publisher = Publisher(); // Simulate a set of data being returned over time var serverStream = function(callback) { Array.apply(null, { length: 5 }).forEach(function(unused, index) { var ms = index * 500 setTimeout(function() { callback('data-piece: ' + ms + ' ms'); }, ms); }); }; serverStream(publisher.publish); // Simulate components being registered over time. publisher.subscribe(function(data) { console.info('subscribe from part 1', data); }); setTimeout(function() { publisher.subscribe(function(data) { console.info('subscribe from part 2', data); }); }, 1000) // subscribe from part 1 data-piece: 0 ms // subscribe from part 1 data-piece: 500 ms // subscribe from part 1 data-piece: 1000 ms // subscribe from part 1 data-piece: 1500 ms // subscribe from part 2 data-piece: 1500 ms // subscribe from part 1 data-piece: 2000 ms // subscribe from part 2 data-piece: 2000 ms

The problem is that same pattern with almost identical code will be written over and over again in the same project. So instead of creating a publisher and subscriber with multiple message types each time this pattern needs to be used, it is simpler to just use new instances of the publisher object each time:

var messageSet1 = function(callback) { Array.apply(null, { length: 3 }).forEach(function(unused, index) { setTimeout(function() { callback('Hello ' + index); }, index * 500); }); }; var messageSet2 = function(callback) { Array.apply(null, { length: 3 }).forEach(function(unused, index) { setTimeout(function() { callback('World ' + index); }, index * 500); }); }; var MessageBox = function() { var self = { publishers: [] }; self.streams = function(streams) { self.publishers = []; streams.forEach(function(stream, index) { self.publishers.push(Publisher()); stream(self.publishers[index].publish); }); }; self.subscribeTo = function(index, callback) { return self.publishers[index].subscribe(callback); } return self; }; var messageBox = MessageBox(); // Use a trivial example to preserve clarity messageBox.streams([messageSet1, messageSet2]); messageBox.subscribeTo(0, function(data) { console.info('subscribe from part 1B', data); }); messageBox.subscribeTo(1, function(data) { console.info('subscribe from part 2B', data); }); // subscribe from part 1B Hello 0 // subscribe from part 2B World 0 // subscribe from part 1B Hello 1 // subscribe from part 2B World 1 // subscribe from part 1B Hello 2 // subscribe from part 2B World 2

A non-index based naming scheme could be introduced by passing more data into the streams call, but I wanted to keep the example as minimal as possible.

Github Location: https://github.com/Jacob-Friesen/obscurejs/blob/master/2016/publishSubscribeAutomation.js

Power Macintosh 7100/80

NASA Astronomy Picture of the Day 2016 September 4 

Io over Jupiter from Voyager 1 

Back in 1979, NASA’s Voyager 1 spacecraft flew past Jupiter and its moons. The images in this mosaic, featuring the moon Io against a background of gas giant Jupiter’s diffuse swirling cloud bands, were recorded by Voyager’s camera from a distance of about 8.3 million kilometers. The Io image from this mosaic may be the first to show curious round features on Io’s surface with dark centers and bright rims more than 60 kilometers across. Now known to be volcanic in origin, these features were then thought likely to be impact craters, commonly seen on rocky bodies throughout the Solar System. But as Voyager continued to approach Io, close-up pictures revealed a bizarre world devoid of impact craters, frequently resurfaced by volcanic activity. Earlier this year a new robotic spacecraft, NASA’s Juno, began to orbit Jupiter and last week made a pass within 5,000 kilometers of Jupiter’s clouds. During the next two years, it is hoped that Juno will discover new things about Jupiter, for example what’s in Jupiter’s core.