Thanks a lot rob05c,

Like always, your transparency has been a fantastic treat as a user of hubski's services.

Where can I send you bacon?

Thanks! I'm really interested in a bunch of the other api's they offer to interact with watson.

I'm running the Windows 10 Insider Preview

That fact kind of invalidates his whole testing regime.

Unless he goes back and tests on release of the OS and his results are the same.

Thanks, rob! Your updates are always a treat!

I can't wait to see how you finalize your approach. I have one co-worker nodding his head violently at the prospect that business logic should be handled by the application and enhanced by interfaces as needed while another swears by handling everything in the db.

I lean toward the latter; but I know nothing.

Thanks for the updates, man. Godspeed.

I wish there were two of you so one could keep an adequate log of all the shit you have to do throughout your conversion process. I'm sad to have missed your livestream.

Enhancing the performance of your queries is a lot of guesswork without the right tools. I need to hop in feet first in some PostgreSQL but that sweet Cassandra is calling my name.

Does the Arc SQL adapter support the use of stored procedures? Have you tried wrapping a view around one of the bulkier tables to filter the results a little and maybe weed out some unnecessary/problem columns? Is your dataset normalized?

I know a bunch of questions isn't going to help; but holy snark I love me some DB discussion.

I just downloaded DrRacket and made a circle.

We'll have to see it when you're done!

I guess those questions are the 'urgent' ones.

My "urgent" questions are more along the following:

"Why is your EULA so overreaching and scary?"

"Why do you have privacy settings and then ignore what I set them to?"

"Touching back on the EULA, why must I accept automated updates? I personally have an environment in which stability is key and automated updating has burned me in the past...just kidding, six days ago.

Updates. The software periodically checks for system and app updates, and downloads and installs them for you. You may obtain updates only from Microsoft or authorized sources, and Microsoft may need to update your system to provide you with those updates. By accepting this agreement, you agree to receive these types of automatic updates without any additional notice.

Did I mention scary?

Haha, I'd call you a blasphemer! Let the application generate the Id?! What kind of voodoo are you throwing out here?! (jk)

I'm slowly finding my love for software development residing within the confines of database work.

Most of our legacy application code is generally stable and a lot of tasks I find myself doing is data migration and query optimization. Before that there was a ton of handwritten replication (don't ever do it, please; but if you have to give me a call) but thats all out the window with an in-house automated solution. Almost all my coworkers are database enthusiasts, a few of which I would call fanatics. A couple posses a lifetime of wisdom within the subject that has left me really inspired.

I'm super stoked about you throwing up the schema, thanks a lot!

It might not be a terrible idea to auto increment a primary key on those reference tables for whenever they get big. You'd just put a FK constraint on those one-to-many relationships in the other tables.

create table if not exists "publication_shared_by" (

  id integer identity(1,1), --primary key will help when this table becomes large
  publication_id       integer, -- fk into publication, NOT a pk, one to many
  username text --create a non-clustered index to the 'username' table or something

I'm not sure if the identity(1,1) syntax is correct (I work primarily with a T-SQL system).

Really all you need to do is get better, or just play with 5's. You'll find that if you're actually playing with competent folks the arguments are generally cogent; albiet a little hostile. At the lower tier matchmaking you get to deal with all sorts of unwelcoming teammates who are frustrated and still learning.

I have a tough time agreeing with the opinion that developers and gaming communities have a moral obligation to take it upon themselves to enforce some code of conduct policy. Policing people's speech is a slippery slope, especially when the fundamental tool (the grand 'ole mute button) already exists to appease those that feel violated. Multiplayer games that are inherently competitive bring inherently competitive people to them. These types of people generally don't enjoy losing and if you're the cause of that, they'll probably let you know.

I'd rather have someone angrily yell at me in an attempt to correct my play-style than me mope in my private chat channel during a game because some algorithm labeled all my teammates as "Toxic Meanies". If what they're spewing in nonsensical garbage, then you mute them; this all seems very melodramatic to try and blow it into the proportion that I think you're attempting to get at.

I'm really curious as to how hubski is choosing to deal with automated posting.

It would be a really fun machine learning project to determine if uploads were done by an actual human or a bot. The hard part would be to getting the bot's programmer to think that everything is kosher while you silently associate a filter to their stuff (I think thats what #spam is doing?) to allow users the choice of whether or not to see it.

I'd personally have a great time at attempting to write a bot to test your simulated Hubski-Turing test.

"Since taking office, President Obama has worked with Congress to secure appropriate reforms that balance the protection of civil liberties with the ability of national security professionals to secure information vital to keep Americans safe.

The Office of Personnel Management (OPM) hack as well as the intrusion to Interior Business Center makes me feel safe as an American /s.

Instead of constructively addressing these issues, Mr. Snowden's dangerous decision to steal and disclose classified information had severe consequences for the security of our country and the people who work day in and day out to protect it.

Snowden reported that he attempted to do his due diligence and escalate matters through the proper channels, but had no channels to do so. The "danger" as reported by the DoD is that some organizations will alter their behavior making it more difficult to eavesdrop on them. As well, having our allies realize we've been unethically spying on them has caused relationships to go through tension. The former being "unprovable" without classified resources and the latter being common sense.

Unfortunately for the American government, vilifying Snowden won't make anything he revealed go away. Finding him guilty in a kangaroo court won't lessen the impact of the government's blatant abuse technology against its own citizens nor will it fix any of these issues moving forward.

One course of action could be to restructure the NSA's primary objective to auditing and securing existing federal infrastructure. At the same time, hold every single director, congressmen, and senator responsible for contributing to the delinquency of American's privacy; much in the same way they wish to hold Snowden accountable for his actions. Until that happens, I have no qualms about him hiding out in Russia, we're not doing anything to solve the problems he has brought to our attention.