| title | layout | author | permalink | source-id | published |
|---|---|---|---|---|---|
Hangout summary, Feb 3, 2016 |
post |
lapin7 |
/hangout-20160203.md/ |
1dD0rpzwt4R2vFkF4PBkkoTJ2k4iX6qa3j4PccejiqmA |
true |
11:00 - Build your segment of the network
15:00 - Login, different persona's
20:38 - Distributed Network Revenue
Dina, Eric, Noy and Greg had long email conversations about design before (why this channel?). Eric gives an overview of how they understand the system. For example what does it look like to login. The setup of a node itself, which is also an essential part of Synereo, is not covered yet.
-
Normal web page. Introduction of Synereo + invite to login page
-
A marketing video that directs you also to the login page
-
A logon page for people that don't have their own node setup. A kind of central place to start. - - Dina will show some designs of the login page later.
-
When you're logged in then you will see the feed that you've selected.
-
If you don't have a login, you get an invite to create an account.
Just going through this it opens up a bunch of questions of the central-decentral problem. If we all have individual islands with content and people. We want our node. We want to be able to connect. Is there a centralised login and what's the difference when you login to your own node.
###07:10 - Bootstrapping nodes
Greg's feeling in 2004 with the Splicious crowd sale was that they wanted to bootstrap as many nodes as possible. And then make it easy to connect and disconnect nodes through node-management. This was important for creating a mindshift with the people from centralised to decentralised. The real value is in the fact that Synereo is decentralised. This is very different from the FB experience. In the early stages we can never measure up against the features of FB, but we can make a difference by creating a new world, decentralised and distributed and there's not only one trusted party. So the network creation experience is the most important. It should be very simple. Most questions of new people were at that time not "How do I login?", but "How do I setup a node?".
Ed proposed putting two options on the login page. The first is just a login to the node and the second is to create your own node.
Greg says it is like the Diaspora model. There you can login to a Diaspora pod or you can set one up for yourself.
###11:00 - Built your segment of the network
Eric thinks that Synereo can provide the building blocks, for example for Joe User to set up a node with his own interface and own login page, and his own people live on that island. And he can do a distributive marketing push to get more people on his node to create his own segment of the network through his own channels. So he wouldn't use the default login page at all. It would be another flavor that is built with the tools that Synereo provides him like posting content or interacting with the social network feed.
So there are two fundamental user sets that happen to overlap: users that want to set up a node and users that want to connect with other people. I want to connect my node to your node so that we can share information. But how do you connect to other people that are on other nodes than you are.
Greg said that if two nodes are connected then it doesn't matter which one you log into. Eric wants to be sure that he understands the transportability of user profile and content. Is there, for example a single identifier over the whole network, or does an identity sit only on a single node and could collide with other identities when he goes off the node and into the network.
Dina mentioned the Wordpress model.You can login with your own credentials but you can set out a kind of avatar. So in that way your actual login name doesn't matter as much.
###15:00 - Login and different personas
Greg stated that indeed the username and login are separate issues. There is an agent identity that can be portable amongst nodes. It's not the same as an identity, but it's a channel by which you can reliably communicate. The agent who has the credentials to access that channel, can reliably get to profile information and the AMP wallet. Agents that create a connection between their channels, can reliably get to information that's been shared over that connection. But a user can create multiple channels, each with an AMP balance. In short you can not treat an agent as a single universal identity, and once you have created a login on one node, you can later logon to any node you want. If you're not recognized on the first node then that node will ask other nodes until your credentials are found. So the login page is exactly the same on each node.
Dina explained it like this: If there were some sandbox nodes, set up by Synereo, and new users login, then no matter where they are later logging into another node on the network, they'll at least be able to access what they set up on that node.
Greg pointed out that if a login can happen anywhere, then it goes against decentralisation. In fact we want people to login on the initial node and when the network is robust enough and we know better how the whole system behaves, then we can allow people to login on any node they want.
Ed said that one way to incentivise node creation is that when you set up a node, then Synereo will reward you with AMPs. If you log on to that node it cost you nothing, but if you use a shared one, then it will cost you AMPs. If that happens to be your node, then you will also be rewarded by the users that use your node to login to.
###20:38 - Distributed Network Revenue
Dina reiterated: if a user signs up at your node, you get a portion of their AMPs; if they sign other users up, then you get also a portion of their AMPs. So it sounds like a multi level marketing approach - LOL!
After all it's important to know what product you are creating. Is it the platform on which third-parties can develop an application and create a node, or is it simply connecting to users and consuming and creating content?
Christian argues that usually it's only 1% of the community who are really active and 99% are just like: Yeah this is cool, stopping in, checking in, consuming.
###23:58 - What is our "Minimum lovable product"?
What will users actually love to use?
And this hangs of course in a long term strategy.
With the considerations of decentralised and distributed applications, own your own data, etc. - and this has to be set out in a time frame.
This mission is a mouth full but Greg likes the sentiment. It's not only for the front page of the web site or for attracting investors. For the designers it's really important for having a criterium to allow for this feature, and not for that feature. It helps to give focus on the design. The mission can of course be expressed in other words. Greg refers to Joseph Gorden-Levitt, Hitrecord. (Their. mission statement: We're a new kind of online community working together as a production company), with a small change. JGL has the final responsibility of what content is released and monetised. Greg hopes that Synereo becomes this amazing place where people come together to create amazing things, but that it is the crowd that has the collective insight of what's good content. That is the same intention that Dor has with the Attention Economy Model. Current social networks are mostly passive: surfing, browsing and less about active focused creative attention.
Below are the modes of web use. And have a look at Jerry's Brain
###36:00 - Ultimate experiences
How are we going to design this thing?
So we start with the login. Then how are we going to present the different content types. How much do we care about people, creating really, really immersive content.
The content life: So what action can be done to content? How does it work with AMPs and REO? Does the content that is displayed really make sense? How do I see the history of what I put up?
The original sketch for showing how we work. We want to know how the icon feels.
This resulted in in the really cool smoky background with kind of the nodes coming out. The idea was that you were to be coming here and you were going to step into this node and that will kind of unfold the rest of the network for you.
For the icon we are working on the "Google-Incognito-mode", "Carmen San Diego", and "Red Hat" mash-up.
So we're creating something that reflects privacy, and hackery. Maybe a bit too sinister. We want to get your reaction. A second version is with a looping video in the background with kind of robot guys.
It gives a kind of censorship and Greg doesn't want to go in that direction. He's also not so much on the robots. He would prefer to go a little bit more organic. Because that world is full of decentralised metaphors. Dina just took the available video, but Greg didn't like so much the metaphors being used. The mechanistic world is kind of the opposite he wants to point to.
Also what's missing is "launch a node" it's only "login".
This has to be figured out.
Eric says that the initial focus is on the bitcoin, hacker minded people to get this network up and running, that want to keep their privacy. A character doesn't replace the logo of Synereo. You have these kind of general characters.
The ideas for this character came out of initial target market and the social self determination, trust and social components.
###Some examples from the community:
Christian likes the ideas of mushrooms with a reference to organic gardening. You start with mushrooms because they build the network out there.
It maybe also a good idea that this character is evolving with the network. Greg liked the evolving character idea.
Ed suggested we consider a turtle: come out of your shell when you feel safe. Also, the turtle could be shown in different states depending on login state, chatting state, etc.
Dina stresses that we have to get really fast to a kind of demo product. And we can not stick to just the login screen. If there's too much churn on a specific kind of side thing like a character, then we never get some UI made and we want Synereo to get running. Too much churn is not workable. How many iterations do we allow for? Or do we just use the Synereo logo and leave the icon for the moment, and keep moving?
Greg says that timeboxing is ok, but we also want to create a culture of ownership and empowerment. We are in this together. What we have to learn is governance. How much crowd attention can we allow on which problems? That's kind of learning as we go.
###Dina summarized, asking:
-
Is the spy kind of icon not wanted for Synereo?
-
Is it ok to bring up an icon, early on in this process, that is a bit more human, organic?
-
How much importance do we attach to such an icon?
The general feeling is that we could stick to the current Synereo logo and do polishing later. Getting Synereo up and running is more important.
###Let's work out the twelve points mentioned and use tools like:
###Links from the chatbox
-
Collaboration platform This is a photoshop plugin that allows for awesome web design. I can see how this could be used for designers to build customized interfaces which users could choose from.
-
How about a page that shows available nodes and their uptime, like pump.io
##That's all for this week!!
CU next week on Februari, 10, 2016
##If you like what we create, send some bitcoin to
18c1en55Cs2jBgBT2LTAiK9M81vMUmXmxw
(Bitcoin address for general Synereo support).