# Phil 9.20.18

7:00 – 5:00 ASRC MKT

• Submit pre-approval for school – done!
• Call bank – done!
• Tried to do stuff on the Lufthansa site but couldn’t log in
• Read through the USPTO RFI and realized it was a good fit for the Research Browser. Sent the RB white paper to those in the decision loop.
• Updated the JuryRoom white paper to include an appendix on self-governance and handling hate speech, etc.
• Introducing Cloud Inference API: uncover insights from large scale, typed time-series data
• Today, we’re announcing the Cloud Inference API to address this need. Cloud Inference API is a simple, highly efficient and scalable system that makes it easier for businesses and developers to quickly gather insights from typed time series datasets. It’s fully integrated with Google Cloud Storage and can handle datasets as large as tens of billions of event records. If you store any time series data in Cloud Storage, you can use the Cloud Inference API to begin generating predictions.
• Realized that there are additional matrices that can post-multiply the Laplacian. That way we can break down the individual components that contribute to “stiffness”. The reason for this is that only identical oscillators will synchronize. Similarity is a type of implicit coordination
• Leave the Master matrix [M]: as degree on the diagonal, with “1” for a connection, “0” for no connection
• =Bandwidth matrix [B]: has a value (0, 1) for each connection
• Alignment matrix [A]: calculates the direction cosine between each connected node. Completely aligned nodes get an edge value of 1.0
• There can also be a Weight vector W: which contains the “mass” of the node. A high mass node will be more influential in the network.
• Had a few thoughts about JuryRoom self governance. The major social networks seem to be a mess with respect to what rights users have, and what constitutes a violation of terms of service. The solutions seem pretty brittle (Radiolab podcast on facebook rule making). JuryRoom has built in a mechanism for deliberation. Can that be used to create an online legal framework for crowdsourcing the rules and the interpretation? Roughly, I think that this requires the following:
• A constitution – a simple document that lays out how JuryRoom will be goverened.
• A bill of rights. What are users entitled to?
• The concept of petition, trial, binding decisions, and precedent.
• Is there a concept of testifying under oath?
• The addition of “evidence” attachments that can be linked to posts. This could be existing documents, commissioned expert opinion, etc.
• A special location for the “legal decisions”. These will become the basis for the precedent in future deliberations. Links to these prior decisions are done as attachments? Or as something else?
• Localization. Since what is acceptable (within the bounds of the constitution and the bill of rights) changes as a function of culture, there needs to be a way that groups can split off from the main group to construct and use their own legal history. Voting/membership may need to be a part of this.
• What is visible to non-members?
• What are the requirements to be a member?
• How are legal decisions implemented in software?
• What are the duties of a “citizen”?
• More iConf paper
• I wanted to make figures align on the bottom. Turns out that the way that you do this is to set top alignment [t] for each minipage. Here’s my example:
\begin{figure}[h]
\centering
\begin{minipage}[t]{.5\textwidth}
\centering
\end{figure}